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

Bug#376229: marked as done (linux-image-2.6.17-1-k7: Intermittent panic during boot)

Your message dated Mon, 15 Jan 2007 14:01:34 +0100
with message-id <20070115130134.GU26700@baikonur.stro.at>
and subject line Bug#376229: linux-image-2.6.17-1-k7: Another BUG invalid opcode
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.17-1-k7
Version: 2.6.17-1
Severity: important

While booting this kernel, I've sometimes seen a panic early in the boot.  The
screen didn't scroll back up so this is all I can grab:

invalid opcode: 0000 [#1]
Modules linked in: ext3 jbd mbcache 8139too ide_cd cdrom ide_disk 8139cp mii
	ehci_hcd usbcore via82cxxx generic ide_core thermal processor fan
	libata scsi_mod

CPU: 0
EIP: 0060:[<b0123f3d>] Not tainted VLI
EFLAGS: 00010292 (2.6.17-1-k7 #1)
EIP is at run_timer_softirq+0x11e/0x151
eax: 0000004c ebx: eff2e000 ecx: ffffffff edx: ffffd018
esi: 20000100 edi: b0345cc0 ebp: b020d1bc esp: eff2ff74
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 3198, threadinfo=eff2e000 task=dfd8b0b0)
Stack:  b028875b b020d1bc 20000100 00000100 eff2ff84 eff2ff84 00000011 b2cf8088
	0000000a 00000000 b012071e 00000046 00000000 0804f098 afd52f78 b01207b6
	00000073 b010362c 00000073 00000073 00000035 00000000 0804f098 afd52f78
Call Trace:
	<b020d1bc> i8042_timer_func+0x0/0xb  <b012071e> __do_softirq+0x58/0xc2
	<b01207b6> do_softirq+0x2e/0x32      <b0103b2c> apic_timer_interrupt+0x1c/0x24
Code: 00 c7 03 00 00 00 00 c6 07 01 fb bb 00 e0 ff ff 21 e3 8b 73 14 ff d5 3b
  73 14 74 14 ff 73 14 56 55 68 5d 87 28 b0 e8 dd 8b ff ff <0f> 0b 83 c4 10 89 f8 e8
  7d fa 14 00 8b 1c 24 39 e3 75 a9 a1 80
EIP: [<b0123f3d>] run_timer_softirq+0x11e/0x151 SS:ESP 0068:eff2ff74
<0> Kernel panic - not syncing: Fatal exception in interrupt

I also sometimes have trouble with this kernel and udev in creating
/dev/input/mice.  Without this, X doesn't work.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.17-1-k7 depends on:
ii  initramfs-tools [linux-initra 0.60       tools for generating an initramfs
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-14  Yet Another mkInitRD

Versions of packages linux-image-2.6.17-1-k7 recommends:
ii  libc6-i686                    2.3.6-15   GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.17-1-k7/prerm/removing-running-kernel-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/preinst/bootloader-initrd-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/postinst/old-dir-initrd-link-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/postinst/depmod-error-initrd-2.6.17-1-k7: false
  linux-image-2.6.17-1-k7/postinst/old-initrd-link-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/postinst/create-kimage-link-2.6.17-1-k7: true
* linux-image-2.6.17-1-k7/preinst/already-running-this-2.6.17-1-k7:
  linux-image-2.6.17-1-k7/preinst/elilo-initrd-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/preinst/overwriting-modules-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/postinst/old-system-map-link-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/prerm/would-invalidate-boot-loader-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/preinst/lilo-initrd-2.6.17-1-k7: true
  linux-image-2.6.17-1-k7/postinst/depmod-error-2.6.17-1-k7: false

--- End Message ---
--- Begin Message ---
On Fri, Jan 12, 2007 at 07:06:12PM -0500, Jerry Quinn wrote:
> It appeared that this problem was actually stemming from overheating.  
> 2.6.17 was more susceptible.  I've since fixed the temperature problem and 
> it now works fine.

ok thanks thus closing.


--- End Message ---

Reply to: