Skip to contentSkip to conversation

BUG: warning at drivers/pci/msi.c:680/pci_enable_msi() - DWARF2 unwinder stuck at syscall_call+0x7/0xb

DISCUSSION Martin Lorenz 1 participant 1 message Oct 9, 2006

lore
Share & tools
lore
#0 lore raw

I currently play around with various options to localize my acpi problem and found the following recurring BUG warning:

Oct  9 15:11:55 gimli kernel: [ 2671.631000] BUG: warning at drivers/pci/msi.c:680/pci_enable_msi()
Oct  9 15:11:55 gimli kernel: [ 2671.632000]  [<c0103bd9>] dump_trace+0x69/0x1af
Oct  9 15:11:55 gimli kernel: [ 2671.632000]  [<c0103d37>] show_trace_log_lvl+0x18/0x2c
Oct  9 15:11:55 gimli kernel: [ 2671.632000]  [<c01043d6>] show_trace+0xf/0x11
Oct  9 15:11:55 gimli kernel: [ 2671.632000]  [<c01044d9>] dump_stack+0x15/0x17
Oct  9 15:11:55 gimli kernel: [ 2671.632000]  [<c0211c5e>] pci_enable_msi+0x78/0x22e
Oct  9 15:11:55 gimli kernel: [ 2671.634000]  [<c0275d8d>] e1000_open+0x64/0x176
Oct  9 15:11:55 gimli kernel: [ 2671.636000]  [<c02b8ec1>] dev_open+0x2b/0x62
Oct  9 15:11:55 gimli kernel: [ 2671.638000]  [<c02b79cf>] dev_change_flags+0x47/0xe4
Oct  9 15:11:55 gimli kernel: [ 2671.640000]  [<c02eba8b>] devinet_ioctl+0x252/0x556
Oct  9 15:11:55 gimli kernel: [ 2671.643000]  [<c02aec3a>] sock_ioctl+0x19e/0x1c2
Oct  9 15:11:55 gimli kernel: [ 2671.645000]  [<c0169a3f>] do_ioctl+0x1f/0x62
Oct  9 15:11:55 gimli kernel: [ 2671.646000]  [<c0169cc7>] vfs_ioctl+0x245/0x257
Oct  9 15:11:55 gimli kernel: [ 2671.647000]  [<c0169d25>] sys_ioctl+0x4c/0x67
Oct  9 15:11:55 gimli kernel: [ 2671.647000]  [<c0102dc3>] syscall_call+0x7/0xb
Oct  9 15:11:55 gimli kernel: [ 2671.647000] DWARF2 unwinder stuck at syscall_call+0x7/0xb
Oct  9 15:11:55 gimli kernel: [ 2671.647000]
Oct  9 15:11:55 gimli kernel: [ 2671.647000] Leftover inexact backtrace:
Oct  9 15:11:55 gimli kernel: [ 2671.647000]
Oct  9 15:11:55 gimli kernel: [ 2671.648000]  =======================

this one happened when undocking for the second time in sequence but I found the same several times in the log in conjunction with suspend2ram

it never happens on first suspend (or dock/undock) after booting but very often on second sometimes not before third time

when it has occured I can still suspend and resume, but after that no ACPI events are generated anymore

gruss
mlo
--
Dipl.-Ing. Martin Lorenz

They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.
Benjamin Franklin

please encrypt your mail to me
GnuPG key-ID: F1AAD37D
get it here:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xF1AAD37D

ICQ UIN: 33588107