Re: Booting a T5140 panics
Hi Rich! On 11/20/21 11:08, Rich wrote: > I did - that's the commit that I mentioned there, 7d5ec3d3. > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=7d5ec3d3 Perfect, thank you! > I reported it to linux-pci@ since it was there; I can easily go CC the > original author and linux-sparc@, but wasn't sure of the etiquette > involved, and didn't want to just blast multiple lists. I fully agree. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Booting a T5140 panics
I did - that's the commit that I mentioned there, 7d5ec3d3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=7d5ec3d3 I reported it to linux-pci@ since it was there; I can easily go CC the original author and linux-sparc@, but wasn't sure of the etiquette involved, and didn't want to just blast multiple lists. - Rich On Sat, Nov 20, 2021 at 5:06 AM John Paul Adrian Glaubitz wrote: > > Hello Rich! > > On 11/20/21 07:38, Rich wrote: > > Curiously, I didn't see other people's replies to my message, probably > > due to not being subscribed. I figured at the point where I just > > bought another SPARC, I might as well... > > > > I've done some digging into it. The short version is that commit > > 7d5ec3d3 introduced the readl() at > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/pci/msi.c?h=v5.14#n748 > > , and for reasons that are currently opaque to me not being familiar > > with low-level SPARC details, that dies in a fire. > > > > Just short-circuiting it to 1 instead of calling readl() seems to > > function fine for my system, but isn't a great general solution... > > I would suggest bisecting the kernel to this point where the breakage was > introduced and report the bug to the author of the original change as well > as the SPARC Linux kernel mailing list [1]. > > Adrian > > > [1] http://vger.kernel.org/vger-lists.html#sparclinux > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >
Re: Booting a T5140 panics
Hello Rich! On 11/20/21 07:38, Rich wrote: > Curiously, I didn't see other people's replies to my message, probably > due to not being subscribed. I figured at the point where I just > bought another SPARC, I might as well... > > I've done some digging into it. The short version is that commit > 7d5ec3d3 introduced the readl() at > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/pci/msi.c?h=v5.14#n748 > , and for reasons that are currently opaque to me not being familiar > with low-level SPARC details, that dies in a fire. > > Just short-circuiting it to 1 instead of calling readl() seems to > function fine for my system, but isn't a great general solution... I would suggest bisecting the kernel to this point where the breakage was introduced and report the bug to the author of the original change as well as the SPARC Linux kernel mailing list [1]. Adrian > [1] http://vger.kernel.org/vger-lists.html#sparclinux -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Booting a T5140 panics
Curiously, I didn't see other people's replies to my message, probably due to not being subscribed. I figured at the point where I just bought another SPARC, I might as well... I've done some digging into it. The short version is that commit 7d5ec3d3 introduced the readl() at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/pci/msi.c?h=v5.14#n748 , and for reasons that are currently opaque to me not being familiar with low-level SPARC details, that dies in a fire. Just short-circuiting it to 1 instead of calling readl() seems to function fine for my system, but isn't a great general solution... (Bonus fun - my T5140 is currently booting from a /boot on a USB drive and a / on an LSI SAS2 PCIe controller because A) the onboard SAS1 card is faulted and not obviously fixable, and B) I only figured out how to get the SAS2 disks to show up as a bootable device by loading the FCode blob onto the card after I did the install...I should probably migrate that at some point.) Last bit of fun is that Linux seems to be misinterpreting the local-mac-address? setting and just unconditionally overriding _everything_'s MAC with the system's, whether it's set to true or false. (Amusingly, the "niu" driver has special casing for this and instead of setting everything to e.g. 00:aa:aa:aa:aa:aa, sets the first port to 00:aa:aa:aa:aa:aa, second to 00:aa:aa:aa:aa:ab, and so on.) - Rich On Tue, Nov 16, 2021 at 3:39 AM John Paul Adrian Glaubitz wrote: > > Hello Rich! > > On 11/16/21 04:19, Rich wrote: > > Anybody have a suggestion for how to not get burned by this? I can try > > just booting older and older snapshots, but I only have so many > > burnable discs. > > Try this image which has a 4.19 kernel which is known to be less problematic > on older SPARCs: > > > https://cdimage.debian.org/cdimage/ports/snapshots/2019-07-16/debian-10.0-sparc64-NETINST-1.iso > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >
Re: Booting a T5140 panics
Greetings, Adrian. On 2021-11-16 03:39, John Paul Adrian Glaubitz wrote: Hello Rich! On 11/16/21 04:19, Rich wrote: Anybody have a suggestion for how to not get burned by this? I can try just booting older and older snapshots, but I only have so many burnable discs. Try this image which has a 4.19 kernel which is known to be less problematic on older SPARCs: https://cdimage.debian.org/cdimage/ports/snapshots/2019-07-16/debian-10.0-sparc64-NETINST-1.iso Will this work on a SB2000? I tried older Debian releases and there were problems with FC. Sincerely, N.
Re: Booting a T5140 panics
Hello Rich! On 11/16/21 04:19, Rich wrote: > Anybody have a suggestion for how to not get burned by this? I can try > just booting older and older snapshots, but I only have so many > burnable discs. Try this image which has a 4.19 kernel which is known to be less problematic on older SPARCs: > https://cdimage.debian.org/cdimage/ports/snapshots/2019-07-16/debian-10.0-sparc64-NETINST-1.iso Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Booting a T5140 panics
On 11/15/21 22:19, Rich wrote: > Hi all, > So, I came into possession of a T5140, and logically decided to try > booting Debian on it. > Wish I could help. I just wanted to say WELL DONE ! I have a Netra sparc unit that seems to run Debian just fine unless I try to do update-grub where it just panics. I am going to try, next week?, to boot a Fujitsu/Oracle M4000 unit that is laying around in my life. Should be a right royal disaster but I will certainly report progress. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional
