From: Andrew Morton <akpm@linux-foundation.org>
To: linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: bugme-daemon@bugzilla.kernel.org, morgoth6@gmail.com
Subject: Re: [Bugme-new] [Bug 9845] New: libata still broken for Pegasos on 2.6.24
Date: Tue, 29 Jan 2008 13:42:14 -0800 [thread overview]
Message-ID: <20080129134214.69b7b5bc.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9845-10286@http.bugzilla.kernel.org/>
On Tue, 29 Jan 2008 12:56:37 -0800 (PST)
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9845
>
> Summary: libata still broken for Pegasos on 2.6.24
> Product: Platform Specific/Hardware
> Version: 2.5
> KernelVersion: 2.6.24
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: PPC-32
> AssignedTo: platform_ppc-32@kernel-bugs.osdl.org
> ReportedBy: morgoth6@gmail.com
>
>
> As 2.6.24 contains fix for pata_via on Pegasos I decide to give a try to this
> version. Unfortunatly it seems it is still broken. Quick look on dmesg from
> faulty boot shows both channels are configured to use IRQ 14 and this is not
> correct in this case.
>
> ....
> ata1: PATA max UDMA/100 cmd 0x1000 ctl 0x100c bmdma 0x1020 irq 14^
> ata2: PATA max UDMA/100 cmd 0x1010 ctl 0x101c bmdma 0x1028 irq 14^
> ....
>
> libata works fine on 2.6.23 when using patch
> https://bugzilla.redhat.com/attachment.cgi?id=167747. Reported also
> https://bugzilla.redhat.com/show_bug.cgi?id=430802
>
Gargh. How does one go from
https://bugzilla.redhat.com/attachment.cgi?id=167747 back to the bug to
which it is attached?
next parent reply other threads:[~2008-01-29 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9845-10286@http.bugzilla.kernel.org/>
2008-01-29 21:42 ` Andrew Morton [this message]
2008-01-29 22:01 ` [Bugme-new] [Bug 9845] New: libata still broken for Pegasos on 2.6.24 Chuck Ebbert
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=20080129134214.69b7b5bc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=morgoth6@gmail.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;
as well as URLs for NNTP newsgroup(s).