2002-10-07 19:17:43

by Andreas Bergen

[permalink] [raw]
Subject: Kernel-oops

Dear kernel-developers,

recently I get quite a lot of kernel oopses. Before 2.4.17 my system
ran very stable but since upgrading to 2.4.18 and still with 2.4.19 I
get an oops every few days.

Can you help me with these? Do you need any additional information?

Attached is the output of ksymoops.

Thanks a lot in advance
yours
Andreas Bergen

--
Andreas Bergen
E-Mail: [email protected]
PGP-Key on keyservers.
"Freuet euch in dem Herrn allewege, und abermals sage ich: Freuet euch!" Phi 4,4


Attachments:
(No filename) (503.00 B)
oops.out (4.52 kB)
oops.out (2.22 kB)
oops.out (2.03 kB)
oops.out (13.35 kB)
oops.out (2.47 kB)
oops.out (4.51 kB)
oops.out (2.53 kB)
oops.out (1.65 kB)
oops.out (6.54 kB)
Download all attachments

2002-10-07 21:09:57

by Joseph D. Wagner

[permalink] [raw]
Subject: RE: Kernel-oops

It's just my best guess, but I'd say there's something wrong with your
modules.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Andreas Bergen
Sent: Monday, October 07, 2002 9:54 AM
To: [email protected]
Subject: Kernel-oops

Dear kernel-developers,

recently I get quite a lot of kernel oopses. Before 2.4.17 my system
ran very stable but since upgrading to 2.4.18 and still with 2.4.19 I
get an oops every few days.

Can you help me with these? Do you need any additional information?

Attached is the output of ksymoops.

Thanks a lot in advance
yours
Andreas Bergen

--
Andreas Bergen
E-Mail: [email protected]
PGP-Key on keyservers.
"Freuet euch in dem Herrn allewege, und abermals sage ich: Freuet euch!"
Phi 4,4

2002-10-08 13:09:47

by Andreas Bergen

[permalink] [raw]
Subject: Re: Kernel-oops

On Mon, Oct 07, 2002 at 04:15:24PM -0500, Joseph D. Wagner wrote:
> It's just my best guess, but I'd say there's something wrong with your
> modules.

Could you be more specific about that? What can I do? Where could be
the problem?
--
Andreas Bergen
E-Mail: [email protected]
PGP-Key on keyservers.
"Freuet euch in dem Herrn allewege, und abermals sage ich: Freuet euch!" Phi 4,4

2002-10-08 13:09:42

by Andreas Bergen

[permalink] [raw]
Subject: Re: Kernel-oops

Dear Dave,

> Is this a machine that had previously been running without a
> problem? I ask because that would mostly eliminate the issue of
> incompatibilities. Right off, I'll say that it's my experience that
> kernel oopses are usually memory or hardware fault related. In order
> to test this hypothesis, you can try:

the problem is, that the machine ran without any problem until I
upgraded to kernel version 2.4.18. Originally I used the kernel which
was provided by the SuSE 8.0-CDs (2.4.18-4GB). Later I compiled my own
kernel, I upgraded to 2.4.19 but nothing helped.


> 1. removing all but one memory module and see if you keep getting oopses. If
> they continue, take that one out and try another. Cycle them all through in
> this manner to see if this might cause a problem. Also, try running memtest86
> for 24 hours of so. I think you can find it on Freshmeat.

I think it's not very likely that the problem is due to a hardware
problem as the first oops I ever got (after several years of happy
Linuxing) happened at the day I upgraded to 2.4.18-4GB and it never
stopped since then. I had memtest86 running once for several hours
which reported no problem.


> 3. After all that, the possibility does exist that there's a bug in a driver
> for one of your devices. Make sure that you're using the latest version of
> the kernel.

I do (2.4.19). BTW, I don't have any special devices running (serial
mouse, ATA CD-ROM, SB16 Soundcard, Matrox Mystique Graphics-Card, the
streamer I have and which works smoothlessly is normally not activated
as the corresponding modules are not loaded).

> If you are, paste the text of the oops into an email to
> linux-kernel, along with a description of when it seems to happen, or any
> other information that might help: the contents of /proc/pci, output of
> lsmod... I think there's a FAQ somewhere that describes what you should
> include, but I don't remember where it is.

I can't find any regularity in when it happens.

/proc/pci:
cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel Corp. 430HX - 82439HX TXC [Triton II] (rev 3).
Master Capable. Latency=32.
Bus 0, device 7, function 0:
ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 1).
Bus 0, device 7, function 1:
IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] (rev 0).
Master Capable. Latency=32.
I/O at 0xf000 [0xf00f].
Bus 0, device 10, function 0:
VGA compatible controller: Matrox Graphics, Inc. MGA 1064SG [Mystique] (rev 2).
IRQ 11.
Master Capable. Latency=32.
Non-prefetchable 32 bit memory at 0xe1000000 [0xe1003fff].
Prefetchable 32 bit memory at 0xe0000000 [0xe07fffff].
Non-prefetchable 32 bit memory at 0xe0800000 [0xe0ffffff].


