Bug 514386 - Kernel oops on bootup
Summary: Kernel oops on bootup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-29 02:19 UTC by Hubert Figuiere
Modified: 2010-12-05 06:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-05 06:40:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
var/log/messages (264.99 KB, text/plain)
2009-07-29 02:19 UTC, Hubert Figuiere
no flags Details
var/log/messages (74.67 KB, text/plain)
2009-07-29 02:22 UTC, Hubert Figuiere
no flags Details

Description Hubert Figuiere 2009-07-29 02:19:46 UTC
Created attachment 355482 [details]
var/log/messages

For bug 498662 I installed the kernel from rawhide in my F11 machine.

Linux version 2.6.30-0.76.rc4.fc12.i686.PAE (mockbuild.phx.redhat.com) (gcc version 4.4.0 20090427 (Red Hat 4.4.0-3) (GCC) ) #1 SMP Thu Apr 30 17:14:01 EDT 2009


During bootup I get some oops:

Jul 28 22:03:36 grinch kernel: modprobe used greatest stack depth: 4468 bytes left
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: =======================================================
Jul 28 22:03:36 grinch kernel: [ INFO: possible circular locking dependency detected ]
Jul 28 22:03:36 grinch kernel: 2.6.30-0.76.rc4.fc12.i686.PAE #1
Jul 28 22:03:36 grinch kernel: -------------------------------------------------------
Jul 28 22:03:36 grinch kernel: plymouthd/39 is trying to acquire lock:
Jul 28 22:03:36 grinch kernel: (&fb_info->lock){+.+.+.}, at: [<c0602465>] fb_mmap+0x94/0x17d
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: but task is already holding lock:
Jul 28 22:03:36 grinch kernel: (&mm->mmap_sem){++++++}, at: [<c040e441>] sys_mmap2+0x72/0xb9
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: which lock already depends on the new lock.
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: the existing dependency chain (in reverse order) is:
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: -> #3 (&mm->mmap_sem){++++++}:
Jul 28 22:03:36 grinch kernel:       [<c046d530>] __lock_acquire+0x981/0xafa
Jul 28 22:03:36 grinch kernel:       [<c046d760>] lock_acquire+0xb7/0xeb
Jul 28 22:03:36 grinch kernel:       [<c04c8b56>] might_fault+0x73/0xa4
Jul 28 22:03:36 grinch kernel:       [<c05d7e88>] copy_to_user+0x41/0x12b
Jul 28 22:03:36 grinch kernel:       [<c04f6841>] filldir+0x90/0xdc
Jul 28 22:03:36 grinch kernel:       [<c0536c74>] sysfs_readdir+0x11a/0x161
Jul 28 22:03:36 grinch kernel:       [<c04f69f9>] vfs_readdir+0x7b/0xb8
Jul 28 22:03:36 grinch kernel:       [<c04f6b79>] sys_getdents+0x74/0xc9
Jul 28 22:03:36 grinch kernel:       [<c040a5eb>] sysenter_do_call+0x12/0x38
Jul 28 22:03:36 grinch kernel:       [<ffffffff>] 0xffffffff
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: -> #2 (sysfs_mutex){+.+.+.}:
Jul 28 22:03:36 grinch kernel:       [<c046d530>] __lock_acquire+0x981/0xafa
Jul 28 22:03:36 grinch kernel:       [<c046d760>] lock_acquire+0xb7/0xeb
Jul 28 22:03:36 grinch kernel:       [<c07f54f5>] __mutex_lock_common+0x43/0x338
Jul 28 22:03:36 grinch kernel:       [<c07f58dd>] mutex_lock_nested+0x41/0x5a
Jul 28 22:03:36 grinch kernel:       [<c0537043>] sysfs_addrm_start+0x34/0xb7
Jul 28 22:03:36 grinch kernel:       [<c05378c0>] create_dir+0x50/0x93
Jul 28 22:03:36 grinch kernel:       [<c0537940>] sysfs_create_dir+0x3d/0x5e
Jul 28 22:03:36 grinch kernel:       [<c05d12e4>] kobject_add_internal+0xfa/0x1d1
Jul 28 22:03:36 grinch kernel:       [<c05d14bc>] kobject_add_varg+0x41/0x5e
Jul 28 22:03:36 grinch kernel:       [<c05d1579>] kobject_add+0x51/0x68
Jul 28 22:03:36 grinch kernel:       [<c06873fa>] device_add+0xe3/0x49d
Jul 28 22:03:36 grinch kernel:       [<c06877db>] device_register+0x27/0x3c
Jul 28 22:03:36 grinch kernel:       [<c068789c>] device_create_vargs+0xac/0xe5
Jul 28 22:03:36 grinch kernel:       [<c0687903>] device_create+0x2e/0x41
Jul 28 22:03:36 grinch kernel:       [<c066ab27>] register_con_driver+0xbb/0x126
Jul 28 22:03:36 grinch kernel:       [<c066bec0>] take_over_console+0x2f/0x61
Jul 28 22:03:36 grinch kernel:       [<c060ed24>] fbcon_takeover+0x6f/0xb3
Jul 28 22:03:36 grinch kernel:       [<c060f34b>] fbcon_event_notify+0x296/0x60e
Jul 28 22:03:36 grinch kernel:       [<c07f9511>] notifier_call_chain+0x5d/0x95
Jul 28 22:03:36 grinch kernel:       [<c045fdb5>] __blocking_notifier_call_chain+0x52/0x78
Jul 28 22:03:36 grinch kernel:       [<c045fdfc>] blocking_notifier_call_chain+0x21/0x37
Jul 28 22:03:36 grinch kernel:       [<c0601d59>] fb_notifier_call_chain+0x25/0x38
Jul 28 22:03:36 grinch kernel:       [<c0603f12>] register_framebuffer+0x1f6/0x218
Jul 28 22:03:36 grinch kernel:       [<f81f443e>] intelfb_probe+0x4a2/0x51d [i915]
Jul 28 22:03:36 grinch kernel:       [<f80e4a17>] drm_helper_initial_config+0x15a/0x175 [drm]
Jul 28 22:03:36 grinch kernel:       [<f81e322c>] i915_driver_load+0x937/0x99f [i915]
Jul 28 22:03:36 grinch kernel:       [<f80dc5c4>] drm_get_dev+0x2f7/0x3bf [drm]
Jul 28 22:03:36 grinch kernel:       [<f81f8f30>] i915_pci_probe+0x21/0x9d [i915]
Jul 28 22:03:36 grinch kernel:       [<c05e9f54>] local_pci_probe+0x22/0x35
Jul 28 22:03:36 grinch kernel:       [<c05eade6>] pci_device_probe+0x54/0x8a
Jul 28 22:03:36 grinch kernel:       [<c068a047>] driver_probe_device+0xcc/0x1db
Jul 28 22:03:36 grinch kernel:       [<c068a1ac>] __driver_attach+0x56/0x84
Jul 28 22:03:36 grinch kernel:       [<c068949b>] bus_for_each_dev+0x53/0x8e
Jul 28 22:03:36 grinch kernel:       [<c0689dc2>] driver_attach+0x27/0x3a
Jul 28 22:03:36 grinch kernel:       [<c0689a8a>] bus_add_driver+0xe2/0x224
Jul 28 22:03:36 grinch kernel:       [<c068a4d3>] driver_register+0x89/0xfe
Jul 28 22:03:36 grinch kernel:       [<c05eb022>] __pci_register_driver+0x5c/0xcd
Jul 28 22:03:36 grinch kernel:       [<f80d7dd6>] drm_init+0x6e/0xd7 [drm]
Jul 28 22:03:36 grinch kernel:       [<f80fc054>] 0xf80fc054
Jul 28 22:03:36 grinch kernel:       [<c040309e>] do_one_initcall+0x75/0x193
Jul 28 22:03:36 grinch kernel:       [<c0476bd5>] sys_init_module+0xa7/0x1c2
Jul 28 22:03:36 grinch kernel:       [<c040a5eb>] sysenter_do_call+0x12/0x38
Jul 28 22:03:36 grinch kernel:       [<ffffffff>] 0xffffffff
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: -> #1 ((fb_notifier_list).rwsem){.+.+.+}:
Jul 28 22:03:36 grinch kernel:       [<c046d530>] __lock_acquire+0x981/0xafa
Jul 28 22:03:36 grinch kernel:       [<c046d760>] lock_acquire+0xb7/0xeb
Jul 28 22:03:36 grinch kernel:       [<c07f5c18>] down_read+0x45/0x93
Jul 28 22:03:36 grinch kernel:       [<c045fda3>] __blocking_notifier_call_chain+0x40/0x78
Jul 28 22:03:36 grinch kernel:       [<c045fdfc>] blocking_notifier_call_chain+0x21/0x37
Jul 28 22:03:36 grinch kernel:       [<c0601d59>] fb_notifier_call_chain+0x25/0x38
Jul 28 22:03:36 grinch kernel:       [<c0603f12>] register_framebuffer+0x1f6/0x218
Jul 28 22:03:36 grinch kernel:       [<f81f443e>] intelfb_probe+0x4a2/0x51d [i915]
Jul 28 22:03:36 grinch kernel:       [<f80e4a17>] drm_helper_initial_config+0x15a/0x175 [drm]
Jul 28 22:03:36 grinch kernel:       [<f81e322c>] i915_driver_load+0x937/0x99f [i915]
Jul 28 22:03:36 grinch kernel:       [<f80dc5c4>] drm_get_dev+0x2f7/0x3bf [drm]
Jul 28 22:03:36 grinch kernel:       [<f81f8f30>] i915_pci_probe+0x21/0x9d [i915]
Jul 28 22:03:36 grinch kernel:       [<c05e9f54>] local_pci_probe+0x22/0x35
Jul 28 22:03:36 grinch kernel:       [<c05eade6>] pci_device_probe+0x54/0x8a
Jul 28 22:03:36 grinch kernel:       [<c068a047>] driver_probe_device+0xcc/0x1db
Jul 28 22:03:36 grinch kernel:       [<c068a1ac>] __driver_attach+0x56/0x84
Jul 28 22:03:36 grinch kernel:       [<c068949b>] bus_for_each_dev+0x53/0x8e
Jul 28 22:03:36 grinch kernel:       [<c0689dc2>] driver_attach+0x27/0x3a
Jul 28 22:03:36 grinch kernel:       [<c0689a8a>] bus_add_driver+0xe2/0x224
Jul 28 22:03:36 grinch kernel:       [<c068a4d3>] driver_register+0x89/0xfe
Jul 28 22:03:36 grinch kernel:       [<c05eb022>] __pci_register_driver+0x5c/0xcd
Jul 28 22:03:36 grinch kernel:       [<f80d7dd6>] drm_init+0x6e/0xd7 [drm]
Jul 28 22:03:36 grinch kernel:       [<f80fc054>] 0xf80fc054
Jul 28 22:03:36 grinch kernel:       [<c040309e>] do_one_initcall+0x75/0x193
Jul 28 22:03:36 grinch kernel:       [<c0476bd5>] sys_init_module+0xa7/0x1c2
Jul 28 22:03:36 grinch kernel:       [<c040a5eb>] sysenter_do_call+0x12/0x38
Jul 28 22:03:36 grinch kernel:       [<ffffffff>] 0xffffffff
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: -> #0 (&fb_info->lock){+.+.+.}:
Jul 28 22:03:36 grinch kernel:       [<c046d437>] __lock_acquire+0x888/0xafa
Jul 28 22:03:36 grinch kernel:       [<c046d760>] lock_acquire+0xb7/0xeb
Jul 28 22:03:36 grinch kernel:       [<c07f54f5>] __mutex_lock_common+0x43/0x338
Jul 28 22:03:36 grinch kernel:       [<c07f58dd>] mutex_lock_nested+0x41/0x5a
Jul 28 22:03:36 grinch kernel:       [<c0602465>] fb_mmap+0x94/0x17d
Jul 28 22:03:36 grinch kernel:       [<c04d08fe>] mmap_region+0x272/0x404
Jul 28 22:03:36 grinch kernel:       [<c04d0d03>] do_mmap_pgoff+0x273/0x2d6
Jul 28 22:03:36 grinch kernel:       [<c040e455>] sys_mmap2+0x86/0xb9
Jul 28 22:03:36 grinch kernel:       [<c040a5eb>] sysenter_do_call+0x12/0x38
Jul 28 22:03:36 grinch kernel:       [<ffffffff>] 0xffffffff
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: other info that might help us debug this:
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: 1 lock held by plymouthd/39:
Jul 28 22:03:36 grinch kernel: #0:  (&mm->mmap_sem){++++++}, at: [<c040e441>] sys_mmap2+0x72/0xb9
Jul 28 22:03:36 grinch kernel:
Jul 28 22:03:36 grinch kernel: stack backtrace:
Jul 28 22:03:36 grinch kernel: Pid: 39, comm: plymouthd Not tainted 2.6.30-0.76.rc4.fc12.i686.PAE #1
Jul 28 22:03:36 grinch kernel: Call Trace:
Jul 28 22:03:36 grinch kernel: [<c07f402d>] ? printk+0x22/0x35
Jul 28 22:03:36 grinch kernel: [<c046c897>] print_circular_bug_tail+0x68/0x84
Jul 28 22:03:36 grinch kernel: [<c046d437>] __lock_acquire+0x888/0xafa
Jul 28 22:03:36 grinch kernel: [<c046d760>] lock_acquire+0xb7/0xeb
Jul 28 22:03:36 grinch kernel: [<c0602465>] ? fb_mmap+0x94/0x17d
Jul 28 22:03:36 grinch kernel: [<c0602465>] ? fb_mmap+0x94/0x17d
Jul 28 22:03:36 grinch kernel: [<c07f54f5>] __mutex_lock_common+0x43/0x338
Jul 28 22:03:36 grinch kernel: [<c0602465>] ? fb_mmap+0x94/0x17d
Jul 28 22:03:36 grinch kernel: [<c046bcd9>] ? mark_lock+0x29/0x1f1
Jul 28 22:03:36 grinch kernel: [<c0602465>] ? fb_mmap+0x94/0x17d
Jul 28 22:03:36 grinch kernel: [<c046beef>] ? mark_held_locks+0x4e/0x78
Jul 28 22:03:36 grinch kernel: [<c07f58dd>] mutex_lock_nested+0x41/0x5a
Jul 28 22:03:36 grinch kernel: [<c0602465>] ? fb_mmap+0x94/0x17d
Jul 28 22:03:36 grinch kernel: [<c0602465>] fb_mmap+0x94/0x17d
Jul 28 22:03:36 grinch kernel: [<c04d08fe>] mmap_region+0x272/0x404
Jul 28 22:03:36 grinch kernel: [<c04d0d03>] do_mmap_pgoff+0x273/0x2d6
Jul 28 22:03:36 grinch kernel: [<c040e455>] sys_mmap2+0x86/0xb9
Jul 28 22:03:36 grinch kernel: [<c040a5eb>] sysenter_do_call+0x12/0x38


In the end I'm unable to start a gnome-terminal, and xterm does not spawn a shell. Loging in the tty do work.


See attached var/log/messages

Comment 1 Hubert Figuiere 2009-07-29 02:22:52 UTC
Created attachment 355483 [details]
var/log/messages

This is actually the same as above, but only with the relevant kernel bootup.

Ignore the previous one.

Comment 2 Hubert Figuiere 2009-11-07 18:26:06 UTC
This no longer occurs on F12 and I think on recent F11 kernels.

Comment 3 Bug Zapper 2009-11-16 11:10:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-11-04 10:39:35 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-12-05 06:40:16 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.