Hi all,
So, I came into possession of a T5140, and logically decided to try
booting Debian on it.
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.
https://cdimage.debian.org/cdimage/ports/snapshots/2019-07-16/debian-10.0-sparc64-NETINST-1.iso
Hello Rich!
On 11/16/21 04:19, Rich wrote:
Anybody have a suggestion for how to not get burned by this? I can tryTry this image which has a 4.19 kernel which is known to be less problematic on older SPARCs:
just booting older and older snapshots, but I only have so many
burnable discs.
https://cdimage.debian.org/cdimage/ports/snapshots/2019-07-16/debian-10.0-sparc64-NETINST-1.iso
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 - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
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...
[1] http://vger.kernel.org/vger-lists.html#sparclinux
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 - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 16:18:16 |
Calls: | 6,646 |
Calls today: | 1 |
Files: | 12,190 |
Messages: | 5,327,107 |