All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Bonilla" <abonilla@linuxwireless.org>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel hda errors on dmesg - new VFS messages
Date: Mon, 20 Mar 2006 10:41:46 -0600	[thread overview]
Message-ID: <20060320162753.M3577@linuxwireless.org> (raw)
In-Reply-To: <20060320033955.GC18898@eugeneteo.net>

After installing 2.6.16, it looks like the hda messages(below) changed to:

[4294840.149000] VFS: busy inodes on changed media.
[4294840.162000] VFS: busy inodes on changed media.
[4294840.251000] VFS: busy inodes on changed media.
[4294840.258000] VFS: busy inodes on changed media.
[4294850.829000] VFS: busy inodes on changed media.
[4294850.830000] VFS: busy inodes on changed media.
[4294850.831000] VFS: busy inodes on changed media.
[4294850.832000] VFS: busy inodes on changed media.
[4294850.837000] VFS: busy inodes on changed media.
[4294852.847000] VFS: busy inodes on changed media.
[4294852.848000] VFS: busy inodes on changed media.
-I inserted a CD and:-
[4294853.924000] UDF-fs: No VRS found
[4294854.199000] UDF-fs: No VRS found
[4294854.517000] ISO 9660 Extensions: Microsoft Joliet Level 3
[4294854.579000] ISO 9660 Extensions: RRIP_1991A

It looks like it was taking /dev/hda as the CDROM before, still I don't see a
symlink and still have no idea why this is flooding my dmesg.

It is a LightScribe CDROM in case it matters.

any idea?

Thanks,

> > I have an Compaq V2000 laptop with Ubuntu Dapper Drake, I'm getting flooded 
> > with the messages below: 
> > ON: Linux ubuntu 2.6.15-18-386 #1 PREEMPT Thu Mar 9 14:41:49 UTC 2006 i686 
> > GNU/Linux 
> > /dev/sda: FUJITSU MHV2060BH:
> > 
> > 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.
> > 
> > I already wrote to the Ubuntu ML but had no luck. 
> > 
> > Any idea?
> > 
> > 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
> > 
> > Thanks,
> > 
> > .Alejandro
> > 
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
> -- 
> 1024D/A6D12F80 print D51D 2633 8DAC 04DB 7265  9BB8 5883 6DAA A6D1 2F80
> main(i) { putchar(182623909 >> (i-1) * 5&31|!!(i<7)<<6) && main(++i)
> ; }


--
Open WebMail Project (http://openwebmail.org)


  parent reply	other threads:[~2006-03-20 16:41 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   ` kernel hda errors on dmesg Alejandro Bonilla
2006-03-20 10:48     ` Christian Trefzer
     [not found]     ` <20060320033955.GC18898@eugeneteo.net>
2006-03-20 16:41       ` Alejandro Bonilla [this message]
2006-03-20 19:26         ` kernel hda errors on dmesg - new VFS messages 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=20060320162753.M3577@linuxwireless.org \
    --to=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 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.