LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Kernel panic: gatt bus addr too high (https://www.linuxquestions.org/questions/slackware-14/kernel-panic-gatt-bus-addr-too-high-473049/)

d-s-r 08-11-2006 01:47 PM

Kernel panic: gatt bus addr too high
 
Since this is my first post on Linux Questions, I'd like to say hi to everyone. I just installed Slackware 10.2 under Parallel Desktop on my MacBook. When I try to boot, I get the kernel panic "gatt bus addr too high". Go to <tinyurl.com/lj25k> to see a screenshot of the console. The line before the kernel panic says "agpgart: Detected Intel i815 chipset", so does that mean there might be a problem either with my CPU or with how Parallels Desktop treats it (all I know is PD doesn't make use of both cores)? It's a 2 GHz Intel Core Duo CPU. Let me know if you need more information.

Thanks,
David

terry.simons 09-18-2006 11:15 PM

Quote:

Originally Posted by d-s-r
Since this is my first post on Linux Questions, I'd like to say hi to everyone. I just installed Slackware 10.2 under Parallel Desktop on my MacBook. When I try to boot, I get the kernel panic "gatt bus addr too high". Go to <tinyurl.com/lj25k> to see a screenshot of the console. The line before the kernel panic says "agpgart: Detected Intel i815 chipset", so does that mean there might be a problem either with my CPU or with how Parallels Desktop treats it (all I know is PD doesn't make use of both cores)? It's a 2 GHz Intel Core Duo CPU. Let me know if you need more information.

Thanks,
David

Hey David,

I ran into the same problem.

Try installing the test26.s kernel instead of the default. I'm actually using build 1884 (the latest stable is 1848) but test26.s works with it. I didn't try test26.s with the stable, and I didn't try 2.4 with the beta, but my particular combination does work.

Good luck. ;)

- Terry

terry.simons 09-18-2006 11:50 PM

Quote:

Originally Posted by terry.simons
Hey David,

I ran into the same problem.

Try installing the test26.s kernel instead of the default. I'm actually using build 1884 (the latest stable is 1848) but test26.s works with it. I didn't try test26.s with the stable, and I didn't try 2.4 with the beta, but my particular combination does work.

Good luck. ;)

- Terry

You'll want to mount disk 2 and run installpkg on the Linux 2.6.13 test kernel modules... they don't get installed by default. Also, it looks like with the modules installed the error comes back, but it doesn't take the kernel out... the system recovers gracefully.

You'll need the modules to get the emulated NIC working.

- Terry

Mythrill 10-17-2006 06:03 AM

Oh, dammit. I've written at the wrong topic. Anyway, your problem is most likely caused by an attempt on writing on some reserved bits stuff. Try what Terry said first. You might consider removing the agp module too if that fails, since some cards like Nvidia have their own.

And Terry, you don't install test26.s. That kernel is just a boot kernel so you can install the system. :)

terry.simons 10-22-2006 03:36 PM

Quote:

Originally Posted by Mythrill
Oh, dammit. I've written at the wrong topic. Anyway, your problem is most likely caused by an attempt on writing on some reserved bits stuff. Try what Terry said first. You might consider removing the agp module too if that fails, since some cards like Nvidia have their own.

And Terry, you don't install test26.s. That kernel is just a boot kernel so you can install the system. :)

Actually, you *do* install the test26.s kernel... at least I had to. I both booted *and* installed test26.s. The 2.4.x kernels cause the issue described, and since Slackware installs the booted kernel by default, I didn't think it was necessary to distinguish between the booted kernel, and the installed kernel.


All times are GMT -5. The time now is 06:57 PM.