> I'm interested if there is an explanation of the MK7 specific code in mmx.c and
> whether that could really be the source of the problem. I would like to get
> to the bottom of this.
As far as we can tell the problem is 'using a VIA chipset'. The code itself
is a fast copying loop using
On Sat, Jul 07, 2001 at 09:10:46AM -0800, Richard Chan wrote:
> Athlon oops saga continues - I consistently get Athlon kernels oopsing
> during the boot up process either in rc.sysinit or loading of usb modules
> (this is a RedHat system 7.1). These kernels can boot to a shell init=/bin/sh
> but
On Sat, Jul 07, 2001 at 09:10:46AM -0800, Richard Chan wrote:
Athlon oops saga continues - I consistently get Athlon kernels oopsing
during the boot up process either in rc.sysinit or loading of usb modules
(this is a RedHat system 7.1). These kernels can boot to a shell init=/bin/sh
but once
I'm interested if there is an explanation of the MK7 specific code in mmx.c and
whether that could really be the source of the problem. I would like to get
to the bottom of this.
As far as we can tell the problem is 'using a VIA chipset'. The code itself
is a fast copying loop using
Athlon oops saga continues - I consistently get Athlon kernels oopsing
during the boot up process either in rc.sysinit or loading of usb modules
(this is a RedHat system 7.1). These kernels can boot to a shell init=/bin/sh
but once I try to do stuff like inserting modules they oops left, right,
Athlon oops saga continues - I consistently get Athlon kernels oopsing
during the boot up process either in rc.sysinit or loading of usb modules
(this is a RedHat system 7.1). These kernels can boot to a shell init=/bin/sh
but once I try to do stuff like inserting modules they oops left, right,
6 matches
Mail list logo
