Ubuntu
linux package

Kernel Panic during system startup

Bug #968675 reported by misko
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Since the update to 3.0.0-17-generic my notebook sometimes crashes when booting up.

My system is an Acer Travelmate 8481TG.

The file linux-image-3.0.0-17-generic.0.crash is attached, the "bt -a" produced by "crash" is:

PID: 0 TASK: ffffffff81c0b020 CPU: 0 COMMAND: "swapper"
 #0 [ffff88023fa03a50] machine_kexec at ffffffff8102de18
 #1 [ffff88023fa03ad0] crash_kexec at ffffffff810aa142
 #2 [ffff88023fa03ba0] oops_end at ffffffff815f4358
 #3 [ffff88023fa03bd0] no_context at ffffffff815dbacf
 #4 [ffff88023fa03c10] __bad_area_nosemaphore at ffffffff815dbc6a
 #5 [ffff88023fa03c60] bad_area_nosemaphore at ffffffff815dbca0
 #6 [ffff88023fa03c70] do_page_fault at ffffffff815f6c7d
 #7 [ffff88023fa03d80] page_fault at ffffffff815f3695
    [exception RIP: azx_update_rirb+100]
    RIP: ffffffffa0fc54f4 RSP: ffff88023fa03e38 RFLAGS: 00010002
    RAX: 0000000000000002 RBX: ffff88020d867c00 RCX: 0000000000000000
    RDX: 0000000000000003 RSI: ffff88020d867c00 RDI: ffff88020d867c00
    RBP: ffff88023fa03e58 R8: ffff88022e662700 R9: ffff88023ec000a0
    R10: 0000000000000cf3 R11: 0000000000000400 R12: 00000000000000ff
    R13: 0000000000000000 R14: 00000000ffffffff R15: ffff88020d867c44
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
 #8 [ffff88023fa03e60] azx_interrupt at ffffffffa0fc60c7 [snd_hda_intel]
 #9 [ffff88023fa03eb0] handle_irq_event_percpu at ffffffff810cde75
#10 [ffff88023fa03f10] handle_irq_event at ffffffff810ce08e
#11 [ffff88023fa03f40] handle_fasteoi_irq at ffffffff810d0854
#12 [ffff88023fa03f60] handle_irq at ffffffff8100c252
#13 [ffff88023fa03f80] do_IRQ at ffffffff815fcdaa
--- <IRQ stack> ---
#14 [ffffffff81c01d80] ret_from_intr at ffffffff815f33d3
    RIP: ffffffffffffff76 RSP: 0000000000000202 RFLAGS: 00000010
    RAX: 00000000fffffffb RBX: ffffffff81c01e88 RCX: 0000000000000000
    RDX: 0000000000000000 RSI: 0000000000000c94 RDI: 0000000000000000
    RBP: ffffffff815f33ce R8: 0000000000000e3b R9: 0000000000000cf3
    R10: 0000000000000400 R11: ffffffff81032a79 R12: ffffffff81c01e48
    R13: ffffffff81012e51 R14: ffff88023fa0ebc0 R15: ffffffff8104c9ae
    ORIG_RAX: 00000000003124ad CS: ffffffff8134b29b SS: ffffffff81c01e38
bt: WARNING: possibly bogus exception frame

PID: 0 TASK: ffff880232c48000 CPU: 1 COMMAND: "kworker/0:0"
 #0 [ffff88023fa47e70] crash_nmi_callback at ffffffff81026268
 #1 [ffff88023fa47e80] notifier_call_chain at ffffffff815f6dbd
 #2 [ffff88023fa47ec0] atomic_notifier_call_chain at ffffffff815f6e1a
 #3 [ffff88023fa47ed0] notify_die at ffffffff815f6e4e
 #4 [ffff88023fa47f00] default_do_nmi at ffffffff815f3b19
 #5 [ffff88023fa47f30] do_nmi at ffffffff815f3ed0
 #6 [ffff88023fa47f50] nmi at ffffffff815f3950
    [exception RIP: intel_idle+157]
    RIP: ffffffff8134b26d RSP: ffff880232c51e58 RFLAGS: 00000046
    RAX: 0000000000000030 RBX: 0000000000000010 RCX: 0000000000000001
    RDX: 0000000000000000 RSI: ffff880232c51fd8 RDI: ffffffff81c0ea00
    RBP: ffff880232c51ea8 R8: 00000000fffffffb R9: 0000000000000f9b
    R10: 0000000000001a87 R11: 0000000000000001 R12: 0000000000000030
    R13: 127feead05305e7c R14: 0000000000000001 R15: 0000000000000000
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
--- <NMI exception stack> ---
 #7 [ffff880232c51e58] intel_idle at ffffffff8134b26d
 #8 [ffff880232c51eb0] cpuidle_idle_call at ffffffff814b387d
 #9 [ffff880232c51f00] cpu_idle at ffffffff8100920b

PID: 0 TASK: ffff880232c4dc80 CPU: 2 COMMAND: "kworker/0:1"
 #0 [ffff88023fa87e70] crash_nmi_callback at ffffffff81026268
 #1 [ffff88023fa87e80] notifier_call_chain at ffffffff815f6dbd
 #2 [ffff88023fa87ec0] atomic_notifier_call_chain at ffffffff815f6e1a
 #3 [ffff88023fa87ed0] notify_die at ffffffff815f6e4e
 #4 [ffff88023fa87f00] default_do_nmi at ffffffff815f3b19
 #5 [ffff88023fa87f30] do_nmi at ffffffff815f3ed0
 #6 [ffff88023fa87f50] nmi at ffffffff815f3950
    [exception RIP: intel_idle+157]
    RIP: ffffffff8134b26d RSP: ffff880232c61e58 RFLAGS: 00000046
    RAX: 0000000000000030 RBX: 0000000000000010 RCX: 0000000000000001
    RDX: 0000000000000000 RSI: ffff880232c61fd8 RDI: ffffffff81c0ea00
    RBP: ffff880232c61ea8 R8: 00000000fffffffb R9: 0000000000000f9a
    R10: 00000000000019cb R11: 0000000000000001 R12: 0000000000000030
    R13: 127feead05306b65 R14: 0000000000000002 R15: 0000000000000000
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
--- <NMI exception stack> ---
 #7 [ffff880232c61e58] intel_idle at ffffffff8134b26d
 #8 [ffff880232c61eb0] cpuidle_idle_call at ffffffff814b387d
 #9 [ffff880232c61f00] cpu_idle at ffffffff8100920b

PID: 0 TASK: ffff880232c6c560 CPU: 3 COMMAND: "kworker/0:1"
 #0 [ffff88023fac7e70] crash_nmi_callback at ffffffff81026268
 #1 [ffff88023fac7e80] notifier_call_chain at ffffffff815f6dbd
 #2 [ffff88023fac7ec0] atomic_notifier_call_chain at ffffffff815f6e1a
 #3 [ffff88023fac7ed0] notify_die at ffffffff815f6e4e
 #4 [ffff88023fac7f00] default_do_nmi at ffffffff815f3b19
 #5 [ffff88023fac7f30] do_nmi at ffffffff815f3ed0
 #6 [ffff88023fac7f50] nmi at ffffffff815f3950
    [exception RIP: intel_idle+157]
    RIP: ffffffff8134b26d RSP: ffff880232c7de58 RFLAGS: 00000046
    RAX: 0000000000000030 RBX: 0000000000000010 RCX: 0000000000000001
    RDX: 0000000000000000 RSI: ffff880232c7dfd8 RDI: ffffffff81c0ea00
    RBP: ffff880232c7dea8 R8: 00000000fffffffb R9: 0000000000000f8f
    R10: 0000000000001ae2 R11: 0000000000000001 R12: 0000000000000030
    R13: 127feead05307394 R14: 0000000000000003 R15: 0000000000000000
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
--- <NMI exception stack> ---
 #7 [ffff880232c7de58] intel_idle at ffffffff8134b26d
 #8 [ffff880232c7deb0] cpuidle_idle_call at ffffffff814b387d
 #9 [ffff880232c7df00] cpu_idle at ffffffff8100920b

Please let me know if further info is needed.

/proc/version_signature is:

PID: 0 TASK: ffffffff81c0b020 CPU: 0 COMMAND: "swapper"
 #0 [ffff88023fa03a50] machine_kexec at ffffffff8102de18
 #1 [ffff88023fa03ad0] crash_kexec at ffffffff810aa142
 #2 [ffff88023fa03ba0] oops_end at ffffffff815f4358
 #3 [ffff88023fa03bd0] no_context at ffffffff815dbacf
 #4 [ffff88023fa03c10] __bad_area_nosemaphore at ffffffff815dbc6a
 #5 [ffff88023fa03c60] bad_area_nosemaphore at ffffffff815dbca0
 #6 [ffff88023fa03c70] do_page_fault at ffffffff815f6c7d
 #7 [ffff88023fa03d80] page_fault at ffffffff815f3695
    [exception RIP: azx_update_rirb+100]
    RIP: ffffffffa0fc54f4 RSP: ffff88023fa03e38 RFLAGS: 00010002
    RAX: 0000000000000002 RBX: ffff88020d867c00 RCX: 0000000000000000
    RDX: 0000000000000003 RSI: ffff88020d867c00 RDI: ffff88020d867c00
    RBP: ffff88023fa03e58 R8: ffff88022e662700 R9: ffff88023ec000a0
    R10: 0000000000000cf3 R11: 0000000000000400 R12: 00000000000000ff
    R13: 0000000000000000 R14: 00000000ffffffff R15: ffff88020d867c44
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
 #8 [ffff88023fa03e60] azx_interrupt at ffffffffa0fc60c7 [snd_hda_intel]
 #9 [ffff88023fa03eb0] handle_irq_event_percpu at ffffffff810cde75
#10 [ffff88023fa03f10] handle_irq_event at ffffffff810ce08e
#11 [ffff88023fa03f40] handle_fasteoi_irq at ffffffff810d0854
#12 [ffff88023fa03f60] handle_irq at ffffffff8100c252
#13 [ffff88023fa03f80] do_IRQ at ffffffff815fcdaa
--- <IRQ stack> ---
#14 [ffffffff81c01d80] ret_from_intr at ffffffff815f33d3
    RIP: ffffffffffffff76 RSP: 0000000000000202 RFLAGS: 00000010
    RAX: 00000000fffffffb RBX: ffffffff81c01e88 RCX: 0000000000000000
    RDX: 0000000000000000 RSI: 0000000000000c94 RDI: 0000000000000000
    RBP: ffffffff815f33ce R8: 0000000000000e3b R9: 0000000000000cf3
    R10: 0000000000000400 R11: ffffffff81032a79 R12: ffffffff81c01e48
    R13: ffffffff81012e51 R14: ffff88023fa0ebc0 R15: ffffffff8104c9ae
    ORIG_RAX: 00000000003124ad CS: ffffffff8134b29b SS: ffffffff81c01e38
bt: WARNING: possibly bogus exception frame

PID: 0 TASK: ffff880232c48000 CPU: 1 COMMAND: "kworker/0:0"
 #0 [ffff88023fa47e70] crash_nmi_callback at ffffffff81026268
 #1 [ffff88023fa47e80] notifier_call_chain at ffffffff815f6dbd
 #2 [ffff88023fa47ec0] atomic_notifier_call_chain at ffffffff815f6e1a
 #3 [ffff88023fa47ed0] notify_die at ffffffff815f6e4e
 #4 [ffff88023fa47f00] default_do_nmi at ffffffff815f3b19
 #5 [ffff88023fa47f30] do_nmi at ffffffff815f3ed0
 #6 [ffff88023fa47f50] nmi at ffffffff815f3950
    [exception RIP: intel_idle+157]
    RIP: ffffffff8134b26d RSP: ffff880232c51e58 RFLAGS: 00000046
    RAX: 0000000000000030 RBX: 0000000000000010 RCX: 0000000000000001
    RDX: 0000000000000000 RSI: ffff880232c51fd8 RDI: ffffffff81c0ea00
    RBP: ffff880232c51ea8 R8: 00000000fffffffb R9: 0000000000000f9b
    R10: 0000000000001a87 R11: 0000000000000001 R12: 0000000000000030
    R13: 127feead05305e7c R14: 0000000000000001 R15: 0000000000000000
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
--- <NMI exception stack> ---
 #7 [ffff880232c51e58] intel_idle at ffffffff8134b26d
 #8 [ffff880232c51eb0] cpuidle_idle_call at ffffffff814b387d
 #9 [ffff880232c51f00] cpu_idle at ffffffff8100920b

PID: 0 TASK: ffff880232c4dc80 CPU: 2 COMMAND: "kworker/0:1"
 #0 [ffff88023fa87e70] crash_nmi_callback at ffffffff81026268
 #1 [ffff88023fa87e80] notifier_call_chain at ffffffff815f6dbd
 #2 [ffff88023fa87ec0] atomic_notifier_call_chain at ffffffff815f6e1a
 #3 [ffff88023fa87ed0] notify_die at ffffffff815f6e4e
 #4 [ffff88023fa87f00] default_do_nmi at ffffffff815f3b19
 #5 [ffff88023fa87f30] do_nmi at ffffffff815f3ed0
 #6 [ffff88023fa87f50] nmi at ffffffff815f3950
    [exception RIP: intel_idle+157]
    RIP: ffffffff8134b26d RSP: ffff880232c61e58 RFLAGS: 00000046
    RAX: 0000000000000030 RBX: 0000000000000010 RCX: 0000000000000001
    RDX: 0000000000000000 RSI: ffff880232c61fd8 RDI: ffffffff81c0ea00
    RBP: ffff880232c61ea8 R8: 00000000fffffffb R9: 0000000000000f9a
    R10: 00000000000019cb R11: 0000000000000001 R12: 0000000000000030
    R13: 127feead05306b65 R14: 0000000000000002 R15: 0000000000000000
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
--- <NMI exception stack> ---
 #7 [ffff880232c61e58] intel_idle at ffffffff8134b26d
 #8 [ffff880232c61eb0] cpuidle_idle_call at ffffffff814b387d
 #9 [ffff880232c61f00] cpu_idle at ffffffff8100920b

PID: 0 TASK: ffff880232c6c560 CPU: 3 COMMAND: "kworker/0:1"
 #0 [ffff88023fac7e70] crash_nmi_callback at ffffffff81026268
 #1 [ffff88023fac7e80] notifier_call_chain at ffffffff815f6dbd
 #2 [ffff88023fac7ec0] atomic_notifier_call_chain at ffffffff815f6e1a
 #3 [ffff88023fac7ed0] notify_die at ffffffff815f6e4e
 #4 [ffff88023fac7f00] default_do_nmi at ffffffff815f3b19
 #5 [ffff88023fac7f30] do_nmi at ffffffff815f3ed0
 #6 [ffff88023fac7f50] nmi at ffffffff815f3950
    [exception RIP: intel_idle+157]
    RIP: ffffffff8134b26d RSP: ffff880232c7de58 RFLAGS: 00000046
    RAX: 0000000000000030 RBX: 0000000000000010 RCX: 0000000000000001
    RDX: 0000000000000000 RSI: ffff880232c7dfd8 RDI: ffffffff81c0ea00
    RBP: ffff880232c7dea8 R8: 00000000fffffffb R9: 0000000000000f8f
    R10: 0000000000001ae2 R11: 0000000000000001 R12: 0000000000000030
    R13: 127feead05307394 R14: 0000000000000003 R15: 0000000000000000
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
--- <NMI exception stack> ---
 #7 [ffff880232c7de58] intel_idle at ffffffff8134b26d
 #8 [ffff880232c7deb0] cpuidle_idle_call at ffffffff814b387d
 #9 [ffff880232c7df00] cpu_idle at ffffffff8100920b

