KVM switch cause a Oops and input devices loss

Bug #96476 reported by Arnaud Quette
4
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6-amd64-generic

having an USB KVM (mine is a Avocent SwitchView USB, 4 ports)

- boot the system,
- get an ssh access to monitor the log,
- switch to another box, using the KVM

there you are:
linux-amd64 kernel: [ 2094.596780] CR2: 0000000000000120
Mar 26 16:09:25 linux-amd64 kernel: [ 1954.313681] <6>usb 1-5: USB disconnect, address 8
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596449] PGD 400d067 PUD 45ec067 PMD 0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596455] CPU 0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596456] Modules linked in: binfmt_misc rfcomm l2cap bluetooth ppdev powernow_k8 cpufreq_ondemand cpufreq_powersave cpufreq_conservative cpufreq_stats freq_table cpufreq_userspace sony_acpi pcc_acpi tc1100_wmi dev_acpi container button sbs video i2c_ec dock ac asus_acpi battery backlight af_packet parport_pc lp parport fuse snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device psmouse snd soundcore pcspkr serio_raw i2c_nforce2 snd_page_alloc k8temp shpchp pci_hotplug i2c_core ipv6 tsdev joydev evdev ext3 jbd mbcache sg sr_mod cdrom sd_mod generic ata_generic usbhid hid b44 mii sata_nv libata scsi_mod ehci_hcd ohci_hcd usbcore thermal processor fan fbcon tileblit font bitblit softcursor vesafb cfbcopyarea cfbimgblt cfbfillrect capability commoncap
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596502] Pid: 2055, comm: khubd Not tainted 2.6.20-9-generic #2
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596505] RIP: 0010:[class_device_remove_attrs+11/80] [class_device_remove_attrs+11/80] class_device_remove_attrs+0xb/0x50
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596510] RSP: 0018:ffff81001b87bc40 EFLAGS: 00010282
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596513] RAX: 00000000fffffffe RBX: ffff810019dab580 RCX: ffffffff880636d0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596517] RDX: ffff810019cf5800 RSI: 485355fc89495441 RDI: ffff810019dab580
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596519] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596522] R10: 0000000000000001 R11: ffffffff80230640 R12: ffff810019dab580
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596524] R13: 0000000000000002 R14: 0000000000000000 R15: 0000000000000000
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596528] FS: 00002b1992b236f0(0000) GS:ffffffff80543000(0000) knlGS:0000000000000000
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596530] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596533] CR2: 0000000000000120 CR3: 0000000018f65000 CR4: 00000000000006e0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596536] Process khubd (pid: 2055, threadinfo ffff81001b87a000, task ffff81000130c820)
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596538] Stack: ffff810019dab580 ffff810019dab580 ffff810019dab590 ffffffff803a4e7b
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596545] ffff81001bd2e280 ffff810019dab580 ffff810019cf5800 0000000000000002
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596549] 0000000000000002 ffff810019cf5888 ffff81001a2f9ca0 ffffffff803a4ec9
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596553] Call Trace:
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596559] [class_device_del+299/368] class_device_del+0x12b/0x170
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596566] [class_device_unregister+9/32] class_device_unregister+0x9/0x20
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596587] [_end+128074410/2130539984] :usbcore:usbdev_notify+0x8a/0xa0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596592] [complete+64/96] complete+0x40/0x60
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596597] [notifier_call_chain+38/64] notifier_call_chain+0x26/0x40
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596604] [blocking_notifier_call_chain+63/112] blocking_notifier_call_chain+0x3f/0x70
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596619] [_end+128081236/2130539984] :usbcore:usb_notify_remove_device+0x24/0x40
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596632] [_end+128081337/2130539984] :usbcore:generic_disconnect+0x9/0x30
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596644] [_end+128051157/2130539984] :usbcore:usb_unbind_device+0x15/0x20
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596648] [__device_release_driver+145/192] __device_release_driver+0x91/0xc0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596653] [device_release_driver+56/96] device_release_driver+0x38/0x60
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596658] [bus_remove_device+137/176] bus_remove_device+0x89/0xb0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596664] [device_del+418/544] device_del+0x1a2/0x220
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596677] [_end+128027922/2130539984] :usbcore:usb_disconnect+0xc2/0x150
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596693] [_end+128031946/2130539984] :usbcore:hub_thread+0x43a/0xcd0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596699] [thread_return+0/255] thread_return+0x0/0xff
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596708] [autoremove_wake_function+0/48] autoremove_wake_function+0x0/0x30
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596724] [_end+128030864/2130539984] :usbcore:hub_thread+0x0/0xcd0
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596727] [keventd_create_kthread+0/144] keventd_create_kthread+0x0/0x90
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596733] [kthread+217/288] kthread+0xd9/0x120
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596738] [__call_usermodehelper+0/128] __call_usermodehelper+0x0/0x80
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596745] [child_rip+10/18] child_rip+0xa/0x12
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596749] [keventd_create_kthread+0/144] keventd_create_kthread+0x0/0x90
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596758] [kthread+0/288] kthread+0x0/0x120
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596762] [child_rip+0/18] child_rip+0x0/0x12
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596766]
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596767]
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596768] Code: 48 8b b5 20 01 00 00 48 85 f6 74 27 48 83 3e 00 74 21 bb 28
Mar 26 16:09:25 linux-amd64 kernel: [ 2094.596779] RSP <ffff81001b87bc40>

Revision history for this message
Adam Niedling (krychek) wrote :

What version of Ubuntu are you using? Is this still an issue?

Changed in linux-meta:
status: New → Incomplete
Revision history for this message
Arnaud Quette (aquette) wrote :

Hi Adam,

2008/11/6 Adam Niedling <email address hidden>:
> What version of Ubuntu are you using? Is this still an issue?
>
> ** Changed in: linux-meta (Ubuntu)
> Status: New => Incomplete
>

ooch, this goes back 1,5 year ago. I was running 6.10
I'm running Intrepid now, still with the same KVM, and this bug has disappeared (somewhere between 6.10 and 7.10, don't recall exactly)

I've attached an output log when switching using the KVM on Intrepid...
So you can safely close this bug.

thanks,
Arnaud
--
Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/

Revision history for this message
Adam Niedling (krychek) wrote :

Thanks. You can also change the status of any bug by clicking on their status.

Changed in linux-meta:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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