Re: [1/6] 2.6.21-rc4: known regressions

Mariusz Kozłowski
2007-03-22T18:21:11Z

Hello,

> > In contrast, the hang reported by Mariusz Kozlowski has a slightly
> > different feel to it, but there's a tantalizing pattern in there too:

Just to make things clear. I didn't say I could reproduce it on 2.6.21-rc4.
In fact I'm running 2.6.21-rc4-mm1 with no problems so far. I just replied
to show my sysrq dumps of processes states with 2.6.21-rc2-mm1.

I could reproduce similar (but still each time slightly different) hangs
on -mm series from 2.6.20-mm1 to 2.6.21-rc2-mm1. 2.6.21-rc3-mm1 worked well
for me so not sure If my report is still valid here.

Sorry if I didn't make it clear enough.

> > http://www.ussg.iu.edu/hypermail/linux/kernel/0703.0/1243.html
> >
> > Call Trace:
> > [<c03ec87e>] io_schedule+0x42/0x59
> > [<c0184915>] sleep_on_buffer+0x8/0xc
> > [<c03ed217>] __wait_on_bit+0x47/0x6c
> > [<c03ed297>] out_of_line_wait_on_bit+0x5b/0x64
> > [<c01848a8>] __wait_on_buffer+0x27/0x2d
> > [<c01b4228>] journal_commit_transaction+0x707/0x127f
> > [<c01b868b>] kjournald+0xac/0x1ed
> > [<c0126af5>] kthread+0xa2/0xc9
> > [<c010422b>] kernel_thread_helper+0x7/0x1c
> >
> > which certainly also looks like an IO never completed (or completed but
> > never woke anything up).

As I previously noticed each time the system hang I/O activity to disk looked
dead (couldn't even sysrq-s).

> It could be possible that ext3 is doing something weird and expecting

True. I'm using ext3.

> fs: nobh data leak... again hard to see how it could cause an unlock/wakeup
> to get lost. Is Mariusz using the nobh mount option?

No. He is not.

Regards,

Mariusz Kozlowski