[Bug 698104] New: 11.4 with mainline kernel 3.0-rc1 fails to boot
From the above, it seems to me that program "udisks-part-id" is looping on the attempt to mount a cdrom. My feeling is that the kernel change for commit ea6949b is correct, but that it is exposing a bug in the udev system,
https://bugzilla.novell.com/show_bug.cgi?id=698104 https://bugzilla.novell.com/show_bug.cgi?id=698104#c0 Summary: 11.4 with mainline kernel 3.0-rc1 fails to boot Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Larry.Finger@lwfinger.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 The kernel in question fails to boot. The problem was bisected to the following commit: ea6949b66d084a197dd7f243b72e216a71d9f2ca is the first bad commit commit ea6949b66d084a197dd7f243b72e216a71d9f2ca Author: Tejun Heo <tj@kernel.org> Date: Thu Apr 21 20:54:44 2011 +0200 cdrom: always check_disk_change() on open cdrom_open() called check_disk_change() after the rest of open path succeeded which leads to the following bizarre behavior. To help debug the problem, I added some printk's before and after the relocated call to check_disk_change(). After those showed that user space was infinite looping, I added a dump_stack() with the following result: Jun 2 23:11:55 (none) kernel: [ 59.311058] Entering cdrom_open Jun 2 23:11:55 (none) kernel: [ 59.313351] Pid: 5776, comm: udisks-part-id Not tainted 3.0.0-rc1-Linus+ #47 Jun 2 23:11:55 (none) kernel: [ 59.313354] Call Trace: Jun 2 23:11:55 (none) kernel: [ 59.313365] [<ffffffffa009ba6f>] cdrom_open+0x4f/0x610 [cdrom] Jun 2 23:11:55 (none) kernel: [ 59.313372] [<ffffffff81351ae1>] ? __mutex_unlock_slowpath+0xc1/0x150 Jun 2 23:11:55 (none) kernel: [ 59.313377] [<ffffffff81081f1d>] ? trace_hardirqs_on_caller+0x13d/0x180 Jun 2 23:11:55 (none) kernel: [ 59.313381] [<ffffffff81081f6d>] ? trace_hardirqs_on+0xd/0x10 Jun 2 23:11:55 (none) kernel: [ 59.313387] [<ffffffffa00da5d7>] idecd_open+0xc7/0xe0 [ide_cd_mod] Jun 2 23:11:55 (none) kernel: [ 59.313393] [<ffffffff811515b7>] __blkdev_get+0x97/0x3e0 Jun 2 23:11:55 (none) kernel: [ 59.313397] [<ffffffff81151c80>] ? blkdev_get+0x380/0x380 Jun 2 23:11:55 (none) kernel: [ 59.313401] [<ffffffff8115194e>] blkdev_get+0x4e/0x380 Jun 2 23:11:55 (none) kernel: [ 59.313406] [<ffffffff81353206>] ? _raw_spin_unlock+0x26/0x30 Jun 2 23:11:55 (none) kernel: [ 59.313410] [<ffffffff81151c80>] ? blkdev_get+0x380/0x380 Jun 2 23:11:55 (none) kernel: [ 59.313414] [<ffffffff81151ce0>] blkdev_open+0x60/0x80 Jun 2 23:11:55 (none) kernel: [ 59.313419] [<ffffffff8111b7af>] __dentry_open+0x12f/0x2f0 Jun 2 23:11:55 (none) kernel: [ 59.313423] [<ffffffff81353206>] ? _raw_spin_unlock+0x26/0x30 Jun 2 23:11:55 (none) kernel: [ 59.313427] [<ffffffff8111c8f1>] nameidata_to_filp+0x71/0x80 Jun 2 23:11:55 (none) kernel: [ 59.313432] [<ffffffff8112b04a>] do_last+0xda/0x910 Jun 2 23:11:55 (none) kernel: [ 59.313437] [<ffffffff8112c26b>] path_openat+0xcb/0x400 Jun 2 23:11:55 (none) kernel: [ 59.313441] [<ffffffff810f7567>] ? might_fault+0x57/0xb0 Jun 2 23:11:55 (none) kernel: [ 59.313445] [<ffffffff810f7567>] ? might_fault+0x57/0xb0 Jun 2 23:11:55 (none) kernel: [ 59.313449] [<ffffffff8112c5e4>] do_filp_open+0x44/0xa0 Jun 2 23:11:55 (none) kernel: [ 59.313454] [<ffffffff81353206>] ? _raw_spin_unlock+0x26/0x30 Jun 2 23:11:55 (none) kernel: [ 59.313458] [<ffffffff81139104>] ? alloc_fd+0xf4/0x150 Jun 2 23:11:55 (none) kernel: [ 59.313462] [<ffffffff8111c9fc>] do_sys_open+0xfc/0x1d0 Jun 2 23:11:55 (none) kernel: [ 59.313467] [<ffffffff8111caeb>] sys_open+0x1b/0x20 Jun 2 23:11:55 (none) kernel: [ 59.313472] [<ffffffff81353c7b>] system_call_fastpath+0x16/0x1b Jun 2 23:11:55 (none) kernel: [ 59.328377] Back from check_disk_change particularly in program udisks-part-id. This problem will be serious once 12.1 switches to kernel 3.0. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698104 https://bugzilla.novell.com/show_bug.cgi?id=698104#c1 Larry Finger <Larry.Finger@lwfinger.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |UPSTREAM --- Comment #1 from Larry Finger <Larry.Finger@lwfinger.net> 2011-06-06 16:28:42 UTC --- Although, I did not think this was a kernel problem, the actual cause was a bad merge. The problem is now fixed in the upstream, mainline kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698104 https://bugzilla.novell.com/show_bug.cgi?id=698104#c2 --- Comment #2 from Larry Finger <Larry.Finger@lwfinger.net> 2011-06-06 16:30:31 UTC --- This was a kernel merge error. Fixed by commit 0f48f2600911 ("block: fix mismerge of the DISK_EVENT_MEDIA_CHANGE removal") -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com