kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x00000100

Thank you for taking the time to report this bug and helping to make Ubuntu better.
This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage.
I have classified this bug as a bug in linux.

I can confirm this bug, using a Sony Vaio VGN-FZ250FE laptop with Ubuntu 8.10 testing.

The kern.log, messages and syslog in /var/log grew to 2048Mb repeating these lines over and over:
Oct 21 18:01:12 BorgClown kernel: [22516.821257] =======================
Oct 21 18:01:12 BorgClown kernel: [22516.821344] bad: scheduling from the idle thread!
Oct 21 18:01:12 BorgClown kernel: [22516.821347] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Oct 21 18:01:12 BorgClown kernel: [22516.821356] [<c037c3e6>] ? printk+0x1d/0x1f
Oct 21 18:01:12 BorgClown kernel: [22516.821361] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
Oct 21 18:01:12 BorgClown kernel: [22516.821364] [<c012107f>] dequeue_task+0xcf/0x130
Oct 21 18:01:12 BorgClown kernel: [22516.821367] [<c012112a>] deactivate_task+0x1a/0x30
Oct 21 18:01:12 BorgClown kernel: [22516.821371] [<c037ca03>] schedule+0x4b3/0x790
Oct 21 18:01:12 BorgClown kernel: [22516.821375] [<c014d3bb>] ? sched_clock_tick+0x7b/0xb0
Oct 21 18:01:12 BorgClown kernel: [22516.821379] [<c0153dcc>] ? tick_nohz_stop_idle+0x5c/0x70
Oct 21 18:01:12 BorgClown kernel: [22516.821384] [<c0153e15>] ? tick_nohz_restart_sched_tick+0x35/0x180
Oct 21 18:01:12 BorgClown kernel: [22516.821388] [<c01028cd>] cpu_idle+0xbd/0x140
Oct 21 18:01:12 BorgClown kernel: [22516.821391] [<c036edb3>] rest_init+0x53/0x60
Oct 21 18:01:12 BorgClown kernel: [22516.821395] =======================
Oct 21 18:01:12 BorgClown kernel: [22516.821458] bad: scheduling from the idle thread!
Oct 21 18:01:12 BorgClown kernel: [22516.821461] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Oct 21 18:01:12 BorgClown kernel: [22516.821463] [<c037c3e6>] ? printk+0x1d/0x1f
Oct 21 18:01:12 BorgClown kernel: [22516.821468] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
Oct 21 18:01:12 BorgClown kernel: [22516.821471] [<c012107f>] dequeue_task+0xcf/0x130
Oct 21 18:01:12 BorgClown kernel: [22516.821475] [<c012112a>] deactivate_task+0x1a/0x30
Oct 21 18:01:12 BorgClown kernel: [22516.821478] [<c037ca03>] schedule+0x4b3/0x790
Oct 21 18:01:12 BorgClown kernel: [22516.821482] [<c014d3bb>] ? sched_clock_tick+0x7b/0xb0
Oct 21 18:01:12 BorgClown kernel: [22516.821486] [<c0153dcc>] ? tick_nohz_stop_idle+0x5c/0x70
Oct 21 18:01:12 BorgClown kernel: [22516.821490] [<c0153e15>] ? tick_nohz_restart_sched_tick+0x35/0x180
Oct 21 18:01:12 BorgClown kernel: [22516.821494] [<c01028cd>] cpu_idle+0xbd/0x140
Oct 21 18:01:12 BorgClown kernel: [22516.821497] [<c036edb3>] rest_init+0x53/0x60
Oct 21 18:01:12 BorgClown kernel: [22516.821501] =======================
Oct 21 18:01:12 BorgClown kernel: [22516.821663] bad: scheduling from the idle thread!
Oct 21 18:01:12 BorgClown kernel: [22516.821666] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Oct 21 18:01:12 BorgClown kernel: [22516.821668] [<c037c3e6>] ? printk+0x1d/0x1f
Oct 21 18:01:12 BorgClown kernel: [22516.821672] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
Oct 21 18:01:12 BorgClown kernel: [22516.821675] [<c012107f>] dequeue_task+0xcf/0x130
Oct 21 18:01:12 BorgClown kernel: [22516.821679] [<c012112a>] deactivate_task+0x1a/0x30
Oct 21 18:01:12 BorgClown kernel: [22516.821683] [<c037ca03>] sche...

Same on an M1330 with kernel 2.6.27-7.13, at home where I use the wireless.

I saw that error only once. It is very hard to reproduce, but I think I saw it also when using wireless network.

I was wrong, I see error too often :). How can I help? What logs or additional informations are required?

I send part of my current log.

My computer shows the same (or a similar) bug. dd and klogd cause considerable load (50% each) and several logfiles (messages, kern.log, syslog) grow at a staggering pace. I actually noticed the problem when those logs used up all the available space.

Due to the excessive resource consumption of this bug, I'd consider it to be critical.

Have been encountering kernel panics very frequently here, both while the system is active and idle, although never with much justification. (Just basic use aboard some pretty meaty hardware). I just recently noticed the message in the log after remembering to check it.

System does slow down frequently and hang without kernel panics, which suggests scheduler problems.

Regrettably my previous logs have been erased so I have no way of finding out whether old lockups were caused by the same issue. I was actually away when this happened and returned hours later to find my computer in a panicked state. At this point I am just guessing that this bug killed it since it is the last thing in my log.

I am attaching my syslog, as well as user.log and daemon.log...

For quick reference, here is the offending snippet from syslog, line 72:
Oct 24 11:52:43 dylan-laptop kernel: [17183.342141] BUG: scheduling while atomic: swapper/0/0x00000100

Here is something I found in daemon.log a few seconds before the crash:
Oct 24 11:13:07 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 6
Oct 24 11:13:07 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 6 -> 7
Oct 24 11:51:47 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 6
Oct 24 11:51:47 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 6 -> 7
Oct 24 11:52:22 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 6
Oct 24 11:52:22 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 6 -> 7
That event doesn't happen very often, so may be related. Still possibly a coincidence.

The event at 17:31 and onwards is restarting after a hard power off.

It is a Ubuntu intrepid bug. How to change url to https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/somenumber?

I can see this bug on my Intrepid installation running on a Lenovo Thinkpad T61p. The problem occurred for the first time today. I am not sure if this is related to updates I installed yesterday (Oct 24).

I have the x86-32 2.6.27-7-generic kernel installed.

Oct 25 12:36:12 crazy88 kernel: [77144.122543] =======================
Oct 25 12:36:12 crazy88 kernel: [77144.122668] bad: scheduling from the idle thread!
Oct 25 12:36:12 crazy88 kernel: [77144.122671] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Oct 25 12:36:12 crazy88 kernel: [77144.122673] [<c037c3f6>] ? printk+0x1d/0x1f
Oct 25 12:36:12 crazy88 kernel: [77144.122676] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
Oct 25 12:36:12 crazy88 kernel: [77144.122679] [<c012107f>] dequeue_task+0xcf/0x130
Oct 25 12:36:12 crazy88 kernel: [77144.122682] [<c012112a>] deactivate_task+0x1a/0x30
Oct 25 12:36:12 crazy88 kernel: [77144.122685] [<c037ca13>] schedule+0x4b3/0x790
Oct 25 12:36:12 crazy88 kernel: [77144.122688] [<c014d3bb>] ? sched_clock_tick+0x7b/0xb0
Oct 25 12:36:12 crazy88 kernel: [77144.122697] [<c0153dcc>] ? tick_nohz_stop_idle+0x5c/0x70
Oct 25 12:36:12 crazy88 kernel: [77144.122706] [<c0153e15>] ? tick_nohz_restart_sched_tick+0x35/0x180
Oct 25 12:36:12 crazy88 kernel: [77144.122710] [<c01028cd>] cpu_idle+0xbd/0x140
Oct 25 12:36:12 crazy88 kernel: [77144.122712] [<c036edc3>] rest_init+0x53/0x60
Oct 25 12:36:12 crazy88 kernel: [77144.122715] =======================

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

HiI have the same kind of problem (dd and klogd taking up a lot of processor cycles). Appears almost daily. If additional info is needed, please drop me a mail. I added also some parts of my syslog. I am using the RC of intrepid. It seems to be related to the wireless module.

Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858677] bad: scheduling from the idle thread!
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858684] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858688]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858689] Call Trace:
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858692] <IRQ> [<ffffffff8023e06d>] dequeue_task_idle+0x2d/0x40
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858705] [<ffffffff8023c436>] dequeue_task+0x96/0xe0
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858711] [<ffffffff8023c4d3>] deactivate_task+0x23/0x30
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858717] [<ffffffff80500685>] thread_return+0x108/0x3c3
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858724] [<ffffffff80500d33>] schedule_timeout+0x63/0xd0
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858732] [<ffffffff8025a3d0>] ? process_timeout+0x0/0x10
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858739] [<ffffffff80500d2e>] ? schedule_timeout+0x5e/0xd0
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858746] [<ffffffff80500dbe>] schedule_timeout_uninterruptible+0x1e/0x20
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858752] [<ffffffff8025ab85>] msleep+0x25/0x40
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858774] [<ffffffffa0b26ca3>] iwl_scan_cancel_timeout+0x63/0xb0 [iwlcore]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858792] [<ffffffffa0b38031>] iwl4965_mac_update_tkip_key+0x51/0x120 [iwlagn]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858822] [<ffffffffa0aadcde>] ieee80211_tkip_decrypt_data+0x19e/0x230 [mac80211]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858832] [<ffffffff802475bd>] ? default_wake_function+0xd/0x10
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858838] [<ffffffff8023c8ca>] ? __wake_up_common+0x5a/0x90
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858865] [<ffffffffa0aa3929>] ieee80211_crypto_tkip_decrypt+0xd9/0x130 [mac80211]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858893] [<ffffffffa0ab01d8>] ieee80211_rx_h_decrypt+0x1b8/0x1d0 [mac80211]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858920] [<ffffffffa0ab24c8>] ieee80211_invoke_rx_handlers+0x108/0x2e0 [mac80211]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858948] [<ffffffffa0ab1ec9>] __ieee80211_rx_handle_packet+0x289/0x380 [mac80211]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.858976] [<ffffffffa0ab2786>] __ieee80211_rx+0xe6/0x200 [mac80211]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.859002] [<ffffffffa0a9f64e>] ieee80211_tasklet_handler+0x12e/0x160 [mac80211]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.859019] [<ffffffffa0b3b309>] ? iwl4965_irq_tasklet+0x129/0x350 [iwlagn]
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.859027] [<ffffffff802546c6>] tasklet_action+0x86/0x110
Oct 26 15:01:35 jeroen-laptop kernel: [ 8973.859034] [<ffffffff80254d8c>] __do_softirq+0x8c/0x100
Oct 26 15:01:35 jeroen-laptop ker...

Same problem here. And it happens almost once a day. Bug seems critical to me ...

I have this problem using a Dell xps m1330.

uname -a: 2.6.27-7-generic #1 SMP Fri Oct 24 06:42:44 UTC 2008 i686 GNU/Linux

dmesg is flooded with post like:

[21823.682414] bad: scheduling from the idle thread!
[21823.682422] Pid: 0, comm: swapper Tainted: P W 2.6.27-7-generic #1
[21823.682428] [<c037c3f6>] ? printk+0x1d/0x1f
[21823.682439] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
[21823.682447] [<c012107f>] dequeue_task+0xcf/0x130
[21823.682457] [<c012112a>] deactivate_task+0x1a/0x30
[21823.682466] [<c037ca13>] schedule+0x4b3/0x790
[21823.682475] [<c014d3bb>] ? sched_clock_tick+0x7b/0xb0
[21823.682487] [<c0153dcc>] ? tick_nohz_stop_idle+0x5c/0x70
[21823.682497] [<c0153e15>] ? tick_nohz_restart_sched_tick+0x35/0x180
[21823.682508] [<c01028cd>] cpu_idle+0xbd/0x140
[21823.682516] [<c037a651>] start_secondary+0x9d/0xcc
[21823.682526] =======================

I have to turn klogd off to be able to use my computer normally. If I do that there is no longer any trace of this problem.

I don't think there is a bug in sysklogd here, so I'm closing that task. klogd is working hard because it is being flooded with call traces from the kernel

That sounds right, my bad.

Bug 289808 describes system freezes as the main symptom. I've also seen system freezes, in addition to the high CPU activity. Have any others amongst you seen freezes?

Hi Everyone,

@Michal Koziorowski, from the log files you attached I see you get a flood of "iwlagn: Can not allocate SKB buffers" (see bug 250139) and then you seem to be hit with this bug. I'm guessing from examining from some of the other logs posted here this is related to wifi and specifically the iwlagn driver you all seem to be using. If you can all try the following report back your results that would be great:

