[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
I can no longer reproduce this bug. I assume it got fixed at some point, either intentionally or as a side effect of some other upstream change. Marking it as invalid – I assume that's the right status for bugs that can no longer be reproduced? ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Invalid Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. The issue was root caused to the device violating the Mass Storage protocol. Hence, the preferred way to resolve is the vendor provides updated firmware. WORKAROUND: echo 1bbb:f000:i | sudo tee /sys/module/usb_storage/parameters/quirks --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
OK, after discussion on the upstream mailing lists, we've concluded that the bug causing the reset loop is in the device itself (that it is failing to respect the USB protocols), but that the buggy part of the Osprey 2 Mini is related to installing the Windows and Mac OS X drivers, which aren't needed by Linux. It's possible to blacklist the buggy part (which does not work under Linux even when the reset loops don't happen) via changing a module parameter; this causes the buggy part (the driver installation) to fail, thus allowing the part that most users are using the device for (the Internet connection) to work. While the system is running, this can be achieved via the following command: $ echo 1bbb:f000:i | sudo tee /sys/module/usb_storage/parameters/quirks (The 1bbb:f000 is specific to the device in question, so it shouldn't have effects on other devices.) I've tested this on the mainline kernel, and it seems to prevent the bug from occurring. I suspect that the same would occur on Ubuntu kernels, but have not tested this yet (I can test it if you think that would be helpful). It might also be possible to set the parameter in question (usb_storage.quirks=1bbb:f000:i) via the kernel command line or configuration; I don't know of a method other than telling the bootloader to set it, which would be far too intrusive a solution for a problem that won't affect most users, but there might be a less intrusive one. This would have the advantage of preventing a crash (on an Ubuntu kernel) if the device were attached during boot. Eventually the Ubuntu kernel is likely to catch up to upstream, meaning that the impact would be much lower and people could just disconnect and reconnect the device to work around this situation. I think it might be worthwhile to get Ubuntu to set the parameter in question automatically in order to fix the bug. However, I'm not sure where the best place to set it would be. The obvious thing to do is to use /etc/sysctl.d, but unfortunately it only seems to affect /proc files rather than /sys files (and the /proc/sys tree and /sys trees are different). Alternatively, if it's possible to set default module arguments in the kernel configuration, that would be another good place. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Triaged Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubu
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Just as a followup: the workaround command I gave only works if the usb_storage module is already loaded. If it isn't loaded, you can write it like this: sudo modprobe usb_storage quirks=1bbb:f000:i Probably it's best to set a default parameter for the module, though, if that's possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Triaged Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. The issue was root caused to the device violating the Mass Storage protocol. Hence, the preferred way to resolve is the vendor provides updated firmware. WORKAROUND: echo 1bbb:f000:i | sudo tee /sys/module/usb_storage/parameters/quirks --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
My email to the mailing list is archived here: http://marc.info/?l =linux-usb=145812520514664=2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Triaged Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
I have sent the email. I will check the mailing list archives on occasion, and provide a link when it becomes available. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Triaged Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
$ usb-devices I've attached the output of the command. ** Attachment added: "output from usb-devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4600769/+files/usb-devices.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
OK, testing on the most recent mainstream kernel, 4.5.0, is now complete. The Ubuntu and kernel version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename: wily $ uname -a Linux tundra 4.5.0-040500-generic #201603140130 SMP Mon Mar 14 05:32:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux The bug is partially fixed, and partially present: - The reset loops still occur intermittently when the device is connected. - However, unplugging the device during a reset loop no longer causes a kernel panic or hang. (There isn't any observable "action that happens instead"; the device stops resetting but that isn't surprising, given that it's no longer physically connected to the computer.) I have used both fixed-upstream and exists-upstream tags because there is still a bug with recognising the device upstream, but the worst symptom (the panic) appears to have been fixed, leaving only a more minor symptom. (This is the same behaviour that I observed when running Ubuntu Vivid.) If this is incorrect, feel free to correct the tags. The syslog from this boot, on which I plugged and unplugged the device repeatedly, is attached. ** Attachment added: "syslog for repeated connection and disconnection on a mainstream kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4600707/+files/syslog ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.5 ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Thanks for your advice. I will test the recent mainstream kernels in a few days, but I am not able to do so immediately. I will leave the bug as incomplete until then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Incomplete Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Oh, and recovering from a reset loop spontaneously doesn't always happen, on an earlier occasion, I was stuck in a reset loop for several minutes before I decided to disconnect the device to see if, when and how the system would crash. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
id. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
The most recent BIOS offered via the page you linked was F.66. I updated my BIOS to that version: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date F.66 07/01/2014 After updating, I connected and disconnected the Osprey 2 Mini four times, with no crashes. Then I rebooted, connected it and got a reset loop, and disconnected it and got a system hang (Caps Lock was not flashing but the system did not respond to any input, not even Alt- SysRq-B, and I had to hold down the power button to shut it off). As such, I believe the BIOS update did nothing to prevent the bug occurring, and that the bug is still present. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
The sticker on the computer itself is reasonably cryptic: Product: F9E45EA#ABU Model: 15-n298sa I also checked the box the computer came in. It contains the same product and model numbers, and additionally the description "HP Pavilion 15 Notebook PC". ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Some more log files I got experimenting. Here's a kern.log excerpt for a successful (i.e. intended behaviour, no visible bug reproduction) connection of the device (I included every line from the relevant time period because I'm not 100% sure which are relevant): Mar 13 03:09:27 tundra kernel: [ 91.132481] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 13 03:09:27 tundra kernel: [ 91.245683] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 13 03:09:27 tundra kernel: [ 91.245689] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 13 03:09:27 tundra kernel: [ 91.245691] usb 3-1.2: Product: MobileBroadBand Mar 13 03:09:27 tundra kernel: [ 91.245693] usb 3-1.2: Manufacturer: Alcatel Mar 13 03:09:27 tundra kernel: [ 91.245695] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 13 03:09:27 tundra kernel: [ 91.338218] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 13 03:09:27 tundra kernel: [ 91.338719] scsi host6: usb-storage 3-1.2:1.0 Mar 13 03:09:27 tundra kernel: [ 91.338900] usbcore: registered new interface driver usb-storage Mar 13 03:09:27 tundra kernel: [ 91.354544] usbcore: registered new interface driver uas Mar 13 03:09:27 tundra kernel: [ 91.377716] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Mar 13 03:09:27 tundra kernel: [ 91.377752] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=8612 DPT=8610 LEN=24 Mar 13 03:09:27 tundra kernel: [ 91.388020] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Mar 13 03:09:27 tundra kernel: [ 91.388070] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=8612 DPT=8610 LEN=24 Mar 13 03:09:28 tundra kernel: [ 92.338460] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 13 03:09:28 tundra kernel: [ 92.339441] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 13 03:09:28 tundra kernel: [ 92.340452] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 13 03:09:28 tundra kernel: [ 92.350362] sr 6:0:0:1: [sr1] scsi-1 drive Mar 13 03:09:28 tundra kernel: [ 92.350592] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 13 03:09:28 tundra kernel: [ 92.350733] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 13 03:09:28 tundra kernel: [ 92.363363] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 13 03:09:28 tundra kernel: [ 92.444043] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 13 03:09:28 tundra kernel: [ 92.643995] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 13 03:09:35 tundra kernel: [ 99.016607] usb 3-1.2: USB disconnect, device number 3 Mar 13 03:09:35 tundra kernel: [ 99.245827] usb 3-1.2: new high-speed USB device number 4 using ehci-pci Mar 13 03:09:35 tundra kernel: [ 99.360175] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=0195 Mar 13 03:09:35 tundra kernel: [ 99.360181] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 13 03:09:35 tundra kernel: [ 99.360183] usb 3-1.2: Product: MobileBroadBand Mar 13 03:09:35 tundra kernel: [ 99.360185] usb 3-1.2: Manufacturer: Alcatel Mar 13 03:09:35 tundra kernel: [ 99.360187] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 13 03:09:35 tundra kernel: [ 99.382621] usb-storage 3-1.2:1.2: USB Mass Storage device detected Mar 13 03:09:35 tundra kernel: [ 99.382837] scsi host7: usb-storage 3-1.2:1.2 Mar 13 03:09:35 tundra kernel: [ 99.439524] usbcore: registered new interface driver cdc_ether Mar 13 03:09:35 tundra kernel: [ 99.467466] rndis_host 3-1.2:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.2, RNDIS device, 46:c4:64:00:d0:da Mar 13 03:09:35 tundra kernel: [ 99.467592] usbcore: registered new interface driver rndis_host Mar 13 03:09:35 tundra kernel: [ 99.484172] rndis_host 3-1.2:1.0 enx46c46400d0da: renamed from usb0 Mar 13 03:09:35 tundra kernel: [ 99.521306] IPv6: ADDRCONF(NETDEV_UP): enx46c46400d0da: link is not ready Mar 13 03:09:36 tundra kernel: [ 100.383747] scsi 7:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 13 03:09:36 tundra kernel: [ 100.384133] sd 7:0:0:0: Attached scsi generic sg2 type 0 Mar 13 03:09:36 tundra kernel: [ 100.391751] sd 7:0:0:0: [sdb] Attached SCSI removable disk Mar 13 03:09:36 tundra kernel: [ 100.462051] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1
[Kernel-packages] [Bug 1556471] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597149/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07
[Kernel-packages] [Bug 1556471] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597145/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597148/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597150/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597154/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not
[Kernel-packages] [Bug 1556471] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597151/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597153/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597152/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597147/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597141/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597142/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
apport-collect has attached the requested files. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra usb_modeswitch_dispatcher[11944]: Error: could not get description string "serial number" Mar
[Kernel-packages] [Bug 1556471] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597146/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597143/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra
[Kernel-packages] [Bug 1556471] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597144/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07
[Kernel-packages] [Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
apport information ** Tags added: apport-collected wily ** Description changed: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra usb_modeswitch_dispatcher[11944]: Error: could not get description string "serial number" Mar 11 20:37:07 tundra usb_modeswitch: switch device 1bbb:f000 on 003/003 Mar 11 20:37:07 tundra kernel: [20659.328319] scsi 6:0:0:0: rejecting I/O to offline device Mar 11 20:37:07 tundra kernel: [20659.328412] scsi 6:0:0:0: killing request Mar 11 20:37:13 tundra systemd-udevd[11969]: inotify_add_watch(9,
[Kernel-packages] [Bug 1556471] [NEW] Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Public bug reported: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra usb_modeswitch_dispatcher[11944]: Error: could not get description string "serial number" Mar 11 20:37:07 tundra usb_modeswitch: switch device 1bbb:f000 on 003/003 Mar 11 20:37:07 tundra kernel: [20659.328319] scsi 6:0:0:0: rejecting I/O to offline device Mar 11 20:37:07 tundra kernel: [20659.328412] scsi 6:0:0:0: killing request Mar 11 20:37:13 tundra systemd-udevd[11969]: inotify_add_watch(9, /dev/sdb, 10) failed: No such file or directory Mar 11 20:37:13 tundra kernel: [20665.683553] usb 3-1.2: USB disconnect, device number 3 Mar 11 20:37:14 tundra kernel:
