All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Martin Michlmayr <tbm@cyrius.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic on PC with broken hard drive, after DMA errors
Date: Wed, 08 Mar 2006 22:03:34 -0600	[thread overview]
Message-ID: <440FA916.5070703@shaw.ca> (raw)
In-Reply-To: <5Okau-77g-9@gated-at.bofh.it>

Martin Michlmayr wrote:
> My laptop hard drive recently died (or is in the process of dying).
> HP wanted me to do some more tests before sending me a replacement, so
> I tried booting Linux again today.  I got lots of DMA errors, which
> was really to be expected, but then I got a kernel panic.  While I'd
> not blame the kernel when a panic occurs with broken RAM or CPU, I'm
> sure sure the kernel should panic just because of a broken IDE drive.
> 
> I posted a picture of the panic at http://cyrius.com/tmp/ide_panic.jpg
> Is this something that can be fixed or is my hardware really so broken
> that the kernel cannot deal with it?

Probably is a genuine bug. These kinds of reports have come up a few 
times recently as I recall - it seems some of the error handling in the 
drivers/ide code isn't quite so robust..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-03-09  4:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5Okau-77g-9@gated-at.bofh.it>
2006-03-09  4:03 ` Robert Hancock [this message]
2006-03-09 15:14   ` Kernel panic on PC with broken hard drive, after DMA errors Martin Michlmayr
2006-03-09 16:45     ` Alan Cox
2006-03-09 16:53       ` Martin Michlmayr
2006-03-09 18:37         ` Alan Cox
2006-03-27  7:06       ` Martin Michlmayr
2006-03-09  3:29 Martin Michlmayr

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=440FA916.5070703@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tbm@cyrius.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.