[Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
Also attached lsusb output from a working kernel for comparison. And yes, it looks like this is a VIA-chipset-specific regression. I stand corrected about the Mac's built-in USB-C ports. Those don't work even after rolling back the kernel to the previous version. I'll file a separate bug for that. ** Attachment added: "lsusb -v from working kernel.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+attachment/5553000/+files/lsusb%20-v%20from%20working%20kernel.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956849 Title: Almost all USB ports suddenly stopped working; unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
** Attachment added: "lsusb -v -v -v" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+attachment/5552994/+files/lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956849 Title: Almost all USB ports suddenly stopped working; unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
-38 was fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956849 Title: Almost all USB ports suddenly stopped working; unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
Reported by another person yesterday: https://askubuntu.com/questions/1385823/some-usb-ports-suddenly-stop- working-not-only-mouse-keyboard -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956849 Title: Almost all USB ports suddenly stopped working; unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956849] [NEW] Almost all USB ports suddenly stopped working; unbootable
Public bug reported: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956849 Title: Almost all USB ports suddenly stopped working; unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 704763] Re: boot loader not installed to target disk
Same problem, 20.04 on 2019 Mac Pro. And in this case, I *can't* install GRUB on the internal drive at all, because the built-in NVME disk is non-writable in Linux. So I had to go through a lengthy process of mounting things and running grub manually with about a hundred- character-long command. Worse, every time I install any kind of update that upgrades the kernel, it looks like I have to repeat that whole lengthy process, or else the system won't be bootable. How is something so critical still so badly broken after this many years? Installing the bootloader on the same disk as the OS should be the DEFAULT. Installing it on some random disk shouldn't even be POSSIBLE, much less the only supported behavior. If the internal disk ever becomes writable in a future kernel update, this bug could be *seriously* bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/704763 Title: boot loader not installed to target disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/704763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129038] Re: lirc overwrote my lircd.conf
This bug seems to have regressed to being broken again in 10.04. -- lirc overwrote my lircd.conf https://bugs.launchpad.net/bugs/129038 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129361] Re: Reproducible crash on second resume from hibernate
Hmm. Just got notification on this bug two months after the last comment *shrugs* I'm assuming the kernel won't be in the Feisty apt repo, and I'm assuming you don't just build from a stock kernel.org tree or something, so where's the easiest place to grab an updated kernel binary package (or a source tarball would be okay, too)? I'll try to pull a new kernel and test it this weekend. -- Reproducible crash on second resume from hibernate https://bugs.launchpad.net/bugs/129361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129361] Re: Reproducible crash on second resume from hibernate
I'm not able to attach the other logs because your server's backend process is crashing. I'll try pasting. Apologies for the formatting problems this causes, but I did try to do what you asked... several times. First, lspci -vvnn results, then a complete /var/log/messages for one cycle of boot, hibernate, resume, hibernate, resume (no log messages generated for this part), then the first couple of lines of the next boot. 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 04) Subsystem: AOPEN Inc. Unknown device [a0a0:0589] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Capabilities: [e0] Vendor Specific Information 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA]) Subsystem: AOPEN Inc. Unknown device [a0a0:0589] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 19 Region 0: Memory at d018 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at ea00 [size=8] Region 2: Memory at c000 (32-bit, prefetchable) [size=256M] Region 3: Memory at d020 (32-bit, non-prefetchable) [size=256K] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 04) Subsystem: AOPEN Inc. Unknown device [a0a0:0589] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Region 0: Memory at d010 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04) (prog-if 00 [UHCI]) Subsystem: AOPEN Inc. Unknown device [a0a0:0589] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 4: I/O ports at eb00 [size=32] 00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04) (prog-if 00 [UHCI]) Subsystem: AOPEN Inc. Unknown device [a0a0:0589] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 17 Region 4: I/O ports at ed00 [size=32] 00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 04) (prog-if 00 [UHCI]) Subsystem: AOPEN Inc. Unknown device [a0a0:0589] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin C routed to IRQ 18 Region 4: I/O ports at e800 [size=32] 00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 04) (prog-if 00 [UHCI]) Subsystem: AOPEN Inc. Unknown device [a0a0:0589] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin D routed to IRQ 19 Region 4: I/O ports at e900 [size=32] 00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 04) (prog-if 20 [EHCI]) Subsystem: AOPEN Inc. Unknown device [a0a0:0589] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0
[Bug 129361] Reproducible crash on second resume from hibernate
Public bug reported: Binary package hint: linux-source-2.6.20 I'm seeing a reproducible crash the second time I resume from hiberation. The first time it hibernates, the screen goes back to a text console, displays some stuff on the screen, and everything works correctly. On resume, the text console shows an Ubuntu boot screen. The progress bar is later partially obliterated by a thin horizontal white box that goes all the way across the screen, but everything else is okay. It appears to be functional, and I've used it for a significant period of time after the first wake with no obvious problems (other than some known issues with lirc and mythtv). The second time it hibernates, the screen goes to what should be a text console, but instead, it's a black screen with bunch of scattered orange and green lines that are quickly replaced by orange boxes, often with what appear to be blinking, white underscore cursors at the top of the boxes. The severely corrupted console notwithstanding, it powers down successfully. Upon resume, it never makes it. I see the Ubuntu text boot screen. The progress bar is quickly covered by a thinner-than-usual horizontal blue box with four false-color Ubuntu logos below it, evenly tiled across the screen. At this point, the machine hangs. It is responsive to pings and responds with a connection refused on unopen ports. Connections to open ports open, but do not send back any data. The UI never changes from a text console back to X11. Hardware is a micro-ATX Pentium M/Intel 915GM box w/ integrated Intel video. In addition to the Intel chipset, it also has built-in FireWire (Agere Systems FW323) and Gig-E (Realtek RTL-8169), but otherwise is about as much a stock Intel board as you can get. Apart from hibernation problems, it has been working flawlessly for months, so I'm pretty sure it doesn't have any hardware problems to speak of. Today was the first time I've tried hibernation. I was hoping to be able to hibernate my MythTV setup with the power button on the remote, but it looks like I'm going to have to do a full shutdown for now. Will attach log files after I submit the bug. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: New -- Reproducible crash on second resume from hibernate https://bugs.launchpad.net/bugs/129361 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129361] Re: Reproducible crash on second resume from hibernate
** Attachment added: uname -a log file http://launchpadlibrarian.net/8620079/uname-a.log -- Reproducible crash on second resume from hibernate https://bugs.launchpad.net/bugs/129361 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129361] Re: Reproducible crash on second resume from hibernate
** Attachment added: dmesg log from a successful boot http://launchpadlibrarian.net/8620081/dmesg.log -- Reproducible crash on second resume from hibernate https://bugs.launchpad.net/bugs/129361 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
