Your message dated Wed, 3 Dec 2008 23:07:46 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#387460: linux-image-2.6.17-2-686: kernel panic when
trying to add vlan to a slave bonded interface
has caused the Debian Bug report #387460,
regarding linux-image-2.6.17-2-686: kernel panic when trying to add vlan to a
slave bonded interface
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 [EMAIL PROTECTED]
immediately.)
--
387460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387460
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-image-2.6.17-2-686
Version: 2.6.17-8
Severity: important
Hello,
I managed to get a kernel panic when I tried to add a vlan to one of the
slave interfaces in a bond. :-(
With hindsight I probably shouldn't have tried it, but crashes are bad,
so reporting it now.
Snip from /var/log/kern.log
---
Sep 14 14:37:20 dxsfw-dc01 kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address 00000148
Sep 14 14:37:20 dxsfw-dc01 kernel: printing eip:
Sep 14 14:37:20 dxsfw-dc01 kernel: f0a6d75d
Sep 14 14:37:20 dxsfw-dc01 kernel: *pde = 00000000
Sep 14 14:37:20 dxsfw-dc01 kernel: Oops: 0000 [#1]
Sep 14 14:37:20 dxsfw-dc01 kernel: SMP
Sep 14 14:37:20 dxsfw-dc01 kernel: Modules linked in: button ac battery
dm_snapshot dm_mirror 8021q bonding ide_disk ide_cd cdrom mousedev tsdev evdev
psmouse hw_random 8250_pnp serio_raw pcspkr usbhid ehci_hcd uhci_hcd e1000 tg3
usbcore thermal processor fan mptsas mptscsih mptbase scsi_transport_sas dm_mod
sd_mod shpchp pci_hotplug piix ata_piix libata scsi_mod ide_generic ide_core
raid1 raid0 md_mod ext3 jbd mbcache
Sep 14 14:37:20 dxsfw-dc01 kernel: CPU: 1
Sep 14 14:37:20 dxsfw-dc01 kernel: EIP: 0060:[<f0a6d75d>] Not tainted VLI
Sep 14 14:37:20 dxsfw-dc01 kernel: EFLAGS: 00210297 (2.6.17-2-686 #1)
Sep 14 14:37:20 dxsfw-dc01 kernel: EIP is at bond_netdev_event+0x67/0x8b
[bonding]
Sep 14 14:37:20 dxsfw-dc01 kernel: eax: 00000000 ebx: f0a7bfc0 ecx:
b1aa2000 edx: 00000005
Sep 14 14:37:20 dxsfw-dc01 kernel: esi: b1aa2000 edi: 00000005 ebp:
b0369b80 esp: ee997ec0
Sep 14 14:37:20 dxsfw-dc01 kernel: ds: 007b es: 007b ss: 0068
Sep 14 14:37:20 dxsfw-dc01 kernel: Process vconfig (pid: 5201,
threadinfo=ee996000 task=dffb6580)
Sep 14 14:37:20 dxsfw-dc01 kernel: Stack: f0a7bfc0 b1aa2000 b0126d43 b1aa2000
00000000 b0369ebc b021bd52 00000001
Sep 14 14:37:20 dxsfw-dc01 kernel: 00000001 b1aa2000 ef47a0de b1aa20de
ef47a000 f09f6636 b013d1b4 0000002c
Sep 14 14:37:20 dxsfw-dc01 kernel: 00000000 31687465 00000000 00000000
00000000 00000000 00000000 0000002c
Sep 14 14:37:20 dxsfw-dc01 kernel: Call Trace:
Sep 14 14:37:20 dxsfw-dc01 kernel: <b0126d43> notifier_call_chain+0x15/0x2e
<b021bd52> register_netdevice+0x2a6/0x2af
Sep 14 14:37:20 dxsfw-dc01 kernel: <f09f6636> vlan_ioctl_handler+0x349/0x553
[8021q] <b013d1b4> filemap_nopage+0x194/0x2f0
Sep 14 14:37:20 dxsfw-dc01 kernel: <b0214056> sock_ioctl+0x13f/0x1b5
<b0213f17> sock_ioctl+0x0/0x1b5
Sep 14 14:37:20 dxsfw-dc01 kernel: <b0161e24> do_ioctl+0x1c/0x5d <b01620af>
vfs_ioctl+0x24a/0x25c
Sep 14 14:37:20 dxsfw-dc01 kernel: <b0162109> sys_ioctl+0x48/0x5f <b0102ae7>
sysenter_past_esp+0x54/0x75
Sep 14 14:37:20 dxsfw-dc01 kernel: Code: f0 e8 ec 4c 00 00 89 f0 e8 16 57 00 00
89 d8 ba ff ff 00 00 f0 0f c1 10 0f 85 d9 14 00 00 eb 2a f6 c4 08 74 25 8b 41
70 83 fa 06 <8b> 98 48 01 00 00 74 07 83 fa 0b 75 12 eb 09 89 ca e8 b9 fc ff
Sep 14 14:37:20 dxsfw-dc01 kernel: EIP: [<f0a6d75d>]
bond_netdev_event+0x67/0x8b [bonding] SS:ESP 0068:ee997ec0
---
HTH,
George B.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages linux-image-2.6.17-2-686 depends on:
ii initramfs-tools [linux-initra 0.78 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/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/preinst/abort-install-2.6.17-2-686:
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/overwriting-modules-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/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/preinst/bootloader-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:
linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686:
--- End Message ---
--- Begin Message ---
Version: 2.6.26-10
On Wed, Dec 03, 2008 at 09:45:08AM +0000, George B. wrote:
> 2008/11/29 Moritz Muehlenhoff <[EMAIL PROTECTED]>:
> > George, did you report that bug upstream?
>
> Hi Mortiz,
>
> I don't think I submitted a bug upstream (I think I may have had some
> problems, but I can't remember now). Since then, I've changed jobs
> twice, so I no longer have access to that hardware.
>
> I tried reproducing the problem on a Lenny VirtualBox VM, but could
> not. Feel free to close this bug - I'll re-open it if I manage to
> reproduce it (I should have some spare real servers available for that
> in our lab at some point in future).
Ok, closing it with the current Lenny kernel version, please reopen
if you manage to reproduce again.
Cheers,
Moritz
--- End Message ---
