Hi, all. I just booted 2.4.19-pre3, and it hung right after the MCE
message. This is an Asus P2B-D with two Intel 450 MHz PIII's. Output
of /proc/cpuinfo appended.
Regards,
Richard....
Permanent: [email protected]
Current: [email protected]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 451.032
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 897.84
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 451.032
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 901.12
On Sun, Mar 17, 2002 at 10:46:25PM -0700, Richard Gooch wrote:
> Hi, all. I just booted 2.4.19-pre3, and it hung right after the MCE
> message. This is an Asus P2B-D with two Intel 450 MHz PIII's. Output
> of /proc/cpuinfo appended.
>
Won't that change hang on *all* pii/piii systems? (I've only tested it on
one pii box)
Richard Gooch wrote:
> Hi, all. I just booted 2.4.19-pre3, and it hung right after the MCE
>message. This is an Asus P2B-D with two Intel 450 MHz PIII's. Output
>of /proc/cpuinfo appended.
>
My ASUS P2B-D with dual P-II 400's is strange...
I -was- getting the hang, but then I recompiled on a different host,
with possibly a different compiler, and the hang went away. Sorry I
cannot be more specific than this :(
The "running ok" case, which came -after- the hang case, was
2.4.19-pre3-BK-latest with gcc 3.0.4-MDK.
Jeff
Jeff Garzik writes:
> Richard Gooch wrote:
>
> > Hi, all. I just booted 2.4.19-pre3, and it hung right after the MCE
> >message. This is an Asus P2B-D with two Intel 450 MHz PIII's. Output
> >of /proc/cpuinfo appended.
> >
>
> My ASUS P2B-D with dual P-II 400's is strange...
>
> I -was- getting the hang, but then I recompiled on a different host,
> with possibly a different compiler, and the hang went away. Sorry I
> cannot be more specific than this :(
>
> The "running ok" case, which came -after- the hang case, was
> 2.4.19-pre3-BK-latest with gcc 3.0.4-MDK.
I'm using egcs-1.1.2. I've bailed out of gcc-2.95.3 because it's
buggy.
Regards,
Richard....
Permanent: [email protected]
Current: [email protected]
> Hi, all. I just booted 2.4.19-pre3, and it hung right after the MCE
> message. This is an Asus P2B-D with two Intel 450 MHz PIII's. Output
> of /proc/cpuinfo appended.
See linux-kernel for the past week. Its been discussed repeatedly. Pre3 only
works on non intel chips unless you kill MCE support
> > The "running ok" case, which came -after- the hang case, was
> > 2.4.19-pre3-BK-latest with gcc 3.0.4-MDK.
>
> I'm using egcs-1.1.2. I've bailed out of gcc-2.95.3 because it's
> buggy.
egcs-1.1.2 is known to miscompile some driver code and other oddments in
2.4.
Alan Cox <[email protected]> writes:
>> > The "running ok" case, which came -after- the hang case, was
>> > 2.4.19-pre3-BK-latest with gcc 3.0.4-MDK.
>>
>> I'm using egcs-1.1.2. I've bailed out of gcc-2.95.3 because it's
>> buggy.
>
> egcs-1.1.2 is known to miscompile some driver code and other oddments in
> 2.4.
Oh, really?
| COMPILING the kernel:
|
| - Make sure you have gcc-2.91.66 (egcs-1.1.2) available. gcc 2.95.2 may
| also work but is not as safe, and *gcc 2.7.2.3 is no longer supported*.
| Also remember to upgrade your binutils package (for as/ld/nm and company)
| if necessary. For more information, refer to ./Documentation/Changes.
(2.4.18 linux/README)
linux/Documentation/Changes is more helpful, though.
--
Florian Weimer [email protected]
University of Stuttgart http://CERT.Uni-Stuttgart.DE/people/fw/
RUS-CERT +49-711-685-5973/fax +49-711-685-5898
> | - Make sure you have gcc-2.91.66 (egcs-1.1.2) available. gcc 2.95.2 may
> | also work but is not as safe, and *gcc 2.7.2.3 is no longer supported*.
> | Also remember to upgrade your binutils package (for as/ld/nm and company)
> | if necessary. For more information, refer to ./Documentation/Changes.
>
> (2.4.18 linux/README)
- Make sure you have gcc 2.95.3 available. gcc 2.91.66 (egcs-1.1.2) may
also work but is not as safe, and *gcc 2.7.2.3 is no longer supported*.
Also remember to upgrade your binutils package (for as/ld/nm and company)
if necessary. For more information, refer to ./Documentation/Changes.
(2.4.19pre3 linux/README)