Summary: | Gentoo-dev-sources 2.6.9 r4 gives an oops at bootup | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Elie De Brauwer <elie> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | tklauser |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The .config |
Description
Elie De Brauwer
2004-11-14 07:51:48 UTC
Created attachment 43932 [details]
The .config
I just tried 2.6.9-gentoo-r1 based on the same config, the problem also exists there and the system hangs at Setting user font. Meaning before sshd was started, so I couldn't ssh in the machine to get the Oops from dmesg. But I think it's reiserfs related since I can just read from console: Checking internal tree.....Unable to handle kernel paging request at ... RIP Both at the 2.6.9 -r1 and -r4 So for now I'll have to rollback to 2.6.8 Are you using any form of framebuffer? Yes, a regular vesa vga framebuffer: Card: 0000:01:00.0 VGA compatible controller: nVidia Corporation NV36 [GeForce FX Go5700] (rev a1) psychotic void # fbset --info mode "1024x768-76" # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 rgba 5/11,6/5,5/0,0/0 endmode Frame buffer device information: Name : VESA VGA Address : 0xe0000000 Size : 3145728 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 0 YPanStep : 0 YWrapStep : 0 LineLength : 2048 Accelerator : No Wich is working perfectly under 2.6.8. I've rolled back to 2.6.8-r10 which still works perfectly It seems like you're using the proprietary nvidia module. Try to boot without loading this module and check if the problem still exists. As Daniel mentioned, if you're using framebuffer (in conjunction with the nvidia module) there may be problems (at least I had using nvidia and frambuffer) so compiling the Kernel without it would also be a good idea. But at the point the error occurs nothing related to the module has happened. Which makes it imo illogical that the framebuffer interfers with the nvidia module because at point of the error no module has already been loaded. Could you please test 2.6.10-rc2? Ok, I'll try it within a couple of hours (first I have some classes to attend :-( ) Please reopen when you have had a chance to test. |