1) Try installing the linux-backports-modules package. It recently pulled in an updated version of the compat-wireless stack:

https://edge.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27

linux-backports-modules-2.6.27 (2.6.27-7.3) intrepid; urgency=low

  [Tim Gardner]

  * Added iwlwifi firmware
  * Added the upstream compat-wireless-2.6 tree.
  * Updated compat-wireless to wireless-testing tag master-2008-10-14
  * Set CONFIG_WIRELESS_OLD_REGULATORY=y by default.

Ideally, the updated version of the driver provided in linux-backports-modules will resolve this issue. If it doesni't help then try the following:

2) Disable wireless by unloading the iwlagn driver - 'sudo rmmod iwlagn'. From the timestamps on the logs it doesn't seem that this issue happens immediately so I don't think it would require require blacklisting the driver from ever loading. Does unloading the driver at least prevent this issue from happening? This will at least confirm my assumption this is related to the iwlagn driver.

Please let us know your results. Thanks.

I forgot to say, that I have been using linux backports modules from the beginning. I cannot repeat the problem now, but I think I will see it again.
I also think bug is related to wireless driver because I saw it twice when using firefox and torrent application. My internet connection speed is about 50KB/s and wireless is mostly not used heavily.

I am experienceing it on a Thinkpad R61 right now. Can I provide any information to help to resolve this bug?

Thanks Michal. It would be interesting to know if you'd be able to nail down a set of steps to trigger/reproduce this issue. However, it sounds like it isn't happening as frequently as before so it may be hard to do so. Anyways, keep us posted with any news.

@Ing0R (as well as anyone else experiencing this issue) - If you'd like to try what I asked of Michal above - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/23 - that would be great.

@Leann: I installed linux-backports-modules yesterday and, after a reboot, used the WLAN card quite heavily since. After 16 hours of stress testing, the bug has yet to reoccur.

Currently using linux-modules-backport-generic 2.6.27-7.4, the "scheduling from the idle thread" problem just occured. I can 90% confirm the problem is wireless related, it's only ever occured at home, where I have WPA Wifi.

Once the problem began, rmmod the iwlagn had no apparent affect, other than disabling wireless. Attached is lspci, and lsmod output. In case either are of use.

I had that error again today.
BUG: scheduling while atomic: swapper/0/0x00000100 .... was proceeded by:
Oct 30 08:31:00 michallo-laptop kernel: [16459.078865] wlan0 direct probe responded
Oct 30 08:31:00 michallo-laptop kernel: [16459.078885] wlan0: authenticate with AP 00:1e:e5:3e:79:20
Oct 30 08:31:00 michallo-laptop kernel: [16459.080769] wlan0: authenticated
Oct 30 08:31:00 michallo-laptop kernel: [16459.080778] wlan0: associate with AP 00:1e:e5:3e:79:20
Oct 30 08:31:00 michallo-laptop kernel: [16459.083234] wlan0: RX ReassocResp from 00:1e:e5:3e:79:20 (capab=0x431 status=0 aid=1)
Oct 30 08:31:00 michallo-laptop kernel: [16459.083241] wlan0: associated
Oct 30 08:31:04 michallo-laptop kernel: [16463.075222] wlan0: deauthenticated
Oct 30 08:31:05 michallo-laptop kernel: [16464.072177] wlan0: direct probe to AP 00:1e:e5:3e:79:20 try 1
Oct 30 08:31:05 michallo-laptop kernel: [16464.074849] wlan0 direct probe responded
Oct 30 08:31:05 michallo-laptop kernel: [16464.074865] wlan0: authenticate with AP 00:1e:e5:3e:79:20
Oct 30 08:31:05 michallo-laptop kernel: [16464.076735] wlan0: authenticated
Oct 30 08:31:05 michallo-laptop kernel: [16464.076749] wlan0: associate with AP 00:1e:e5:3e:79:20
Oct 30 08:31:05 michallo-laptop kernel: [16464.079203] wlan0: RX ReassocResp from 00:1e:e5:3e:79:20 (capab=0x431 status=0 aid=1)
Oct 30 08:31:05 michallo-laptop kernel: [16464.079215] wlan0: associated
Oct 30 11:10:11 michallo-laptop kernel: [26009.696222] wlan0: No ProbeResp from current AP 00:1e:e5:3e:79:20 - assume out of range
Oct 30 11:10:25 michallo-laptop kernel: [26024.266423] wlan0: deauthenticated
Oct 30 11:10:25 michallo-laptop kernel: [26024.275783] wlan0: direct probe to AP 00:1e:e5:3e:79:20 try 1
Oct 30 11:10:25 michallo-laptop kernel: [26024.289945] wlan0: direct probe to AP 00:1e:e5:3e:79:20 try 1
Oct 30 11:10:25 michallo-laptop kernel: [26024.292624] wlan0 direct probe responded
Oct 30 11:10:25 michallo-laptop kernel: [26024.292640] wlan0: authenticate with AP 00:1e:e5:3e:79:20
Oct 30 11:10:25 michallo-laptop kernel: [26024.294492] wlan0: authenticated
Oct 30 11:10:25 michallo-laptop kernel: [26024.294501] wlan0: associate with AP 00:1e:e5:3e:79:20
Oct 30 11:10:25 michallo-laptop kernel: [26024.297143] wlan0: RX ReassocResp from 00:1e:e5:3e:79:20 (capab=0x431 status=0 aid=1)
Oct 30 11:10:25 michallo-laptop kernel: [26024.297157] wlan0: associated

Maybe it is related. I also have:
iwlagn: Can not allocate SKB buffers but it was hours before BUG: scheduling while atomic: swapper... appeared.
I use newest packages + linux-backports-modules. I will try now using laptop without linux-backports-modules

Well, the bug reappeared today, which makes me suspect that the graphics card may play a role. My laptop (ThinkPad T400) has both a discrete graphics card (ATi 3470 or something like that) and an onboard Intel chip (4500MHD). When I saw the bug last week, I had the Intel chip activated. Later, I changed to the ATi card and the bug disappeared. Today, I went back to the Intel chip, and there it is again.

Of course, Michal Koziorowski and Alex Willmer both have an nVidia graphics card according to their logs, which doesn't really support this theory.

Anyway, linux-backports-modules doesn't seem to resolve this bug (sorry for the false alarm above).

I am adding attachments gathered from my Dell Latitude D630 running Linux 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 (2.6.27.7.11) and linux-backports-modules-intrepid-generic 2.6.27.7.11.

* 10K lines from kern.log starting with the crash, which occurred immediately after I ran Add/Remove and failed to properly install "Active Directory Membership" (likewise-open) because I canceled configuration of "krb5-config" due to lack of kerberos information on hand. I was running on a wireless network at the time of the crash.

* lspci and lsmod

I've killed klogd and dd since they were filling up my /var/log folder and the system is running, but still logging plenty of messages to the console.

Same here using a Dell Latitude E6400 with an nvidia quadro 160M and an Intel WiFi 5100.
Bug always happen under heavy use of WPA wifi network.

Nov 1 22:04:09 ithil kernel: [ 2042.313640] BUG: scheduling while atomic: swapper/0/0x00000100
Nov 1 22:04:09 ithil kernel: [ 2042.313656] Modules linked in: ipv6 af_packet sco rfcomm bridge stp bnep l2cap bluetooth ppdev sbs sbshc container pci_slot acpi_cpufreq cpufreq_powersave cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_ondemand freq_table iptable_filter ip_tables x_tables sbp2 parport_pc lp parport arc4 ecb joydev crypto_blkcipher iwlagn iwlcore snd_hda_intel rfkill snd_pcm_oss led_class snd_mixer_oss dcdbas serio_raw mac80211 evdev snd_pcm psmouse snd_seq_dummy cfg80211 snd_seq_oss pcspkr nvidia(P) snd_seq_midi i2c_core sdhci_pci video snd_rawmidi output sdhci snd_seq_midi_event mmc_core wmi ricoh_mmc snd_seq battery button ac snd_timer snd_seq_device snd soundcore intel_agp agpgart snd_page_alloc shpchp pci_hotplug ext3 jbd mbcache sr_mod cdrom sd_mod crc_t10dif sg usbhid hid ahci libata scsi_mod dock ohci1394 uhci_hcd ehci_hcd ieee1394 e1000e usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse
Nov 1 22:04:09 ithil kernel: [ 2042.313848]
Nov 1 22:04:09 ithil kernel: [ 2042.313855] Pid: 0, comm: swapper Tainted: P (2.6.27-7-generic #1)
Nov 1 22:04:09 ithil kernel: [ 2042.313861] EIP: 0060:[<f885e800>] EFLAGS: 00000246 CPU: 1
Nov 1 22:04:09 ithil kernel: [ 2042.313878] EIP is at acpi_idle_enter_bm+0x268/0x2b7 [processor]
Nov 1 22:04:09 ithil kernel: [ 2042.313885] EAX: c0510760 EBX: 00000415 ECX: 00000000 EDX: 013f2000
Nov 1 22:04:09 ithil kernel: [ 2042.313890] ESI: 00000000 EDI: 0094f86a EBP: f7477f80 ESP: f7477f64
Nov 1 22:04:09 ithil kernel: [ 2042.313895] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Nov 1 22:04:09 ithil kernel: [ 2042.313901] CR0: 8005003b CR2: b6d13000 CR3: 00515000 CR4: 00000690
Nov 1 22:04:09 ithil kernel: [ 2042.313906] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Nov 1 22:04:09 ithil kernel: [ 2042.313911] DR6: ffff0ff0 DR7: 00000400
Nov 1 22:04:09 ithil kernel: [ 2042.313917] [<c02dbf7b>] cpuidle_idle_call+0x7b/0xd0
Nov 1 22:04:09 ithil kernel: [ 2042.313930] [<c010288d>] cpu_idle+0x7d/0x140
Nov 1 22:04:09 ithil kernel: [ 2042.313939] [<c037a661>] start_secondary+0x9d/0xcc
Nov 1 22:04:09 ithil kernel: [ 2042.313952] =======================
Nov 1 22:04:09 ithil kernel: [ 2042.313957] bad: scheduling from the idle thread!
Nov 1 22:04:09 ithil kernel: [ 2042.313964] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Nov 1 22:04:09 ithil kernel: [ 2042.313971] [<c037c406>] ? printk+0x1d/0x1f
Nov 1 22:04:09 ithil kernel: [ 2042.313980] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
Nov 1 22:04:09 ithil kernel: [ 2042.313988] [<c012107f>] dequeue_task+0xcf/0x130
Nov 1 22:04:09 ithil kernel: [ 2042.313998] [<c012112a>] deactivate_task+0x1a/0x30
Nov 1 22:04:09 ithil kernel: [ 2042.314006] [<c037ca23>] schedule+0x4b3/0x790
Nov 1 22:04:09 ithil kernel: [ 2042.314015] [<c012b6ab>] ? default_wake_function+0xb/0x10
Nov 1 22:04:09 ithil kernel: [ 2042.314025] [<c037e511>] ? _spin_l...

I'm am also seeing this same error. However I have only noticed it and can reproduce it by using WPA2. Killing klogd allows me to continue working. I am able to use my wireless card on all networks except those that are WPA2. Wired networking seems to be working just fine as well. If I also disable wireless networking completely, I don't see that problem.

I have an HP Elitebook 6930p
Wifi link 5100

I'm also on a WPA2 network, Dell inspiron 1720 with an intel wireless 4965. The problem seems to occur most often when there is a lot of wireless activity, but it is too sporadic to pin down exactly.

I'm using WPA2 too.

Even after disabling klogd, I get sporadic kernel panics (freeze and blinking keyboard leds) almost daily.

My wifi card, as reported by lspci, is a: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61).

It might be unimportant, but the emifreq-applet panel applet always abends on logon, but after choosing to reload it, it works well. I've attached my /proc/cpuinfo.

I use WPA2 Enterprise when this happens. My username is simple, but my password is long and includes many special characters. A verbose lspci of my wifi card is below. I also use a docking station, and network manager. Is anyone with this bug NOT using the Intel 4965AG, rev61?

What 'Type' of WPA2 are you all using?

My access point is some blue, NetGear, small business WAP. The same subnet is in use wirelessly and on the wired lan. What access points are we using?

Could this be some switching loop?

I will try to cause it with high network load. At home on WPA2 Personal, and Monday, at work.

On the topic of graphics cards, I'm using an Quadro FX 3600M vbios version 62.92.2b.00.03. Is anyone seeing this error without proprietary graphics drivers?

0c:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 4965 AG or
AGN Network Connection [8086:4229] (rev 61)
 Subsystem: Intel Corporation Device [8086:1120]
 Flags: bus master, fast devsel, latency 0, IRQ 10
 Memory at 00000000f1ffe000 (64-bit, non-prefetchable)
 Capabilities: [c8] Power Management version 3
 Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Count=1/1
Enable-
 Capabilities: [e0] Express Endpoint, MSI 00
 Capabilities: [100] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP-
ECRC- UnsupReq- ACSVoil-
  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP-
ECRC- UnsupReq- ACSVoil-
  UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+
ECRC- UnsupReq- ACSVoil-
  CESta: RxErr+ BadTLP+ BadDLLP- Rollover- Timeout- NonFatalErr-
  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
 Capabilities: [140] Device Serial Number ed-03-7c-ff-ff-3b-1f-00
 Kernel driver in use: iwlagn
 Kernel modules: iwlagn

01:00.0 VGA compatible controller [0300]: nVidia Corporation Device [10de:061c] (rev a2) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:019b]
 Flags: bus master, fast devsel, latency 0, IRQ 7
 Memory at f5000000 (32-bit, non-prefetchable)
 Memory at 00000000e0000000 (64-bit, prefetchable)
 Memory at 00000000f2000000 (64-bit, non-prefetchable)
 I/O ports at ef00
 Capabilities: [60] Power Management version 3
 Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable-
 Capabilities: [78] Express Endpoint, MSI 00
 Capabilities: [100] Virtual Channel <?>
 Capabilities: [128] Power Budgeting <?>
 Capabilities: [600] Vendor Specific Information <?>
 Kernel driver in use: nvidia
 Kernel modules: nvidia, nvidiafb

CPU:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz
stepping : 6
cpu MHz : 800.000
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl vmx est tm2 ssse3 cx16 xt...

02:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

I've checked my settings and I'm using only WPA, not WPA2. The pre-shared key doesn't have special characters and isn't excessively long.

The access point is a D-Link DIR-655 (http://www.dlink.com/products/?pid=530)

Regarding proprietary video drivers, I'm using the NVidia one.

01:00.0 VGA compatible controller: nVidia Corporation G86M [GeForce 8400M GT] (rev a1)
 Subsystem: Sony Corporation Device 9005
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at ce000000 (32-bit, non-prefetchable) [size=16M]
 Memory at d0000000 (64-bit, prefetchable) [size=256M]
 Memory at cc000000 (64-bit, non-prefetchable) [size=32M]
 I/O ports at 2000 [size=128]
 Capabilities: [60] Power Management version 2
 Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
 Capabilities: [78] Express Endpoint, MSI 00
 Capabilities: [100] Virtual Channel <?>
 Capabilities: [128] Power Budgeting <?>
 Capabilities: [600] Vendor Specific Information <?>
 Kernel driver in use: nvidia
 Kernel modules: nvidiafb, nvidia

Regarding WPA, I have been seeing the high load/scheduling while atomic, whilst using Wifi on a WPA PSK home router - the only wireless I use for an extended period.

I've switched to WEP 128 bit, I'll report on future occurrence of the symptoms

It's about a week after I've installed the linux-backports-modules and problem seems to be gone (at least it haven't occured ever since). In case the bug will occur I'll report it.

BTW I'm using 8.10 on Samsung Q310. As said before the bug seems to be connected with extensive use of WiFi (I use only Wifi with WPA right now) during extensive use (for me it occured mostly during fast download of torrents f.e. ubuntu iso). Below I enclose outcome of lspci (might be useful).

00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 9200M GS (rev a1)
02:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
06:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 13)

I've been cheering too soon... The bug is still here (just occured). Same scheme: WiFi, torrent download, the flooding started after some time from the begining of the download. One thing for sure that the bug occurs less often (f.e. I've downloaded ubuntu iso several times just to test it and nothing happened). One thing I've noticed is that I've never seen the problem during extensive use of the net by some other programs (e.g. Firefox with BBC iPlayer or other streaming media, updating the system what uses most of the bandwidth, Skype etc). Thus, maybe it's problem connected with the way that this programs use the threading mechanism (just a speculation though). I even switched from Transmission to Deluge to confirm that it isn't problem with the application, but as you can see it still happens.

ISSUE: Woke up to fan running, CPUs busy -- TOP showed 'dd' was consuming the CPU. Had to kill tasks 5007 and 5009 to save off enough info to file this report before rebooting. kern.log was over 2 GB in size and last logged events were from 5 hours earlier, the same sequence of 11 lines. Reboot was normal and issue is not reoccuring. Some detailed data is below.

Linux topol015 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 GNU/Linux

robb@topol015:~$ sudo ps auxf
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 5007 66.3 0.0 1940 548 ? R Nov01 347:50 /bin/dd bs 1 if /proc/kmsg of /var/run/klogd/kmsg
klog 5009 42.2 0.1 4240 2976 ? Ss Nov01 221:14 /sbin/klogd -P /var/run/klogd/kmsg

kill 5007
kill 5009

I think the key kern.log lines are these:

Nov 1 23:32:31 topol015 kernel: [ 78.808449] BUG: scheduling while atomic: swapper/0/0x00000100
Nov 1 23:32:31 topol015 kernel: [ 78.808466] Modules linked in: aes_i586 aes_generic af_packet binfmt_misc rfcomm bridge stp bnep sco l2cap bluetooth ppdev acpi_cpufreq cpufreq_ondemand cpufreq_userspace cpufreq_conservative cpufreq_stats freq_table cpufreq_powersave container sbs pci_slot sbshc iptable_filter ip_tables x_tables coretemp sbp2 parport_pc lp parport joydev snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm arc4 ecb crypto_blkcipher snd_seq_dummy snd_seq_oss sdhci_pci uvcvideo iwlagn sdhci iwlcore compat_ioctl32 iTCO_wdt psmouse videodev mmc_core rfkill serio_raw evdev v4l1_compat snd_seq_midi iTCO_vendor_support pcspkr snd_rawmidi led_class nvidia(P) ricoh_mmc mac80211 snd_seq_midi_event snd_seq cfg80211 i2c_core snd_timer snd_seq_device snd video wmi button ac output battery soundcore intel_agp agpgart snd_page_alloc shpchp pci_hotplug ext3 jbd mbcache sr_mod cdrom ata_generic sd_mod crc_t10dif sg ata_piix pata_acpi ahci ohci1394 libata r8169 ieee1394 scsi_mod dock uhci_hcd ehci_hcd usbcore therma
Nov 1 23:32:31 topol015 kernel: processor fan fbcon tileblit font bitblit softcursor fuse
Nov 1 23:32:31 topol015 kernel: [ 78.808688]
Nov 1 23:32:31 topol015 kernel: [ 78.808695] Pid: 0, comm: swapper Tainted: P (2.6.27-7-generic #1)
Nov 1 23:32:31 topol015 kernel: [ 78.808703] EIP: 0060:[<f886c582>] EFLAGS: 00000246 CPU: 0
Nov 1 23:32:31 topol015 kernel: [ 78.808720] EIP is at acpi_idle_enter_c1+0x72/0x88 [processor]
Nov 1 23:32:31 topol015 kernel: [ 78.808726] EAX: 009f4d34 EBX: 009f2876 ECX: 00000001 EDX: 009f4d34
Nov 1 23:32:31 topol015 kernel: [ 78.808732] ESI: f7445bdc EDI: f744581c EBP: c04a7f90 ESP: c04a7f88
Nov 1 23:32:31 topol015 kernel: [ 78.808738] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Nov 1 23:32:31 topol015 kernel: [ 78.808744] CR0: 8005003b CR2: b7ec60c0 CR3: 3581f000 CR4: 00000690
Nov 1 23:32:31 topol015 kernel: [ 78.808750] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Nov 1 23:32:31 topol015 kernel: [ 78.808755] DR6: ffff0ff0 DR7: 00000400
Nov 1 23:32:31 topol015 kernel: [ 78.808761] [<c02dbf7b>] cpuidle_idle_call+0x7b/0xd0
Nov 1 23:32:31 topol015 kernel: [ 78.808773] [<c010288d>] cpu_idle+0x7d/0x140
Nov 1 23:32:31 topol015 kerne...

We seem to be sharing very similar situations for WiFi stuff. I also have an Intel 4965AGN adapter (iwalgn driver). My computer is a notebook computer - the Asus F8SV-A1. Normally connecting (at home) to a D-Link DIR-655 router with wireless N. Security is WPA2.

For graphics I have the proprietary NVidia driver, but have encountered similar kernel panics with both available versions of that and with the free alternative.

My setup is quite different. 5100AGN, Linksys access point, WPA1 (PSK), Intel 4500MHD graphics card. My lspci -vv output is attached.

To add a somewhat different data point, I observed this bug report's problem on a Thinkpad W500, which has an Intel WiFi Link 5300 card managed by iwlagn, connecting to an 802.11bg AP (Verizon's Westell 7500) and using WPA2. My video card is Intel's GM45 integrated graphics (4500MHD). I doubt the characters in my WPA passphrase matter in this case, since it's hashed to a fixed-size key way before anything that seems to be going on in this bug. "lspci -vvnn" output attached.

Since this issue seems to occur only in connection with the iwlagn driver, I've forwarded this report to the intellinuxwireless upstream project:

http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1812

Have exactly the same problem with a Lenovo Thinkpad T61:
After upgrade from Ubuntu 8.04 to 8.10, sometimes the following procs are consuming 1 of my cpu cores
no problems with 8.04.

system also will hang couple of times a day, see bug 292569, don't know if this has something to do with it.

Top output:
 5466 root 20 0 1940 544 448 R 56% 0.0 1:01.15 dd
 5468 klog 20 0 3768 2568 444 R 40% 0.1 0:58.18 klogd

ps-list
root 8765 1 35 12:04 ? 00:03:38 /bin/dd bs 1 if /proc/kmsg of /var/run/klogd/kmsg
klog 8767 1 33 12:04 ? 00:03:28 /sbin/klogd -P /var/run/klogd/kmsg

thanks to the fact these daemons are single-treathed, only one core is fully busy, so I can work.

part of the messages and syslog file:

