Re: [2.6.20.3] Oops with syscall_is_too_hard...

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

 



On Tue, Mar 20, 2007 at 04:28:54PM -0500, Tom spot Callaway wrote:
> On Tue, 2007-03-20 at 19:52 +0100, BERTRAND =?utf-8?Q?Jo=EBl?= wrote:
> > 	Hello,
> > 
> > 	I have tried to untar the sources of 2.6.21-rc4 kernel. My SS20 runs with
> > 	2.6.20.3/SMP.
> 
> As Dave has recently pointed out, sparc32 is unmaintained.
> sparc32 SMP is known to be broken. And bug reports are going to fall on
> deaf ears, sadly.

	Even with SMP support, 2.6 kernel is more stable than the 2.4 (and its lot
	of unexpected watchdog reset). I have used all kernel on sparc32 since
	2.2. The last stable SMP kernel is the 2.2. Problem : NetBSD SMP support
	is broken, Solaris 9 too (it works only with two CPU, three and four are
	started, but kernel is not stable and randomly panics. It's not an
	hardware problem.).

	Thus, only two choices: definitively shutting down all sparc32 or use
	old OS ?

	I would help to debug this kernel, but I have no idea to fix it.

	Regards,

	JKB
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux