RE: [2.5.69-mm8] ide_dmaq_intr: stat=40, not expected

[Mudama, Eric]

Just so you know, 0x40 status indicates "queued command received, not ready
for service yet".  However, some drives we've tested internally will stay
0x40 status instead of switching back to 0x50 status once they've serviced
the last queued tag.

They will go 0x50 following a successful non-queued command however.

--eric

-----Original Message-----
From: Julien Oster [mailto:[e-mail]]
Sent: Thursday, May 22, 2003 5:26 PM
To: Bartlomiej Zolnierkiewicz
Cc: [e-mail]
Subject: Re: [2.5.69-mm8] ide_dmaq_intr: stat=40, not expected

Bartlomiej Zolnierkiewicz <[e-mail]> writes:

> Hello,

Hello Bartlomiej,

> Can you compile without IDE TCQ and tell whats the difference?

Uh, well.

The message disappeared. However, since keyboard and mouse still
didn't work (although all input devices are compiled in - did I miss
something?), I had to press reset again.

Now my system seems quite fucked up. (or, better: "fscked up", since
the problems appeared there...)

After rebooting (again my stable 2.4.21-rc1 kernel), fsck ate a lot of
files on the root partition, all with "unused
inode... CLEARED". Strangely, ONLY on the root filesystem. All other
filesystems (all on md devices, like the root filesystem) are perfect.

I don't know if that's still an issue of IDE TCQ, but I think I'll
quit trying it out, since I already lost X right now and have to
restore quite a few things.

Well, of course I have backups, I wouldn't install a development
kernel without expecting things that are even much worse, but all
those recompile, reboot, retry, reset and restore backup cycles are
currently a bit too time consuming :)

However, if you need additional information to track the TCQ-problem
down, I see what I can give.

Regards,
Julien