From: Julien Oster <lkml@mf.frodoid.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.69-mm8] ide_dmaq_intr: stat=40, not expected
Date: Fri, 23 May 2003 01:26:14 +0200 [thread overview]
Message-ID: <frodoid.frodo.87fzn68sx5.fsf@usenet.frodoid.org> (raw)
In-Reply-To: <20030522225011$5a69@gated-at.bofh.it> (Bartlomiej Zolnierkiewicz's message of "Fri, 23 May 2003 00:50:11 +0200")
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> 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
next parent reply other threads:[~2003-05-22 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030522224010$6dac@gated-at.bofh.it>
[not found] ` <20030522225011$5a69@gated-at.bofh.it>
2003-05-22 23:26 ` Julien Oster [this message]
2003-05-23 0:30 Mudama, Eric
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 22:29 Julien Oster
2003-05-22 22:43 ` Bartlomiej Zolnierkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=frodoid.frodo.87fzn68sx5.fsf@usenet.frodoid.org \
--to=lkml@mf.frodoid.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®