From: Jan Sembera <fis@bofh.cz>
To: linux-ide@vger.kernel.org
Cc: mjg@redhat.com, holger@homac.de, ming.m.lin@intel.com,
1126766@bugs.launchpad.net
Subject: Re: Regression between v3.5 and v3.6 in libata
Date: Tue, 26 Feb 2013 23:07:02 +0100 [thread overview]
Message-ID: <20130226220702.GC25087@abydos.bofh.cz> (raw)
In-Reply-To: <20130226200348.GA25087@abydos.bofh.cz>
So I apparently missed two most important differences between good and bad
boots.
On Tue, Feb 26, 2013 at 09:03:48PM +0100, Jan Sembera wrote:
> [ 2.877438] scsi6 : pata_atiixp
> [ 2.881369] scsi7 : pata_atiixp
>
> [ 2.391535] scsi6 : pata_acpi
> [ 2.391994] scsi7 : pata_acpi
pata-acpi doesn't play very well with this controller. Disabling it in
kernel and rebooting (even with 3.8) provided completely working kernel.
So either this driver shouldn't bind pata-acpi and leave it on pata-atiixp
as before (some kind of blacklisting needed?), or it needs some fixing to
work nicely with this controller.
As a workaround for now, I'll just not compile PATA_ACPI into the kernel.
00:14.1 IDE interface: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 IDE Controller (rev 40) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. Device 8496
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at f100 [size=16]
Kernel driver in use: pata_atiixp
next prev parent reply other threads:[~2013-02-26 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 20:03 Regression between v3.5 and v3.6 in libata Jan Sembera
2013-02-26 22:07 ` Jan Sembera [this message]
2013-02-27 6:36 ` Robert Hancock
2013-02-27 9:38 ` Jan Sembera
2013-02-27 12:42 ` Aaron Lu
2013-02-27 14:25 ` Jan Sembera
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=20130226220702.GC25087@abydos.bofh.cz \
--to=fis@bofh.cz \
--cc=1126766@bugs.launchpad.net \
--cc=holger@homac.de \
--cc=linux-ide@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mjg@redhat.com \
/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