Installing Xubuntu 15.04 to boot in UEFI non-secure mode has some
challenges of it's own. But once I got the system working, it doesn't
freeze anymore.
If you want to use legacy BIOS mode, you'll have to compile a kernel.
However, it is not necessary to apply the patch above. Just disable the
USB
The cause of the freeze seems to be a BIOS problem, as Alan suggested on
the linux-usb mailing list. When booting in UEFI mode (from a Xubuntu
15.04 installation medium), three of the devices listed by lspci are
missing, compared to legacy BIOS mode. One of those is the device that
caused the freez
** Attachment added: "output of lspci when booting in legacy BIOS mode"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4474852/+files/lspci-legacy.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
contents of /sys/kernel/debug/usb/ehci/:00:1d.0/registers before unbinding:
bus pci, device :00:1d.0
EHCI Host Controller
EHCI 1.00, rh state running
ownership 0001
SMI sts/enable 0xc008
structural params 0x0028
capability params 0x00036881
status 6008 Periodic Recl FLR
command
contents of /sys/kernel/debug/usb/ehci/:00:1d.0/registers before unbinding
the bus which triggers the freeze:
bus pci, device :00:1d.0
EHCI Host Controller
EHCI 1.00, rh state suspended
ownership 0101 linux
SMI sts/enable 0xe000
structural params 0x0028
capability params 0x0003
I removed the bios-outdated tag. The guy who wrote about his BIOS update
in comment #9 has a completely different problem and commented off-
topic.
** Tags removed: bios-outdated-1.13
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Current state of things: I've tracked down the code line where the
freeze happens. It's in function ehci_halt within file ehci-hcd.c. The
function is executed on shutdown as well as when the usb devices on the
bus are about to be probed again. The latter is triggered by "lsusb -v"
as root. Apparent
For the records, here's a screenshot (photo) of the system after a freeze.
Series of actions to get there:
1. enable kernel debug output
2. detach external mouse, to verify that messages appear
3. hit enter to get a new prompt line
4. trigger the freeze with "lsusb -v"
lsusb prints the name of the
** Attachment added: "photo of the virtual terminal after the freeze"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4458832/+files/screenshot-freeze.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
Sorry, the link in comment #14 is nonsense, a paste error.
The new way to trigger a freeze is:
echo :00:1d.0 >/sys/bus/pci/drivers/ehci-pci/unbind
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Sorry, the link in comment #14 is nonsense, a paste error.
The new way to trigger a freeze is:
echo :00:1d.0 >/sys/bus/pci/drivers/ehci-pci/unbind
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
As suggested by Alan Stone on the linux-usb mailing list, I've verified
that the "USB cable is bad" messages are caused by the order in which
the USB devices are initialized.
I've also found a new way of triggering the freeze on a bad kernel:
https://bugs.freedesktop.org/show_bug.cgi?id=76935#c1
The previous log for the "bad" kernel was incomplete, due to kernel
buffer overflows caused by systemd output. I've switched that off as
explained here: https://bugs.freedesktop.org/show_bug.cgi?id=76935#c1
** Bug watch added: freedesktop.org Bugzilla #76935
https://bugs.freedesktop.org/show_b
Valentine, your problem is almost certainly not related to the one I reported
here.
You should seek advice in forums or on mailing lists for your computer and/or
distribution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
As suggested on the linux.usb mailing list, I've added some additional debug
print statements to the first bad kernel. They are not triggered by "lsusb -v"
though. I'm attaching kernel debug output from the boot sequence of two kernels:
- the bad one, with additional print statements
- the last g
** Attachment added: "last good kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4456919/+files/dmesg.good.full.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
I've verified that the freeze on shutdown is caused by the same commit.
Contrary to my initial report here, the freeze on shutdown happens late in the
sequence, not early.
I'm used to much longer shutdown times from my desktop :-)
** Summary changed:
- "lsusb -v" as root freezes the kernel on A
As requested on the linux-usb mailing list, I've bisected the problem in
the mainline git repository.
638139eb95d2d241781330a321e88c8dafe46078 is the first bad commit
commit 638139eb95d2d241781330a321e88c8dafe46078
Author: Petr Mladek
Date: Fri Sep 19 17:32:24 2014 +0200
usb: hub: allow to
** Attachment added: "output of "git bisect log""
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4451330/+files/bisect.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
Thanks for your advice!
I've posted a bug report upstream:
http://permalink.gmane.org/gmane.linux.usb.general/129790
I also checked out some older kernels.
The problem is present since 3.18, while 3.17.x was OK.
Or rather, had other, less dramatic problems on the machine.
** Tags added: kernel-b
** Attachment added: "output of lsusb -t"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/865/+files/lsusb-t.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
reproducible: always
Steps to reproduce:
- open a terminal
- sudo bash
- lsusb -v
In a virtual terminal, the command prints the name of the first device
it finds, then the system freezes completely. In a terminal of the
desktop, I don't even get the name of the device, the s
22 matches
Mail list logo
