From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Peter F. Patel-Schneider" <pfps@verizon.net>
Cc: Tejun Heo <htejun@gmail.com>,
linux-kernel@vger.kernel.org,
"Peter F. Patel-Schneider" <pfps@research.bell-labs.com>
Subject: Re: 2.6.23-rc9-git4: pata_pcmcia, disabling IRQ #9 and Re: libata and legacy ide pcmcia failure
Date: Fri, 21 Mar 2008 11:27:51 +0000 [thread overview]
Message-ID: <20080321112751.15b37f02@core> (raw)
In-Reply-To: <47E39C7A.2090706@verizon.net>
> It is entirely possible that some change triggered a BIOS(?) bug, or
> even that a BIOS upgrade caused the breakage, of course.
Yes, and if your testing shows what I think it will then the bug can
instead become an ACPI bug and maybe Len and the ACPI folks can work
around it.
>
> I'll try to try out the hardware in another Linux box - it may take a
> while, as I have to find out who at work has liberated their machine
> from corporate IT. :-)
Thanks
Alan
next prev parent reply other threads:[~2008-03-21 11:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 18:08 2.6.23-rc9-git4: pata_pcmcia, disabling IRQ #9 Manuel Lauss
2008-03-21 0:26 ` 2.6.23-rc9-git4: pata_pcmcia, disabling IRQ #9 and Re: libata and legacy ide pcmcia failure Peter F. Patel-Schneider
2008-03-21 1:12 ` Alan Cox
2008-03-21 1:38 ` Tejun Heo
2008-03-21 10:40 ` Alan Cox
2008-03-21 11:17 ` Peter F. Patel-Schneider
2008-03-21 11:13 ` Alan Cox
2008-03-21 11:29 ` Peter F. Patel-Schneider
2008-03-21 12:51 ` Reporting ThinkPad BIOS bugs Henrique de Moraes Holschuh
2008-03-21 13:40 ` Peter F. Patel-Schneider
2008-03-21 11:31 ` 2.6.23-rc9-git4: pata_pcmcia, disabling IRQ #9 and Re: libata and legacy ide pcmcia failure Peter F. Patel-Schneider
2008-03-21 11:27 ` Alan Cox [this message]
2008-03-21 2:23 ` Peter F. Patel-Schneider
2008-03-21 10:41 ` Alan Cox
2008-03-26 14:13 ` Peter F. Patel-Schneider
2008-03-26 14:44 ` Tejun Heo
2008-03-26 15:28 ` Peter F. Patel-Schneider
2008-03-29 4:40 ` Tejun Heo
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=20080321112751.15b37f02@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pfps@research.bell-labs.com \
--cc=pfps@verizon.net \
/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.