linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: n0diamond@yahoo.co.jp
Cc: linux-ide@vger.kernel.org, Mark Lord <liml@rtr.ca>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Chuck Ebbert <cebbert@redhat.com>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Kernel bug crashing in HDIO_DRIVE_TASKFILE
Date: Sun, 01 Mar 2009 20:38:05 -0600	[thread overview]
Message-ID: <49AB468D.6030506@gmail.com> (raw)
In-Reply-To: <20090302002434.62707.qmail@web4109.mail.ogk.yahoo.co.jp>

Norman Diamond wrote:
> I will try building a kernel without legacy IDE drivers,
> but meanwhile here's the latest bug.
> 
> Knoppix 6.0.1 is built on kernel 2.6.28.4.  Legacy IDE
> drivers still claim /dev/hda and /dev/hdc (the Knoppix CD
> being on /dev/hdc).
> 
> In order to view part of a dump if it occurs, I typed the
> following boot command:
> knoppix 3 lang=en keyboard=jp106
> 
> When I try to do a TASKFILE WRITE_DMA (LBA28), the process
> hangs.  No dump.  Ctrl+C and Ctrl+Z were ignored. 
> Ctrl+Alt+F2 switched to a second VT (by the way this no
> longer works if Knoppix 6.0.1 is booted to graphical
> mode).  The second VT responded at first.  Then tried to
> do a dd if=/dev/hda bs=512 count=5 | od, and the second VT
> hanged too.
> 
> In the third VT, dmesg showed this error message:
> hda-intel: Invalid position buffer, using LPIB read method
> instead.
> 
> Google found several threads where people are blaming this
> error message on audio drivers or wireless LAN drivers. 
> Some people are saying it was fixed somewhere earlier than
> 2.6.28.4.  2.6.28.4 tells me it's not fixed, and the
> timing sure doesn't look like audio or wireless LAN.

I'm guessing that's a symptom and not a cause, if the IDE driver is
causing some kind of partial lockup then that could be messing with the
audio driver..

> 
> I'll try building a kernel without legacy IDE drivers, but
> I wonder which kernel version to try.

Normally latest is best..

  reply	other threads:[~2009-03-02  2:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 11:36 Kernel bug crashing in HDIO_DRIVE_TASKFILE Norman Diamond
2009-02-24 22:10 ` Chuck Ebbert
2009-02-25 11:43   ` Norman Diamond
2009-02-25 16:24     ` Mark Lord
2009-02-25 19:35       ` Bartlomiej Zolnierkiewicz
2009-02-25 21:18         ` Norman Diamond
2009-02-25 22:43           ` Mark Lord
2009-02-26 11:56             ` Norman Diamond
2009-02-28  3:14               ` Robert Hancock
2009-03-01  0:58                 ` Norman Diamond
2009-03-01  1:16                   ` Alan Cox
2009-03-01 11:06                   ` Robert Hancock
2009-03-02  0:24                     ` Norman Diamond
2009-03-02  2:38                       ` Robert Hancock [this message]
2009-03-02 11:43                         ` Norman Diamond
2009-03-11 22:33                       ` Bartlomiej Zolnierkiewicz
2009-03-11 23:00                         ` Norman Diamond
  -- strict thread matches above, loose matches on Subject: below --
2009-03-03 11:44 Norman Diamond

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=49AB468D.6030506@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=bzolnier@gmail.com \
    --cc=cebbert@redhat.com \
    --cc=jens.axboe@oracle.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=n0diamond@yahoo.co.jp \
    /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).