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

Re: Run out of nocached RAM! kernel BUG at srmmu.c:397!



On Sat, Jul 26, 2003 at 07:54:26PM +0200, Norrsken wrote:
> I have recently installed Debian 3.0 on my SPARCstation20 MP(configuration
> details below). Tesing apache on it with httperf (from a different box) I got
> what looks like a kernel panic:
> --------- 8< syslog 8<---------------------------------------------------------
> Jul 26 11:13:26 therion kernel: kernel BUG at srmmu.c:397!
> Jul 26 11:13:26 therion kernel: Unable to handle kernel NULL pointer dereference
> <1>tsk->{mm,active_mm}->context = 000000e5
> Jul 26 11:13:26 therion kernel: tsk->{mm,active_mm}->pgd = fc01f800
> Jul 26 11:13:26 therion kernel:               \|/ ____ \|/
> Jul 26 11:13:26 therion kernel:               "@'/ ,. \`@"
> Jul 26 11:13:26 therion kernel:               /_| \__/ |_\
> Jul 26 11:13:26 therion kernel:                  \__U_/
> Jul 26 11:13:26 therion kernel: top(241): Oops
> Jul 26 11:13:26 therion kernel: PSR: 408000c7 PC: f0023f38 NPC: f0023f3c Y: 0000
> 0000    Not tainted
> Jul 26 11:13:26 therion kernel: g0: f0195000 g1: 40800fe5 g2: 00000001 g3: 40400
> fe6 g4: f002b7a0 g5: 53545556 g6: fbb96000 g7: 00000100
> Jul 26 11:13:26 therion kernel: o0: 0000001b o1: 404000e7 o2: f0195000 o3: f0195
> 000 o4: f0195270 o5: f015bfa0 sp: fbb97d48 o7: f0023f30
> Jul 26 11:13:26 therion kernel: l0: fbb96368 l1: fbb963c8 l2: 00000001 l3: efffe
> fff l4: 0000007c l5: 00313300 l6: fbb96000 l7: 50041fa8
> Jul 26 11:13:26 therion kernel: i0: f01bec60 i1: 00040000 i2: f01e7c00 i3: 00000
> 003 i4: f0d1df20 i5: 0002bc00 fp: fbb97db0 i7: f003ee20
> Jul 26 11:13:26 therion kernel: Caller[f003ee20]
> --------- >8 syslog >8---------------------------------------------------------

Please send this to sparclinux@vger.kernel.org.

One thing I can tell you is that 2.4 is not as stable as 2.2 on sparc32
systems, especially 2.4.18. If you want to try 2.4 on sparc32, I
strongly suggest 2.4.21, or even 2.4.22-pre's. Likely, you'll be asked
to try atleast reproducing it on 2.4.21 before you get any help with
this bug. 2.4.18 is very old.

If you want stability (and don't mind going back to ipchains and ext2),
stick with 2.2.x on critical sparc32 systems.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/



Reply to: