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:
** Description changed:
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
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
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.
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556471
Title:
Connecting an Osprey 2 Mini (USB
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556471
Title:
Connecting an
ais523, the issue you are reporting is an upstream one. Could you please
report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Greg Kroah-Hartman CC linux-usb)?
Please provide a direct URL to your post to the
$ 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
ais523, given the root issue of resets is still not addressed, and the
panics appear collateral damage from this, let the scope of this report
be the resets.
To clarify, could you please post the results of the following terminal command
when the device is working fine:
usb-devices
** Changed
** Tags removed: kernel-bug-exists-upstream-3.5 kernel-fixed-upstream
kernel-fixed-upstream-3.5
** Tags added: kernel-bug-exists-upstream-4.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556471
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
ais523, in order to allow additional upstream developers to examine the issue,
at your earliest convenience, could you please test the latest upstream kernel
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please
keep in mind the following:
1) The one to test is at the
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
Thanks. I found the update in question. (It seems that some HP BIOS
updates install on Linux, and others require Windows; luckily I had a
dual-boot setup available to install it.)
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
F.68
09/21/2015
I can confirm that the issue
ais523, you didn't see F.68 because HP interferes with the URL based on
browser agent string. You have to click to the right of "Software
available for your operating system:" the word "Change" to see other
options.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You
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,
ais523, as per http://support.hp.com/us-en/drivers/selfservice/hp-
pavilion-15-n200-notebook-pc-
series/6529948/model/6732721#Z7_3054ICK0K8UDA0AQC11TA930O2 an update to
your computer's buggy, insecure, and outdated BIOS is available (F.68).
If you update to this following
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)
ais523, thank you for reporting this and helping make Ubuntu better.
Could you please provide the full computer model as noted on the sticker
of the computer itself (not from the Bug Description)?
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Cut from Description.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog
** Description changed:
Steps to reproduce (happens > 50% of the time, but not every time):
- Turn on an Osprey 2 Mini
-
- Connect it to a
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: [
apport-collect has attached the requested files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556471
Title:
Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes
causes an
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)
24 matches
Mail list logo
