Launchpad has imported 14 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=217993.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2023-10-10T21:00:25+00:00 matthias.schrumpf wrote: Kernel 6.5 causes a crash immediately after selecting it in GRUB or trying to boot with it via other means. This crash always leads into a bootloop if no other kernel is selected. A successful boot with kernel 6.5 is impossible, so no log data could be collected. This error can be reproduced on many distros including Arch, Endeavour OS, Manjaro, Fedora and OpenSuse. The computer is working perfectly fine with older kernels up to and including 6.4. CPU, RAM and hard drives have all been checked thoroughly and no errors could be found. Current OS: Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.4.15-200.fc38.x86_64 (64-bit) Graphics Platform: X11 Hardware: Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C91 System Version: 1.0 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/0 ------------------------------------------------------------------------ On 2023-10-11T14:41:55+00:00 aros wrote: Could you please bisect? https://docs.kernel.org/admin-guide/bug-bisect.html Otherwise this bug report has very slim chances of being fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/1 ------------------------------------------------------------------------ On 2023-10-12T09:39:15+00:00 bagasdotme wrote: Do you have any out-of-tree modules that may cause this regression? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/2 ------------------------------------------------------------------------ On 2023-10-16T21:01:04+00:00 matthias.schrumpf wrote: (In reply to Artem S. Tashkinov from comment #1) > Could you please bisect? > > https://docs.kernel.org/admin-guide/bug-bisect.html > > Otherwise this bug report has very slim chances of being fixed. I'm sorry, I don't have the basic knowledge necessary for performing a bisection. (In reply to Bagas Sanjaya from comment #2) > Do you have any out-of-tree modules that may cause this regression? No, not to my knowledge. I tried this with live images or fresh installs of Arch, Endeavour OS, Manjaro, Fedora and OpenSuse and I didn't change anything beyond the settings and customizations that these distros do by default. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/3 ------------------------------------------------------------------------ On 2023-10-16T23:55:15+00:00 bagasdotme wrote: On 17/10/2023 04:01, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=217993 > > --- Comment #3 from matthias.schru...@freenet.de --- > (In reply to Artem S. Tashkinov from comment #1) >> Could you please bisect? >> >> https://docs.kernel.org/admin-guide/bug-bisect.html >> >> Otherwise this bug report has very slim chances of being fixed. > I'm sorry, I don't have the basic knowledge necessary for performing a > bisection. > Then refer to Documentation/admin-guide/bug-bisect.rst in the kernel sources for instructions. > (In reply to Bagas Sanjaya from comment #2) >> Do you have any out-of-tree modules that may cause this regression? > No, not to my knowledge. I tried this with live images or fresh installs of > Arch, Endeavour OS, Manjaro, Fedora and OpenSuse and I didn't change anything > beyond the settings and customizations that these distros do by default. > So you have this regression there? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/4 ------------------------------------------------------------------------ On 2023-10-18T21:36:42+00:00 matthias.schrumpf wrote: (In reply to Bagas Sanjaya from comment #4) > So you have this regression there? What do you mean? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/5 ------------------------------------------------------------------------ On 2023-10-24T14:54:14+00:00 aros wrote: Given that seemingly you're the only Linux user who has this issue, your only bet of fixing it is performing regression testing. The URL provided above has enough information to do so. If that's not enough, you may simply Google the appropriate questions, e.g. 1) How to compile and install the Linux kernel 2) How to install GCC in Distro_X It's all quite easy if you get down to it. No one but you can do it unfortunately. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/6 ------------------------------------------------------------------------ On 2023-10-25T22:31:30+00:00 a.mark.broadworth wrote: This is occurring for me as well on the generic 6.5 kernel that Ubuntu 23.10 installed. Seems to happen early in the bootup process (at least before amdgpu is loaded). Basic Hardware: AMD Ryzen 7 5800X 8-Core Processor Asus TUF GAMING X570-PLUS (BIOS 4802 06/15/2023) 64 GB RAM Radeon 6800 XT Demonstrated regression: v6.4.14 - good v6.5 - bad I'm attempting a bisect. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/7 ------------------------------------------------------------------------ On 2023-10-28T23:29:35+00:00 a.mark.broadworth wrote: This appears to have been introduced with: commit dcadfd7f7c74ef9ee415e072a19bdf6c085159eb (HEAD -> dcadfd7f7c7) Author: Takashi Sakamoto <o-taka...@sakamocchi.jp> Date: Tue May 30 08:12:40 2023 +0900 firewire: core: use union for callback of transaction completion In 1394 OHCI, the OUTPUT_LAST descriptor of Asynchronous Transmit (AT) request context has timeStamp field, in which 1394 OHCI controller record the isochronous cycle when the packet was sent for the request subaction. Additionally, for the case of split transaction in IEEE 1394, Asynchronous Receive (AT) request context is used for response subaction to finish the transaction. The trailer quadlet of descriptor in the context has timeStamp field, in which 1394 OHCI controller records the isochronous cycle when the packet arrived. Current implementation of 1394 OHCI controller driver stores values of both fields to internal structure as time stamp, while Linux FireWire subsystem provides no way to access to it. When using asynchronous transaction service provided by the subsystem, callback function is passed to kernel API. The prototype of callback function has the lack of argument for the values. This commit adds a new callback function for the purpose. It has an additional argument to point to the constant array with two elements. For backward compatibility to kernel space, a new union is also adds to wrap two different prototype of callback function. The fw_transaction structure has the union as a member and a boolean flag to express which function callback is available. The core function is changed to handle the two cases; with or without time stamp. For the error path to process transaction, the isochronous cycle is computed by current value of CYCLE_TIMER register in 1394 OHCI controller. Especially for the case of timeout of split transaction, the expected isochronous cycle is computed. Link: https://lore.kernel.org/r/20230529113406.986289-6-o-taka...@sakamocchi.jp Signed-off-by: Takashi Sakamoto <o-taka...@sakamocchi.jp> Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/8 ------------------------------------------------------------------------ On 2023-10-28T23:41:01+00:00 a.mark.broadworth wrote: I have a firewire card in my system. Affected kernels boot fine with the firewire card removed. 06:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 80) What are the next steps? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/9 ------------------------------------------------------------------------ On 2023-10-28T23:43:52+00:00 a.mark.broadworth wrote: (The print on the chip itself reads VIA VT6307) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/10 ------------------------------------------------------------------------ On 2023-10-30T11:39:35+00:00 matthias.schrumpf wrote: (In reply to Mark Broadworth from comment #9) > I have a firewire card in my system. Affected kernels boot fine with the > firewire card removed. > > 06:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] > IEEE 1394 OHCI Controller (rev 80) > > What are the next steps? Oh my god. It was the Firewire card the whole time? I also had a VIA VT6307 in my computer. I just removed it and now I can boot with the 6.5+ kernels without any issues. I wasn't using this anyway, I just never would have expected it to cause such a problem. Hope you find a solution that works for you. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/11 ------------------------------------------------------------------------ On 2023-11-07T21:28:54+00:00 mario.limonciello wrote: *** Bug 217994 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/12 ------------------------------------------------------------------------ On 2023-11-20T05:09:22+00:00 rjbgolding wrote: I also am experiencing this issue, reported it to https://bugs.launchpad.net/bugs/2043905 in the Ubuntu forums, the piece I didn't report there is that I also tried the ubuntu built 6.6 Rc4 generic 64-bit beta kernel and it was also the same problem with that 6.6 kernel... so this may also effect 6.6 as well as the 6.5 kernels. My system is CPU: AMD Ryzen 5600X MB: MSI MPG Gaming Plus (Bios 7C56v1F dated 12 Oct 2023) Ram: 64 Gig 3200 ddr4 GPU: AMD Radeon RX6600 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/14 ** Changed in: linux Status: Unknown => In Progress ** Changed in: linux Importance: Unknown => High -- 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/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: In Progress Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+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
