From: Albert Lee <albertcc@tw.ibm.com>
To: bruss@alum.wpi.edu
Cc: Jeff Garzik <jgarzik@pobox.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Doug Maxey <dwm@maxeymade.com>,
Linux IDE <linux-ide@vger.kernel.org>
Subject: Re: [PATCH libata-dev-2.6 1/2] ata_dev_identify() check status fix
Date: Fri, 01 Apr 2005 15:25:37 +0800 [thread overview]
Message-ID: <424CF771.60508@tw.ibm.com> (raw)
In-Reply-To: <424CE1B4.10107@gmail.com>
Brett Russ wrote:
> Albert Lee wrote:
>
>> - printk(KERN_WARNING "ata%u: PIO error, drv_stat 0x%x\n",
>> - ap->id, drv_stat);
>> + DPRINTK("ata%u: PIO error, drv_stat 0x%x\n", ap->id, drv_stat);
>
>
> You'd probably want this to stay a printk so it persists when ATA_DEBUG
> is off, right?
>
> BR
Hi Brett,
The problem is ata_pio_error() doesn't know whether the error condition is normal or not.
Only the caller that issued the command knows what's going on.
Please see the attached dmesg for an example.
If we print out error message each time ata_pio_error() is called, it might be too noisy.
Albert
============================================================================================================
Mar 31 18:57:28 linux kernel: libata version 1.10 loaded.
Mar 31 18:57:28 linux kernel: pata_pdc2027x version 0.58
Mar 31 18:57:28 linux kernel: pata_pdc2027x: PLL input clock 65552 kHz
Mar 31 18:57:28 linux kernel: ata1: PATA max UDMA/133 cmd 0xDE400 ctl 0xDDC02 bmdma 0xDEC00 irq 134
Mar 31 18:57:28 linux kernel: ata2: PATA max UDMA/133 cmd 0xDE800 ctl 0xDE002 bmdma 0xDEC08 irq 134
Mar 31 18:57:28 linux kernel: ata1: dev 0 cfg 49:0f00 82:4210 83:4000 84:4000 85:0000 86:0000 87:0000 88:0407
Mar 31 18:57:28 linux kernel: ata1: dev 0 ATAPI, max UDMA/33
Mar 31 18:57:29 linux kernel: ata1: PIO error, drv_stat 0x0 <== We have single master (dev 0) configuration here.
<== The error was caused by phantom slave device. (please ref ATA-4 9.16.1 and 8.9.5)
<== It is normal and the end users should not see this as error.
Mar 31 18:57:29 linux kernel: ata1: dev 0 configured for UDMA/33
Mar 31 18:57:29 linux kernel: scsi11 : pata_pdc2027x
Mar 31 18:57:29 linux kernel: ATA: abnormal status 0x8 on port 0xDE807
Mar 31 18:57:29 linux kernel: ata2: disabling port
Mar 31 18:57:29 linux kernel: scsi12 : pata_pdc2027x
Mar 31 18:57:29 linux kernel: Vendor: IBM Model: CD-RW 1234 Rev: 123
Mar 31 18:57:29 linux kernel: Type: CD-ROM ANSI SCSI revision: 05
Mar 31 18:57:29 linux kernel: Attached scsi generic sg3 at scsi11, channel 0, id 0, lun 0, type 5
Mar 31 18:57:29 linux /etc/hotplug/scsi_generic.agent[22556]: cd: can't cd to /sys/class/scsi_generic/sg3/device/block
Mar 31 18:57:29 linux kernel: sr0: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray
Mar 31 18:57:29 linux kernel: Attached scsi CD-ROM sr0 at scsi11, channel 0, id 0, lun 0
Mar 31 18:57:29 linux /etc/hotplug/block.agent[22638]: new block device /block/sr0
next prev parent reply other threads:[~2005-04-01 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 5:46 [PATCH libata-dev-2.6 1/2] ata_dev_identify() check status fix Albert Lee
2005-04-01 5:52 ` Brett Russ
2005-04-01 7:25 ` Albert Lee [this message]
2005-04-02 15:55 ` Albert Lee
2005-05-15 23:13 ` Jeff Garzik
2005-05-16 6:35 ` Albert Lee
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=424CF771.60508@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=bruss@alum.wpi.edu \
--cc=bzolnier@gmail.com \
--cc=dwm@maxeymade.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).