2000-12-06 19:20:50

by Ragnar Hojland Espinosa

[permalink] [raw]
Subject: test12pre6: BUG in schedule (sched.c, 115)

as per subject.. BUG in schedule (sched.c, 115)
--
____/| Ragnar H?jland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O| 2F0D27DE025BE2302C
=(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
U chaos and madness await thee at its end." hkp://keys.pgp.com

Handle via comment channels only.


2000-12-06 22:31:13

by Mike Kravetz

[permalink] [raw]
Subject: Re: test12pre6: BUG in schedule (sched.c, 115)

Ragnar,

Are you sure that was line 115? Could it have been line 515?
Also, do you have any Oops data?

Thanks,
--
Mike Kravetz [email protected]
IBM Linux Technology Center
15450 SW Koll Parkway
Beaverton, OR 97006-6063 (503)578-3494


On Wed, Dec 06, 2000 at 07:59:08PM +0100, Ragnar Hojland Espinosa wrote:
> as per subject.. BUG in schedule (sched.c, 115)
> --
> ____/| Ragnar H?jland Freedom - Linux - OpenGL Fingerprint 94C4B
> \ o.O| 2F0D27DE025BE2302C
> =(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
> U chaos and madness await thee at its end." hkp://keys.pgp.com
>
> Handle via comment channels only.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> Please read the FAQ at http://www.tux.org/lkml/

2000-12-06 23:45:50

by Petr Vandrovec

[permalink] [raw]
Subject: Re: test12pre6: BUG in schedule (sched.c, 115)

On 6 Dec 00 at 14:00, Mike Kravetz wrote:
>
> Are you sure that was line 115? Could it have been line 515?
> Also, do you have any Oops data?
>

Yesterday BUG in schedule at 515 happened for me with test12-pre4.
As there were no data, and it was followed by

NMI detected lockup on CPU24 ...

(without any further data... no stack trace), I throwed it away as
some -pre4 memory corruption. Maybe it was not random corruption, but
stack overflow? Of course, my machine does not have 25 CPUs, but only
two PIII...

And no, I have no oops data. I was reviewing Debian changes
(apt-listchanges) when picture scrolled up one line (bug in sched) and
then, after 5 seconds, another one line, with 'NMI detected'... And
that was all, time to hit reset.

It was very patched test12-pre4, it contained Al Viro & Sct dirty buffer
patches, Andrew Morton's exec_usermodehelper, and couple of other
patches, brutto 153KB unzipped unified diff.

Filesystem ext2, 256MB RAM, dual PIII/450, kernel compiled with Debian's
gcc-2.95.2, matroxfb. On background there were Debian's XF4.0.1-9
running with Gnome and DRI, as I was tracking why that beast reprograms
matrox hardware every second (or every minute, depending on format of
clock in left upper corner; but that's another story) even if X are not
visible... (btw that's reason, why matroxfb does not work correctly with
XF4 & DRI...)
Best regards,
Petr Vandrovec
[email protected]

2000-12-07 05:03:07

by Ragnar Hojland Espinosa

[permalink] [raw]
Subject: Re: test12pre6: BUG in schedule (sched.c, 115)

On Wed, Dec 06, 2000 at 02:00:12PM -0800, Mike Kravetz wrote:
> Ragnar,
>
> Are you sure that was line 115? Could it have been line 515?

Yes, yes, it was 515. 115 is the result of human cache corruption ;)

> Also, do you have any Oops data?

It just froze there.

--
____/| Ragnar H?jland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O| 2F0D27DE025BE2302C
=(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
U chaos and madness await thee at its end." hkp://keys.pgp.com