Bug#513808: linux-image-2.6.26-1-amd64: ACPI Error Method parse/execution failed after suspend
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: important After testing the suspend to RAM options in KDE3.5.9 i noticed the next output after resume : [ 1033.998126] ACPI Exception (exoparg2-0444): AE_AML_PACKAGE_LIMIT, Index (7) is beyond end of object [20080321] [ 1033.998136] ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.WMID.WMBA] (Node 8100371da2d0), AE_AML_PACKAGE_LIMIT higher in dmesg there was : PM: Writing back config space on device :06:04.1 at offset 4 (was 0, writing c0210400) [ 1033.207361] PM: Writing back config space on device :06:04.1 at offset 3 (was 80, writing 804008) [ 1033.207370] PM: Writing back config space on device :06:04.1 at offset 1 (was 210, writing 216) [ 1033.223348] PM: Writing back config space on device :06:04.2 at offset f (was 482002ff, writing 4820020b) [ 1033.223377] PM: Writing back config space on device :06:04.2 at offset 4 (was 0, writing c0210800) [ 1033.223384] PM: Writing back config space on device :06:04.2 at offset 3 (was 80, writing 804008) [ 1033.223394] PM: Writing back config space on device :06:04.2 at offset 1 (was 210, writing 216) -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 ** Command line: root=/dev/sda5 ro quiet ** Tainted: P (1) ** Kernel log: [ 1033.051086] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 [ 1033.067105] PM: Writing back config space on device :06:02.0 at offset f (was 1c0a0100, writing 1c0a010b) [ 1033.067133] PM: Writing back config space on device :06:02.0 at offset 4 (was 0, writing c020) [ 1033.067140] PM: Writing back config space on device :06:02.0 at offset 3 (was 0, writing 6008) [ 1033.067149] PM: Writing back config space on device :06:02.0 at offset 1 (was 290, writing 2900016) [ 1033.067175] ACPI: PCI Interrupt :06:02.0[A] - GSI 22 (level, low) - IRQ 22 [ 1033.069256] PM: Writing back config space on device :06:04.0 at offset f (was 744010b, writing 5c0010b) [ 1033.069264] PM: Writing back config space on device :06:04.0 at offset e (was 0, writing a8fc) [ 1033.069271] PM: Writing back config space on device :06:04.0 at offset d (was 0, writing a800) [ 1033.069278] PM: Writing back config space on device :06:04.0 at offset c (was 0, writing a4fc) [ 1033.069285] PM: Writing back config space on device :06:04.0 at offset b (was 0, writing a400) [ 1033.069292] PM: Writing back config space on device :06:04.0 at offset a (was 0, writing 57fff000) [ 1033.069299] PM: Writing back config space on device :06:04.0 at offset 9 (was 0, writing 5400) [ 1033.069306] PM: Writing back config space on device :06:04.0 at offset 8 (was 0, writing 507ff000) [ 1033.069313] PM: Writing back config space on device :06:04.0 at offset 7 (was 0, writing 5040) [ 1033.069321] PM: Writing back config space on device :06:04.0 at offset 6 (was 20070706, writing b0070706) [ 1033.069332] PM: Writing back config space on device :06:04.0 at offset 3 (was 824008, writing 82a820) [ 1033.179293] ata2: SATA link down (SStatus 0 SControl 310) [ 1033.207325] PM: Writing back config space on device :06:04.1 at offset f (was 40102ff, writing 401020b) [ 1033.207353] PM: Writing back config space on device :06:04.1 at offset 4 (was 0, writing c0210400) [ 1033.207361] PM: Writing back config space on device :06:04.1 at offset 3 (was 80, writing 804008) [ 1033.207370] PM: Writing back config space on device :06:04.1 at offset 1 (was 210, writing 216) [ 1033.223348] PM: Writing back config space on device :06:04.2 at offset f (was 482002ff, writing 4820020b) [ 1033.223377] PM: Writing back config space on device :06:04.2 at offset 4 (was 0, writing c0210800) [ 1033.223384] PM: Writing back config space on device :06:04.2 at offset 3 (was 80, writing 804008) [ 1033.223394] PM: Writing back config space on device :06:04.2 at offset 1 (was 210, writing 216) [ 1033.223421] ACPI: PCI Interrupt :06:04.2[B] - GSI 23 (level, low) - IRQ 23 [ 1033.223451] PM: Writing back config space on device :06:04.3 at offset f (was 40102ff, writing 401020b) [ 1033.223479] PM: Writing back config space on device :06:04.3 at offset 4 (was 0, writing c0210c00) [ 1033.223487] PM: Writing back config space on device :06:04.3 at offset 3 (was 80, writing 804008) [ 1033.223496] PM: Writing back config space on device :06:04.3 at offset 1 (was 210, writing 216) [ 1033.239399] PM: Writing back config space on device :06:04.4 at offset 4 (was 0, writing c0210100) [ 1033.239410] PM: Writing back config space on device :06:04.4 at offset 1 (was 210, writing 212) [ 1033.239435] ACPI: PCI Interrupt
Meeting(s) at FOSDEM
Hi folks, Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? Cheers, -- Steve McIntyre, Cambridge, UK.st...@einval.com I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop -- Vivek Dasmohapatra -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
Once more, with correct addresses. :-/ On Sun, Feb 01, 2009 at 02:53:58PM +, Steve McIntyre wrote: Hi folks, Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? -- Steve McIntyre, Cambridge, UK.st...@einval.com I suspect most samba developers are already technically insane... Of course, since many of them are Australians, you can't tell. -- Linus Torvalds -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513835: linux-image-2.6.26-1-xen-686: xen kernel fails at recognizing keyboard and at ACPI handling
Package: linux-image-2.6.26-1-xen-686 Version: 2.6.26-13 Severity: normal Hello the hurd, Preambule: I stick with Xen Dom0 for now. The only kernel I don't run on the bare hardware is linux-image-2.6.26-1-xen-686 which is then paravirtualized with Xen. That is I don't attempt to run any kernel through Xen HVM. My problem: With linux-image-2.6.26-1-xen-686 I experience a similar bug as with linux-image-2.6.26-1-openvz-686 ; see my previous bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513095 That is, not only my keyboard seems dead (with not even SysReq keys functionning), but, likewise, my touchpad seems dead too. It behaves like both (keyboard and touchpad) were not power supplied. Note that I don't have those problems with linux-image-2.6.26-1-686 or linux-image-2.6.26-1-vserver-686 ; don't you think it's strange ? This might be a 'false bug' since Xen is known not to support ACPI. However it is embarrassing if keyboard and touchpad functions depend effectively on proper OS-Side ACPI initialisation while the keyboard can be used seamlessly to tell the boot loader what to boot. In hope my report will prove useful. Sincerely, Valentin QUEQUET -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-xen-686 depends on: hi initramfs-tools 0.92o tools for generating an initramfs ii linux-modules-2.6.26-1-xen-68 2.6.26-13 Linux 2.6.26 modules on i686 Versions of packages linux-image-2.6.26-1-xen-686 recommends: ii libc6-xen 2.7-18 GNU C Library: Shared libraries [X Versions of packages linux-image-2.6.26-1-xen-686 suggests: hi grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v hi linux-doc-2.6.26 2.6.26-13 Linux kernel specific documentatio -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513827: the problem seems to be in fact with cpufreq_stats
I think I misinterpreted the kernel oops. If I disable loading cpufreq_stats, no oops occurs at boot time. If I load the module after the machine has booted, it loads cleanly. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #497931 # * http://bugzilla.kernel.org/show_bug.cgi?id=10487 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 497931 + fixed-upstream Bug#497931: forcedeth: don't work after resume There were no tags set. Tags added: fixed-upstream usertags 497931 - status-NEW Bug#497931: forcedeth: don't work after resume Usertags were: status-NEW. Usertags are now: . usertags 497931 + status-RESOLVED resolution-CODE-FIX Bug#497931: forcedeth: don't work after resume There were no usertags set. Usertags are now: resolution-CODE-FIX status-RESOLVED. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #497931 # * http://bugzilla.kernel.org/show_bug.cgi?id=10487 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 497931 + fixed-upstream usertags 497931 - status-NEW usertags 497931 + status-RESOLVED resolution-CODE-FIX thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#472462: linux-image-2.6.24-1-amd64: log cluttered with ide failed opcode for dvd drive
Yes, I can confirm that this bug still exist on lenny. This is using the
latest 2.6.26-1-amd64 kernel. I am attaching the relevant information.
For me, the bug manifests itself when playing an audio cd. There is a
constant buzzing noise and dmesg shows:
[ 9227.846775] hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
[ 9227.846784] ide: failed opcode was: unknown
[ 9227.846790] hdb: drive not ready for command
[ 9227.847331] hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
[ 9227.847338] ide: failed opcode was: unknown
[ 9227.847342] hdb: drive not ready for command
[ 9227.847351] hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
[ 9227.847351] ide: failed opcode was: unknown
[ 9227.847351] hdb: drive not ready for command
[ 9227.847351] hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
[ 9227.847351] ide: failed opcode was: unknown
[ 9227.847351] hdb: drive not ready for command
[ 9227.847351] hdb: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
[ 9227.847351] ide: failed opcode was: unknown
[ 9227.847351] hdb: drive not ready for command
lsmod shows:
Module Size Used by
aes_x86_64 12416 0
aes_generic32552 1 aes_x86_64
rt2500pci 23168 0
fglrx296 27
ipv6 288328 18
ppdev 11656 0
lp 14724 0
vmnet 43332 13
parport_pc 31016 0
parport41776 3 ppdev,lp,parport_pc
vmblock18128 3
vmci 52904 0
vmmon 72144 0
acpi_cpufreq 11792 1
cpufreq_stats 9120 0
cpufreq_ondemand 11792 1
cpufreq_conservative11784 0
cpufreq_powersave 6400 0
freq_table 9344 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
cpufreq_userspace 8452 0
fuse 53184 1
loop 19468 0
arc46272 2
ecb 7296 2
crypto_blkcipher 21636 1 ecb
rt61pci27136 0
crc_itu_t 6528 1 rt61pci
rt2x00pci 13056 2 rt2500pci,rt61pci
rt2x00lib 30080 3 rt2500pci,rt61pci,rt2x00pci
firmware_class 12544 1 rt2x00lib
rfkill 11168 2 rt2x00lib
led_class 8968 1 rt2x00lib
input_polldev 8720 1 rt2x00lib
mac80211 162864 2 rt2x00pci,rt2x00lib
cfg80211 30224 2 rt2x00lib,mac80211
psmouse42268 0
pcspkr 7040 0
serio_raw 9860 0
snd_hda_intel 434904 5
eeprom_93cx66784 2 rt2500pci,rt61pci
snd_pcm_oss41760 0
snd_mixer_oss 18816 1 snd_pcm_oss
snd_pcm81672 3 snd_hda_intel,snd_pcm_oss
i2c_i801 13596 0
snd_seq_dummy 7428 0
snd_seq_oss33152 0
i2c_core 27936 1 i2c_i801
iTCO_wdt 15696 0
snd_seq_midi 11072 0
snd_rawmidi26784 1 snd_seq_midi
snd_seq_midi_event 11904 2 snd_seq_oss,snd_seq_midi
snd_seq54304 6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 25744 3 snd_pcm,snd_seq
snd_seq_device 11668 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd63688 17
snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 12064 1 snd
snd_page_alloc 13072 2 snd_hda_intel,snd_pcm
button 11680 0
intel_agp 31728 0
evdev 14208 3
ext3 125072 1
jbd51240 1 ext3
mbcache12804 1 ext3
raid1 24192 2
md_mod 80164 3 raid1
sd_mod 29376 6
ide_cd_mod 36360 0
cdrom 37928 1 ide_cd_mod
ata_generic10116 0
usbhid 45792 0
hid41792 1 usbhid
ff_memless 9224 1 usbhid
ide_pci_generic 9220 0 [permanent]
ahci 33036 4
r8169 31492 0
libata165472 2 ata_generic,ahci
scsi_mod 160760 2 sd_mod,libata
dock 14112 1 libata
jmicron 6912 0 [permanent]
ide_core 128284 3 ide_cd_mod,ide_pci_generic,jmicron
ehci_hcd 36108 0
uhci_hcd 25760 0
thermal22688 0
processor 42304 2 acpi_cpufreq,thermal
fan 9352 0
thermal_sys17728 3 thermal,processor,fan
I believe the guilty party is the module jmicron, as evidenced by the post
at http://bbs.archlinux.org/viewtopic.php?pid=274632
Are there plans to use the module pata_jmicron instead?
--
To UNSUBSCRIBE, email to
Bug#465278: Appletouch failure upon resume after suspend2ram
Severity: grave I am increasing the gravity of this bug, because it makes the apple iBook G4 laptop pretty much unusable without an external mouse, and because people seems to just ignore this PowerPC specific bug. A very easy way to systematicaly reproduce this bug is to close the lid (or make it to sleep somehow), and then touch continously the mousepad during the wakeup. If you don't touch the trackpad, it might wakeup properly (maybe 1 chance on 3 to still have a working mouse). I also tried the same with the 2.6.18 kernel, and got similar results but with a significant difference: with the 2.6.18 kernel, I can make the mouse working again by simply doing rmmod appletouch and then modprobe -a appletouch. If I use the 2.6.26 kernel instead, I get the already reported following errors and the only way I know to make the mouse working again is rebooting. [45692.025239] appletouch: Could not do mode read request from device (Geyser Raw mode) [45692.025289] appletouch: probe of 1-2:1.0 failed with error -5 [45692.025347] usbcore: registered new interface driver appletouch Please note that xserver-xorg-input-synaptics is not even installed, and that the bug is reproducible in runlevel 1 with just enough things running to be able to put the laptop in sleep mode. My guess is that there is 2 bugs involved: a new bug in the appletouch driver in the kernel = 2.6.24 (maybe before) that prevent removing and adding again the driver properly in some conditions, and another possibly old bug that, for some reasons, showup systematically in Lenny while it was seldom appearing in Etch. In Etch, you could sometime lost the mouse after a wakeup, but it happened maybe just once a month, and since you could just remove and add again the driver, it was mostly just a nuisance. This bug is really annoying, reducing enough the usability of the iBook to make me seriously considering downgrading to Etch or looking at another distribution if it fix my problem. Simon Valiquette -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#465278: severity of 465278 is important
# Automatically generated email from bts, devscripts version 2.10.35lenny2 # driver specific bug severity 465278 important -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 465278 is important
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny2 # driver specific bug severity 465278 important Bug#465278: linux-image-2.6.24-1-powerpc: appletouch failure upon resume after suspend2ram Severity set to `important' from `normal' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#465278: Appletouch failure upon resume after suspend2ram
Severity 465278 grave By searching a little on mailing lists, I saw that someone reported that the problems might be related with this patch, or at least related with this part of the code, but nobody seems to have seriously looked at it: http://www.linuxhq.com/kernel/v2.6/24/drivers/input/mouse/appletouch.c http://www.mail-archive.com/debian-powe...@lists.debian.org/msg59480.html From the Debian PowerPC mailing list, I deduce that the problem appeared in Debian Sid with the kernel 2.6.24. Simon Valiquette -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513889: linux-image-2.6.24-etchnhalf.1-amd64: AMD Phenom soft lockup - CPU#3 stuck for 11s [events/3:18]
Package: linux-image-2.6.24-etchnhalf.1-amd64 Version: 2.6.24-6~etchnhalf.7 Severity: critical Justification: breaks the whole system My amd64 system is subject to random lockups. Sometimes I can perform an emergency sync, umount, and reboot using MagicSysRq. Other times I can not. Sometimes I get a couple of days of uptime. Other times I have to reboot several times a day. This particular case was one of the times that I had to use the reset button to restart the system. The system had become unresponsive after running for about 48 hours without X running or any console user logins (total uptime was ~ 5 days). The first lock-up was: Jan 30 00:49:14 stasis kernel: BUG: soft lockup - CPU#3 stuck for 11s! [events/3:18] Jan 30 00:49:14 stasis kernel: CPU 3: Jan 30 00:49:14 stasis kernel: Modules linked in: isofs zlib_inflate ext2 tcp_diag inet_diag ppdev parport_pc lp parport autofs4 ipv6 tun nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc fuse dm_snapshot dm_mirror dm_mod it87 hwmon_vid eeprom loop snd_usb_audio snd_usb_lib snd_hwdep snd_seq_dummy snd_seq_oss snd_hda_intel snd_seq_midi snd_rawmidi snd_pcm_oss snd_mixer_oss snd_seq_midi_event rtc_cmos snd_seq snd_pcm rtc_core psmouse snd_timer floppy rtc_lib pwc snd_seq_device i2c_piix4 pcspkr snd_page_alloc serio_raw compat_ioctl32 videodev snd v4l2_common i2c_core v4l1_compat soundcore usblp atl1 button mii sg evdev ext3 jbd mbcache raid10 raid1 md_mod ide_generic generic atiixp ide_core sd_mod usbhid hid aic7xxx scsi_transport_spi ata_generic ahci ehci_hcd libata scsi_mod ohci_hcd thermal processor fan Jan 30 00:49:14 stasis kernel: Pid: 18, comm: events/3 Not tainted 2.6.24-etchnhalf.1-amd64 #1 Jan 30 00:49:14 stasis kernel: RIP: 0010:[8021bd36] [8021bd36] __smp_call_function_mask+0x9c/0xc0 Jan 30 00:49:14 stasis kernel: RSP: 0018:81012b763e00 EFLAGS: 0297 Jan 30 00:49:14 stasis kernel: RAX: 08fc RBX: 0003 RCX: 0001 Jan 30 00:49:14 stasis kernel: RDX: 08fc RSI: 00fc RDI: 0007 Jan 30 00:49:14 stasis kernel: RBP: 81000103c930 R08: 00f9 R09: 81011401fac8 Jan 30 00:49:14 stasis kernel: R10: 81012b72abe8 R11: R12: Jan 30 00:49:14 stasis kernel: R13: 00030282 R14: 81012b763ea0 R15: 00020001 Jan 30 00:49:14 stasis kernel: FS: 2b04ef9bccc0() GS:81012b6b78c0() knlGS:f6dfdb90 Jan 30 00:49:14 stasis kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Jan 30 00:49:14 stasis kernel: CR2: 2b8ba51cf000 CR3: 000114053000 CR4: 06e0 Jan 30 00:49:14 stasis kernel: DR0: DR1: DR2: Jan 30 00:49:14 stasis kernel: DR3: DR6: 0ff0 DR7: 0400 Jan 30 00:49:14 stasis kernel: Jan 30 00:49:14 stasis kernel: Call Trace: Jan 30 00:49:14 stasis kernel: [80216193] mcheck_check_cpu+0x0/0x37 Jan 30 00:49:14 stasis kernel: [8023e28b] lock_timer_base+0x26/0x4c Jan 30 00:49:14 stasis kernel: [80216193] mcheck_check_cpu+0x0/0x37 Jan 30 00:49:14 stasis kernel: [8021bdb8] smp_call_function_mask+0x5e/0x70 Jan 30 00:49:14 stasis kernel: [80215a31] mcheck_timer+0x0/0x7c Jan 30 00:49:14 stasis kernel: [80216193] mcheck_check_cpu+0x0/0x37 Jan 30 00:49:14 stasis kernel: [8023a243] on_each_cpu+0x10/0x22 Jan 30 00:49:14 stasis kernel: [80215a4e] mcheck_timer+0x1d/0x7c Jan 30 00:49:14 stasis kernel: [8027d1f0] vmstat_update+0x0/0x31 Jan 30 00:49:14 stasis kernel: [802448dd] run_workqueue+0x7f/0x10b Jan 30 00:49:14 stasis kernel: [802451ef] worker_thread+0x0/0xe4 Jan 30 00:49:14 stasis kernel: [802452c9] worker_thread+0xda/0xe4 Jan 30 00:49:14 stasis kernel: [802481fe] autoremove_wake_function+0x0/0x2e Jan 30 00:49:14 stasis kernel: [802480de] kthread+0x47/0x75 Jan 30 00:49:14 stasis kernel: [8020cc48] child_rip+0xa/0x12 Jan 30 00:49:14 stasis kernel: [80248097] kthread+0x0/0x75 Jan 30 00:49:14 stasis kernel: [8020cc3e] child_rip+0x0/0x12 This repeated 1703 times until the system became totally unresponsive with: Jan 30 06:25:05 stasis kernel: BUG: soft lockup - CPU#3 stuck for 11s! [events/3:18] Jan 30 06:25:05 stasis kernel: CPU 3: Jan 30 06:25:05 stasis kernel: Modules linked in: isofs zlib_inflate ext2 tcp_diag inet_diag ppdev parport_pc lp parport autofs4 ipv6 tun nfsd auth_rpc gss exportfs nfs lockd nfs_acl sunrpc fuse dm_snapshot dm_mirror dm_mod it87 hwmon_vid eeprom loop snd_usb_audio snd_usb_lib snd_hwdep snd_seq_dummy sn d_seq_oss snd_hda_intel snd_seq_midi snd_rawmidi snd_pcm_oss snd_mixer_oss snd_seq_midi_event rtc_cmos snd_seq snd_pcm rtc_core psmouse snd_timer flopp y rtc_lib pwc snd_seq_device i2c_piix4 pcspkr snd_page_alloc serio_raw compat_ioctl32 videodev snd v4l2_common i2c_core v4l1_compat
Processed: reassign 513894 to linux-image-2.6.26-1-ixp4xx
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny2 reassign 513894 linux-image-2.6.26-1-ixp4xx Bug#513894: base: Internal error: Oops: f3 [#2] Bug reassigned from package `base' to `linux-image-2.6.26-1-ixp4xx'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
