two seperate 2.4.x problems...

[PinkFreud]

I am not subscribed to this list, so please CC me in any replies.  Thank 
you.

Hey, all.  I have two entirely seperate problems with 2.4.x kernels, on
two seperate systems.

The first occurs on a UDB (Digital Multia, model VX-51, Intel Pentium
100).  I recently installed Slackware 8.0, which includes 2.4.5.  Within a
day of installing, the kernel paniced.  I did not get a chance to save the
text of the oops.  The second time this happened was early this morning,
within a couple hours after a reboot (under 2.4.6).  Text of the oops and
panic are included below (note that this seems similar to the first one -
I noted, at least, that klogd seems to be listed as the culprit in both
cases).

Unable to handle kernel paging request at virtual address 0119c3c1
*pde = 00000000
Oops: 0000
CPU:	0
EIP:	0010:[<c01aba03>]
EFLAGS: 00010006
eax: c119a7d8	ebx: 0119c3a4	ecx: 0119c2cc	edx: 0000004f
esi: 00000010	edi: c119e000	ebp: 0119c2c4	esp: c4633e9c
ds: 0018   es: 0018   ss: 0018
Process klogd (pid: 88, stackpage=c4633000)
Stack: c119e000 c119e000 0000000b c4633f2c c01ac897 c119e000 c119e000 00000246
       0000000b c4633f2c c4633ee8 00000286 c4666300 c01ae8ae c119e000 c11e7460
       04000001 0000000b c0107c8f 0000000b c119e000 c4633f2c 00000160 c029fa60
Call Trace: [<c01ac897>] [<c01ae8ae>] [<c0107c8f>] [<c0107dee>] [<c0106b60>] [<c0110062>] [<c01463d5>]
       [<c012b376>] [<c0106ac3>]

Code: 8a 43 1d 84 c0 7d 09 53 57 e8 5f f9 ff ff eb 0e a9 20 00 00
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

I had to copy this from the screen, so I *may* have typoed some of the
addresses - but I think I got them right.

I previously ran Slackware 7.1 on this system (2.2.16 followed by 2.2.19,
I believe) with no adverse effects.  The problems only started to happen
when I installed Slackware 8.0, and, by extension, the 2.4.x kernels.  I
have not tried 2.2.19 under Slackware 8.0 yet.

The other problem I've been experiencing has to do with SMP and XFree86
4.x.x.  I believe this to be an XFree86 problem, but as they have yet to
respond after several requests for help, and due to the nature of the
problem, it may very well be kernel related.

On a SMP system (dual PIII/1 ghz, VIA chipset) running 2.4.x
(anything up to 2.4.6) kernels and XFree86 4.x.x (I've tried 4.0.1 up to
the current 4.1.0), I can pretty reliably cause the system to lock up.  I
simply start X, switch to a text console, and back to X.  The box locks
up, no keyboard, mouse, or network, and the display is blank.  Only thing
I can do is hit the reset button.  Obviously in such a situation, there
aren't any visible errors, nor are any able to be logged, as nothing is
actually written to disk by the time of the crash.  Under a uniprocessor
kernel, the lockup does *NOT* occur.

Again, I don't know if this is necessarily a kernel problem - trying the
same thing with svgalib doesn't seem to have any adverse effects.

Any help would be *greatly* appreciated.

Thanks!

	Mike Edwards

Brainbench certified Master Linux Administrator
http://www.brainbench.com/transcript.jsp?pid=158188
-----------------------------------
Unsolicited advertisments to this address are not welcome.