test12 lockups -- need feedback
Subject: Re: test12 lockups -- need feedback
Date: Thu, 14 Dec 2000 15:31:38 +0000
From: Eckhard Jokisch <[email protected]>
To: dep <[email protected]>
Quoted 7 lines · dep
On Thursday 14 December 2000 07:15, Mohammad A. Haque wrote:
| Were you connected to a network or receiving/sending anything?a conditional yes -- little lan here, d-link dfe-530tx+ (rtl8139) to dlink hub, di-701 gateway, cable modem. so far as i know, i was neither sending nor receiving at the time, and i've done both things extensively with test12 without a lockup.
Is it possible that there is something wrong with the 8139too driver? ( I also use a card with 8139 chip )
Or do you use the "old" rtl8139 ? With that I don't have any problems. I have an extra machine here where I can do all testing - how can I help?
Eckhard
-------------------------------------------------------
-
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/
Quoted 4 lines · Eckhard Jokisch
Is it possible that there is something wrong with the 8139too driver? ( I also use a card with 8139 chip )
Or do you use the "old" rtl8139 ? With that I don't have any problems. I have an extra machine here where I can do all testing - how can I help?
I have no Realtek-Card and have the same lockup.
I also got a hard lockup (but with Oops) while calling the "vendor CPU init" function during system boot.
This was on Cyrix III.
PS: CC'ed hpa, because he is cpu-detection maintainer and davej,
because he added Cyrix III support and might know details ;-)
Regards
Ingo Oeser
Signature · 6 lines
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< come and join the fun >>>>>>>>>>>>
-
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/Quoted 11 lines
I have no Realtek-Card and have the same lockup.
I also got a hard lockup (but with Oops) while calling the "vendor CPU init" function during system boot.
This was on Cyrix III.
PS: CC'ed hpa, because he is cpu-detection maintainer and davej,
because he added Cyrix III support and might know details ;-)
Please include the oops information, as well as the /proc/cpuinfo output.
-hpa
-
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/
Quoted 8 lines
Quoted 6 lines
I also got a hard lockup (but with Oops) while calling the "vendor CPU init" function during system boot.
This was on Cyrix III.
PS: CC'ed hpa, because he is cpu-detection maintainer and davej,
because he added Cyrix III support and might know details ;-)Please include the oops information, as well as the
/proc/cpuinfooutput.
Also be sure you built Pentium/TSC kernels as Cyrix III is a 686 core without the cmov instruction it seems
-
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/
Quoted 3 lines · H. Peter Anvin
Quoted 1 line
This was on Cyrix III.
Please include the oops information, as well as the
/proc/cpuinfooutput.
processor : 0vendor_id : CentaurHauls
cpu family : 6
model : 6
model name : WinChip ??
stepping : 0
cpu MHz : 501.000148
cache size : 128 KBfdiv_bug : nohlt_bug : nosep_bug : nof00f_bug : nocoma_bug : no
fpu : yesfpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu de tsc msr mce cx8 mtrr pge mmx
bogomips : 999.42
processor : 0vendor_id : CentaurHauls
cpu family : 6
model : 6
model name : WinChip ??
stepping : 0
cpu MHz : 501.000148
cache size : 128 KBfdiv_bug : nohlt_bug : nosep_bug : nof00f_bug : nocoma_bug : no
fpu : yesfpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu de tsc msr mce cx8 mtrr pge mmx
bogomips : 999.42
Oops not available, because this machine is in a frozen state (in project management context) running a specially patched test9.
It oopsed after this message:
CPU: Before vendor init, caps: <the actual caps>
The only symbols on stack where "empty_bad_page" and "L6" without any offset.
I'll get access to a clone of this machine on monday and oops it again ;-)
But perhaps this is helpful in any matter.
Regards & Thanks
Ingo Oeser
Signature · 6 lines
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< come and join the fun >>>>>>>>>>>>
-
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/Quoted 4 lines · Alan Cox
Quoted 2 lines
Quoted 1 line
This was on Cyrix III.
Please include the oops information, as well as the
/proc/cpuinfooutput.Also be sure you built Pentium/TSC kernels as Cyrix III is a 686 core without the cmov instruction it seems
I did. And built with gcc 2.95.2 (debian potato) if that matters.
Regards
Ingo Oeser
Signature · 6 lines
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< come and join the fun >>>>>>>>>>>>
-
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/I have a DLink DFE-530TX+ with a RTL8139 and I lock up cold every once in a while too. 2.4.0-test12-pre3 is the latest kernel I've tried. The machine is a dual PII450 on a Tyan Tiger 100 BX board w/ 128MB.
Locks up cold meaning "It's dead Jim". Non sysrq facilities available and no Oops trail.
I don't see the old Becker 8139 driver in the 2.4 tree so I don't know if it happens with 2.4 and the old driver.
I can provide what ever info that is available and would be useful.
NOTE also: I have an old Dell P133 48MB masquerading machine with 2 of these same boards that Panic's on current 2.4 kernels with the "Aieee killing interrupt handler" message to the console but doesn't get around to writing the console to the log before going toe up. 2.4.0-test12-pre3. Before that I get a bunch of the RxFIFOOwv interrupt sending it into the rtl8139_weird_interrupt routine, but it says in the driver code that this could be related to CPU speed and the machine's a P133. Should the machine panic though?
I can't get the console off to the serial port cause the ports are dead on this machine for some reason. The BIOS allocates irq 4 to the second of the 8139 cards and neither serial port is recognised so I'm not sure how to get any major chunk of the Panic info off teh 14" screen. Note that this machine runs 2.2.18 fine albiet my OnStream drive doesn't function right so maybe the old Becker driver does solve some of the problems. Arg! =)
-mwe
Quoted 19 lines · Ingo Oeser
Quoted 4 lines · Eckhard Jokisch
Is it possible that there is something wrong with the 8139too driver? ( I also use a card with 8139 chip )
Or do you use the "old" rtl8139 ? With that I don't have any problems. I have an extra machine here where I can do all testing - how can I help?I have no Realtek-Card and have the same lockup.
I also got a hard lockup (but with Oops) while calling the "vendor CPU init" function during system boot.
This was on Cyrix III.
PS: CC'ed hpa, because he is cpu-detection maintainer and davej,
because he added Cyrix III support and might know details ;-)Regards
Ingo Oeser
Signature · 10 lines
Mike Elmore [email protected] "Never confuse activity with accomplishment." -unknown - 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/