linux-kernel - Re: 2.6.19-git3 panics on boot - ata_piix/PCI related [still in -git17]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <5a4c581d0612110526j26a07b31q26edc075d4981cd8@mail.gmail.com>
Date:	Mon, 11 Dec 2006 14:26:30 +0100
From:	"Alessandro Suardi" <alessandro.suardi@...il.com>
To:	Alan <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19-git3 panics on boot - ata_piix/PCI related [still in -git17]

On 12/3/06, Alessandro Suardi <alessandro.suardi@...il.com> wrote:
> On 12/3/06, Alan <alan@...rguk.ukuu.org.uk> wrote:
> > > > ACPI: PCI Interrupt 0000:00:1f.2[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ5
> > > > PCI: Unable to reserve I/O region #1:8@1f0 for device 0000:00:1f.2
> > > > ata_piix: probe of 0000:00:1f.2 failed with error -16
> > > > [snip]
> > > > mount: could not find filesystem '/dev/root'
> > >
> > > Same failure is also in 2.6.19-git4...
> >
> > Thats the PCI updates - you need the matching fix to libata-sff where it
> > tries to reserve stuff it shouldn't.
>
> Thanks Alan. Indeed -git1 is where stuff breaks for me.
> I'll watch out for when libata-sff gets fixed in the -git
>  snapshots and will then report back.

Alan,

  I still have this problem in 2.6.19-git17. Is this expected behavior
  or should it have been fixed by now ?

Thanks,

--alessandro

"...when I get it, I _get_ it"

     (Lara Eidemiller)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/