/sbin/lsmod:
Module Size Used by Not tainted
ipt_TCPMSS 2368 0 (autoclean)
ipt_TOS 1024 0 (autoclean)
ipt_state 608 0 (autoclean)
ipt_LOG 3168 0 (autoclean)
ip_nat_ftp 2944 0 (unused)
ip_conntrack_ftp 3200 0 (unused)
ppp_deflate 39456 0 (autoclean)
bsd_comp 4032 0 (autoclean)
ppp_async 6336 0 (autoclean)
snd-mixer-oss 8736 1 (autoclean)
snd-pcm-oss 34628 0 (autoclean)
autofs 8868 1 (autoclean)
parport_pc 11972 1 (autoclean)
lp 5856 0 (autoclean)
parport 13888 1 (autoclean) [parport_pc lp]
snd-opl3-synth 8476 0 (unused)
snd-seq-instr 4224 0 [snd-opl3-synth]
snd-seq-midi-emul 4464 0 [snd-opl3-synth]
snd-seq 33292 0 [snd-opl3-synth snd-seq-instr snd-seq-midi-emul]
snd-ainstr-fm 1332 0 [snd-opl3-synth]
snd-sb16 3236 1
snd-sb16-csp 15072 0 [snd-sb16]
snd-opl3-lib 5152 0 [snd-opl3-synth snd-sb16]
snd-hwdep 3456 0 [snd-sb16-csp snd-opl3-lib]
snd-sb16-dsp 5248 0 [snd-sb16]
snd-pcm 46912 0 [snd-pcm-oss snd-sb16-dsp]
snd-timer 9088 0 [snd-seq snd-opl3-lib snd-pcm]
snd-sb-common 6056 0 [snd-sb16 snd-sb16-csp snd-sb16-dsp]
snd-mpu401-uart 2592 0 [snd-sb16 snd-sb16-dsp]
snd-rawmidi 11776 0 [snd-mpu401-uart]
snd-seq-device 3696 0 [snd-opl3-synth snd-seq snd-opl3-lib snd-rawmidi]
snd 23592 0 [snd-mixer-oss snd-pcm-oss snd-opl3-synth snd-seq-instr snd-seq snd-sb16 snd-sb16-csp snd-opl3-lib snd-hwdep snd-sb16-dsp snd-pcm snd-timer snd-sb-common snd-mpu401-uart snd-rawmidi snd-seq-device]
soundcore 3492 6 [snd]
ipv6 124864 -1 (autoclean)
ppp_generic 16236 0 (autoclean) [ppp_deflate bsd_comp ppp_async]
slhc 4480 0 (autoclean) [ppp_generic]
ipt_REJECT 2784 0 (autoclean)
iptable_mangle 2112 0 (autoclean)
iptable_nat 13076 1 (autoclean) [ip_nat_ftp]
ip_conntrack 13228 3 (autoclean) [ipt_state ip_nat_ftp ip_conntrack_ftp iptable_nat]
iptable_filter 1728 0 (autoclean)
ip_tables 10528 10 [ipt_TCPMSS ipt_TOS ipt_state ipt_LOG ipt_REJECT iptable_mangle iptable_nat iptable_filter]
md 56896 0 (autoclean)


What makes me wonder is the message from Sep 16 saying:
Sep 16 14:31:18 erde kernel: kernel BUG at page_alloc.c:206!


> I hope this helps! Sorry I can't be more specific. I'm not really a kernel guy
> - I just try to keep up with all of the goings-on! :-)

Thanks for your suggestions. I hope we can find the problem.

Andreas

--
Andreas Bergen
E-Mail: [email protected]
PGP-Key on keyservers.
"Freuet euch in dem Herrn allewege, und abermals sage ich: Freuet euch!" Phi 4,4

2002-10-09 10:26:06

by Andreas Bergen

[permalink] [raw]
Subject: Re: Kernel-oops

Probably this helps, too: Here is my
/usr/src/linux/.config


--
Andreas Bergen
E-Mail: [email protected]
PGP-Key on keyservers.
"Freuet euch in dem Herrn allewege, und abermals sage ich: Freuet euch!" Phi 4,4


Attachments:
(No filename) (220.00 B)
.config (16.00 kB)
Download all attachments

2002-10-09 10:26:08

by Andreas Bergen

[permalink] [raw]
Subject: Re: Kernel-oops

On Tue, Oct 08, 2002 at 08:13:35PM -0200, Denis Vlasenko wrote:
> On 8 October 2002 10:59, Andreas Bergen wrote:
> > the problem is, that the machine ran without any problem until I
> > upgraded to kernel version 2.4.18. Originally I used the kernel which
> > was provided by the SuSE 8.0-CDs (2.4.18-4GB). Later I compiled my
> > own kernel, I upgraded to 2.4.19 but nothing helped.
>
> Okay, you have two versions of kernel, one runs fine, one does not.
> Pick up all the -preN kernels between them and do a binary search.

The 2.4.17 was the standard-kernel without any patches, the 2.4.18 and
2.4.19 as well. Unfortunately I don't have the .config-file for the
2.4.17 anymore, so I can't tell the configuration-difference between
the two. Is there a way to find out the configuration of a kernel?

One thing that came to my mind: Is the problem probably related to the
fact that with 2.4.18/19 my computer won't suspend anymore? It blanks
the screen but doesn't beep and then resumes immediately normally as
the log-file says. When I boot the 2.4.17 everything works as expected.

Thanx a lot in advance
yours
Andreas Bergen

--
Andreas Bergen
E-Mail: [email protected]
PGP-Key on keyservers.
"Freuet euch in dem Herrn allewege, und abermals sage ich: Freuet euch!" Phi 4,4