Re: 2.6.18-rc3-mm2 - ext3 locking issue?

On Wed, 09 Aug 2006 16:43:20 EDT, [email protected] 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?

Attachment: pgp2CKGqFT1Pq.pgp
Description: PGP signature

---

• Follow-Ups:
  • Re: 2.6.18-rc3-mm2 - ext3 locking issue?
    • From: Jiri Slaby <[email protected]>

• References:
  • 2.6.18-rc3-mm2
    • From: Andrew Morton <[email protected]>
  • 2.6.18-rc3-mm2 - ext3 locking issue?
    • From: [email protected]
  • Re: 2.6.18-rc3-mm2 - ext3 locking issue?
    • From: Andrew Morton <[email protected]>
  • Re: 2.6.18-rc3-mm2 - ext3 locking issue?
    • From: [email protected]

• Prev by Date: Re: ext3 corruption
• Next by Date: Re: [PATCH] not empty pages list after fuse_readpages
• Previous by thread: Re: 2.6.18-rc3-mm2 - ext3 locking issue?
• Next by thread: Re: 2.6.18-rc3-mm2 - ext3 locking issue?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]