[arch-general] kernel 3.3 & khubd problem/freezing failed
linux 3.3 from testing - fully updated from test repo. I had plugged my cell phone in to usb - a few times in and out. After unplugging, I closed laptop lid - the sleep light which normally flashes then goes steady to indicate laptop is sleeping did not. I opened lid - and found khubd process at 100% cpu. In earlier kernels there were some problems with usb if I attempted to sleep a laptop with a USB device plugged in - but i thought there were some fixes to this problem. Anyway - this is what got recorded in system log: Where is the preferred place to report this? thanks! gene./ =========== system log for khubd problem ============================ Mar 20 18:08:55 lap3 kernel: [75845.892579] EXT4-fs (dm-0): re-mounted. Opts: commit=0 Mar 20 18:08:57 lap3 kernel: [75848.292547] PM: Syncing filesystems ... done. Mar 20 18:08:57 lap3 kernel: [75848.298398] PM: Preparing system for mem sleep Mar 20 18:09:19 lap3 kernel: [75849.834400] Freezing user space processes ... (elapsed 0.01 seconds) done. Mar 20 18:09:19 lap3 kernel: [75849.847519] Freezing remaining freezable tasks ... Mar 20 18:09:19 lap3 kernel: [75869.819451] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0 ): Mar 20 18:09:19 lap3 kernel: [75869.819457] khubd R running task 0 91 2 0x00000000 Mar 20 18:09:19 lap3 kernel: [75869.819459] ffff88030a4bda48 ffffffff8146ed06 ffffffff812f5dcc ffffffff816dba22 Mar 20 18:09:19 lap3 kernel: [75869.819462] ffff88030a420800 ffff88030a4bdfd8 ffff88030a4bdfd8 ffff88030a4bdfd8 Mar 20 18:09:19 lap3 kernel: [75869.819465] ffff880306188000 ffff88030a420800 ffffffff8189e150 0000000000000030 Mar 20 18:09:19 lap3 kernel: [75869.819467] Call Trace: Mar 20 18:09:19 lap3 kernel: [75869.819473] [<ffffffff8146ed06>] ? __schedule+0x436/0x910 Mar 20 18:09:19 lap3 kernel: [75869.819476] [<ffffffff812f5dcc>] ? vt_console_print+0x2cc/0x3b0 Mar 20 18:09:19 lap3 kernel: [75869.819479] [<ffffffff81050e77>] ? __call_console_drivers+0x97/0xb0 Mar 20 18:09:19 lap3 kernel: [75869.819481] [<ffffffff81079482>] ? up+0x32/0x50 Mar 20 18:09:19 lap3 kernel: [75869.819483] [<ffffffff81051159>] ? _call_console_drivers+0x49/0x70 Mar 20 18:09:19 lap3 kernel: [75869.819485] [<ffffffff8146f602>] preempt_schedule_irq+0x52/0x80 Mar 20 18:09:19 lap3 kernel: [75869.819488] [<ffffffff81470866>] retint_kernel+0x26/0x30 Mar 20 18:09:19 lap3 kernel: [75869.819491] [<ffffffff81060924>] ? lock_timer_base.isra.32+0x64/0x70 Mar 20 18:09:19 lap3 kernel: [75869.819493] [<ffffffff81060b32>] del_timer+0x42/0x150 Mar 20 18:09:19 lap3 kernel: [75869.819501] [<ffffffffa0685e25>] ? bt_printk+0x55/0x60 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819505] [<ffffffffa066afc6>] hci_conn_del+0x26/0x230 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819508] [<ffffffffa066b240>] hci_conn_hash_flush+0x70/0xc0 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819511] [<ffffffffa0667121>] hci_dev_do_close+0xa1/0x2c0 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819515] [<ffffffffa066922b>] hci_unregister_dev+0x5b/0x170 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819517] [<ffffffffa03c1c80>] btusb_disconnect+0x60/0xd0 [btusb] Mar 20 18:09:19 lap3 kernel: [75869.819529] [<ffffffffa00111e2>] usb_unbind_interface+0x52/0x180 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819533] [<ffffffff81313e2c>] __device_release_driver+0x7c/0xe0 Mar 20 18:09:19 lap3 kernel: [75869.819535] [<ffffffff81313ebc>] device_release_driver+0x2c/0x40 Mar 20 18:09:19 lap3 kernel: [75869.819536] [<ffffffff81313961>] bus_remove_device+0xe1/0x120 Mar 20 18:09:19 lap3 kernel: [75869.819539] [<ffffffff81311510>] device_del+0x120/0x1a0 Mar 20 18:09:19 lap3 kernel: [75869.819544] [<ffffffffa000ef6f>] usb_disable_device+0xaf/0x1d0 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819548] [<ffffffffa00073f8>] usb_disconnect+0x98/0x130 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819553] [<ffffffffa0009296>] hub_thread+0xa56/0x12e0 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819557] [<ffffffff81073d00>] ? abort_exclusive_wait+0xb0/0xb0 Mar 20 18:09:19 lap3 kernel: [75869.819561] [<ffffffffa0008840>] ? usb_remote_wakeup+0x40/0x40 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819563] [<ffffffff810733c3>] kthread+0x93/0xa0 Mar 20 18:09:19 lap3 kernel: [75869.819566] [<ffffffff81472464>] kernel_thread_helper+0x4/0x10 Mar 20 18:09:19 lap3 kernel: [75869.819568] [<ffffffff81073330>] ? kthread_freezable_should_stop+0x70/0x70 Mar 20 18:09:19 lap3 kernel: [75869.819570] [<ffffffff81472460>] ? gs_change+0x13/0x13 Mar 20 18:09:19 lap3 kernel: [75869.819581] Mar 20 18:09:19 lap3 kernel: [75869.819581] Restarting kernel threads ... done. Mar 20 18:09:19 lap3 kernel: [75869.819641] Restarting tasks ... done. Mar 20 18:09:19 lap3 kernel: [75869.829806] sdhci-pci 0000:0d:00.0: could not set regulator OCR (-22) Mar 20 18:09:19 lap3 kernel: [75869.829857] video LNXVIDEO:00: Restoring backlight state Mar 20 18:09:19 lap3 kernel: [75869.865629] sdhci-pci 0000:0d:00.0: could not set regulator OCR (-22) Mar 20 18:09:19 lap3 kernel: [75869.899151] sdhci-pci 0000:0d:00.0: could not set regulator OCR (-22) Mar 20 18:09:19 lap3 kernel: [75869.932325] sdhci-pci 0000:0d:00.0: could not set regulator OCR (-22) Mar 20 18:09:20 lap3 kernel: [75870.954441] EXT4-fs (sdb1): re-mounted. Opts: commit=0 Mar 20 18:09:20 lap3 kernel: [75870.956487] EXT4-fs (sda6): re-mounted. Opts: commit=0 Mar 20 18:09:20 lap3 kernel: [75870.958144] EXT4-fs (sdb2): re-mounted. Opts: commit=0 Mar 20 18:09:20 lap3 kernel: [75871.182979] EXT4-fs (dm-0): re-mounted. Opts: commit=0 Mar 20 18:09:20 lap3 NetworkManager[955]: <info> wake requested (sleeping: yes enabled: yes) Mar 20 18:09:20 lap3 NetworkManager[955]: <info> waking up and re-enabling... Mar 20 18:09:20 lap3 NetworkManager[955]: <info> (eth0): now managed Mar 20 18:09:20 lap3 NetworkManager[955]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 2 0 2]
I've not upgraded to this kernel yet, waiting for it to go into core. But
is it infact working other than this issue?
On Tue, Mar 20, 2012 at 5:08 PM, Genes MailLists
linux 3.3 from testing - fully updated from test repo.
I had plugged my cell phone in to usb - a few times in and out. After unplugging, I closed laptop lid - the sleep light which normally flashes then goes steady to indicate laptop is sleeping did not. I opened lid - and found khubd process at 100% cpu.
In earlier kernels there were some problems with usb if I attempted to sleep a laptop with a USB device plugged in - but i thought there were some fixes to this problem.
Anyway - this is what got recorded in system log:
Where is the preferred place to report this?
thanks!
gene./
=========== system log for khubd problem ============================
Mar 20 18:08:55 lap3 kernel: [75845.892579] EXT4-fs (dm-0): re-mounted. Opts: commit=0 Mar 20 18:08:57 lap3 kernel: [75848.292547] PM: Syncing filesystems ... done. Mar 20 18:08:57 lap3 kernel: [75848.298398] PM: Preparing system for mem sleep Mar 20 18:09:19 lap3 kernel: [75849.834400] Freezing user space processes ... (elapsed 0.01 seconds) done. Mar 20 18:09:19 lap3 kernel: [75849.847519] Freezing remaining freezable tasks ... Mar 20 18:09:19 lap3 kernel: [75869.819451] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0 ): Mar 20 18:09:19 lap3 kernel: [75869.819457] khubd R running task 0 91 2 0x00000000 Mar 20 18:09:19 lap3 kernel: [75869.819459] ffff88030a4bda48 ffffffff8146ed06 ffffffff812f5dcc ffffffff816dba22 Mar 20 18:09:19 lap3 kernel: [75869.819462] ffff88030a420800 ffff88030a4bdfd8 ffff88030a4bdfd8 ffff88030a4bdfd8 Mar 20 18:09:19 lap3 kernel: [75869.819465] ffff880306188000 ffff88030a420800 ffffffff8189e150 0000000000000030 Mar 20 18:09:19 lap3 kernel: [75869.819467] Call Trace: Mar 20 18:09:19 lap3 kernel: [75869.819473] [<ffffffff8146ed06>] ? __schedule+0x436/0x910 Mar 20 18:09:19 lap3 kernel: [75869.819476] [<ffffffff812f5dcc>] ? vt_console_print+0x2cc/0x3b0 Mar 20 18:09:19 lap3 kernel: [75869.819479] [<ffffffff81050e77>] ? __call_console_drivers+0x97/0xb0 Mar 20 18:09:19 lap3 kernel: [75869.819481] [<ffffffff81079482>] ? up+0x32/0x50 Mar 20 18:09:19 lap3 kernel: [75869.819483] [<ffffffff81051159>] ? _call_console_drivers+0x49/0x70 Mar 20 18:09:19 lap3 kernel: [75869.819485] [<ffffffff8146f602>] preempt_schedule_irq+0x52/0x80 Mar 20 18:09:19 lap3 kernel: [75869.819488] [<ffffffff81470866>] retint_kernel+0x26/0x30 Mar 20 18:09:19 lap3 kernel: [75869.819491] [<ffffffff81060924>] ? lock_timer_base.isra.32+0x64/0x70 Mar 20 18:09:19 lap3 kernel: [75869.819493] [<ffffffff81060b32>] del_timer+0x42/0x150 Mar 20 18:09:19 lap3 kernel: [75869.819501] [<ffffffffa0685e25>] ? bt_printk+0x55/0x60 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819505] [<ffffffffa066afc6>] hci_conn_del+0x26/0x230 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819508] [<ffffffffa066b240>] hci_conn_hash_flush+0x70/0xc0 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819511] [<ffffffffa0667121>] hci_dev_do_close+0xa1/0x2c0 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819515] [<ffffffffa066922b>] hci_unregister_dev+0x5b/0x170 [bluetooth] Mar 20 18:09:19 lap3 kernel: [75869.819517] [<ffffffffa03c1c80>] btusb_disconnect+0x60/0xd0 [btusb] Mar 20 18:09:19 lap3 kernel: [75869.819529] [<ffffffffa00111e2>] usb_unbind_interface+0x52/0x180 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819533] [<ffffffff81313e2c>] __device_release_driver+0x7c/0xe0 Mar 20 18:09:19 lap3 kernel: [75869.819535] [<ffffffff81313ebc>] device_release_driver+0x2c/0x40 Mar 20 18:09:19 lap3 kernel: [75869.819536] [<ffffffff81313961>] bus_remove_device+0xe1/0x120 Mar 20 18:09:19 lap3 kernel: [75869.819539] [<ffffffff81311510>] device_del+0x120/0x1a0 Mar 20 18:09:19 lap3 kernel: [75869.819544] [<ffffffffa000ef6f>] usb_disable_device+0xaf/0x1d0 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819548] [<ffffffffa00073f8>] usb_disconnect+0x98/0x130 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819553] [<ffffffffa0009296>] hub_thread+0xa56/0x12e0 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819557] [<ffffffff81073d00>] ? abort_exclusive_wait+0xb0/0xb0 Mar 20 18:09:19 lap3 kernel: [75869.819561] [<ffffffffa0008840>] ? usb_remote_wakeup+0x40/0x40 [usbcore] Mar 20 18:09:19 lap3 kernel: [75869.819563] [<ffffffff810733c3>] kthread+0x93/0xa0 Mar 20 18:09:19 lap3 kernel: [75869.819566] [<ffffffff81472464>] kernel_thread_helper+0x4/0x10 Mar 20 18:09:19 lap3 kernel: [75869.819568] [<ffffffff81073330>] ? kthread_freezable_should_stop+0x70/0x70 Mar 20 18:09:19 lap3 kernel: [75869.819570] [<ffffffff81472460>] ? gs_change+0x13/0x13 Mar 20 18:09:19 lap3 kernel: [75869.819581] Mar 20 18:09:19 lap3 kernel: [75869.819581] Restarting kernel threads ... done. Mar 20 18:09:19 lap3 kernel: [75869.819641] Restarting tasks ... done. Mar 20 18:09:19 lap3 kernel: [75869.829806] sdhci-pci 0000:0d:00.0: could not set regulator OCR (-22) Mar 20 18:09:19 lap3 kernel: [75869.829857] video LNXVIDEO:00: Restoring backlight state Mar 20 18:09:19 lap3 kernel: [75869.865629] sdhci-pci 0000:0d:00.0: could not set regulator OCR (-22) Mar 20 18:09:19 lap3 kernel: [75869.899151] sdhci-pci 0000:0d:00.0: could not set regulator OCR (-22) Mar 20 18:09:19 lap3 kernel: [75869.932325] sdhci-pci 0000:0d:00.0: could not set regulator OCR (-22) Mar 20 18:09:20 lap3 kernel: [75870.954441] EXT4-fs (sdb1): re-mounted. Opts: commit=0 Mar 20 18:09:20 lap3 kernel: [75870.956487] EXT4-fs (sda6): re-mounted. Opts: commit=0 Mar 20 18:09:20 lap3 kernel: [75870.958144] EXT4-fs (sdb2): re-mounted. Opts: commit=0 Mar 20 18:09:20 lap3 kernel: [75871.182979] EXT4-fs (dm-0): re-mounted. Opts: commit=0 Mar 20 18:09:20 lap3 NetworkManager[955]: <info> wake requested (sleeping: yes enabled: yes) Mar 20 18:09:20 lap3 NetworkManager[955]: <info> waking up and re-enabling... Mar 20 18:09:20 lap3 NetworkManager[955]: <info> (eth0): now managed Mar 20 18:09:20 lap3 NetworkManager[955]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 2 0 2]
On Tue, Mar 20, 2012 at 09:14:36PM -0700, Mr Destruction wrote:
I've not upgraded to this kernel yet, waiting for it to go into core. But is it infact working other than this issue?
Let's hope it breaks in other, yet more interesting ways. :) cheers! mar77i
On 03/21/2012 12:14 AM, Mr Destruction wrote:
I've not upgraded to this kernel yet, waiting for it to go into core. But is it infact working other than this issue?
Yes its working very well (aside from this one issue). testing on 3 desktops and 1 laptop ... gene
On Wed, Mar 21, 2012 at 11:30 AM, Genes MailLists
On 03/21/2012 12:14 AM, Mr Destruction wrote:
I've not upgraded to this kernel yet, waiting for it to go into core. But is it infact working other than this issue?
Yes its working very well (aside from this one issue). testing on 3 desktops and 1 laptop ...
There is also a known problem with btrfs (where your fs sometimes appears to be out of space, even though it is not). -t
On 03/21/2012 06:37 AM, Tom Gundersen wrote:
There is also a known problem with btrfs (where your fs sometimes appears to be out of space, even though it is not).
There is also a reported issue with ASPM - I seem not to have a problem even tho lspci -vvv | egrep ASPM shows it enabled for me. https://lkml.org/lkml/2012/3/19/227 gene
On 03/21/2012 06:53 AM, Genes MailLists wrote:
Followup with another crash: Today when I closed laptop lid to sleep it - I got an oops. Appears this is really from bluetooth not usb. I took a pic of the oops which starts with: BUG: unable to handle kernel paging request ........... raw_spin_lock_irq_save+xxx khubd tainted (from vbox which had not been run even tho module was loaded) ... btusb_disconnect ... ... usb_unbind_inteface .. .. etc. I can upload the cell phone image of the oops - or I can report upstream - what is the preferred way to proceed? This seems to happen at end of day after at 1 sleep/resume and using bluetooth. gene
On 03/21/2012 11:56 PM, Genes MailLists wrote:
To add to this - I get an oops on shutdown as well. Fresh boot and sleep/shutdown is not a problem. It seems to need aging and oddly happens only at work (so far). Work has 802.11 wifi (not N) and a different Bluetooth mouse - and I occasionally charge my cell via usb but not always ... no response to above bz.
Am 27.03.2012 14:00, schrieb Genes MailLists:
On 03/21/2012 11:56 PM, Genes MailLists wrote:
To add to this - I get an oops on shutdown as well. Fresh boot and sleep/shutdown is not a problem. It seems to need aging and oddly happens only at work (so far). Work has 802.11 wifi (not N) and a different Bluetooth mouse - and I occasionally charge my cell via usb but not always ... no response to above bz.
Yes, there is some oops concerned with bluetooth at shutdown. I get so many small bugs, that we should absolutely wait for 3.3.1 before pushing any further.
On 03/27/2012 08:22 AM, Thomas Bächler wrote:
Yes, there is some oops concerned with bluetooth at shutdown. I get so many small bugs, that we should absolutely wait for 3.3.1 before pushing any further.
Yes definitely agreed.
participants (5)
-
Genes MailLists
-
Martti Kühne
-
Mr Destruction
-
Thomas Bächler
-
Tom Gundersen