All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dieter Ries <clip2@gmx.de>,
	Maciej Rutecki <maciej.rutecki@gmail.com>,
	travis@sgi.com, rusty@rustcorp.com.au,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: 2.6.29-rc1 does not boot
Date: Mon, 12 Jan 2009 21:45:44 -0700	[thread overview]
Message-ID: <20090113044544.GA22166@ellpspace.math.ualberta.ca> (raw)
In-Reply-To: <20090112185954.GB15494@elte.hu>

On Mon, Jan 12, 2009 at 07:59:54PM +0100, Ingo Molnar wrote:
> * Dieter Ries <clip2@gmx.de> wrote:
> 
> > 
> > This is what I have got:
> > 
> > [   12.340122] =============================================
> > [   12.341044] [ INFO: possible recursive locking detected ]
> > [   12.341044] 2.6.29-rc1-00041-gacd1e11 #143
> > [   12.341044] ---------------------------------------------
> > [   12.341044] events/0/9 is trying to acquire lock:
> > [   12.341044]  (events){--..}, at: [<ffffffff80254783>]
....
> > Hope that helps,
> 
> thanks, it helps!

I bumped into something pretty similar, although not precisely the
same, with 2.6.29-0.28.rc1.fc11.x86_64 Fedora rawhide kernel.

=============================================
[ INFO: possible recursive locking detected ]
2.6.29-0.28.rc1.fc11.x86_64 #1
---------------------------------------------
events/0/6 is trying to acquire lock:
 (events){--..}, at: [<ffffffff8105b843>] flush_workqueue+0x0/0xa4

but task is already holding lock:
 (events){--..}, at: [<ffffffff8105ae26>] run_workqueue+0xb1/0x20a

It appears that this during an initialization of AC97 sound system.
What I got is at https://bugzilla.redhat.com/show_bug.cgi?id=479778
and close to the bottom of
https://bugzilla.redhat.com/attachment.cgi?id=328808

It is a throw of a dice if this kernel will boot or not.

   Michal

  reply	other threads:[~2009-01-13  4:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 14:55 2.6.29-rc1 does not boot Dieter Ries
2009-01-11 15:19 ` Ingo Molnar
2009-01-11 15:30   ` Dieter Ries
2009-01-11 15:35     ` Ingo Molnar
2009-01-11 15:41       ` Dieter Ries
2009-01-11 18:50       ` Dieter Ries
2009-01-11 19:02         ` Mike Travis
2009-01-11 19:30           ` Dieter Ries
2009-01-12 10:00           ` Ingo Molnar
2009-01-12 17:53             ` Mike Travis
2009-01-12 18:55               ` Ingo Molnar
2009-01-15  0:54             ` Rusty Russell
2009-01-11 19:02         ` Ingo Molnar
2009-01-11 19:14           ` Mike Travis
2009-01-11 23:19             ` Mike Travis
2009-01-12  1:01             ` H. Peter Anvin
2009-01-12 11:22         ` Maciej Rutecki
2009-01-12 11:26           ` Ingo Molnar
2009-01-12 11:28             ` Maciej Rutecki
2009-01-12 12:10             ` Dieter Ries
2009-01-12 12:21               ` Ingo Molnar
2009-01-12 16:37                 ` Dieter Ries
2009-01-12 18:59                   ` Ingo Molnar
2009-01-13  4:45                     ` Michal Jaegermann [this message]
2009-01-12 17:22             ` 2.6.29-rc1 does not boot and fails to resume Rafael J. Wysocki
2009-01-14  1:16             ` 2.6.29-rc1 does not boot Rusty Russell
2009-01-14 11:30               ` Ingo Molnar
2009-01-14 12:47               ` Dieter Ries
2009-01-15 20:01         ` Mike Travis
2009-01-15 21:03           ` Dieter Ries
2009-01-15 21:48             ` Maciej Rutecki
2009-01-15 21:54               ` Mike Travis
2009-01-15 23:04                 ` Maciej Rutecki
2009-01-15 23:31                   ` Mike Travis
2009-01-15 21:54             ` Mike Travis
2009-01-15 23:02               ` Dieter Ries
2009-01-15 23:30                 ` Mike Travis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090113044544.GA22166@ellpspace.math.ualberta.ca \
    --to=michal@ellpspace.math.ualberta.ca \
    --cc=a.p.zijlstra@chello.nl \
    --cc=clip2@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=travis@sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.