Re: Athlon problem report summary
Disconnect wrote: > Addendum to 1. So far everyone (at least on LKML) who has had the > crash-immediatly-do-not-pass-go issues has been using an iwill kk266 (or > kk266r, IIRC) mobo. > > Have we gotten any fix, other than not using K7 optimizations? I think it has something to do with the BIOS version also. The original January KK266 BIOS can use K7 optimizations, but any BIOS after that crashes hard. -- Jeff Lightfoot --jeffml at pobox.com -- http://thefoots.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Athlon runtime problems
[ sent to linux-kernel due to Alan rejecting all mail from Earthlink/Mindspring, I'm assuming he is still interested in the report though ] On Saturday 14 April 2001 09:13, Alan Cox wrote: > Can the folks who are seeing crashes running athlon optimised > kernels all mail me I have two Athlon machines with mysterious (no oops) lockups. I've just started running them as 586 to see if that stops the lockups. The first one: > - CPU model/stepping model : 4 model name : AMD Athlon(tm) Processor stepping: 2 cpu MHz : 1195.214 > - Chipset VIA KT133/KM133 (Iwill KK266) > - Amount of RAM MemTotal: 770960 kB > - /proc/mtrr output reg00: base=0x ( 0MB), size= 512MB: write-back, count=1 reg01: base=0x2000 ( 512MB), size= 256MB: write-back, count=1 reg02: base=0xd400 (3392MB), size= 32MB: write-combining, count=2 reg05: base=0xd000 (3328MB), size= 64MB: write-combining, count=2 > - compiler used gcc 2.95.4 The second one: > - CPU model/stepping model : 4 model name : AMD Athlon(tm) Processor stepping: 2 cpu MHz : 1000.050 > - Chipset VIA KT133/KM133 (MSI K7TPro) > - Amount of RAM MemTotal: 255588 kB > - /proc/mtrr output reg00: base=0x ( 0MB), size= 256MB: write-back, count=1 reg05: base=0xd000 (3328MB), size= 64MB: write-combining, count=1 > - compiler used gcc 2.95.4 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: NETDEV WATCHDOG: eth0: transmit timed out on LNE100TX 4.0, kernel2.4.2-ac11 and earlier.
On Tuesday 20 March 2001 14:58, Jeff Garzik wrote: > > With all the above kernel revisions/drivers, my network card > > hangs at random (sometimes within minutes, other times it takes > > days). To restart it I need to do an ifdown/ifup cycle and it > > will work fine until the next hang. I upgraded to 2.4.2-ac11 > > because of the documented tulip fixes, but after a few days got > > this again. The error log shows: > > In Alan Cox terms, that's a long time ago :) > > Can you please try 2.4.2-ac20? It includes fixes specifically for > this problem. I started having the same problem with my LNE100TX and switched it out with another LNE100TX and had the same problem. Figured it was my BP6 SMP motherboard and ordered a new computer. Doh. :-) Using 2.4.2-ac20. Current LNE100TX having problems (other is different Rev): Lite-On Communications Inc LNE100TX (rev 20) The first card would get "unexpected IRQ trap at vector d0" before dying whereas the second one didn't give that indication. It would just freeze and the traditional "NETDEV WATCHDOG: eth0: transmit timed out" message. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.1pre9 Oops (was Re: 2.4.1pre8 Oops)
On Sunday 21 January 2001 11:41, I wrote: > Nothing special with this box. SMP no modules, Squid proxy and > running VNC/Pan at the time. Using kernel version of reiserfs on > filesystems other than root. I also failed to mention that I use devfs. [Oops snipped] Upgraded to 2.4.1pre9 and got the following Oops: EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 0086 eax: 0001 ebx: 0001 ecx: 0001 edx: c0238440 esi: c02d7068 edi: 0020 ebp: 000d esp: c7a63ed0 ds: 0018 es: 0018 ss: 0018 Process pan (pid: 2318, stackpage=c7a63000) Stack: 0001 c02d7068 0020 000d 0082 0001 c02da381 001e c01125bf c0238440 0001 0001 0001 0001 c0233d6d 0001 0020 c02f502c c02d7068 0020 000d e000 c1460018 c0100018 Call Trace: [] [] [] [] [] [] [] [] [] [] [] Code: 80 3d c0 6d 28 c0 00 f3 90 7e f5 e9 d6 b7 ee ff 80 3d c0 6d >>EIP; c022b533<= Trace; c01125bf Trace; c0100018 Trace; c01ed565 Trace; c011916c Trace; c010a8c5 Trace; c0109014 Trace; 0018 Trace; c0130018 Trace; c0130e19 Trace; c0108f53 Trace; c010002b Code; c022b533 <_EIP>: Code; c022b533<= 0: 80 3d c0 6d 28 c0 00 cmpb $0x0,0xc0286dc0 <= Code; c022b53a 7: f3 90 repz nop Code; c022b53c 9: 7e f5 jle0 <_EIP> Code; c022b53e b: e9 d6 b7 ee ffjmpffeeb7e6 <_EIP+0xffeeb7e6> c0116d19 Code; c022b543 10: 80 3d c0 6d 00 00 00 cmpb $0x0,0x6dc0 - 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/
2.4.1pre8 Oops
Nothing special with this box. SMP no modules, Squid proxy and running VNC/Pan at the time. Using kernel version of reiserfs on filesystems other than root. Be glad to offer any other info if needed. EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 0002 eax: 0300 ebx: 000f41fb ecx: 4000 edx: 03fd esi: c02ed380 edi: c0303da0 ebp: c02ed381 esp: c992fe9c ds: 0018 es: 0018 ss: 0018 Process pan (pid: 23322, stackpage=c992f000) Stack: c01c7858 c0303da0 0005 c02a61a0 001b c02ed366 c02ed381 001b 000d c0116e42 c02a61a0 c02ed366 001b 0001 c02ea068 0020 000d 0082 0001 c02ed381 001e c01125bf c023d0a0 0001 Call Trace: [] [] [] [] [] [] [] [] [] [] [] Code: 0f b6 c0 c3 90 53 8b 54 24 08 8b 44 24 0c 8b 5c 24 10 83 7a >>EIP; c01c36a7<= Trace; c01c7858 Trace; c0116e42 Trace; c01125bf Trace; c0100018 Trace; c01f2aa5 Trace; c011aafc Trace; c010a8c5 Trace; c0109014 Trace; c0130018 Trace; c0132a30 Trace; c0108f53 Code; c01c36a7 <_EIP>: Code; c01c36a7<= 0: 0f b6 c0 movzbl %al,%eax <= Code; c01c36aa 3: c3ret Code; c01c36ab 4: 90nop Code; c01c36ac 5: 53push %ebx Code; c01c36ad 6: 8b 54 24 08 mov0x8(%esp,1),%edx Code; c01c36b1 a: 8b 44 24 0c mov0xc(%esp,1),%eax Code; c01c36b5 e: 8b 5c 24 10 mov0x10(%esp,1),%ebx Code; c01c36b9 12: 83 7a 00 00 cmpl $0x0,0x0(%edx) - 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/
Re: innd mmap bug in 2.4.0-test12
"Marco d'Itri" ([EMAIL PROTECTED]) wrote: > I can confirm the bug which loses updates to the inn active file when > it's unmapped is present again in 2.4.0-test12. It is also still in 2.4.0-test13-pre4 in case someone thought they had fixed it. -- Jeff Lightfoot --jeffml at pobox.com -- http://thefoots.com/ "I see the light at the end of the tunnel now ... someone please tell me it's not a train" -- Cracker - 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/
