Re: more cfq spinlock badness
- From: Dave Jones <davej@xxxxxxxxxx>
- Date: Tue, 31 Jan 2006 12:36:01 -0500
On Tue, Jan 31, 2006 at 10:09:45AM +0100, Jens Axboe wrote:
> On Tue, Jan 31 2006, Dave Jones wrote:
> > Not seen this break for a while, but I just hit it again in 2.6.16rc1-git4.
> >
> > Dave
> >
> > BUG: spinlock bad magic on CPU#0, pdflush/1128
> > lock: ffff81003a219000, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
> >
> > Call Trace: <ffffffff80206edc>{spin_bug+177} <ffffffff80207045>{_raw_spin_lock+25}
> > <ffffffff801fea4a>{cfq_exit_single_io_context+85} <ffffffff801ff9a6>{cfq_exit_io_context+24}
> > <ffffffff801f79b0>{exit_io_context+137} <ffffffff80135fbc>{do_exit+182}
> > <ffffffff8010ba49>{child_rip+15} <ffffffff80146087>{keventd_create_kthread+0}
> > <ffffffff8014629c>{kthread+0} <ffffffff8010ba3a>{child_rip+0}
> > Kernel panic - not syncing: bad locking
>
> Again, which devices have you used?
nothing special (Ie, no usb bits, just the onboard ata_piix SATA)
> Did it happen at shutdown, or?
whislt starting up a bunch of gnome panel applets.
> Did the ub bug get fixed
yes
> if you are using that? The bug above has in the
> past always been able to be explained by a driver destroying a structure
> embedding the queue lock before the queue is dead.
as there were no ub devices plugged in at the time, I think
Pete is off the hook for this one.
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- more cfq spinlock badness
- From: Dave Jones
- Re: more cfq spinlock badness
- From: Jens Axboe
- more cfq spinlock badness
- Prev by Date: Re: 2.6.16-rc1-mm4: ACX=y, ACX_USB=n compile error
- Next by Date: Re: [PATCH 4/11] LED: Add LED Timer Trigger
- Previous by thread: Re: more cfq spinlock badness
- Next by thread: Linux 2.6.15.2
- Index(es):
Relevant Pages
|
|
