[Bug 8905] Hang when loading some module

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=8905
Ubuntu | linux





------- Additional Comments From Daniel_Faken at brown.edu  2005-04-15 15:41 UTC -------
(In reply to comment #3)
> This report is still lacking information.  If control+scrolllock doesn't work
> for you, use Alt+SysRq+t.

This prints 'SysRq : Show State'   (thats its); but if I set log-level to 1 (or
anything other than 0), it prints out a bunch of stuff - more than the screen
holds.  A summary of what fit on the screen:

 [<c01011f9>] kernel_thread_helper+05x/0xb
usb.rc   S C0111C20   0 4768  1861  4793   (NOTLB)
deb73f20 00000086 (+bunch more hex codes)

Call Trace:
 [<c0111c20>] do_page_fault ....
 [...] do_wait ...
 [...] default_wake_function ...
 [...] deault_wake_function ...
 [...] sys_wait4...
 [...] sys_waitpid...
 [...] sysenter_past_esp...
sleep    S C011CAEC     0   4793  4768
deafbf68 00000086 (+ bunch more codes..)

Call trace:
 [...] __mod_timer...
 [...] schedule_timeout...
 [...] process_timeout...
 [...] sys_nanosleep...
 [...] sys_nanosleep..
 [...] sysenter_past_esp..

> Also, booting in recovery mode should cause hotplug to print the name of each
> module as it is loaded.  Do you or do you not see this information?  It would
> help to know the last module you see being loaded before the hang

I see the same info that a normal boot shows (not sure if this the info you mean).

The last five lines are:
* Checking all file systems... [ok]
* Mounting local filesystems...
* Running 0dns-down to make sure resolv.conf is ok... [ok]
* Initializing ifupdown state... [ok]
* Starting hotplug subsystem

BTW, the recovery boot commands are:

root (hd0,3)
kernel /boot/vmlinuz-2.6.10-5-386 root=/dev/sda4 ro noapic nolapic single
initrd /boot/initrd.img-2.6.10-5-386
savedefault
boot



Thanks for the help!



-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.