mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Trefzer <ctrefzer@gmx.de>
To: Alejandro Bonilla <abonilla@linuxwireless.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel hda errors on dmesg
Date: Mon, 20 Mar 2006 11:48:40 +0100	[thread overview]
Message-ID: <20060320104839.GA20646@hermes.uziel.local> (raw)
In-Reply-To: <20060319235255.M28695@linuxwireless.org>

[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]

Hi Alejandro,


On Sun, Mar 19, 2006 at 05:57:09PM -0600, Alejandro Bonilla wrote:
> Why am I getting hda errors when I don't even have a hda drive? Mine is sda.
> The syslog says is the kernel itself, no other application is causing this as
> I have stopped most services and still happen.
> 
> dmesg
> 
> [4295643.338000] ide: failed opcode was: 0xef 
> [4295644.283000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
> [4295644.295000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
> [4295645.963000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
> [4295645.966000] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } 
> [4295645.966000] hda: drive_cmd: error=0x04 { AbortedCommand } 
> [4295645.966000] ide: failed opcode was: 0xec 
> [4295646.000000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
> [4295646.003000] hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } 
> [4295646.003000 ] hda: drive_cmd: error=0x04 { AbortedCommand } 
> [4295646.003000] ide: failed opcode was: 0xec 
> [4295646.345000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
> [4295646.357000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30  ascq: 0x00 
> [4295648.408000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
> [4295648.421000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
> [4295650.471000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30   ascq: 0x00 
> [4295650.483000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
> [4295652.534000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00 
> [4295652.546000] hda: error code: 0x70  sense_key: 0x02  asc: 0x30   ascq: 0x00 
> [4295654.601000] hda: error code: 0x70  sense_key: 0x02   asc: 0x30  ascq: 0x00 
> [4295654.612000] hda: error code: 0x70   sense_key: 0x02  asc: 0x30  ascq: 0x00
>
> Any idea?

Just an idea, but this looks to me like problems reading a CD - if you
use ide-cd and a normal parralel ATA / ATAPI CD-ROM drive, you might
have /dev/hda and a symlink pointing to that node as well. In this case,
you only care for e.g. /dev/cdrom, but in fact are using /dev/hda.


Regards,
Chris

[-- Attachment #2: Type: application/pgp-signature, Size: 829 bytes --]

  reply	other threads:[~2006-03-20 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060318081134.M30026@linuxwireless.org>
     [not found] ` <17915ac50603180054l4c3c6646ifcdee47e8f76887c@mail.gmail.com>
2006-03-19 23:57   ` Alejandro Bonilla
2006-03-20 10:48     ` Christian Trefzer [this message]
     [not found]     ` <20060320033955.GC18898@eugeneteo.net>
2006-03-20 16:41       ` kernel hda errors on dmesg - new VFS messages Alejandro Bonilla
2006-03-20 19:26         ` Nick Warne

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=20060320104839.GA20646@hermes.uziel.local \
    --to=ctrefzer@gmx.de \
    --cc=abonilla@linuxwireless.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

all inboxes | Powered by JetHome®