VM oops in RH7.3 2.4.18-3

VM oops in RH7.3 2.4.18-3

[Matt Bernstein]

This is a dual Athlon, 1 gig registered ECC DDR RAM, will try 2.4.18-4 but
it doesn't look ext3-related (the only big local filesystem is reiserfs
over s/w raid0).

I do suspect the hardware on this machine. If someone could tell me "that
looks like a bad x", I'd be very grateful. More details on request :-/

Unable to handle kernel paging request at virtual address 0200f82b
 printing eip:
c0137dc0
*pde = 00000000
Oops: 0000
nls_iso8859-1 nls_cp437 vfat fat soundcore nfs tuner tvaudio bttv videodev i2c
CPU:    0
EIP:    0010:[<c0137dc0>]    Not tainted
EFLAGS: 00010206

EIP is at page_remove_rmap [kernel] 0x50 (2.4.18-3)
eax: 0200f827   ebx: c1df9c38   ecx: c1000030   edx: c3a19168
esi: c3a19168   edi: c33bc618   ebp: 3fe37025   esp: c6b87eb0
ds: 0018   es: 0018   ss: 0018
Process crond (pid: 7463, stackpage=c6b87000)
Stack: 00100000 c3a19168 0005a000 c0126ab1 00000020 00000000 42100000 c6b85420
       42000000 00000000 42100000 c6b85420 c011c6e6 00000000 c6b86000 00000000
       00000000 00000000 c6b86000 c6b860b4 00100000 0012c000 42000000 00000001
Call Trace: [<c0126ab1>] do_zap_page_range [kernel] 0x181
[<c011c6e6>] sys_wait4 [kernel] 0x396
[<c0127010>] zap_page_range [kernel] 0x50
[<c01297da>] exit_mmap [kernel] 0xca
[<c0117e36>] mmput [kernel] 0x26
[<c011c183>] do_exit [kernel] 0xb3
[<c011c6e6>] sys_wait4 [kernel] 0x396
[<c0108913>] system_call [kernel] 0x33


Code: 39 70 04 75 0d 53 57 50 e8 a3 02 00 00 83 c4 0c eb 08 89 c7

$ mount
/dev/sda3 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/sda2 on /boot type ext3 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/md0 on /export type reiserfs (rw,noatime,notail)
none on /dev/shm type tmpfs (rw)
none on /tmp type tmpfs (rw)

[ + plus some autofs / nfs stuff ]

Re: VM oops in RH7.3 2.4.18-3

[Jes Sorensen]

>>>>> "Matt" == Matt Bernstein <matt@theBachChoir.org.uk> writes:

Matt> This is a dual Athlon, 1 gig registered ECC DDR RAM, will try
Matt> 2.4.18-4 but it doesn't look ext3-related (the only big local
Matt> filesystem is reiserfs over s/w raid0).

Please send this to Red Hat before the kernel list. They are
responsible for maintaining their kernel.

Jes

Re: VM oops in RH7.3 2.4.18-3

[Benjamin LaHaise]

On Mon, May 27, 2002 at 10:33:12AM -0400, Jes Sorensen wrote:
> >>>>> "Matt" == Matt Bernstein <matt@theBachChoir.org.uk> writes:
> 
> Matt> This is a dual Athlon, 1 gig registered ECC DDR RAM, will try
> Matt> 2.4.18-4 but it doesn't look ext3-related (the only big local
> Matt> filesystem is reiserfs over s/w raid0).
> 
> Please send this to Red Hat before the kernel list. They are
> responsible for maintaining their kernel.

I'm sure Rik is interested in any feedback on the rmap patches that 
occur out in the wild...  even if they happen in vendor kernels.  With 
that said, we appreciate getting bugs like this filed in bugzilla.

		-ben
-- 
"You will be reincarnated as a toad; and you will be much happier."

Re: VM oops in RH7.3 2.4.18-3

[Matt Bernstein]

On May 27 Benjamin LaHaise wrote:

>On Mon, May 27, 2002 at 10:33:12AM -0400, Jes Sorensen wrote:
>> >>>>> "Matt" == Matt Bernstein <matt@theBachChoir.org.uk> writes:
>>
>> Matt> This is a dual Athlon, 1 gig registered ECC DDR RAM, will try
>> Matt> 2.4.18-4 but it doesn't look ext3-related (the only big local
>> Matt> filesystem is reiserfs over s/w raid0).
>>
>> Please send this to Red Hat before the kernel list. They are
>> responsible for maintaining their kernel.
>
>I'm sure Rik is interested in any feedback on the rmap patches that
>occur out in the wild...  even if they happen in vendor kernels.  With
>that said, we appreciate getting bugs like this filed in bugzilla.

Thanks--I'll see what I can do, though I really don't have much more to go
on than the oops. I think power supply / cooling are not to blame.. :-/

Matt

Re: VM oops in RH7.3 2.4.18-3

[Denis Vlasenko]

On 27 May 2002 21:28, Matt Bernstein wrote:
> On May 27 Benjamin LaHaise wrote:
> >On Mon, May 27, 2002 at 10:33:12AM -0400, Jes Sorensen wrote:
> >> >>>>> "Matt" == Matt Bernstein <matt@theBachChoir.org.uk> writes:
> >>
> >> Matt> This is a dual Athlon, 1 gig registered ECC DDR RAM, will try
> >> Matt> 2.4.18-4 but it doesn't look ext3-related (the only big local
> >> Matt> filesystem is reiserfs over s/w raid0).
> >>
> >> Please send this to Red Hat before the kernel list. They are
> >> responsible for maintaining their kernel.
> >
> >I'm sure Rik is interested in any feedback on the rmap patches that
> >occur out in the wild...  even if they happen in vendor kernels.  With
> >that said, we appreciate getting bugs like this filed in bugzilla.
>
> Thanks--I'll see what I can do, though I really don't have much more to go
> on than the oops. I think power supply / cooling are not to blame.. :-/

You may slightly underclock your system. This will lower wattage and heat
production.

Wait a day or two for the oops. If it's gone, you have a hw problem.
--
vda

Re: VM oops in RH7.3 2.4.18-3

[Alan Cox]

On Mon, 2002-05-27 at 15:26, Matt Bernstein wrote:
> This is a dual Athlon, 1 gig registered ECC DDR RAM, will try 2.4.18-4 but
> it doesn't look ext3-related (the only big local filesystem is reiserfs
> over s/w raid0).
> 
> I do suspect the hardware on this machine. If someone could tell me "that
> looks like a bad x", I'd be very grateful. More details on request :-/

It could be bad RAM but there is nothing in the dump that stands out and
says it is. memtest86 is stil the best test of that. If you are running
dual Athlon also check your ventilation and PSU - you need a 400W PSU
but not all 400W PSUs provide enough power on the specific lines.

Alan

Re: VM oops in RH7.3 2.4.18-3

[Matt Bernstein]

memtest86 3.0 (which knows something about ECC :) found the problem in
seconds. It had passed a memtest86 2.something months ago before going
into production. Case closed--thanks/sorry!

On May 27 Matt Bernstein wrote:

>This is a dual Athlon, 1 gig registered ECC DDR RAM, will try 2.4.18-4 but
>it doesn't look ext3-related (the only big local filesystem is reiserfs
>over s/w raid0).