Nov 2 11:53:50 roland-ppt kernel: [ 396.774834] bad: scheduling from the idle thread!
Nov 2 11:53:50 roland-ppt kernel: [ 396.774842] Pid: 0, comm: swapper Not taint 9 ick+0x0nxl0[3le+0x4b3/0x790
Nov 2 11:53:50 roland-ppt kernel: [ 396.776504] [<c0380ff5>] ? notifier_call_chain+0x35/0x70
Nov 2 11:53:50 roland-ppt kernel: [ 396.776509] [<c014cd6>7/7k] deactivate_tas[o>7= ] deactivate__[o>7/7] de3[[.ainted 2.6.27-7-generic #1
Nov 2 11:53:50 roland-ppt kernel: [ 396.779379] [<c037c406>] ? printk+0x1d/0x1f
Nov 2 11:53:50 roland-ppt kernel: [ 396.779384] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
Nov 2 11:53:50 roland-ppt kernel: [ 396.779388] [<c012107f>] dequeue_task+0xcf/0x130
Nov 2 11:53:50 roland-ppt kernel: [ 396.779393] [<c012112a>] deactivate_task+0x1a/0x30
Nov 2 11:53:50 roland-ppt kernel: [ 396.779397] [<c037ca23>] schedule+0x4b3/0x790
Nov 2 11:53:50 roland-ppt kernel: [ 396.779400] [<c0380ff5>] ? notifier_call_chain+0x35/0x70
Nov 2 11:53:50 roland-ppt kernel: [ 396.779405] [<c0151b55>] ? clockevents_notify+0x35/0x80
Nov 2 11:53:50 roland-ppt kernel: [ 396.779423] [<f8875a43>] ? ticks_elapsed_in_us+0xb/0x4d [processor]
Nov 2 11:53:50 roland-ppt kernel: [ 396.779441] [<f88762d7>] ? acpi_state_timer_broadcast+0x36/0x39 [processor]
Nov 2 11:53:50 roland-ppt kernel: [ 396.779449] [<c0153d82>] ? tick_nohz_stop_idle+0x12/0x70
Nov 2 11:53:50 roland-ppt kernel: [ 396.779454] [<c0153e15>] ? tick_nohz_restart_sched_tick+0x35/0x180
Nov 2 11:53:50 roland-ppt kernel: [ 396.779458] [<c01028cd>] cpu_idle+0xbd/0x140
Nov 2 11:53:50 roland-ppt kernel: [ 396.779462] [<c037a661>] start_secondary+0x9d/0xcc

Find some identical problems which should be solved with Backports, following are installed on my PC:
linux-backports-modules-2.6.24-21-generic
linux-backports-modules-2.6.27-7-generic
linux-backports-modules-intrepid
linux-backports-modules-intrepid-generic

The same problems stay, with and withouth these backports

also removing the iwlagn module didn't give results, The lenovo T61 has the possibility to hardware-switch-off bluetooth and wireless, this also didn't give results.

regards Roland
Fenestras morituri erant, liber origo causidicus te salutant.

This problem also occurs on HP 6130b

top gives:
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 5429 root 20 0 1940 544 448 R 56 0.0 9:09.91 dd
 5431 klog 20 0 3624 2444 444 S 45 0.1 6:59.17 klogd

lspci gives:

root@amos:~# lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
02:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
85:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
86:02.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70)

Computer ends up freezing. Also this happens while I am plugged into the wired network (but wireless turned on). Turning wireless off doesn't solve error messages to syslog once started.

Syslog repeats:

Nov 3 16:07:15 amos kernel: [ 5096.172396] =======================
Nov 3 16:07:15 amos kernel: [ 5096.172429] bad: scheduling from the idle thread!
Nov 3 16:07:15 amos kernel: [ 50...

Problem is also occurring to me on my Toshiba A205-S4777 (also intel 4965agn) using WAP2. The wireless driver seems to have problems when resuming also.

Upstream pointed us to this patch:

http://marc.info/?l=linux-wireless&m=122547922114718&w=2

I've attached updated modules that contain the patch. Could someone who can reproduce this bug please check them out to see if they fix the issue? (please make sure that the linux-backports-modules package is NOT installed, as it takes precedence over the regular kernel module):

tar -xzf bug286285.tar.gz
sudo cp -b bug286285/* /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/

Hi, i find the same problem, but happens when i plug in the external-usb hard disk formatted in ntfs, i can't use it(the hard disk) because ubuntu 8.10 don't recognize it and dd & klogd are taking 100% of my cpu.! In /var/log/kern.log there is:

Nov 4 01:21:44 ben-laptop kernel: [ 2020.752120] sd 4:0:0:0: [sdb] Attached SCSI disk
Nov 4 01:21:44 ben-laptop kernel: [ 2020.755316] sd 4:0:0:0: Attached scsi generic sg2 type 0
Nov 4 01:21:44 ben-laptop kernel: [ 2020.982279] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2020.982300] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2020.984775] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2020.984792] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2020.991025] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2020.991040] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2020.997767] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2020.997782] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.000059] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.000073] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.002401] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.002416] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.003413] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.003423] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.004417] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.004427] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.005421] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.005431] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.006415] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.006425] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.007522] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.007532] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.008540] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.008550] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44 ben-laptop kernel: [ 2021.009515] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Nov 4 01:21:44 ben-laptop kernel: [ 2021.009525] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information
Nov 4 01:21:44...

Tom, if I use apt-get to remove backports and then try the patch, is that a clean test?

I removed backports, rebooted, then installed the patch per Tom's instructions, rebooted, and now I've rebooted several times.

I cannot reproduce the original problem. However, I can't shut down without hitting the wifi killswitch.

18:45 Shut down from Gnome
18:46 Hanging... hanging... (and will continue to hang)
18:47 Flip the Wi-Fi switch
18:48 Shutdown completes

/var/log/kern.log
Nov 3 18:42:30 topol015 kernel: [ 158.992820] type=1503 audit(1225766550.341:14): operation="socket_create" family="x25" sock_type="seqpacket" protocol=0 pid=6230 profile="/usr/sbin/cupsd"
Nov 3 18:45:44 topol015 kernel: [ 352.808577] apm: BIOS not found.
Nov 3 18:45:46 topol015 kernel: [ 355.263861] ip6_tables: (C) 2000-2006 Netfilter Core Team
Nov 3 18:47:15 topol015 kernel: [ 444.087373] iwlagn: Radio Frequency Kill Switch is On:
Nov 3 18:47:15 topol015 kernel: [ 444.087378] Kill switch must be turned off for wireless networking to work.
Nov 3 18:47:20 topol015 kernel: [ 449.308039] wlan0: No ProbeResp from current AP 00:1e:58:f3:26:e5 - assume out of range
Nov 3 18:47:20 topol015 kernel: [ 449.310549] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
Nov 3 18:47:20 topol015 kernel: [ 449.310727] mac80211-phy0: failed to remove key (0, 00:1e:58:f3:26:e5) from hardware (-5)
Nov 3 18:47:20 topol015 kernel: [ 449.317281] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
Nov 3 18:47:20 topol015 kernel: [ 449.317438] mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5)
Nov 3 18:48:31 topol015 kernel: Inspecting /boot/System.map-2.6.27-7-generic
Nov 3 18:48:31 topol015 kernel: Cannot find map file.
Nov 3 18:48:31 topol015 kernel: Loaded 70488 symbols from 101 modules.
Nov 3 18:48:31 topol015 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Nov 3 18:48:31 topol015 kernel: [ 0.000000] Initializing cgroup subsys cpu
Nov 3 18:48:31 topol015 kernel: [ 0.000000] Linux version 2.6.27-7-generic (buildd@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Oct 30 04:18:38 UTC 2008 (Ubuntu 2.6.27-7.15-generic)

/var/log/messages
Nov 3 18:42:30 topol015 kernel: [ 158.992815] type=1503 audit(1225766550.341:13): operation="socket_create" family="ash" sock_type="dgram" protocol=0 pid=6230 profile="/usr/sbin/cupsd"
Nov 3 18:42:30 topol015 kernel: [ 158.992820] type=1503 audit(1225766550.341:14): operation="socket_create" family="x25" sock_type="seqpacket" protocol=0 pid=6230 profile="/usr/sbin/cupsd"
Nov 3 18:45:40 topol015 bonobo-activation-server (robb-6323): could not associate with desktop session: Failed to connect to socket /tmp/dbus-8pCCuzghiS: Connection refused
Nov 3 18:45:44 topol015 kernel: [ 352.808577] apm: BIOS not found.
Nov 3 18:45:46 topol015 kernel: [ 355.263861] ip6_tables: (C) 2000-2006 Netfilter Core Team
Nov 3 18:47:15 topol015 kernel: [ 444.087373] iwlagn: Radio Frequency Kill Switch is On:
Nov 3 18:47:15 topol015 kernel: [ 444.087378] Kill switch must be turned off for wireless networking to work.
Nov 3 18:47:38 topol015 exiting on signal 15
Nov 3 18:48:31 topol015 syslogd 1.5.0#2ubuntu6: restart.
Nov 3 18:48:31 topol015 kernel: Inspecti...

My Lenovo T61 has the possibility to switch of blue-tooth and wireless (hardware-switch)
I'm running, for test, now 2 days without these problems, and without BT and Wireless of course.
Will now going for test Tom's patch (thanks for that)

regards Roland
Fenestras morituri erant, liber origo causidicus te salutant.

Robb, do a search in Synaptic for linux-backports. If none of the resulting packages are installed you are well to try the patched driver. I'm also trying it, the bug hasn't appeared yet.

Thank you Antonio. That helps assure me that the results I'm seeing apply to the patch. As also reported above, I now can't shutdown cleanly without hitting the wifi switch. I'm not certain whether this is a new behavior or heightened awareness of an existing issue.

for clarity's sake,

11 hours ago, I removed...
linux-backports-modules-intrepid
linux-backports-modules-intrepid-generic
linux-backports-modules-2.6.27-7-generic
...and followed that with a reboot. Then I patched and rebooted again. Then I rebooted several times and haven't seen the "scheduling" bug.

Currently synaptic shows no backports packages installed.

$ ls -lc --full-time Desktop/bug286285
total 4020
-rw-r--r-- 1 robb robb 1057703 2008-11-03 18:31:30.000000000 -0800 iwl3945.ko
-rw-r--r-- 1 robb robb 1076975 2008-11-03 18:31:30.000000000 -0800 iwlagn.ko
-rw-r--r-- 1 robb robb 1964712 2008-11-03 18:31:30.000000000 -0800 iwlcore.ko

$ ls -lc --full-time /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/
total 4396
-rw-r--r-- 1 root root 1057703 2008-11-03 18:31:35.000000000 -0800 iwl3945.ko
-rw-r--r-- 1 root root 125004 2008-11-03 18:31:35.000000000 -0800 iwl3945.ko~
-rw-r--r-- 1 root root 1076975 2008-11-03 18:31:35.000000000 -0800 iwlagn.ko
-rw-r--r-- 1 root root 129776 2008-11-03 18:31:35.000000000 -0800 iwlagn.ko~
-rw-r--r-- 1 root root 1964712 2008-11-03 18:31:35.000000000 -0800 iwlcore.ko
-rw-r--r-- 1 root root 111220 2008-11-03 18:31:35.000000000 -0800 iwlcore.ko~

$ modprobe --list | grep "iwlwifi"
/lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
/lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
/lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko

$ lsmod | grep "iwl"
iwlagn 99844 0
iwlcore 91972 1 iwlagn
rfkill 17176 2 iwlcore
led_class 12164 1 iwlcore
mac80211 216820 2 iwlagn,iwlcore
cfg80211 32392 3 iwlagn,iwlcore,mac80211

HTH & thanks everyone!

Hi, I'm using a Dell XPS M1330, with a graphic card nvidia 8400, a wifi Intel Pro wireless 4965.

I have exactly the same problem described, the files syslog.0 messeges.0 and kern.log.0 me almost 12GB dealing with the same message described above.

Using the kernel 2.6.27-7-generic and version of ubuntu is the intrepid ibex 64 bits.

uname -a
Linux m1330 2.6.27-7-generic #1 SMP Thu Oct 30 04:12:22 UTC 2008 x86_64 GNU/Linux

lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev a1)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)
09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

ifconfig
wlan0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
          inet addr:172.26.0.5 Bcast:172.26.0.15 Mask:255.255.255.240
          inet6 addr: fe80::221:5cff:XX43:XXXX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:9824 errors:0 dropped:0 overruns:0 frame:0
        ...

Nov 3 07:35:05 intrepid kernel: [35527.615957] Call Trace:
Nov 3 07:35:05 intrepid kernel: [35527.615959] [<ffffffff8023e06d>] dequeue_task_idle+0x2d/0x40
Nov 3 07:35:05 intrepid kernel: [35527.615961] [<ffffffff8023c436>] dequeue_task+0x96/0xe0
Nov 3 07:35:05 intrepid kernel: [35527.615964] [<ffffffff8023c4d3>] deactivate_task+0x23/0x30
Nov 3 07:35:05 intrepid kernel: [35527.615966] [<ffffffff80500685>] thread_return+0x108/0x3c3
Nov 3 07:35:05 intrepid kernel: [35527.615968] [<ffffffff8026d12e>] ? sched_clock_idle_wakeup_event+0xe/0x10
Nov 3 07:35:05 intrepid kernel: [35527.615971] [<ffffffff80210ecd>] cpu_idle+0xad/0x110
Nov 3 07:35:05 intrepid kernel: [35527.615974] [<ffffffff804f0446>] rest_init+0x66/0x70
Nov 3 07:35:05 intrepid kernel: [35527.615975]
Nov 3 07:35:05 intrepid kernel: [35527.616044] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Nov 3 07:35:05 intrepid kernel: [35527.616046]

#########################################################################
... This prints several thousand times within a brief second burst.
... Then nothing for about half an hour.
#########################################################################

Nov 3 07:35:05 intrepid kernel: [35527.616638] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Nov 3 07:35:05 intrepid kernel: [35527Nov 3 08:02:43 intrepid kernel: [37185.889585] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Nov 3 08:02:43 intrepid kernel: [37185.889587]
Nov 3 08:02:43 intrepid kernel: [37185.889588] Call Trace:
Nov 3 08:02:43 intrepid kernel: [37185.889592] [<ffffffff8023e06d>] dequeue_task_idle+0x2d/0x40
Nov 3 08:02:43 intrepid kernel: [37185.889594] [<ffffffff8023c436>] dequeue_task+0x96/0xe0
Nov 3 08:02:43 intrepid kernel: [37185.889597] [<ffffffff8023c4d3>] deactivate_task+0x23/0x30
Nov 3 08:02:43 intrepid kernel: [37185.889600] [<ffffffff80500685>] thread_return+0x108/0x3c3
Nov 3 08:02:43 intrepid kernel: [37185.889603] [<ffffffff80271612>] ? clockevents_notify+0x42/0xa0
Nov 3 08:02:43 intrepid kernel: [37185.889606] [<ffffffff80210ecd>] cpu_idle+0xad/0x110
Nov 3 08:02:43 intrepid kernel: [37185.889608] [<ffffffff804f0446>] rest_init+0x66/0x70
Nov 3 08:02:43 intrepid kernel: [37185.889610]
Nov 3 08:02:43 intrepid kernel: [37185.894344] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Nov 3 08:02:43 intrepid kernel: [37185.894345]

#########################################################################
... End result? a two log files with 1.7GB of data :/
#########################################################################

This affects the following:
   /var/log/messages
   /var/log/kern.log

Hardware Profile:
   HP DV2750ea
   Intel Wireless
   NVIDIA Graphics

Attachments:
   dmesg.log

Regards
Iain Bucław

Attached:
   lsmod

Regards
Iain Bucław

I've been running the patched driver for 48 hours: The dd/klog cpu hogging hasn't appeared, the consoles remain unspammed by error messages, and no kernel panic.
This bug usually appeared a few hours after booting, and turning off klogd only gave me a few hours more before a kernel panic. It felt like Windows 95. Now it looks stable again.

Tom,

I got the kern.log entry mentioned at https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990/comments/92 which is the patched (comment 85) behavior of that bug. The news is that I didn't use that patch, I used the patch from comment 52 in this bug.

The patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 has eased both problems, the scheduling report churning into kern.log and turns the wrong command queue hang into a log event.

The entry that I received is
Nov 4 12:13:33 topol015 kernel: [20559.634756] ------------[ cut here ]------------
Nov 4 12:13:33 topol015 kernel: [20559.634774] WARNING: at drivers/net/wireless/iwlwifi/iwl-tx.c:1196 iwl_tx_cmd_complete+0x2c9/0x2d0 [iwlcore]()
Nov 4 12:13:33 topol015 kernel: [20559.634781] wrong command queue 63, command id 0x0
Nov 4 12:13:33 topol015 kernel: [20559.634786] Modules linked in: aes_i586 aes_generic af_packet binfmt_misc rfcomm bridge stp bnep sco l2cap bluetooth ipv6 ppdev acpi_cpufreq cpufreq_ondemand cpufreq_userspace cpufreq_conservative cpufreq_stats freq_table cpufreq_powersave container sbs pci_slot sbshc iptable_filter ip_tables x_tables coretemp sbp2 parport_pc lp parport joydev snd_hda_intel arc4 ecb crypto_blkcipher snd_pcm_oss snd_mixer_oss snd_pcm iwlagn snd_seq_dummy iwlcore snd_seq_oss uvcvideo rfkill snd_seq_midi compat_ioctl32 led_class videodev snd_rawmidi psmouse mac80211 v4l1_compat snd_seq_midi_event serio_raw pcspkr evdev nvidia(P) snd_seq cfg80211 i2c_core snd_timer snd_seq_device sdhci_pci snd sdhci video output ricoh_mmc mmc_core battery wmi soundcore ac button iTCO_wdt iTCO_vendor_support intel_agp agpgart snd_page_alloc shpchp pci_hotplug ext3 jbd mbcache sr_mod cdrom ata_generic sd_mod crc_t10dif sg ata_piix ahci ohci1394 pata_acpi ieee1394 libata scsi_mod dock r8169 ehci_hcd uhci_hcd usbcore t
Nov 4 12:13:33 topol015 kernel: ermal processor fan fbcon tileblit font bitblit softcursor fuse
Nov 4 12:13:33 topol015 kernel: [20559.635009] Pid: 5617, comm: Xorg Tainted: P 2.6.27-7-generic #1
Nov 4 12:13:33 topol015 kernel: [20559.635016] [<c0131d65>] warn_slowpath+0x65/0x90
Nov 4 12:13:33 topol015 kernel: [20559.635035] [<c0234775>] ? apparmor_socket_recvmsg+0x15/0x20
Nov 4 12:13:33 topol015 kernel: [20559.635048] [<c02e5036>] ? __sock_recvmsg+0x66/0x80
Nov 4 12:13:33 topol015 kernel: [20559.635059] [<c02e512c>] ? sock_aio_read+0xdc/0x120
Nov 4 12:13:33 topol015 kernel: [20559.635069] [<f8d8ef49>] iwl_tx_cmd_complete+0x2c9/0x2d0 [iwlcore]
Nov 4 12:13:33 topol015 kernel: [20559.635094] [<c01b1f19>] ? do_sync_read+0xd9/0x120
Nov 4 12:13:33 topol015 kernel: [20559.635106] [<f8cb2a49>] iwl_rx_handle+0xd9/0x260 [iwlagn]
Nov 4 12:13:33 topol015 kernel: [20559.635125] [<f8cb469d>] iwl4965_irq_tasklet+0x1ad/0x2f0 [iwlagn]
Nov 4 12:13:33 topol015 kernel: [20559.635140] [<c01e1fce>] ? inotify_inode_queue_event+0xe/0xe0
Nov 4 12:13:33 topol015 kernel: [20559.635152] [<c0137258>] tasklet_action+0x78/0x100
Nov 4 12:13:33 topol015 kernel: [20559.635161] [<c0137682>] __do_softirq+0x92/0x120
Nov 4 12:13:33 topol015 kernel: [20559.635169] [<c013776d>] do_softirq+0x5d/0x60
Nov 4 12:13:33 top...

Tom, the patch fixed the problem for me.

06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

Robb,

Thanks for testing. I actually included the patch for bug #276990 in
the modules I posted in comment #52, which is why they fix both bugs.

Robb Topolski wrote:
> Tom,
>
> I got the kern.log entry mentioned at
> https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990/comments/92
> which is the patched (comment 85) behavior of that bug. The news is that
> I didn't use that patch, I used the patch from comment 52 in this bug.
>
> The patch at
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52
> has eased both problems, the scheduling report churning into kern.log
> and turns the wrong command queue hang into a log event.
>

Yesterday worked the whole day with the path, everything works fine now !
Tom, you are great !

regards Roland
Fenestras morituri erant, liber origo causidicus te salutant.

Tom Jaeger wrote:
> Upstream pointed us to this patch:
>
> http://marc.info/?l=linux-wireless&m=122547922114718&w=2
>
> I've attached updated modules that contain the patch. Could someone who
> can reproduce this bug please check them out to see if they fix the
> issue? (please make sure that the linux-backports-modules package is NOT
> installed, as it takes precedence over the regular kernel module):
>
> tar -xzf bug286285.tar.gz
> sudo cp -b bug286285/* /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/
>
> ** Attachment added: "bug286285.tar.gz"
> http://launchpadlibrarian.net/19312723/bug286285.tar.gz
>

I've been running the pathced modules under heavy WPA wifi use and the
kernel panic didn't show anymore. This patch seems to fix the problem
for me too (Intel 5100 wireless card on a dell latitude E6400).

Thank you!

I confirm. This patch fixed the problem for me.

Hello,

I have a different approach that has temporarily fixed the problem for me on my Sony Vaio SZ650N. I noticed the problem started after I disabled /etc/init.d/bluetooth from automatically starting at boot as well as disabling the bluetooth radio after booting. I checked lsmod and noticed that the bluetooth modules were still being loaded so I added btusb to /etc/modprobe.d/blacklist then rebooted. The problem disappeared. Maybe it is a relationship between the iwlagn and the btusb modules. I have not installed any of the patches from this report and it is an otherwise clean and current install of 8.10. I hope this helps.

Best regards!

Interesting,

Patrick, I always execute the following command when I log in:

gksudo -u root "bash -c 'echo disable > /proc/acpi/ibm/bluetooth'"

So it should stop the BT as well. However, after 2 days of uptime, the symptoms appeared again - lots of junk is being written into kern.log
P.S I use the intrepid and I DO NOT use the patched kernel at the moment. So the bug might not be related to BT at all?

SRU Justification

Impact: iwl4965 driver can oops when scanning for access points

Patch Description: Do not sleep during scan cancellation

Patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commit;h=8e80cc54c0b08f38cf1f9a66ebd96284b55f0d2f

Test Case: See bug description

David, I have created a boot script that runs the following at boot time automatically:

echo "0" > /sys/devices/platform/sony-laptop/bluetoothpower

This turns off the bluetooth radio but the modules seem to stay loaded. I blacklisted them as I mentioned before so as to prevent the modules from loading into the kernel and so far I haven't seen the junk apppear into kern.log. If I see it appear again I will post the details here.

Accepted into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I had a lockup this morning where the numlock, scroll-lock and "speed" switch light flashed repeatedly. The system was completely unusable including the power switch. I had to pull the power and battery to turn the laptop off. When I restarted, the bug re-appeared although not as intense as before. I will be testing the proposed patch now.

@ Martin Pitt

tried the "intrepid-proposed" , the problem is back after a couple of minutes :-(
the files are replaced by:
-rw-r--r-- 1 root root 125004 2008-11-04 22:01 iwl3945.ko
-rw-r--r-- 1 root root 1057703 2008-11-04 09:35 iwl3945.ko~
-rw-r--r-- 1 root root 129776 2008-11-04 22:01 iwlagn.ko
-rw-r--r-- 1 root root 1076975 2008-11-04 09:35 iwlagn.ko~
-rw-r--r-- 1 root root 111220 2008-11-04 22:01 iwlcore.ko
-rw-r--r-- 1 root root 1964712 2008-11-04 09:35 iwlcore.ko~
(the big-originals where from Tom's patch)

@ Martin Pitt

tried the "intrepid-proposed" , the problem is back after a couple of minutes :-(
the files are replaced by:
-rw-r--r-- 1 root root 125004 2008-11-04 22:01 iwl3945.ko
-rw-r--r-- 1 root root 1057703 2008-11-04 09:35 iwl3945.ko~
-rw-r--r-- 1 root root 129776 2008-11-04 22:01 iwlagn.ko
-rw-r--r-- 1 root root 1076975 2008-11-04 09:35 iwlagn.ko~
-rw-r--r-- 1 root root 111220 2008-11-04 22:01 iwlcore.ko
-rw-r--r-- 1 root root 1964712 2008-11-04 09:35 iwlcore.ko~
(the big-originals where from Tom's patch)
so am falling back to Tom's patch

I can confirm as well, that enabling bluetooth and btusb modules in my T61 does not help to prevent the hangups and sudden log writing activity. So I installed the patch Tom provided and I'll keep posted about any irregular HD/CPU activity.

I've seen the kernel hanging problem that Patrick described several times - everything freezes, even the ssh server, and the WLAN/bluetooth/caps locks keys flash, requiring a hard power cycle to reset things. Is it related to this problem though?

Hi Rocko,

The problem you are describing is https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990 and a patch was available for that problem.

But it gets better.

The patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 includes the patch from bug#276990 and so it eases both problems.

My suggestion today is to use the patch mentioned https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990 as testers who have tried today's "intrepid-proposed" fixed report that it is not helping.

Robb

Roland [2008-11-06 19:46 -0000]:
> tried the "intrepid-proposed" , the problem is back after a couple of minutes :-(

Sorry, the update was stuck in the NEW queue. I processed it now, it
should be available at archive.ubuntu.com in about 1.5 hours, and
within a day on the mirrors.

You need to test linux-image-2.6.27-8-generic (or -server). Beware
that this doesn't yet have linux-restricted-modules or
-backports-modules available, these will follow in a bit.

Is the patch available for amd64? I don't see 2.6.27-8 in proposed

Wow, here is something super weird that has just cropped up on my system. (I also do not have the patch applied since I'm on amd64).

[11545.731478] bad: scheduling from the idle thread!
[11545.731482] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
[11545.731484]
[11545.731485] Call Trace:
[11545.731489] [<ffffffff8023e06d>] dequeue_task_idle+0x2d/0x40
[11545.731491] [<ffffffff8023c436>] dequeue_task+0x96/0xe0
[11545.731493] [<ffffffff8023c4d3>] deactivate_task+0x23/0x30
[11545.731496] [<ffffffff80500685>] thread_return+0x108/0x3c3
[11545.731499] [<ffffffff8026d12e>] ? sched_clock_idle_wakeup_event+0xe/0x10
[11545.731502] [<ffffffff80210ecd>] cpu_idle+0xad/0x110
[11545.731505] [<ffffffff804f0446>] rest_init+0x66/0x70
[11545.731507]
[11545.731538] bad: scheduling from the idle thread!
[11545.731540] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
[11545.731542]
[11545.731542] Call Trace:
[11545.731544] [<ffffffff8023e06d>] dequeue_task_idle+0x2d/0x40
[11545.731547] [<ffffffff8023c436>] dequeue_task+0x96/0xe0
[11545.731549] [<ffffffff8023c4d3>] deactivate_task+0x23/0x30
[11545.731551] [<ffffffff80500685>] thread_return+0x108/0x3c3
[11545.731554] [<ffffffff8026d12e>] ? sched_clock_idle_wakeup_event+0xe/0x10
[11545.731556] [<ffffffff80210ecd>] cpu_idle+0xad/0x110
[11545.731558] [<ffffffff804f0446>] rest_init+0x66/0x70
[11545.731560]

...and so on for infinity. That mesage is repeating itself CONSTANTLY. In fact, it is happening to the point that my system log has consumed the entire / partition (/var/log is over 4 GB). Ran an apt cleanup to avoid disaster and the freed 250 MB was consumed in less than an hour. (Someone really needs to fix that issue with log files dominating space). The problem is causing incredible slowdowns and instability, and it probably isn't just the log at fault considering the horribly ugly looking error message. Lots of stuff in it, though, so I hope it's useful!
My only proprietary driver is for the video card, so I'll try resurrecting some space and switching to the free driver.

System Log viewer hangs and ultimately is force killed; I got that stuff via dmesg.

Curiously, this did not happen before. Was there a stable kernel update recently? (I wasn't watching the updates very closely).

Since I seem to have come across the big boss version of this problem, I guess I should share some more info. So that last message spams syslog and kern.log, found via dmesg. Those logs are way too big for any human (or machine, for that matter) to parse any other information out of them so we can just assume it is strictly that one problem. Attached is /var/log/debug.

Sorry about all the repeat posting. I hate to say I deleted my /var/log directory to get the system working well again. I checked through my history of packages upgraded by apt, for notable system things that could have created this new problem. I haven't been paying much attention to this recently so it could be anything:

Wednesday Nov 5, I upgraded:
linux-headers-2.6.27-7 (2.6.27-7.15) to 2.6.27-7.16
linux-headers-2.6.27-7-generic (2.6.27-7.15) to 2.6.27-7.16
linux-image-2.6.27-7-generic (2.6.27-7.15) to 2.6.27-7.16

Thursday Nov 6, I upgraded:
nvidia-96-modaliases (96.43.05-0ubuntu10) to 96.43.09-0ubuntu1

And 'my bad, I think I'm posting in the wrong bug report :O

Dylan, you've most probably got the correct bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52 has a patch that will ease the issue.

There is an update forthcoming in the "proposed" repository, but so far nobody has reported on it (it was still missing as of my last check a few hours ago). Read about it https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/73 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/80.

For my don't appear the update on "proposed" repository, I apply the patch
that anyone specify and this thread and seems that all work well now.
What's the name of update for check it again linux-image-2.6.27-8-generic
linux-headers-2.6.27-8-generic?

By §h@wæ
http://www.islatux.es

2008/11/8 Robb Topolski <email address hidden>

> Dylan, you've most probably got the correct bug report.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52
> has a patch that will ease the issue.
>
> There is an update forthcoming in the "proposed" repository, but so far
> nobody has reported on it (it was still missing as of my last check a
> few hours ago). Read about it
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/73
> and
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/80.
>
> --
> kernel 2.6.27-7-generic bug BUG: scheduling while atomic:
> swapper/0/0x00000100
> https://bugs.launchpad.net/bugs/286285
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Same here. I enabled the Proposed repository and was expecting for a linux-image-* package to appear in the updates after a refresh, but so far it hasn't. Retried just seconds ago.
I'm using the patch meanwhile, and the good news is that the bug hasn't appeared again.

The package you're looking for is, I think, linux-backports-modules-2.6.27-7-generic (2.6.27-7.6), not linux-image-whatever. Since I've installed that package (two or three resumes from suspend) I haven't had any problems.

The way I found the package was by filtering for upgradable packages in synaptic after enabling the -proposed repo. The only one that was kernel-related was the backports-modules package.

Or I could be all mixed up between -backports and -proposed and have gotten lucky so far. I looked again and I do see linux-image-2.6.27-8

linux-image-2.6.27-8-generic is looking good.

 > Beware that this doesn't yet have linux-restricted-modules or
 > -backports-modules available, these will follow in a bit.

Worth repeating.

I tried to apply only linux-image-2.6.27-8-generic and Synaptic let me do so without complaint. I booted into a low-res gdm. Then I went to apply all the other proposed and still ended up with graphics-related error messages and a low-res gnome. Ultimately I went back to 2.6.27-7 to System-Administration-Hardware and turned off the Restricted Nvidia driver, I then uninstalled and reinstalled linux-image-2.6.27-8-generic which fixed whatever dependencies I broke.

Now that I'm up, linux-image-2.6.27-8-generic is looking good.

So far linux-image 2.6.27-8 (amd64) is working fine.

@Robb Topolski: I used envyng to install the nvidia driver and it is working fine with this kernel. There's the envyng-qt version if you want the GUI or envyng -t (ie text mode) if you run from the kernel. I tried the qt version, rebooted, and it hadn't worked (I got the lowres warning); so I ran envyng -t from a console (ie via ctrl-alt-f2), installed the driver, rebooted, and hey presto, it all worked.

I've just got the freeze with flashing caps lock/num lock. To reboot I needed to use power button so was quite serious... :/ I haven't seen any particular reason or thing in the logs. I just get this sort of messages all the time (messaes, syslog, kern.log):

Nov 10 15:51:21 newdumolap kernel: [ 505.625162] Inbound IN=wlan0 OUT= MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=202.71.128.65 DST=192.168.1.3 LEN=95 TOS=0x00 PREC=0x00 TTL=107 ID=61278 PROTO=UDP SPT=10646 DPT=55575 LEN=75
Nov 10 15:51:21 newdumolap kernel: [ 505.770846] Inbound IN=wlan0 OUT= MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=137.222.10.55 DST=192.168.1.3 LEN=413 TOS=0x00 PREC=0x00 TTL=48 ID=44345 DF PROTO=TCP SPT=993 DPT=46920 WINDOW=49680 RES=0x00 ACK PSH URGP=0
Nov 10 15:51:27 newdumolap kernel: [ 512.176301] Inbound IN=wlan0 OUT= MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=89.77.212.69 DST=192.168.1.3 LEN=1500 TOS=0x00 PREC=0x00 TTL=49 ID=16264 DF PROTO=TCP SPT=51413 DPT=52243 WINDOW=65535 RES=0x00 ACK URGP=0
Nov 10 15:51:30 newdumolap kernel: [ 514.612723] Inbound IN=wlan0 OUT= MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 15:51:30 newdumolap kernel: [ 514.869275] Inbound IN=wlan0 OUT= MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 15:51:30 newdumolap kernel: [ 515.371863] Inbound IN=wlan0 OUT= MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 15:51:31 newdumolap kernel: [ 516.130154] Inbound IN=wlan0 OUT= MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 15:51:32 newdumolap kernel: [ 517.133522] Inbound IN=wlan0 OUT= MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 15:51:59 newdumolap kernel: [ 543.982282] Inbound IN=wlan0 OUT= MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=203.219.128.249 DST=192.168.1.3 LEN=1492 TOS=0x00 PREC=0x00 TTL=110 ID=27805 DF PROTO=TCP SPT=22585 DPT=60695 WINDOW=64816 RES=0x00 ACK URGP=0
Nov 10 15:52:21 newdumolap kernel: [ 565.768684] Inbound IN=wlan0 OUT= MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=137.222.10.55 DST=192.168.1.3 LEN=413 TOS=0x00 PREC=0x00 TTL=48 ID=38809 DF PROTO=TCP SPT=993 DPT=46920 WINDOW=49680 RES=0x00 ACK PSH URGP=0
Nov 10 15:52:25 newdumolap kernel: [ 569.521948] Inbound IN=wlan0 OUT= MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=74.192.8.134 DST=192.168.1.3 LEN=1500 TOS=0x00 PREC=0x00 TTL=44 ID=24899 DF PROTO=TCP SPT=8080 DPT=59175 WINDOW=65535 RES=0x00 ACK URGP=0
Nov 10 15:52:25 newdumolap kernel: [ 570.454386] Inbound IN=wlan0 OUT= MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=85.225.63.54 DST=192.168.1.3 LEN=43 TOS=0x00 PREC=0x40 TTL=49 ID=40900 DF PROTO=TCP SPT=6881 DPT=37173 WINDOW=23067 RES=0x00 ACK PSH URGP=0
Nov 10 15:52:26 newdumolap kernel: [ 570.536133] Inbound IN=wlan0 OUT= MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=72.177.235.169 DST=192.168.1.3 LEN=231 TOS=0x...

Jakub,

What was the date/time when the system locked up? You'll want to check your logs matching up those times to help figure out why the kernel panicked.

As to the printout you provided, those look like routine firewall logs. To get help with turning that off, see http://www.ubuntu.com/support/communitysupport for different ways to get help. If I had that logging problem and couldn't find the answer by searching, I might go to http://ubuntuforums.org/forumdisplay.php?f=336 and ask.

The time of the lock up was on 16:06. As I said here is nothing in the
logs. Every aforementioned log have message:

Nov 10 16:06:31 newdumolap kernel: [ 1416.138732] Inbound IN=wlan0 OUT=
MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00
TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 16:06:32 newdumolap kernel: [ 1417.146590] Inbound IN=wlan0 OUT=
MAC= SRC=192.168.1.3 DST=239.192.152.143 LEN=147 TOS=0x00 PREC=0x00
TTL=1 ID=0 DF PROTO=UDP SPT=44287 DPT=6771 LEN=127
Nov 10 16:06:36 newdumolap kernel: [ 1420.934073] Inbound IN=wlan0 OUT=
MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=79.173.31.87
DST=192.168.1.3 LEN=58 TOS=0x00 PREC=0x00 TTL=112 ID=18080 DF PROTO=TCP
SPT=33372 DPT=50557 WINDOW=16098 RES=0x00 ACK PSH URGP=0
Nov 10 16:06:44 newdumolap kernel: [ 1428.840973] Inbound IN=wlan0 OUT=
MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=79.173.31.87
DST=192.168.1.3 LEN=58 TOS=0x00 PREC=0x00 TTL=112 ID=18783 DF PROTO=TCP
SPT=33372 DPT=50557 WINDOW=16098 RES=0x00 ACK PSH URGP=0
Nov 10 16:06:54 newdumolap kernel: [ 1438.914986] Inbound IN=wlan0 OUT=
MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=75.157.153.91
DST=192.168.1.3 LEN=75 TOS=0x00 PREC=0x00 TTL=106 ID=12920 PROTO=UDP
SPT=7403 DPT=55575 LEN=55
Nov 10 16:06:54 newdumolap kernel: [ 1439.424686] Inbound IN=wlan0 OUT=
MAC=00:16:ea:d1:ba:c6:00:1e:2a:61:af:e8:08:00 SRC=85.217.178.210
DST=192.168.1.3 LEN=75 TOS=0x00 PREC=0x00 TTL=110 ID=57128 PROTO=UDP
SPT=17953 DPT=55575 LEN=55
Nov 10 16:08:01 newdumolap syslogd 1.5.0#2ubuntu6: restart.
Nov 10 16:08:01 newdumolap kernel: Inspecting
/boot/System.map-2.6.27-7-server
Nov 10 16:08:01 newdumolap kernel: Cannot find map file.
Nov 10 16:08:01 newdumolap kernel: Loaded 70900 symbols from 97 modules.
Nov 10 16:08:01 newdumolap kernel: [ 0.000000] Initializing cgroup
subsys cpuset
Nov 10 16:08:01 newdumolap kernel: [ 0.000000] Initializing cgroup
subsys cpu
Nov 10 16:08:01 newdumolap kernel: [ 0.000000] Linux version
2.6.27-7-server (buildd@palmer) (gcc version 4.3.2 (Ubuntu
4.3.2-1ubuntu11) ) #1 SMP Tue Nov 4 20:18:35 UTC 2008 (Ubuntu
2.6.27-7.16-server)
Nov 10 16:08:01 newdumolap kernel: [ 0.000000] BIOS-provided physical
RAM map:

So it just acts like normal reboot... Actually there were two lock ups
first was 15 min before and it looked exactly the same (in logs as
well). Both occured during high network activity.

Robb Topolski wrote:
> Jakub,
>
> What was the date/time when the system locked up? You'll want to check
> your logs matching up those times to help figure out why the kernel
> panicked.
>
> As to the printout you provided, those look like routine firewall logs.
> To get help with turning that off, see
> http://www.ubuntu.com/support/communitysupport for different ways to get
> help. If I had that logging problem and couldn't find the answer by
> searching, I might go to http://ubuntuforums.org/forumdisplay.php?f=336
> and ask.
>

This lockup seemed to random to me with no kernel errors or anything being reported in the logs. It's a hard freeze of the entire system with the only activity being the flashing lights on the computer. I was almost starting to think I was having the beginnings of a hardware failure but now someone else is experiencing it too.

Jakub and Patrick, this sounds like bug #276990.

I'm also getting these 'bad: scheduling from the idle thread!' entries that eventually exhaust the hard disk due to giant log file sizes in /var/log. The interesting thing is that it starts to happen only and immediately after I disable Wireless through the NetworkManager tray icon. Re-enabling Wireless doesn't fix the problem though, only reboot does. Another observation is that klogd begins to eat 50% of the dual core CPU when the problem starts. The machine is Lenovo T61p type 6460-D8G if it matters.

Thinkpad T61 I can confirm that this is a intel wireless 4965 bug related to WPA. I used to sporadically get this bug as far back as linux 2.6.25.10 custom complied on a Hardy system through 2.6.26.5 and now on a Intrepid system stock kernel. It started with the driver that added LED support, it doesn't matter whether LED support is enabled or not both cases triggered the bug. I only get it to happen while at work on a WPA wireless link, it never occurs at home on an unsecured network. I haven't been able to find a way to trigger it at will. My laptop has no bluetooth hardware.

Afrer stress testing (about 2 minutes) I realized that fix is not working for me. Kernel intrepid 2.6.27-8.17 + linux-backports-modules-2.6.27-8.7

Yesterday when I used kernel without l-b-m I havent got any errors.

That's not surprising at all, linux-backports-modules still has a buggy version of the driver. You should remove that package, it has other problems, too.

The version of linux-modules from intrepid-proposed seems to have resolved the issue for me (no issues after a day of use) and has not caused any further regressions. Turns out this bug also caused most of my other problems, such as with sleep and hibernate, and it being fixed has greatly improved performance.

I recommend releasing this soon since the issue affects a lot of users and is something of a black eye for Intrepid Ibex. The number of people I have noticed on Ubuntu Forums, for instance, with frequent kernel panics and enormous logs is mind boggling, and I have traced a few of them back to having iwlagn cards.

I have installed a new kernel 2.6.27.8 from interpid-proposed and the problem has gone. Thanks.

I still have this problem, though only after resume from suspend/hibernation despite having kernel
2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux

 dpkg -l |grep linux
ii linux-backports-modules-2.6.27-8-generic 2.6.27-8.7
ii linux-firmware 1.2
ii linux-headers-2.6.27-8 2.6.27-8.17
ii linux-image-2.6.27-8-generic 2.6.27-8.17
ii linux-libc-dev 2.6.27-8.17
ii linux-restricted-modules-2.6.27-8-generic 2.6.27-8.13
ii linux-restricted-modules-common 2.6.27-8.13

After patching my kernel with http://marc.info/?l=linux-wireless&m=122547922114718&w=2 and recompiling, the problem seams to be gone on my hp 8530w.

BTW, to fix the problems with RF kill I applied this 2 patches:
http://www.intellinuxwireless.org/bugzilla/attachment.cgi?id=1645
http://www.intellinuxwireless.org/bugzilla/attachment.cgi?id=1646

@aldebx re https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/103

What is your failure symptom after the suspend or hibernation?

aldebx, the bug is still present in the
linux-backports-modules-2.6.27-8-generic package. After removing this
package you should be fine.

aldebx wrote:
> I still have this problem, though only after resume from suspend/hibernation despite having kernel
> 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux
>
> dpkg -l |grep linux
> ii linux-backports-modules-2.6.27-8-generic 2.6.27-8.7

Thanks for replying Robb and Tom!
My failure symptom is exactly the one described in the bug description:
- both after suspend and hibernation
- syslog, messages and kernel.log in /var/log grow to 2Gb in size and more
- they have listed a recurrent error message which starts with "bad: scheduling from the idle thread! swapper tainted" and refers to iwlagn.
- program 'dd' then starts to intensively use the disk and the CPU (which should be a consequence of the huge size of the logs)

I did not know the problem was still present in linux-backports-modules-2.6.27-8, I'll try removing it.
However why not patching the backports as well?
Furthermore, shuldn't be the backport drivers more recent than the kernel ones? And if not shouldn't be the kernel ones attributed a higher priority when choosing which to load on behalf of the higher version number?

It appears to me that these two bugs are duplicates:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/295722

Removing linux-backports-modules-2.6.27-8 prevents me from connecting to a WPA access point.
Kern.log shows the following error:

wlan0: associated
wlan0: disassociating by local choice (reason=3)
wlan0: associate with AP xx:xx:xx:xx:xx:xx
wlan0: RX ReassocResp from xx:xx:xx:xx:xx:xx (capab=0x461 status=0 aid=1)

wlan0: associated
wlan0: disassociating by local choice (reason=3)
and so on cycling

By the way connecting to an unprotected network succeeds.
Installing again the backport modules restores this capability.

some more logs of the misbehaviour attached

I've applied the -8-generic kernel and backport modules from -proposed. It solves the constant "scheduling from the idle thread!" but I still got one "scheduling while atomic", and a couple of "attaching NULL sched-domain"s.

I haven't tried it after a resume, I'll do that tonight. dmesg logs attached.

2.6.27-8 fix working fine for me after a suspend and 24hrs solid torrenting over wlan, with the exception of the above "atomic" and "sched-domain" messages

I got the same problem (and the one with kernel panics from the intel wifi), but it seems to be solved too.

jems@jems-microlaptop:~$ dpkg -l | grep linux
ii linux-backports-modules-2.6.27-7-generic 2.6.27-7.4 Ubuntu supplied Linux modules for version 2.
ii linux-backports-modules-intrepid 2.6.27.7.11 Generic Linux backported drivers.
ii linux-backports-modules-intrepid-generic 2.6.27.7.11 Backported drivers for generic kernel image
ii linux-firmware 1.2 Firmware for Linux kernel drivers
ii linux-generic 2.6.27.7.11 Complete Generic Linux kernel
ii linux-image-2.6.27-7-generic 2.6.27-7.16 Linux kernel image for version 2.6.27 on x86
ii linux-image-generic 2.6.27.7.11 Generic Linux kernel image
ii linux-restricted-modules-2.6.27-7-generic 2.6.27-7.12 Non-free Linux kernel modules for version 2.
ii linux-restricted-modules-common 2.6.27-7.12 Non-free Linux 2.6.27 modules helper script
ii linux-restricted-modules-generic 2.6.27.7.11 Restricted Linux modules for generic kernels

Now I've got no more kern.log growing too fast, nor kernel panics caused by the wifi.

I also got the same problem (/var/log ate my hd and from time to time the system froze). After removing linux-restricted-modules and linux-backports and installing 2.6.27-8 from proposed everything is working fine again.

pierre@cyberiada:~$ lspci | grep Wireless
10:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

pierre@cyberiada:~$ uname -a
Linux cyberiada 2.6.27-8-generic #1 SMP Thu Nov 6 17:38:14 UTC 2008 x86_64 GNU/Linux

2.6.27-8 fixed the issue for me. rsynced lots of data over WLAN without troubles. That would have been impossible with -7.

2.6.27-8 didn't fix the problem for me, but disabling wifi worked out well. I also had several random kernel panics/freeze by day when using wifi, so I guess all of this is related, but since I don't know much about coding or kernel issues, tell me if I can help by giving more informations.
nicoco@keynux:~$ lspci | grep Wireless
05:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
nicoco@keynux:~$ uname -a
Linux keynux 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux
Tell me if I can do something useful !

2.6.27-8 has been reliable for me - I haven't had the kernel freeze or "scheduling while atomic" message ever since I installed it.

Occasionally under heavy system load, I've noticed the 'iwlagn cannot allocate SKB buffers' but it doesn't flood the log any more. (Having said that, gnome-system-log only ever shows "today's" logs now and nothing from previous days.)

@Nicoco: This bug seems fairly specific to Intel 4965 controllers, your 5100 sounds like it may be having a separate issue. I'd suggest searching for similar bugs which aren't duplicates of this one, and perhaps logging a new bug if you can't find existing reports of your issue.

Here is the info the Kernel Team needs to start with:
https://wiki.ubuntu.com/KernelTeamBugPolicies
the correct package to log bugs under for Hardy and Intrepid is "linux":
https://wiki.ubuntu.com/Bugs/FindRightPackage

Just happened for me today on kernel 2.6.27-8. But it was the first appearance of the bug for some time now. But the scheme is the same - high network load whilst downloading torrents. The difference was that this time the processor load was more noticeable then usual (today the system was 'chocking' while usually the load was high but it wasn't so straight forward).

@Jamie: The problem occurred on my Intel 5100 with kernel 2.6.27-7.

The update to 2.6.27-8 fixed it.

user@host:~$ lspci | grep Wireless
02:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100

@Jamie: I've found many bugs reporting kernel panics using intel wifi chips, is it really necessary that I file a new one ?
The interesting thing is that using ethernet solved my kernel panics, the /var/log/ growing and the dd process using the whole CPU. I attached the files concerning minimal information. I didn't use any wifi since my last reboot so the dmesg is "clean" from the repeating scheduler error. If needed, I can use wifi, wait for the bug and run some tests/logs for you before my PC crash (which happens soon or later when I use wifi).

Nicoco - Yes, you do need to report a new bug unless you are absolutely 100% certain that you are experiencing the same bug as the one described in the original bug description, otherwise your problem will not be fixed and you will just make this bug report even more confusing than it already is.

After looking at the warning message in your dmesg, I very much doubt you are experiencing the same bug as this one.

Nicco: it looks like all you need to do is uninstall linux-backports-modules, which contains an iwlagn module that doesn't have the fix yet. Please don't file a new bug report.

Removing linux-backports-module seems to work. After a few hours using wifi, no crash, no repeating message about the scheduler in the logs. So the bugs also occurs on 5100 chips.

Hi, I'm using 8.10 64bits on a Lenovo Y530 with a intel 5100 and nvidia 9500M GS card. I've got exactly the same bug than the others ones : dd and klogd eating all of one of my cpu core. My system is up to date and the bug seems only to occur when I'm using wpa2...
dmesg show me a lot of :

[ 1502.815644] Call Trace:
[ 1502.815651] [<ffffffff8023e06d>] dequeue_task_idle+0x2d/0x40
[ 1502.815656] [<ffffffff8023c436>] dequeue_task+0x96/0xe0
[ 1502.815662] [<ffffffff8023c4d3>] deactivate_task+0x23/0x30
[ 1502.815668] [<ffffffff80500685>] thread_return+0x108/0x3c3
[ 1502.815676] [<ffffffff80210ecd>] cpu_idle+0xad/0x110
[ 1502.815682] [<ffffffff804fd735>] start_secondary+0x97/0xc2
[ 1502.815686]
[ 1502.816047] bad: scheduling from the idle thread!
[ 1502.816053] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1

I've joined my dmesg log.
Btw I got strange behavior from times to times, kernel panic at boot (see dmesg.0), and sometimes the wireless card need to get a ifconfig wlan0 up before working...

Here is the dmesg.0. Actually it doesn't show any Kernel Panic but I'm sure it's one, my led are going on
and off and the screen is all black.

today, daid the reguler upgrade to Ubuntu 2.6.27-9-generic
problem's back!
so re-run the bugfix, it's also working fine for this kernel.
think the fixed kernel modules for iwlwifi are not in this kernel yet.

regards Roland

Same here...

Looks like the new module is only in the -8 kernel from -proposed, it's not in the changelogs for -9.

Looks like the -9 security update fixed a number of concerning-looking issues. Is that why our fix wasn't in it?

I tried reapplying the patch from comment 52 into the (-9 directories instead of -7) and wound up with a system with no wireless devices. (Fortunately that process left me with .ko~ backup files I could restore. Nice!)

Okay, (whew!)

1. so what do I do now to prevent kernel panics from burning up the computer or filling the disk?
2. when can I expect to trust system updates again?

Thanks,

Robb

I had the same problem and appear to have sorted it by updating the kernel. I added 'intrepid-proposed' to my update sources, pinned back to intrepid-updates by default (to stop everything upgrading), and upgraded just 'linux-generic' to the latest 2.6.27-10-generic version and have not seen this issue since.

  Linux shim 2.6.27-10-generic #1 SMP Fri Nov 21 19:19:18 UTC 2008 x86_64 GNU/Linux

I haven't experience any badness from this proposed kernel with a 8.10 on a Lenovo X301, YMMV.

/etc/apt/preferences
--------------------------------
Package: *
Pin: release a=intrepid-updates
Pin-Priority: 900

Package: *
Pin: release a=intrepid-proposed
Pin-Priority: 400
--------------------------------

Aaron.

Yes, the -9 is a security update of -7, it is not based on -8. -10 is the updated version of -8 with the security fixes from -9 included. So if you could test the -10 kernel from -proposed that would be most helpful. Please report back here.

-10 kernel from -proposed working great here, with heavy wlan usage both before and after a suspend. no dmesg module errors whatsoever

I confirm 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 works great, no more logs getting crazy!
Thanks devs!

WARNING: Error inserting iwlcore (/lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko): Invalid module format
FATAL: Error inserting iwlagn (/lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko): Invalid module format

kernel 2.6.27-7-generic 64b.

After applying Tom's patch to solve this problem, my wireless refused to work.
modprobe iwlagn gave above mentioned error.
Device: Intel Corporation PRO/Wireless 5300 AGN

I can confirm this bug on HP 8510w with ubuntu 64 bit.

nikolaj@frodo:/var/log$ uname -a
Linux frodo 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

Barnabas, please read comments. -9 doesn't have the fix applied. Install -10 from -prerelase and report if you still have problems.

I can confirm it, now solved with proposed updates and... also on fedora 10 beta. I have not cheched if they solved it in the release version.

Just for the record

I can confirm this bug, I'm running
2.6.27-9-generic
In Ubuntu Intrepid on a Sony Vaio VGN-TZ27GN. I have a newbie question: where is the prerelease repository and how do I add it?

On Tue, Dec 02, 2008 at 04:06:56PM -0000, NickTouik wrote:
> I can confirm this bug, I'm running
> 2.6.27-9-generic
> In Ubuntu Intrepid on a Sony Vaio VGN-TZ27GN. I have a newbie question: where is the prerelease repository and how do I add it?

I assume they mean the -proposed repository. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.

-apw

I began exhibiting these problems upgrading from gutsy to hardy to ibex the other day, and it got annoying fast. I updated a bit ago to the -10 kernel, and it's much better now. Thanks!

The only side-effect I'm seeing thus far is my thinkfinger/fingerprint hardware is broken and my wireless won't auto-connect any longer after a reboot or suspend/awake. It's a 4965, so i'm assuming it is affected somehow in all of this as you mention iwl specifically. The kernel and firmware blobs are included in the kernel releases, no? Are there separate iwl updates that need applied? Am I the only one seeing this?

Flicking off and on the wireless seems to get it going again. When Network Manager tries, I never see the driver actually attempt to connect to my ssid via iwconfig, though NM clearly says it's trying. After reloading the hardware via hotpug and the switch, NM connects to the ssid, and auths fine. I'll check it a bit more with another suspend or boot to see if the hardware probes properly. Dmesg shows some oddities, included as attachment - my ap is xx:xx...

Something is amiss as NM was perfect before this scheduler bug became an issue. Thoughts on if you believe this was a direct relation to the kernel changes?

I'm not at all sure what's up with the fingerprint reader either, it seems to probe just fine, but I get no response when I attempt "tf-tool --acquire", which normally I would. I was using a dev build of the driver, not the stock ubuntu package, so I'll try reapplying. This pretty much breaks anyone with a thinkpad or dell at moment using that driver.

Let me know if you'd like any specific info, I'd be happy to dig into it a bit more as the hardware switch will get annoying fast.

My wireless adapter is connecting smoothly after suspend. I did notice that NetworkManager took a bit longer than usual to detect my network and connect to it, but everything is as before for me except for the very visible absense of a kernel panic. I am running an Intel 4965 abgn card, too, aboard and Asus F8SV-A1 notebook.
The wifi status light still does not light up after resuming from sleep for me, as usual. Other people seem to report different outcomes with that light, so it could be some vendor-specific tweeks on my end.

Who were the changes in iwlagn supposed to benefit? I recall reading somewhere (perhaps here...) that the change was meant to help someone, with unexpected side-effects for some existing users. Is that true?
If so, we REALLY need to find some people who iwlagn worked for in Intrepid and ask them to apply the proposed update.

Further, I think it's important to stress that this patch should be pushed to stable ASAP and Ubuntu's images rebuilt (possibly after a few more bugs like this one are resolved). At the least, something Needs To Be added to the release notes. Shipping with a system crasher like this is very, very bad. Shipping with a system crasher like this after one month (let alone two) is suicidal.
With this bug it is entirely possible that someone could be installing Ubuntu from the live CD and have the thing kernel panic while writing to his MBR. That would be really bad.

I am using the -10 proposed kernel on a Lenovo X301 with Intel 5300 wifi. So I should be using the iwlagn module. It is working for me and no more kernel messages. Still not perfect though, the wifi interface does not come up after a suspend or hibernate. I have to do a

  sudo ifconfig wlan0 up

after any suspend or hibernate. I actually built it into a sleep.d script. Now I reliably get the interface back on resume/thaw.

As long as I bring up the interface fast enough, NetworkManager does reconnect me, though it takes it 10-20 seconds to start reconnecting me.

If I don't manually bring up the interface fast enough after a resume/thaw, I also find I need to restart NetworkManager to convince it to notice the wifi interface and reconnect.

As there seems to be some confusion about which kernels work / don't work, and I'm still finding new duplicates, I added a quick summary to the top of the bug report.

Please correct if any of the information is incorrect (this bug report is quite difficult to follow now)

+ ***Important summary for those experiencing this bug***
+ Kernel versions where this bug is fixed:
+ 1) 2.6.27-10 from intrepid-proposed

CORRECT

+ Kernel versions where this bug is NOT fixed (if you are running one of these, please upgrade to known working kernel):
+ 1) 2.6.27-7 from intrepid
+ 2) 2.6.27-9 from intrepid-updates and intrepid-security

CORRECT

+ If you are experiencing this bug, please remove the linux-backports-
+ modules packages too, as they don't contain a fix

I have read that here, but I can't vouch for it as I'm not running backports.

This bug has indeed been solved in 2.6.27-10-generic, how long for it to reach the Updates repository? This chipset and card are very common for the bug to remain in the default installation 8.10 almost two months already.
Sometimes the Live CD triggers this bug before the installation is finished.

If the change can't be pushed through fast enough because it needs more testing, what about disabling sysklogd on affected systems as a workaround?

Thanks for the temporary fix, I was experiencing this problem on a Intel Wifi Link 5100.

However, the update did not fix what I hoped was a related problem, namely, that my network connection is incredibly slow. I have tested my network speeds, with what is reported as a good-quality signal, and can't get any faster than one megabit. Other wireless devices on the same LAN do much better. Is there some known problem with the 5100, or should I be looking to get a new laptop (this is a new computer)?

(I know this isn't quite the right forum, but I know there's a number of 5100 users here. Thanks.)

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

According to http://packages.ubuntu.com/intrepid-updates/base/, this STILL isn't in the updates repository.

What's the hold up?

What has worked for me:
Go to "System->Administration->Software Sources".
Under the "Updates" tab, check "Pre-released updates (intrepid-proposed)"
and "Unsupported updates (intrepid-backports)".
Run updates.

On Tue, Jan 6, 2009 at 11:39 AM, Mikel Ward <email address hidden> wrote:

> According to http://packages.ubuntu.com/intrepid-updates/base/, this
> STILL isn't in the updates repository.
>
> What's the hold up?
>
> --
> kernel 2.6.27-7-generic bug BUG: scheduling while atomic:
> swapper/0/0x00000100
> https://bugs.launchpad.net/bugs/286285
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

What Mikel means is that this fix should be out of -proposed and into the main intrepid branch, so you don't have to run the -proposed kernel or -backports modules.

I avoid running -proposed updates unless there's a package I specifically know I need, I've had other things break in the past.

On Mon, Jan 5, 2009 at 7:22 PM, Super Jamie <email address hidden> wrote:

> What Mikel means is that this fix should be out of -proposed and into
> the main intrepid branch, so you don't have to run the -proposed kernel
> or -backports modules.

I very much agree with Mikel. This bug is the single reason I dropped
Ubuntu 8.10 and went back to 8.04 LTS.

I am very surprised that this bug persists in the 8.10 Live (and Install) CD
distributed from Ubuntu. Does Canonical lack resources to fix it? or, Is
this bug not considered priority? When should I plan to upgrade to 8.10?
In a month? Or, should I just wait for 9.04?

Cheers,
James

>
>
> I avoid running -proposed updates unless there's a package I
> specifically know I need, I've had other things break in the past.
>
> --
> kernel 2.6.27-7-generic bug BUG: scheduling while atomic:
> swapper/0/0x00000100
> https://bugs.launchpad.net/bugs/286285
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Exactly Jamie.

I'm fine, but I've had friends ask me about this problem, and it's silly that I should have to tell them to enable the -proposed repository.

I have the same problem as a user noted above with my log files being filled with the following...

Jan 8 19:30:36 media-linux kernel: [ 525.910359] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
Jan 8 19:30:36 media-linux kernel: [ 525.910367] sd 4:0:0:0: [sdb] Add. Sense: No additional sense information

for 100's of megabytes. The logs will continually grow until I kill dd and klogd

I have no wireless on my computer (a HP mediacenter 1170.uk) so not sure if this is exactly related.

I am running Intrepid an the bug occurs in kernel 27-9 and 27-11. No idea what to do.

First time I've ever been bitten doing an upgrade in Ubuntu.

Regards,

Paul

Paul,

On Thu, Jan 8, 2009 at 12:47 PM, pauliephonic <email address hidden>wrote:

> I am running Intrepid an the bug occurs in kernel 27-9 and 27-11. No
> idea what to do.

Did you see Mogwai's post on 5 Jan 2009?

---------- Forwarded message ----------
From: mogwai
Date: Mon, Jan 5, 2009 at 7:05 PM

What has worked for me:
Go to "System->Administration->Software Sources".
Under the "Updates" tab, check "Pre-released updates (intrepid-proposed)"
and "Unsupported updates (intrepid-backports)".
Run updates.

While this is less than ideal, I believe this quick and easy solution will
work for you. Please let us know if it doesn't.

Cheers,
James

I experienced this bug a few times (last one 5 min ago). Is there any ETA for kernel 2.6.27-10 reaching intrepid-updates repo? Enabling proposed repo is at best a workaround...

Greetings,
co0lingFir3

Are we being fooled here?

How does it come a bug that produces full cpu usage and a full root partition
does not get fixed since months?

That's exactly my point. I mean this is a blocker and therefore should be fixed asap. Is there any known issue with 2.6.27-10 or why isnt it released to intrepid-updates?

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commit;h=14d108b846d0b561a7def2f4734f112f6f2ce8ba

I have found that the patch that was supposed to fix this bug has been reverted.
But the link to the patch that supersedes it does not work.

I followed instructions exactly and it made no difference.

Should I even be posting in this thread or somewhere else? I don't have wireless LAN and am now on kernel 2.6.27-11. Is it possible to downgrade Ubuntu? Or do I have to do a full re-install? All older kernels have been removed from the system.

I have attached a stripped syslog. The file was originally over 50Mb (I stopped dd and klogd as soon as I logged in which stopped it from growing even larger)

I have removed any line that matched /sd 4:0:0:0/ with a ruby script, this was to remove all lines like:
>Jan 8 19:30:36 media-linux kernel: [ 525.910359] sd 4:0:0:0: [sdb] Sense Key : No Sense [current]
>Jan 8 19:30:36 media-linux kernel: [ 525.910367] sd 4:0:0:0: [sdb] Add. Sense: No additional sense
which filled up the log

As you can see from the log, the events were happening so often that the log file is corrupted, e.g.

>Jan 13 20:47:13 media-linux kernel: [ 264.719966] sd 4:0:0 [current]
>Jan 13 20:47:12 media-linux kernel: [ 264.367664] sd 4i [current]

that is, incomplete versions of the lines I was excluding.

There also seem to be a lot of errors in the log that wouldn't normally be there (perhaps explaining the long delay on the boot splash screen while X tries to get up and running) I assume these are caused by updates I have included in order to try and get the dd and klogd errors sorted.

Another question why is DD running at all? Is it not a disk data copying program?

Any advice (even where else to go to sort the issue) would be appreciated.

@pauliephonic: This bug is only for Intel Wireless LAN. /sd 4:0:0:0/ indicates a storage problem. Have a look around the rest of Launchpad for the text in your logs, Google also indicates some users on Fedora 10 are experiencing the same issue. This bug is completely unrelated to your issue.

Apologies, Bens comment way above with the same symptoms lead meto believe they were related.

regards,

Paul

The patch is still in the latest kernel source. Only the reference in the revert was broken:

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=commitdiff;h=4b14e44c5dc36bc963e4d26ba15b7e8988d91619

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=blob;f=drivers/net/wireless/iwlwifi/iwl-agn.c;h=3d5f2ba0d8782925f080c311b082561b14190177;hb=5f4cff12e701a09044f0a87d69e8a6f3dabe57ca#l3281

The revert was done to reapply the patch from the 2.6.27.7 stable patchset. It will get to updates hopefully soon now. There had been some regressions that needed fixing before that.

Thank you.

That was an explanation I was waiting for.

Is this fixed in 2.6.27-11-generic that has been released today?

It seems to be fixed for me with 2.6.27-11.

It also did not happen for me since version -11.

But the changelog does not mention this bug report.
And also it has not been marked as "fixed released" for intrepid.

This was released to intrepid-updates a while ago.