On Tue, Apr 06, 2010 at 05:38:15AM +0100, Ben Hutchings wrote:
> On Sat, 2010-02-27 at 22:32 +0000, Ben Hutchings wrote:
> > On Sat, 2010-02-27 at 20:21 +0000, David Goodenough wrote:
> > > Package: linux-2.6
> > > Version: 2.6.32-8
> > > Severity: important
> > >
> > >
> > > With kernels up to 2.6.26 this ancient machine did not require any
> > > special kernel boot options, but with 2.6.32
> > > I need to add noapic to the kernel command in grub.
> > >
> > > If I do not add noapic the kernel gets as far as the pcmcia socket and
> > > gets through that completely, and then hangs
> > > competely - nothing works.
> > >
> > > Looking in the 2.6.26 kernel dmesg just after the initialisation of the
> > > pcmcia socket there were messages about
> > > ACPI derived interrupts. So I thought trying noapic was worth trying
> > > noapic, and now 2.6.32 boots normally.
> >
> > ACPI and APIC are two entirely different technologies, although they are
> > both involved in interrupt routing.
> >
> > > This suggests that something has changed in the APIC handling for the old
> > > chip in the 430, for the worse. Of course
> > > now manual intervention is required to make this machine boot.
> >
> > Please report this upstream at <http://bugzilla.debian.org> under
> > product 'Platform Specific/Hardware', component 'i386'. Attach the
> > kernel logs for 2.6.32 with and without 'noapic' to the bug report.
>
> Sorry, I don't know how I came up with that URL... please use the bug
> tracker at <https://bugzilla.kernel.org>! Then, let us know the bug
> number so we can track it.
David, did you report this upstream?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
