On Thu, 10 Aug 2006 13:39:11 +0159
Jiri Slaby <[email protected]> wrote:
> [email protected] wrote:
> > 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?
>
> Hmm, I have the accurately same problem...
> yum + CFQ + BLK_DEV_PIIX + nothing odd in dmesg
>
> [ 3438.574864] yum D 00000000 0 21659 3838
> (NOTLB)
> [ 3438.575098] e5c09d24 00000001 c180f5a8 00000000 e5c09ce0 c01683e8
> fe37c0bc 000002c4
> [ 3438.575388] 00001000 00000001 c18fbbd0 0023001f 00000007 f26cc560
> c1913560 fe4166d5
> [ 3438.575713] 000002c4 0009a619 00000001 f26cc66c c180ec40 c04ff140
> e5c09d14 c01fad44
> [ 3438.576039] Call Trace:
> [ 3438.576113] [<c0373d3b>] io_schedule+0x26/0x30
> [ 3438.576187] [<c014653c>] sync_page+0x39/0x45
> [ 3438.576260] [<c0374401>] __wait_on_bit_lock+0x41/0x64
> [ 3438.576333] [<c01464ef>] __lock_page+0x57/0x5f
> [ 3438.576405] [<c014f5f2>] truncate_inode_pages_range+0x1b6/0x304
> [ 3438.576480] [<c014f76f>] truncate_inode_pages+0x2f/0x40
> [ 3438.576553] [<c01a7bc4>] ext3_delete_inode+0x29/0xf7
> [ 3438.576627] [<c017f26b>] generic_delete_inode+0x65/0xe7
> [ 3438.576701] [<c017f3aa>] generic_drop_inode+0xbd/0x173
> [ 3438.576774] [<c017ed25>] iput+0x6b/0x7b
> [ 3438.576846] [<c017cc57>] dentry_iput+0x68/0xb3
> [ 3438.576919] [<c017d99e>] dput+0x4f/0x19f
> [ 3438.576990] [<c0176164>] sys_renameat+0x1e0/0x212
> [ 3438.577063] [<c01761be>] sys_rename+0x28/0x2a
> [ 3438.577135] [<c01030fb>] syscall_call+0x7/0xb
>
Is yum the only process which was stuck in D state?
If so, I'd still be expecting a device driver/iosched bug.
If not, it's probably a vfs/fs deadlock.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[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]
