[lkml]   [2002]   [Feb]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Oopses in scheduler on Linux-2.4.17-xfs
Alan Cox schrieb:
> > I recently get oopses on 2.4.14-xfs and 2.4.17-xfs.
> > box is SMP with old Pentium Pro
> > There were some changes with erratas of the Pro ans something
> > with "cacheline alignment" and a fence.
> Unrelated - in fact you have bugs before and after. The fixes in question
> were two sets
> 1. In certain bizarre situations the ppro violates store ordering. It
> needs lock based spin_unlock to avoid that. Ditto locks to ensure
> stores don't bypass stuff on pci_map interfaces. (This btw is the
> same errata as the FENCE stuff in libglide is all about)
> 2. Certain address ranges must never be cached on the ppro due to an
> errata. We broke that in two ways - if there was RAM there, and
> if we mapped a card there and set MTRR's to write combine it.

Perhaps you three remember my reports about crashes in the scheduler.

After I was able to fetch an Oops on 2.4.17 (without kdb) I noticed

my bt848 didn't generate any interrupts (so videotext and epg didn't work
but TV worked)

In a last temptation I checked the BIOS and switched from MPP 1.4 to 1.1
And guess what? The box is running fine again for several weeks.

The BIOS was buggy before(different MTRR on CPUs) , I upgraded "years" ago.

I can't remember when I switched this entry in the BIOS.
Possibly there is a bug in the MPP tables (setup through BIOS) when set to 1.4?

Damn, never play with your BIOS settings if the box runs fine ... especially
if you forget that fact ;-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:20    [W:0.062 / U:0.608 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site