Re: [Bugme-new] [Bug 9845] New: libata still broken for Pegasos on 2.6.24

Re: [Bugme-new] [Bug 9845] New: libata still broken for Pegasos on 2.6.24

[Andrew Morton]

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?

Re: [Bugme-new] [Bug 9845] New: libata still broken for Pegasos on 2.6.24

[Chuck Ebbert]

On 01/29/2008 04:42 PM, Andrew Morton wrote:
> 
> Gargh.  How does one go from
> https://bugzilla.redhat.com/attachment.cgi?id=167747 back to the bug to
> which it is attached?
> 

You can't do that because the attachments are plain text in view mode.

There is a backlink to the bug in edit mode, though:

https://bugzilla.redhat.com/attachment.cgi?id=167747&action=edit