Please let me know whether further info is needed.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-17-generic 3.0.0-17.30
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 Home directory /home/misko not ours.
 **** List of PLAYBACK Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC271X Analog [ALC271X Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
 Home directory /home/misko not ours.
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC271X Analog [ALC271X Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: misko 1667 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xd3c00000 irq 50'
   Mixer name : 'Realtek ALC271X'
   Components : 'HDA:10ec0269,10250567,00100100'
   Controls : 15
   Simple ctrls : 10
Date: Thu Mar 29 23:52:00 2012
HibernationDevice: RESUME=UUID=d7575c4e-9a01-4e85-9867-c0dd51aedfed
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Acer TravelMate 8481TG
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, no user)
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic root=UUID=5ce7a766-0e91-491b-afda-4e3a3e2909e9 ro i915.i915_enable_rc6=1 acpi_backlight=vendor pcie_aspm=force crashkernel=384M-2G:64M,2G-:128M nosplash vt.handoff=7
PulseSinks:
 Error: command ['pacmd', 'list-sinks'] failed with exit code 1: Home directory /home/misko not ours.
 No PulseAudio daemon running, or not running as session daemon.
PulseSources:
 Error: command ['pacmd', 'list-sources'] failed with exit code 1: Home directory /home/misko not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-17-generic N/A
 linux-backports-modules-3.0.0-17-generic N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: rts_pstor mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/07/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: BA41_HS
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.10
dmi.modalias: dmi:bvnAcer:bvrV2.10:bd02/07/2012:svnAcer:pnTravelMate8481TG:pvrV2.10:rvnAcer:rnBA41_HS:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.10:
dmi.product.name: TravelMate 8481TG
dmi.product.version: V2.10
dmi.sys.vendor: Acer

Revision history for this message
misko (michael-wagner-gmx) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
misko (michael-wagner-gmx) wrote :

attached crashdump.

penalvch (penalvch)
tags: added: regression-update
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@misko,

Can you boot into the previous kernel version(3.0.0-16) and see if the panics go away?

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Revision history for this message
misko (michael-wagner-gmx) wrote :
Download full text (6.3 KiB)

Hi,

i tried booting 3.0.0-16 20 times - no panic.

Then I retried with 3.0.0.17: at the 6th attempt (today, ... sometimes it happens even faster) another crash occured. Below you can find the backtrace. Shall I upload the complete dumpfile?

      KERNEL: kernel_link
    DUMPFILE: dump.201203311908 [PARTIAL DUMP]
        CPUS: 4
        DATE: Sat Mar 31 19:08:04 2012
      UPTIME: 00:00:12
LOAD AVERAGE: 0.39, 0.08, 0.03
       TASKS: 171
    NODENAME: hitchhiker
     RELEASE: 3.0.0-17-generic
     VERSION: #30-Ubuntu SMP Thu Mar 8 20:45:39 UTC 2012
     MACHINE: x86_64 (1796 Mhz)
      MEMORY: 7.9 GB
       PANIC: "[ 12.591344] Oops: 0000 [#1] SMP " (check log for details)
         PID: 0
     COMMAND: "swapper"
        TASK: ffffffff81c0b020 (1 of 4) [THREAD_INFO: ffffffff81c00000]
         CPU: 0
       STATE: TASK_RUNNING (PANIC)

crash> bt -a

PID: 0 TASK: ffffffff81c0b020 CPU: 0 COMMAND: "swapper"
 #0 [ffff88023fa03a50] machine_kexec at ffffffff8102de18
 #1 [ffff88023fa03ad0] crash_kexec at ffffffff810aa142
 #2 [ffff88023fa03ba0] oops_end at ffffffff815f4358
 #3 [ffff88023fa03bd0] no_context at ffffffff815dbacf
 #4 [ffff88023fa03c10] __bad_area_nosemaphore at ffffffff815dbc6a
 #5 [ffff88023fa03c60] bad_area_nosemaphore at ffffffff815dbca0
 #6 [ffff88023fa03c70] do_page_fault at ffffffff815f6c7d
 #7 [ffff88023fa03d80] page_fault at ffffffff815f3695
    [exception RIP: azx_update_rirb+100]
    RIP: ffffffffa0f374f4 RSP: ffff88023fa03e38 RFLAGS: 00010002
    RAX: 0000000000000002 RBX: ffff88022df82c00 RCX: 0000000000000000
    RDX: 0000000000000003 RSI: ffff88022df82c00 RDI: ffff88022df82c00
    RBP: ffff88023fa03e58 R8: ffff88022e6d5e00 R9: ffff88023ec000a0
    R10: 0000000000001086 R11: 0000000000000400 R12: 00000000000000ff
    R13: 0000000000000000 R14: 00000000ffffffff R15: ffff88022df82c44
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
 #8 [ffff88023fa03e60] azx_interrupt at ffffffffa0f380c7 [snd_hda_intel]
 #9 [ffff88023fa03eb0] handle_irq_event_percpu at ffffffff810cde75
#10 [ffff88023fa03f10] handle_irq_event at ffffffff810ce08e
#11 [ffff88023fa03f40] handle_fasteoi_irq at ffffffff810d0854
#12 [ffff88023fa03f60] handle_irq at ffffffff8100c252
#13 [ffff88023fa03f80] do_IRQ at ffffffff815fcdaa
--- <IRQ stack> ---
#14 [ffffffff81c01d80] ret_from_intr at ffffffff815f33d3
    RIP: ffffffffffffff7e RSP: 0000000000000202 RFLAGS: 00000010
    RAX: 00000000fffffffb RBX: ffffffff81c01e88 RCX: 0000000000000000
    RDX: 0000000000000000 RSI: 0000000000000268 RDI: 0000000000000000
    RBP: ffffffff815f33ce R8: 0000000000000f4d R9: 0000000000001086
    R10: 0000000000000400 R11: ffffffff81032a79 R12: ffffffff81c01da8
    R13: 0000000000000000 R14: ffff88023fa0ebc0 R15: ffffffff8104c9ae
    ORIG_RAX: 00000000000969a9 CS: ffffffff8134b29b SS: ffffffff81c01e38
bt: WARNING: possibly bogus exception frame

PID: 0 TASK: ffff880232c48000 CPU: 1 COMMAND: "kworker/0:0"
 #0 [ffff88023fa47e70] crash_nmi_callback at ffffffff81026268
 #1 [ffff88023fa47e80] notifier_call_chain at ffffffff815f6dbd
 #2 [ffff88023fa47ec0] atomic_notifier_call_chain at ffffffff815f6e1a
 #3 [ffff88023f...

Read more...

Revision history for this message
Brad Figg (brad-figg) wrote :

@misko,

There is a new kernel in proposed. I have no idea if it resolves this issue or not but it would be worth a try. You should probably boot back to -16 and then enable the proposed pocket. Then you can do another update and pull in this new kernel.

Revision history for this message
Luis Henriques (henrix) wrote :

I'm attaching the full dmesg from the crashdump report. It looks like an issue with the snd_hda_intel module, but still under investigation.

Revision history for this message
misko (michael-wagner-gmx) wrote :

Also occured with th proposed kernel, backtrace is attached.

Revision history for this message
misko (michael-wagner-gmx) wrote :

attached full dump.

Revision history for this message
misko (michael-wagner-gmx) wrote :

@henrix: indeed there might be some troubles with snd_hda_intel on my system, dmesg allways contains following entries (if the system starts up without a panic). However, the sound works.

[ 10.614554] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 10.614616] HDA Intel 0000:00:1b.0: irq 50 for MSI/MSI-X
[ 10.614640] HDA Intel 0000:00:1b.0: setting latency timer to 64
...
[ 10.669549] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 10.669617] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 10.679159] Bad target number (1:0)
[ 10.683126] HDA Intel 0000:01:00.1: Refused to change power state, currently in D3
[ 10.683146] HDA Intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 10.683159] hda_intel: Disabling MSI
[ 10.695173] Bad target number (2:0)
[ 10.711280] Bad target number (3:0)
[ 10.727649] Bad target number (4:0)
[ 10.747186] Bad target number (5:0)
...
[ 12.627279] hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
=> this message is repeated 254 times
...
[ 15.653604] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000
[ 16.661298] hda-intel: Codec #1 probe error; disabling it...
[ 17.069175] hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
=> this message is repeated 254 times

