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

Bug#438814: marked as done (linux-image-2.6.18-3-amd64: invalid opcode: 0000 [1] SMP)

Your message dated Mon, 20 Aug 2007 15:57:56 -0600
with message-id <20070820215755.GD29341@colo.lackof.org>
and subject line Bug#438814: linux-image-2.6.18-3-amd64: invalid opcode: 0000 [1] SMP
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.18-3-amd64
Version: 2.6.18-7
Severity: normal



-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-3-amd64 depends on:
ii  coreutil 5.97-5.3                        The GNU core utilities
ii  debconf  1.5.11                          Debian configuration management sy
ii  e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib
ii  initramf 0.85g                           tools for generating an initramfs
ii  module-i 3.3-pre4-2                      tools for managing Linux kernel mo

linux-image-2.6.18-3-amd64 recommends no packages.

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


----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at fs/ext3/namei.c:383
invalid opcode: 0000 [1] SMP
CPU 1
Modules linked in: nfsd exportfs ppdev parport_pc lp parport button ac battery i pv6 nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_mod sbp2 loop tsdev snd_hd a_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore i2c_i801 snd_page_alloc psmouse eth1394 i2c_core usblp sky2 evdev joydev serio_r aw pcspkr ext3 jbd mbcache raid456 md_mod xor ide_cd cdrom ide_disk sd_mod gener ic ide_core usbhid ohci1394 skge ieee1394 ahci libata scsi_mod ehci_hcd uhci_hcd  thermal processor fan
Pid: 6815, comm: du Not tainted 2.6.18-3-amd64 #1
RIP: 0010:[<ffffffff881a30b2>]  [<ffffffff881a30b2>] :ext3:dx_probe+0x14b/0x2bf
RSP: 0018:ffff810062ac9d28  EFLAGS: 00010292
RAX: 0000000000000081 RBX: ffff81011207f018 RCX: ffffffff8044f868
RDX: ffffffff8044f868 RSI: 0000000000000096 RDI: ffffffff8044f860
RBP: 0000000000000000 R08: ffffffff8044f868 R09: 0000000000000020
R10: 0000000000000046 R11: 0000000000000000 R12: 0000000000000000
R13: ffff8101120618b0 R14: ffff810127fc8730 R15: ffff810062ac9dd4
FS:  00002ad3dcef76d0(0000) GS:ffff81017a888ac0(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000000843b000 CR3: 0000000062a53000 CR4: 00000000000006e0
Process du (pid: 6815, threadinfo ffff810062ac8000, task ffff810079a44100)
Stack:  ffff810062ac9d88 0000000200000000 000000006d4c78d0 ffff81012981c940
 ffff81017145b280 ffff810127fc8730 0000000000000000 ffff81017145b280
 ffff810127fc8730 ffffffff881a444f ffff81012981c968 0000000000018801
Call Trace:
 [<ffffffff881a444f>] :ext3:ext3_htree_fill_tree+0xae/0x1d1
 [<ffffffff80238baf>] filldir64+0x0/0xb8
 [<ffffffff8819ce5a>] :ext3:ext3_readdir+0x1a9/0x4d3
 [<ffffffff80238baf>] filldir64+0x0/0xb8
 [<ffffffff80218d09>] cp_new_stat+0xe7/0xff
 [<ffffffff80238baf>] filldir64+0x0/0xb8
 [<ffffffff80232d0d>] vfs_readdir+0x77/0xa9
 [<ffffffff802c0b9f>] sys_getdents64+0x75/0xba
 [<ffffffff80239673>] sys_fchdir+0x72/0x7e
 [<ffffffff8025860e>] system_call+0x7e/0x83


Code: 0f 0b 68 d2 ee 1a 88 c2 7f 01 48 8b 04 24 48 89 44 24 08 66
RIP  [<ffffffff881a30b2>] :ext3:dx_probe+0x14b/0x2bf
 RSP <ffff810062ac9d28>

--- End Message ---
--- Begin Message --- 
On Mon, Aug 20, 2007 at 07:49:53PM +0200, sioc wrote:
> I ran a fsck.ext3 on the HD...
>
> it found an invalid root i-nod.
>
> The problem is no longer there.
>
> Sorry for the waste of time...

no problem, thanks for following up.

-- 
dann frazier

--- End Message ---
Reply to: