[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#381719: marked as done (Kernel panic enabling IO-APIC IRQs on MacBook Pro)

Your message dated Sun, 26 Jul 2009 18:46:16 +0200
with message-id <20090726164616.GA7114@galadriel.inutil.org>
and subject line Re: Still happening with 2.6.26-8
has caused the Debian Bug report #381719,
regarding Kernel panic enabling IO-APIC IRQs on MacBook Pro
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
381719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=381719
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.16-17

When I boot the installer on my MacBook Pro, it sometimes kernel
panics:

 Getting VERSION: 50014
 Getting VERSION: 50014
 Getting ID: 0
 Getting LVT0: 700
 Getting LVT1: 400
 enabled ExtINT on CPU#0
 ENABLING IO-APIC IRQs
 ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
 ..MP-BIOS bug: 8254 timer not connected to IO-APIC
 ...trying to set up timer (IRQ0) through the 8259A ...  failed.
 ...trying to set up timer as Virtual Wire IRQ... failed.
 ...trying to set up timer as ExtINT IRQ... failed :(.
 Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the 'noapic' option

-- 
Matt

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Sun, Jul 26, 2009 at 08:56:40AM -0700, Matt Kraai wrote:
> On Sun, Jul 26, 2009 at 05:51:09PM +0200, Moritz Muehlenhoff wrote:
> > On Mon, Dec 15, 2008 at 12:02:28AM +0100, Moritz Muehlenhoff wrote:
> > > On Wed, Oct 15, 2008 at 08:54:03AM -0700, Matt Kraai wrote:
> > > > Howdy,
> > > > 
> > > > I'm still experiencing this problem with 2.6.26-8.  Should I report it
> > > > upstream or should I reproduce it with a pristine upstream kernel
> > > > first?
> > > 
> > > Please try to reproduce it with a pristine 2.6.28-rcX kernel. If the
> > > problem persists, please file a bug at bugzilla.kernel.org and pass
> > > it to the bug report.
> > 
> > Did you test this and/or file a bug report upstream?
> 
> I've been running upstream kernels, but I haven't experienced this in
> quite a while, so I haven't reported it upstream.

Marking as closed, then.

Cheers,
        Moritz

--- End Message ---
Reply to: