Your message dated Tue, 21 May 2013 15:02:41 +0100 with message-id <1369144961.3469.184.camel@deadeye.wl.decadent.org.uk> and subject line Re: Bug#709176: base: kernel panic with swapper when interface flaps has caused the Debian Bug report #709176, regarding base: kernel panic with swapper when interface flaps 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.) -- 709176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709176 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: base: kernel panic with swapper when interface flaps
- From: Daniel Petre <daniel.petre@rcs-rds.ro>
- Date: Tue, 21 May 2013 13:28:09 +0300
- Message-id: <20130521102809.23423.52538.reportbug@crunchbang>
Package: base Severity: critical Justification: breaks the whole system Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? debian squeeze box up-to-date but running kernel 3.8.13 with e1000e and tg3 interfaces with few gre tunnels and dual stack. * What exactly did you do (or not do) that was effective (or ineffective)? flapping a intel or broadcom nic will result in kernel panic * What was the outcome of this action? kernel panic with swapper (found by crash inspection on the vmcore) * What outcome did you expect instead? kernel should not be affected by the interface down/up.. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash *** /home/dani/documents/kernel_panic.txt dani@crunchbang:~$ crash-7.0.0/crash s vmlinux vmcore.201305211445 crash> sys KERNEL: vmlinux DUMPFILE: vmcore.201305211445 CPUS: 2 DATE: Tue May 21 14:45:16 2013 UPTIME: 00:31:25 LOAD AVERAGE: 0.00, 0.01, 0.05 TASKS: 105 NODENAME: server RELEASE: 3.8.13 VERSION: #3 SMP Mon May 20 13:09:05 EEST 2013 MACHINE: x86_64 (3000 Mhz) MEMORY: 1 GB PANIC: "Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ffffffff814d5fec" crash> bt PID: 0 TASK: ffff88003e06b8e0 CPU: 1 COMMAND: "swapper/1" #0 [ffff88003fd03798] machine_kexec at ffffffff81027430 #1 [ffff88003fd037e8] crash_kexec at ffffffff8107da80 #2 [ffff88003fd038b8] panic at ffffffff81540026 #3 [ffff88003fd03938] __stack_chk_fail at ffffffff81037f77 #4 [ffff88003fd03948] icmp_send at ffffffff814d5fec #5 [ffff88003fd03b78] dev_hard_start_xmit at ffffffff8146e032 #6 [ffff88003fd03bc8] sch_direct_xmit at ffffffff81487d66 #7 [ffff88003fd03c08] __qdisc_run at ffffffff81487efd #8 [ffff88003fd03c48] dev_queue_xmit at ffffffff8146e5a7 #9 [ffff88003fd03c88] ip_finish_output at ffffffff814ab596 #10 [ffff88003fd03ce8] __netif_receive_skb at ffffffff8146ed13 #11 [ffff88003fd03d88] napi_gro_receive at ffffffff8146fc50 #12 [ffff88003fd03da8] e1000_clean_rx_irq at ffffffff813bc67b #13 [ffff88003fd03e48] e1000e_poll at ffffffff813c3a20 #14 [ffff88003fd03e98] net_rx_action at ffffffff8146f796 #15 [ffff88003fd03ee8] __do_softirq at ffffffff8103ebb9 #16 [ffff88003fd03f38] call_softirq at ffffffff8154444c #17 [ffff88003fd03f50] do_softirq at ffffffff810047dd #18 [ffff88003fd03f80] do_IRQ at ffffffff81003f6c -- <IRQ stack> --- #19 [ffff88003e097e58] ret_from_intr at ffffffff81542c2a [exception RIP: mwait_idle+95] RIP: ffffffff8100ad8f RSP: ffff88003e097f00 RFLAGS: 00000246 RAX: 0000000000000000 RBX: ffffffff8154194e RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff88003e097fd8 RDI: ffff88003fd0d840 RBP: ffffffff8185be80 R8: 0000000000000000 R9: 0000000000000001 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff88003e06b8e0 R14: ffff88003fd11000 R15: ffff88003e06b8e0 ORIG_RAX: ffffffffffffff1e CS: 0010 SS: 0018 #20 [ffff88003e097f00] cpu_idle at ffffffff8100b126 crash>dani@crunchbang:~$ crash-7.0.0/crash s vmlinux vmcore.201305211445 crash> sys KERNEL: vmlinux DUMPFILE: vmcore.201305211445 CPUS: 2 DATE: Tue May 21 14:45:16 2013 UPTIME: 00:31:25 LOAD AVERAGE: 0.00, 0.01, 0.05 TASKS: 105 NODENAME: server RELEASE: 3.8.13 VERSION: #3 SMP Mon May 20 13:09:05 EEST 2013 MACHINE: x86_64 (3000 Mhz) MEMORY: 1 GB PANIC: "Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ffffffff814d5fec" crash> bt PID: 0 TASK: ffff88003e06b8e0 CPU: 1 COMMAND: "swapper/1" #0 [ffff88003fd03798] machine_kexec at ffffffff81027430 #1 [ffff88003fd037e8] crash_kexec at ffffffff8107da80 #2 [ffff88003fd038b8] panic at ffffffff81540026 #3 [ffff88003fd03938] __stack_chk_fail at ffffffff81037f77 #4 [ffff88003fd03948] icmp_send at ffffffff814d5fec #5 [ffff88003fd03b78] dev_hard_start_xmit at ffffffff8146e032 #6 [ffff88003fd03bc8] sch_direct_xmit at ffffffff81487d66 #7 [ffff88003fd03c08] __qdisc_run at ffffffff81487efd #8 [ffff88003fd03c48] dev_queue_xmit at ffffffff8146e5a7 #9 [ffff88003fd03c88] ip_finish_output at ffffffff814ab596 #10 [ffff88003fd03ce8] __netif_receive_skb at ffffffff8146ed13 #11 [ffff88003fd03d88] napi_gro_receive at ffffffff8146fc50 #12 [ffff88003fd03da8] e1000_clean_rx_irq at ffffffff813bc67b #13 [ffff88003fd03e48] e1000e_poll at ffffffff813c3a20 #14 [ffff88003fd03e98] net_rx_action at ffffffff8146f796 #15 [ffff88003fd03ee8] __do_softirq at ffffffff8103ebb9 #16 [ffff88003fd03f38] call_softirq at ffffffff8154444c #17 [ffff88003fd03f50] do_softirq at ffffffff810047dd #18 [ffff88003fd03f80] do_IRQ at ffffffff81003f6c -- <IRQ stack> --- #19 [ffff88003e097e58] ret_from_intr at ffffffff81542c2a [exception RIP: mwait_idle+95] RIP: ffffffff8100ad8f RSP: ffff88003e097f00 RFLAGS: 00000246 RAX: 0000000000000000 RBX: ffffffff8154194e RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff88003e097fd8 RDI: ffff88003fd0d840 RBP: ffffffff8185be80 R8: 0000000000000000 R9: 0000000000000001 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff88003e06b8e0 R14: ffff88003fd11000 R15: ffff88003e06b8e0 ORIG_RAX: ffffffffffffff1e CS: 0010 SS: 0018 #20 [ffff88003e097f00] cpu_idle at ffffffff8100b126 crash>
--- End Message ---
--- Begin Message ---
- To: 709176-done@bugs.debian.org
- Cc: Holger Levsen <holger@layer-acht.org>
- Subject: Re: Bug#709176: base: kernel panic with swapper when interface flaps
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Tue, 21 May 2013 15:02:41 +0100
- Message-id: <1369144961.3469.184.camel@deadeye.wl.decadent.org.uk>
- In-reply-to: <[🔎] 201305211331.17479.holger@layer-acht.org>
- References: <20130521102809.23423.52538.reportbug@crunchbang> <[🔎] 201305211331.17479.holger@layer-acht.org>
On Tue, 2013-05-21 at 13:31 +0200, Holger Levsen wrote: > reassign 709176 src:linux > thanks > > On Dienstag, 21. Mai 2013, Daniel Petre wrote: [...] > > NODENAME: server > > RELEASE: 3.8.13 > > VERSION: #3 SMP Mon May 20 13:09:05 EEST 2013 [...] This is a not a Debian kernel. You need to report the bug upstream on netdev@vger.kernel.org Ben. -- Ben Hutchings friends: People who know you well, but like you anyway.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---