From: Jeff Garzik <jeff@garzik.org>
To: Fabio Comolli <fabio.comolli@gmail.com>, Alan <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: [git patches] libata (and devres) fixes
Date: Fri, 09 Mar 2007 16:43:04 -0500 [thread overview]
Message-ID: <45F1D4E8.3030400@garzik.org> (raw)
In-Reply-To: <b637ec0b0703091324q7f15fddbpc8c24b4e1131e3f4@mail.gmail.com>
Fabio Comolli wrote:
> Hi.
> This update gives a new warning:
>
> libata version 2.20 loaded.
> ata_piix 0000:00:1f.1: version 2.10ac1
> ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x000118c0
> irq 14
> ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x000118c8
> irq 15
> scsi0 : ata_piix
> ata1.00: ATA-6: TOSHIBA MK8025GAS, KA024A, max UDMA/100
> ata1.00: 156301488 sectors, multi 16: LBA
> ata1.01: ATAPI, max MWDMA2
> ata1.00: configured for UDMA/33
> ata1.01: configured for MWDMA2
> scsi1 : ata_piix
> ata2: port disabled. ignoring.
> ata2: reset failed, giving up <--- THIS IS NEW.
>
> However, I think it's just bogus as there is ata2 is disabled on this
> laptop.
That looks like Alan's patch to ata_piix.
Jeff
next prev parent reply other threads:[~2007-03-09 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 16:31 [git patches] libata (and devres) fixes Jeff Garzik
2007-03-09 21:24 ` Fabio Comolli
2007-03-09 21:43 ` Jeff Garzik [this message]
2007-03-09 23:48 ` Alan Cox
2007-03-10 15:28 ` Fabio Comolli
2007-03-12 8:24 ` [PATCH] libata: don't whine if ->prereset() returns -ENOENT Tejun Heo
2007-03-12 12:10 ` Alan Cox
2007-03-12 20:14 ` Fabio Comolli
2007-03-19 16:03 ` Jeff Garzik
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=45F1D4E8.3030400@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fabio.comolli@gmail.com \
--cc=greg@kroah.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.