From: Andre Costa <costa@tecgraf.puc-rio.br>
To: tom st denis <tomstdenis@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.26: IDE drives become unavailable randomly
Date: Wed, 30 Jun 2004 11:51:43 -0300 [thread overview]
Message-ID: <20040630115143.3748d296.costa@tecgraf.puc-rio.br> (raw)
In-Reply-To: <20040630135907.98538.qmail@web41115.mail.yahoo.com>
(please cc me on any replies, because I am not subscribed to this list)
Hi Tom,
On Wed, 30 Jun 2004 06:59:07 -0700 (PDT)
tom st denis <tomstdenis@yahoo.com> wrote:
> --- Andre Costa <costa@tecgraf.puc-rio.br> wrote:
> > (please cc me on any replies, because I am not subscribed to this
> > list;
> > if I do need to subscribe, just let me know)
> >
> > Hi,
> >
> > I am using 2.4.26 SMP on a ABIT AT7 mobo, with a 2.8GHz P4 processor
> > with hyper-threading enabled. I have one 80GB Seagate IDE disk
> > as /dev/hda, and from time to time it seems to "disappear", usually
> > after these messages appear a couple of trimes on/var/log/messages:
>
> I get a similar problem on my Presario laptop. In my case "all of a
> suddend" hda3 becomes write-only. Next time it happens I'll see if I
> can capture a dmesg log or something. It only seems to happen when I
> enable my wifi and do a lot of disk activity [but only once in a
> while]. Could be that my wifi and IDE0 share an IRQ?
I can't say the situation is the same here -- actually, it seems to be
more related (in my case) to idle times: usually this happens when the
system is under light load (or under no load at all), like between
0:00am and 6:00am. This is why my primary suspect is APM (I could be
completely wrong, of course). Also, I don't have wifi.
> Of course I'm more apt to blame my laptop than Linux since the same
> kernel [well diff build options but you know what I mean] works just
> fine on my two desktops in the house...
Yeah, I know what you mean: the same Linux distro has been running
flawlessly on other boxes around here for months (with different
hardware specs, though). Mine OTOH has a sad uptime record of 5 days...
=(
I agree Linux works (actually, it rocks =)), been using it for years
both at home and at work, but sometimes a specific hardware combination
(or buggy hardware/BIOS/firmware etc.) pushes it to the edge, reaching
some weak spots that need to be "hardened". Some hardware simply doesn't
work at all (I hope that's not my case...)
Best,
Andre
--
Andre Oliveira da Costa
(costa@tecgraf.puc-rio.br)
next prev parent reply other threads:[~2004-06-30 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 11:41 Andre Costa
2004-06-30 13:59 ` tom st denis
2004-06-30 14:51 ` Andre Costa [this message]
2004-06-30 15:18 Nick Warne
2004-07-01 9:48 ` Bruce Allen
2004-07-01 10:49 ` Andre Costa
2004-07-01 18:43 ` Nick Warne
2004-07-01 19:03 ` Andre Costa
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=20040630115143.3748d296.costa@tecgraf.puc-rio.br \
--to=costa@tecgraf.puc-rio.br \
--cc=linux-kernel@vger.kernel.org \
--cc=tomstdenis@yahoo.com \
/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®