[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: 2.6.12 testers wanted | sparc32 kernel on SPARC4 sun4m

Hi All,

I upgraded to the 2.6.12 image with only a few minor issues on a SPARC 4
sun4m box (floppy drive only).

I deleted and re-created the symlinks for the kernel and initrd after
the kernel install as this looked like it would be the same issue I saw
with the upgrade to 2.4.27.

The symlinks were created as follows: -

lrwxrwxrwx   1 root root     33 Jul 19 20:02 initrd.img ->
lrwxrwxrwx   1 root root     30 Jul 19 20:01 vmlinuz ->

Changed them to: -

lrwxrwxrwx   1 root root     33 Jul 19 20:02 initrd.img ->
lrwxrwxrwx   1 root root     30 Jul 19 20:01 vmlinuz ->

After the upgrade I couldn't ssh to the box and my keyboard didn't work.

I booted into the old 2.4.27 kernel, removed the console-data and
console-tools packages (as suggested by Jurij, thanks) and rebooted.
Seemed fine for the keyboard but I still couldn't ssh into the box even
though I saw sshd had started.

Added the following line to /etc/fstab: -

    none            /dev/pts        devpts        gid=5,mode=620    0 0

After a reboot and all worked fine.

System seems happy enough on 2.6.12-1-sparc32.



-----Original Message-----
From: Jurij Smakov [mailto:jurij@wooyd.org] 
Sent: 13 July 2005 06:27
To: debian-sparc@lists.debian.org
Subject: 2.6.12 testers wanted


The kernel team is currently preparing the release of kernel 2.6.12. I 
have been testing the new release on sparc, with some mixed results.

For sparc64 everything seems to look good, the kernel boots fine on my 
testing machine(s) and appears to function properly. I've received a 
report of it not booting on Netra X1, however the person who reported it

have come up with a working kernel config. This config differs a bit
the one used in official kernels, so I hope that we'll be able to find
problem fairly soon. Note that tg3 driver has been readded to 2.6.12 
Debian kernel source.

On sparc32 things do not look good at all. First, all attempts to boot
initrd-enabled kernel have failed miserably, with kernel failing to
initrd and subsequently panicking. Few days ago I have disabled initrd 
support and finally managed to get kernel to boot on my SS10 with 
HyperSparc CPU. Unfortunately, it appears to occasionally corrupt the 
filesystem under heavy memory/disk activity (such as sarge to sid 
upgrade). So, at this moment I am not sure whether it makes sense to
the sparc32 debs for 2.6.12 at all, as the kernel is pretty badly
It might be though, that the issues are specific to the Hypersparc CPU,
the images might work fine for others.

In order to make a more informed decision about sparc32 and make sure 
that everything is fine on sparc64, it would be great if the preliminary

debs would receive testing on a wider variety of hardware. Note, that 
testing the sparc32 image may COMPLETELY BREAK your system, so backup
data on the machine, if it is of any value. Even though there are 
currently now known issues on sparc64, backing up important stuff is 
always useful when testing the new kernels. The kernel images are 
available at


Please report your experiences either by replying to this thread, or to 
the SparcKernelStatus wiki page at


Thanks for your cooperation,

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

P.S. Don't be alarmed by the fact that the packages are called
now, instead of kernel-image. This renaming is part of the transition to
common kernel packaging scheme, in which all the kernel debs are built 
from the same source package.

To UNSUBSCRIBE, email to debian-sparc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact

Reply to: