Debian Bug report logs - #381719
Kernel panic enabling IO-APIC IRQs on MacBook Pro

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Matt Kraai <kraai@ftbfs.org>

To: submit@bugs.debian.org

Subject: Kernel panic enabling IO-APIC IRQs on MacBook Pro

Date: Sun, 6 Aug 2006 11:28:18 -0700

[Message part 1 (text/plain, inline)]

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

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 381719@bugs.debian.org (full text, mbox, reply):

From: richard <richard.guenther@gmail.com>

To: Debian Bug Tracking System <381719@bugs.debian.org>

Subject: Still happens regularly with linux-image-2.6.17-2-686

Date: Sat, 02 Sep 2006 14:44:52 +0200

[Message part 1 (text/plain, inline)]

Package: linux-image-2.6.17-2-686
Version: 2.6.17-8
Followup-For: Bug #381719


This still happens _very_ regularly for me on my MacBook Pro,
not only during install.

I attached the bootlog of a _working_ boot.

Richard.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.17-2-686 depends on:
ii  initramfs-tools [linux-initra 0.77b      tools for generating an initramfs
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo

Versions of packages linux-image-2.6.17-2-686 recommends:
ii  libc6-i686                   2.3.6.ds1-4 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/really-run-bootloader-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686:
* linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686:

[kern.log.0 (text/plain, attachment)]

Message #15 received at 381719@bugs.debian.org (full text, mbox, reply):

From: Matt Kraai <kraai@ftbfs.org>

To: 381719@bugs.debian.org

Subject: Fails to boot with noapic on a MacBook Pro

Date: Sat, 28 Jul 2007 09:31:48 -0700

Howdy,

When I try to boot linux-image-2.6.22-1-686 2.6.22-2 with the noapic
option on my MacBook Pro, it fails with the following messages:

> Testing NMI watchdog ... CPU#0: NMI appears to be stuck (0->0)!
> CPU#1: NMI appears to be stuck (0->0)!
> Using IPI No-Shortcut mode
> int3: 0000 [#1]
> Freeing unused memory: 244k freed
> SMP

I haven't been able to reproduce the original problem with this
version.

-- 
Matt

Message #20 received at 381719@bugs.debian.org (full text, mbox, reply):

From: Matt Kraai <kraai@ftbfs.org>

To: 381719@bugs.debian.org

Subject: Found in 2.6.22-5

Date: Thu, 8 Nov 2007 21:40:42 -0800

Howdy,

The problem just occurred again with 2.6.22-5.

-- 
Matt

Message #25 received at 381719@bugs.debian.org (full text, mbox, reply):

From: maximilian attems <max@stro.at>

To: Matt Kraai <kraai@ftbfs.org>, 381719@bugs.debian.org

Subject: Re: Bug#381719: Found in 2.6.22-5

Date: Fri, 9 Nov 2007 10:46:49 +0100

On Thu, Nov 08, 2007 at 09:40:42PM -0800, Matt Kraai wrote:
> Howdy,
> 
> The problem just occurred again with 2.6.22-5.
> 
> -- 
> Matt

trunk snapshots have 2.6.23, already tried? see apt lines
-> http://wiki.debian.org/DebianKernel

if you can still reproduce please bug upstream on
bugzilla.kernel.org

thanks

-- 
maks

Message #30 received at 381719@bugs.debian.org (full text, mbox, reply):

From: Matt Kraai <kraai@ftbfs.org>

To: 381719@bugs.debian.org

Subject: Still happening with 2.6.26-8

Date: Wed, 15 Oct 2008 08:54:03 -0700

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?

-- 
Matt                                                 http://ftbfs.org/

Message #35 received at 381719@bugs.debian.org (full text, mbox, reply):

From: Moritz Muehlenhoff <jmm@inutil.org>

To: Matt Kraai <kraai@ftbfs.org>

Cc: 381719@bugs.debian.org, jmm@debian.org

Subject: Re: Still happening with 2.6.26-8

Date: Mon, 15 Dec 2008 00:02:28 +0100

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.

Cheers,
        Moritz

Message #40 received at 381719@bugs.debian.org (full text, mbox, reply):

From: Moritz Muehlenhoff <jmm@inutil.org>

To: Matt Kraai <kraai@ftbfs.org>

Cc: 381719@bugs.debian.org

Subject: Re: Still happening with 2.6.26-8

Date: Sun, 26 Jul 2009 17:51:09 +0200

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?

Cheers,
        Moritz

Message #45 received at 381719@bugs.debian.org (full text, mbox, reply):

From: Matt Kraai <kraai@ftbfs.org>

To: Moritz Muehlenhoff <jmm@inutil.org>

Cc: 381719@bugs.debian.org

Subject: Re: Still happening with 2.6.26-8

Date: Sun, 26 Jul 2009 08:56:40 -0700

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.

-- 
Matt Kraai                                           http://ftbfs.org/

Message #50 received at 381719-done@bugs.debian.org (full text, mbox, reply):

From: Moritz Muehlenhoff <jmm@inutil.org>

To: Matt Kraai <kraai@ftbfs.org>

Cc: 381719-done@bugs.debian.org

Subject: Re: Still happening with 2.6.26-8

Date: Sun, 26 Jul 2009 18:46:16 +0200

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

Send a report that this bug log contains spam.