Messages in this thread | | | Date | Thu, 10 Aug 2006 19:33:13 +0200 | From | Mattia Dongili <> | Subject | Re: 2.6.18-rc3-mm2 - ext3 locking issue? |
| |
On Thu, Aug 10, 2006 at 08:27:49AM -0700, Andrew Morton wrote: > On Thu, 10 Aug 2006 13:39:11 +0159 > Jiri Slaby <jirislaby@gmail.com> wrote: > > > Valdis.Kletnieks@vt.edu wrote: > > > On Wed, 09 Aug 2006 16:43:20 EDT, Valdis.Kletnieks@vt.edu said: > > > > > >>> Usually this means that there's an IO request in flight and it got lost > > >>> somewhere. Device driver bug, IO scheduler bug, etc. Conceivably a > > >>> lost interrupt (hardware bug, PCI setup bug, etc). > > > > > >> Aug 9 14:30:24 turing-police kernel: [ 3535.720000] end_request: I/O error, dev fd0, sector 0 > > > > > > Red herring. yum just wedged again, this time with no reference to floppy drive. > > > Same traceback. Anybody have anything to suggest before I start playing > > > hunt-the-wumpus with a -mm bisection? > > > > Hmm, I have the accurately same problem... > > yum + CFQ + BLK_DEV_PIIX + nothing odd in dmesg
oooh, same setup and same trace here, but no yum, see some screenshots here: http://oioio.altervista.org/linux/dsc03448.jpg http://oioio.altervista.org/linux/dsc03449.jpg
The use case for me was simply: - boot (in single user for the 2 shots) - suspend - resume - wait some seconds and do anything that accesses the disk
[...] > Is yum the only process which was stuck in D state?
in my case anything accessing the disk, leading to lockup shortly
> If so, I'd still be expecting a device driver/iosched bug. > > If not, it's probably a vfs/fs deadlock.
I reverted the full git-block.patch and I'm now using rc3-mm2 since then suspending to ram, disk and using my laptop for daily stuff:
reboot system boot 2.6.18-rc3-mm2-1 Tue Aug 8 00:02 - 19:30 (2+19:27)
PS: my previous pasts are here: http://lkml.org/lkml/2006/8/7/264 probably an unfortunate Cc list :)
-- mattia :wq! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |