Re: Debian SID kernel results in "Fast Data Access MMU Miss" on Sun Ultra 30

Joacim Nilsson <[email protected]>
Newsgroups gmane.linux.debian.ports.sparc
Message-ID <ZMAzayc7Uuu9TB5l@DESKTOP-0KJC77J>
On Tue, Jul 25, 2023 at 12:36:57PM +0000, Ignacio Soriano Hernandez wrote:
> Hi,
> 
> interesting error as the latest Openindiana/SPARC (Beta)  (https://dlc.openindiana.aurora-opencloud.org/SPARC/release) was showing the same error BUT in a MP environment.
> 
> ERROR: Last Trap: Fast Data Access MMU Miss
> 
> Cheers
> 
> Iggi
> 
> 
> Am 25.07.23, 12:07 schrieb "Joacim Nilsson" <[email protected] <mailto:[email protected]>>:
> 
> 
> On Mon, Jul 24, 2023 at 03:46:12PM -0600, Stan Johnson wrote:
> > Hello,
> > 
> > The latest Debian SID kernel (vmlinux-6.4.0-1-sparc64) fails on a Sun
> > Ultra 30 with the following error at the PROM:
> > 
> > -----
> > ...
> > Loaded kernel version 6.4.4
> > Loading initial ramdisk (23022746 bytes at 0x64000000 phys, 0x40C00000
> > virt)...
> > Fast Data Access MMU Miss
> > ok
> > -----
> > 
> > I have been running a custom 6.2.10 kernel, and that continues to work.
> > I'm not sure whether this is related to Joacim Nilsson's cgroup fail
> > error on his Sun Ultra 5, but the failure message is different. I'll
> > have to investigate whether this could be a kernel regression.
> > 
> > The previous Debian SID kernel that I have is vmlinux-6.1.0-7-sparc64,
> > and it also results in the "Fast Data Access MMU Miss" error.
> > 
> > An earlier kernel (vmlinux-5.16.0-6-sparc64) works as expected:
> > 
> > # uname -a
> > Linux ultra-30 5.16.0-6-sparc64 #1 Debian 5.16.18-1 (2022-03-29) sparc64
> > GNU/Linux
> > 
> > # cat /proc/cpuinfo
> > cpu : TI UltraSparc II (BlackBird)
> > fpu : UltraSparc II integrated FPU
> > pmu : ultra12
> > prom : OBP 3.9.5 1997/04/11 10:03
> > type : sun4u
> > ncpus probed : 1
> > ncpus active : 1
> > D$ parity tl1 : 0
> > I$ parity tl1 : 0
> > Cpu0ClkTck : 0000000011a4783f
> > cpucaps : flush,stbar,swap,muldiv,v9,mul32,div32,v8plus,vis
> > MMU Type : Spitfire
> > MMU PGSZs : 8K,64K,512K,4MB
> > 
> > root@ultra-30:~# cat /proc/swaps
> > Filename Type Size Used Priority
> > /dev/sda2 partition 1052248 0 -2
> > 
> > # fdisk -l
> > Disk /dev/sda: 136.73 GiB, 146815737856 bytes, 286749488 sectors
> > Disk model: ST3146807LC
> > Geometry: 255 heads, 63 sectors/track, 17849 cylinders
> > Units: sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disklabel type: sun
> > 
> > Device Start End Sectors Size Id Type Flags
> > /dev/sda1 0 1060289 1060290 517.7M 1 Boot
> > /dev/sda2 1060290 3164804 2104515 1G 82 Linux swap
> > /dev/sda3 0 286744184 286744185 136.7G 5 Whole disk
> > /dev/sda4 3164805 19936664 16771860 8G 83 Linux native
> > /dev/sda5 19936665 53496449 33559785 16G 83 Linux native
> > /dev/sda6 53496450 87056234 33559785 16G 83 Linux native
> > /dev/sda7 87056235 103828094 16771860 8G 83 Linux native
> > /dev/sda8 103828095 286744184 182916090 87.2G 83 Linux native
> > 
> > -Stan
> > 
> I will install Debian on my Sun Fire V440 and se whats happen
> 
> 
> -- 
> Mvh
> Joacim Nilsson
> [email protected] <mailto:[email protected]>
> 
> 
> 
> 
My SunFire V440 fails in a similar way as my U5.
I dont get any errors bouncing me back to the ok promt though.
Let me know if you want any logs or anything.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.