From: Ronald Wahl <ronald.wahl@informatik.tu-chemnitz.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.9] HPT372N - oops (NULL pointer dereference)
Date: Sat, 23 Oct 2004 00:58:35 +0200 [thread overview]
Message-ID: <m21xfqpdgk.fsf@rohan.middle-earth.priv> (raw)
In-Reply-To: <m23c09p01z.fsf@rohan.middle-earth.priv> (Ronald Wahl's message of "Wed, 20 Oct 2004 23:11:20 +0200")
On Wed, 20 Oct 2004 23:11:20 +0200, Ronald Wahl wrote:
> Hello,
> I just tried upgrading from 2.6.7 to 2.6.9 and got a kernel oops during
> boot. Stack trace looked very similar to the one João Luis Meloni Assirati
> reported on Oct 05 2004 (Subject: hpt366 under hpt372N oops). I have a
> HPT372N on my board with one disk attached.
> Is there any news on this issue yet? It keeps me from using 2.6.9. :-/
Since no one seems to care about it I had a quick look by myself into
drivers/ide/pci/hpt366.c:
For the HPT372N pci_get_drvdata(dev) will return NULL and this will
result in an oops during pci_bus_clock_list() which is called from
hpt372_tune_chipset().
- ron
prev parent reply other threads:[~2004-10-22 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 21:11 [2.6.9] HPT372N - oops (NULL pointer dereference) Ronald Wahl
2004-10-22 22:58 ` Ronald Wahl [this message]
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=m21xfqpdgk.fsf@rohan.middle-earth.priv \
--to=ronald.wahl@informatik.tu-chemnitz.de \
--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