View previous topic :: View next topic |
Author |
Message |
ArloWhite n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
Joined: 23 May 2003 Posts: 53
|
Posted: Mon Mar 01, 2004 9:34 pm Post subject: Critical Error at boot, Seg. related to modprobe & hotpl |
|
|
When I boot I sometimes get this error right as USB and PCI hotplugging is started.
(This took me a while to copy down so I replaced a lot of the debugging numbers with the # sign.)
Code: | Starting USB and PCI hotplugging:
Oops: 0000 [#1]
CPU: 1
EIP: 0060:[<f092ef3a>] Not tainted
EFLAGS: 00010292
EIP is at i2c_transfer+0x1a/0xd0 [i2c_core]
eax: # ebx: # ecx: # edx: # esi: # edi: # ebp: # esp: # ds: # es: # ss: #
Process modprobe (pid: 3405, threadinfo=ef59e000 task=ef646710)
Stack:
(Bunch of #'s I don't care to copy down unless someone wants it)
Call Trace: (Each of these contained a few debuging #'s)
radeon_do_probe_i2c_edid [radeonfb]
schedule_timeout
process_timeout
radeon_probe_i2c_connector [radeonfb]
radeon_probe_screens [radeonfb]
radeon_fb_pci_register
pci_device_probe_static
__pci_device_probe
pci_device_probe
bus_match
driver_attach
bus_add_driver
pci_register_driver
init_module
sys_init_module
syscall_call
Code: 8x 40 24 85 etc etc.
/etc/hotplug/pci.agent: line 168: 3405 Segmentation fault $MODPROBE $MODULE > /dev/null 2>&1
|
At this point all I could do was use Shift+Pageup to go up the screen and hit Ctrl+Alt+Delete to restart. As it reboots it gives another error related to the problem. I am unable to get to a VT or anything when this error occurs. This happens fairly regularly. Usually once it happens it will occur for two or three more boots and then boot fine. I am unable to find a log related to this error anywhere once I'm in the system.
These are the things I'd like to know:
* Is it possible my video card (radeon 8500) is going bad and causing this probe error?
* Why are these errors random?
* Is it possible I should disable some pci option or remove the radeonfb module from the kernel?
* Should I report this to kernel-dev?
* Is there a way I can log this? Maybe I need to enable extra logging features?
I am using gentoo-dev-sources-2.6.3-r1 as well as mm-sources-2.6.3-r4. All my radeon stuff (DRI,FrameBuffer,agpgart) is compiled as modules and I'm not explicitly loading any of it (though it seems hotplug finds it). I have been using these kernels for a while before the problem occured.
I have a gut feeling that my card may be going bad, but if you have any insight into the problem it would be appriciated.
-Arlo |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
striscio n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
![](images/avatars/gallery/Simpsons/Simpsons_-_Side_Show_Bob.jpg)
Joined: 30 Aug 2002 Posts: 23 Location: milano - italy
|
Posted: Wed Apr 21, 2004 11:11 pm Post subject: |
|
|
I have the same error. A kernel oops during hotplug start.
It seems (but I'm not sure) related to the hotplug trying to load a module that is built into the kernel (scsi controller in my case).
It happens with 2.6.4-r1, 2.6.5-r1, 2.6.6-rc2 from kernel.org
For the moment I disabled hotplug, but I think it's not the right solution.
[update]
I still have the same error with 2.6.6-rc3, vanilla 2.6.6 and 2.6.6-mm
Is it possible that so few people is having this problem? |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|