kobject: tried to init an uninitialized object when removing and re-inserting sd-mod
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I downloaded the Intrepid Alternate Install CD daily image (2008-09-01) and I booted a machine to perform a clean install after re-partitioning the disks and doing some testing/
Unusual things happened when I unloaded the module sd-mod (modprobe -r sd-mod): the disks powered down -- but I guess this was ok. Then, when I reloaded the module (modprobe sd-mod), I got some oopses and a kernel panic. The bug was reproducible after a reboot, and I saved the syslog.
Steps to reproduce:
* Boot from the Intrepid Alternate Install CD
* At partman's stage, Go Back and then switch to a console/open a shell
* modprobe -v -r sd-mod:
rmmod /lib/modules/
rmmod /lib/modules/
The usual noise made by the disk(s) powering down will be heard.
* modprobe -v sd-mod
insmod /lib/modules/
insmod /lib/modules/
The kernel will print "kobject (f736d29c): tried to init an initialized object, something is seriously wrong." and a stack trace. Possibly, it will produce an oops and panic.
I was able to save only the first snippet of the kernel messages (from /proc/kmsg) before the kernel panicked.