On Mon, Dec 04, 2006 at 07:52:43AM +0100, BERTRAND Joël wrote: > I don't try with debian package, only with official linux kernel. I > have tested the 2.6.19 but sunlance doesn't work for me in a SS20 that > runs with two sunlance (eth0/1)and one hme (eth2) interfaces... I don't > know the difference between the debian and official kernels.
It should be relatively minor, the only sparc-related patches included are backports of some essential bugfixes. > Is your kernel SMP ? Do you use HIGHMEM ? CONFIG_HIGHMEM is set. CONFIG_SMP is not, since it has not been deemed mature enough. Current plan is that etch is not going to support SMP on sparc32, so we are building only one, uniprocessor, flavour. You can find the complete config used when building Debian kernel at http://www.wooyd.org/misc/config-2.6.18-3-sparc32 In general, if the problem is not reproducible with the Debian's stock kernel, then the bug clearly should not be RC. Please let me know if that's the case, or lower the severity yourself, if applicable. > I have a 2.25 from Sun in one, a 2.25R from ROSS in another one and > a 2.25W (?) from an HyperSTATION in the third one. Tested modules are > single and dual RT-626 with a VSIMM (4 and 8MB) and 448 MB. I think it > is not an hardware trouble because all configurations I have tried > return exactly the same error. Hardware of the main station I use for > tests are validated with Solaris9 and without any trouble during several > days (but I cannot use three or four CPU with Solaris9 without having > "Watchdog reset!", all combinaisons with more than two CPU are not > stable. Same results on the three stations. If I have time, I shall try > to install a Solaris 2.7...). Sorry that I cannot be more helpful. As much as I would like to see working SMP on sparc32, I don't have neither skills nor time to work on improving it. Best regards, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC