From: "Ralf Müller" <ralf@bj-ig.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com,
linux-ide@vger.kernel.org
Subject: Re: Kernel panic with 2.6.15-rc7 + libata1 patch
Date: Sun, 01 Jan 2006 17:43:51 +0100 [thread overview]
Message-ID: <43B806C7.5000607@bj-ig.de> (raw)
In-Reply-To: <20060101145702.GV3811@stusta.de>
Adrian Bunk schrieb:
> Is this problem present with older kernel (e.g. 2.6.14.x) or is it a
> newly introduced bug?
It is a newly installed system - 2.6.15-rc6 has been the first kernel at
all on this machine - this kernel crashed too. After that I upgraded to
2.6.15-rc7 - it crashed as written in the initial mail. Next was to
apply the libata1 patch. It did not give a kernel panic but shut down
the SATA subsystem (the hardware is a Promise SATA II 300 TX4 PDC 20718
and an onboard Promise SATA II 150 PDC20579) - non of the six attached
disks has been accessible anymore after calling hddtemp on one of the
disks which have been in standby. Calling hddtemp on a spinning disk
works without a problem.
A further problem is that calling "hdparm -C" _always_ give "drive state
is: standby" - even when the disks are clearly active. Maybe this
indicates something to you.
I can try to downgrade to 2.6.14 if you like. I started with 2.6.15
because I have been told it is the first kernel which is able to deal
with "hdparm -S x" / "hdparm -y" for SATA devices.
> I've put Jeff into the Cc of this email since he is the SATA maintainer.
Thanks.
Regards
Ralf
next prev parent reply other threads:[~2006-01-01 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43B724BA.90405@bj-ig.de>
[not found] ` <43B7EA0A.7040805@bj-ig.de>
2006-01-01 14:57 ` Kernel panic with 2.6.15-rc7 + libata1 patch Adrian Bunk
2006-01-01 16:43 ` Ralf Müller [this message]
2006-01-02 14:06 ` Mark Lord
2006-01-03 16:53 ` hdparm -C always give drive state is standby (was: Kernel panic with 2.6.15-rc7 + libata1 patch) Ralf Müller
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=43B806C7.5000607@bj-ig.de \
--to=ralf@bj-ig.de \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).