[ 18.076774] hda-intel: Codec #2 probe error; disabling it...
[ 18.484637] hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
=> this message is repeated 254 times

[ 19.488313] hda-intel: Codec #3 probe error; disabling it...
[ 19.896288] hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
=> this message is repeated 254 times

[ 20.899953] hda-intel: Codec #4 probe error; disabling it...
[ 21.307825] hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
=> this message is repeated 254 times

[ 22.315412] hda-intel: Codec #5 probe error; disabling it...
[ 22.723279] hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
=> this message is repeated 254 times

[ 23.730961] hda-intel: Codec #6 probe error; disabling it...
[ 24.138834] hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
=> this message is repeated 254 times

[ 25.146614] hda-intel: Codec #7 probe error; disabling it...
[ 25.554487] hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
=> this message is repeated 253 times

[ 26.562063] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x000f0001
[ 26.562157] azx_single_send_cmd: 6 callbacks suppressed
[ 26.562337] hda-intel: no codecs initialized
[ 26.562433] HDA Intel 0000:01:00.1: PCI INT B disabled

penalvch (penalvch)
tags: added: needs-upstream-testing
Revision history for this message
misko (michael-wagner-gmx) wrote :

After the bug seemed to be gone for several months, it occured again (twice) with 3.2.0-29, and also twice since I upgraded to 3.2.0-30.
Attached you can find a backtrace created from the coredump of the latest occurence with 3.2.0-30. If necessary I can also upload the full coredumps of all four occurences.

