From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at drivers/ide/ide.c:1384!
Date: Mon, 09 Jan 2006 14:19:12 +0000 [thread overview]
Message-ID: <1136816352.6659.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20060109095159.GE4535@charite.de>
On Llu, 2006-01-09 at 10:51 +0100, Ralf Hildebrandt wrote:
> I invoked "hdparm -w /dev/hda"
>
> # uname -a
> Linux hummus.charite.de 2.6.15 #1 Tue Jan 3 09:30:04 CET 2006 i686 GNU/Linux
>
> Before you flame away at me for using the nvidia kernel module: I will
> reproduce this WITHOUT the nvidia kernel module. At least I'll try.
You should be able to reproduce it without the Nvidia code loaded if you
do I/O on the disk and run hdparm -w in a tight loop while doing so.
You might want to do it on a disk you have a backup of
next prev parent reply other threads:[~2006-01-09 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 9:51 kernel BUG at drivers/ide/ide.c:1384! Ralf Hildebrandt
2006-01-09 10:06 ` Ralf Hildebrandt
2006-01-09 14:19 ` Alan Cox [this message]
2006-01-09 14:19 ` Ralf Hildebrandt
2006-01-09 15:30 ` linux-os (Dick Johnson)
2006-01-09 16:02 ` Alan Cox
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=1136816352.6659.10.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Ralf.Hildebrandt@charite.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