Revision history for this message
misko (michael-wagner-gmx) wrote :

Attached dmesg extracted from the coredump of the latest occurence with 3.2.0-30.

Revision history for this message
misko (michael-wagner-gmx) wrote :

Ocurred again with 3.2.0-31-generic #50-Ubuntu SMP, output of "bt -a" is attached.

Revision history for this message
misko (michael-wagner-gmx) wrote :

attached dmesg.

Revision history for this message
3dom (3dom) wrote :

have your tried the modifying the boot parameters? ( sudo gedit /etc/default/grub )

For my 8481G,
GRUB_CMDLINE_LINUX="acpi_osi=Linux acpi=noirq"

acpi_osi=Linux //Fix brightness
acpi=noirq //Fix kernel panic at boot

Remember to "sudo update-grub" after modifying the file.
hope this help.

Revision history for this message
Steve Langasek (vorlon) wrote :

"acpi_osi=Linux" is never an appropriate workaround for any issue.

Revision history for this message
misko (michael-wagner-gmx) wrote :

Hi,

for me, "acpi_backlight=vendor" fixed the brightness-issues.
Now I also added "acpi=noirq".

However, the panic did not occur for several weeks now, even without this setting.

Revision history for this message
penalvch (penalvch) wrote :

misko, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
misko (michael-wagner-gmx) wrote :

The crash did not occur for months now (currently I'm using 3.2.0-52-generic), IMO it is fixed already.

Revision history for this message
penalvch (penalvch) wrote :

misko, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/968675/comments/18 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.