Can the folks who are seeing crashes running athlon optimised kernels all mail
me
- CPU model/stepping
- Chipset
- Amount of RAM
- /proc/mtrr output
- compiler used
Alan
On Sat, 14 Apr 2001, Alan Cox wrote:
> Can the folks who are seeing crashes running athlon optimised kernels all mail
> me
>
> - CPU model/stepping
Athlon Thunderbird 700mhz
/proc/cpu:
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 700.034
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips : 1395.91
> - Chipset
VIA KT133
> - Amount of RAM
256MB
> - /proc/mtrr output
reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
reg01: base=0xd4000000 (3392MB), size= 32MB: write-combining, count=2
reg05: base=0xd0000000 (3328MB), size= 64MB: write-combining, count=3
> - compiler used
kgcc under redhat:
gcc driver version 2.95.3 19991030 (prerelease) executing gcc version
egcs-2.91.66
>
> Alan
>
> -
> 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/
>
--
There are a thousand hacking at the branches of evil to the one
who is striking at the root.
--Henry D. Thoreau
On Sat, Apr 14, 2001 at 04:12:09PM +0100, Alan Cox wrote:
> Can the folks who are seeing crashes running athlon optimised kernels all mail
> me
Just trying to privide you with usefull info. I'm NOT seeing any
crashes at all.
> - CPU model/stepping
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 807.190
cache size : 256 KB
> - Chipset
VIA KT133/KM133
(An Asus A7V)
> - Amount of RAM
128 MiB
> - /proc/mtrr output
No support for it compiled in.
> - compiler used
gcc version 2.95.3 20010315 (release)
(compiled myself)
Kurt
[ 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=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x20000000 ( 512MB), size= 256MB: write-back, count=1
reg02: base=0xd4000000 (3392MB), size= 32MB: write-combining, count=2
reg05: base=0xd0000000 (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=0x00000000 ( 0MB), size= 256MB: write-back, count=1
reg05: base=0xd0000000 (3328MB), size= 64MB: write-combining, count=1
> - compiler used
gcc 2.95.4
Alan Cox wrote:
> Can the folks who are seeing crashes running athlon optimised kernels all mail
> me
>
> - CPU model/stepping
AMD Athlon Thunderbird 850Mhz
Stepping - 2
> - Chipset
VIA KT133A chipset, Iwill KK266 MB.
According to a couple other people this problem may only occur on this
motherboard.
> - Amount of RAM
256 MB Corsair PC150
> - /proc/mtrr output
reg: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
reg: base=0xd5000000 (3408MB), size= 16MB: write-combining, count=1
> - compiler used
2.95.3 - Debian unstable package.
>
> Alan
When these errors occur, I never get to a shell prompt. Is there a way
to save the errors or have them saved somewhere so I don't have to write
all that stuff down? Also, how can I set the console buffer (what is it
called, where you can view previous screens with SHIFT + PgUP/DOWN?) to
hold more so I don't lose some of the errors?
Thanks,
Moses
> Can the folks who are seeing crashes running athlon optimised kernels all mail
> me
> - CPU model/stepping
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 1202.743
(/proc/cpuinfo attached) 1.2G Tbird
> - Chipset
Iwill KK266, VIA KT133
> - Amount of RAM
512M PC133 amd-approved
> - /proc/mtrr output
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0xd0000000 (3328MB), size= 64MB: write-combining, count=1
reg05: base=0xd8000000 (3456MB), size= 64MB: write-combining, count=1
(This is from inside X on a K6 kernel. I can try to save it out from the
K7 kernel if needed.)
> - compiler used
gcc version 2.95.3 20010219 (prerelease)
debian gcc 2.95.3-5
---
_.-=<Disconnect>=-._
| [email protected] | And Remember...
\ [email protected] / He who controls Purple controls the Universe..
PGP Key given on Request Or at least the Purple parts!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [http://www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P+>+++ L++++>+++++
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5---
X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------
> Can the folks who are seeing crashes running athlon optimised kernels all
> mail me
> - CPU model/stepping
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 902.064
thunderbird 900 (200 MHz FSB)
> - Chipset
IWill KK266R, VIA KT133A north, 686B south bridges. IDE RAID is disabled.
> - Amount of RAM
256 M generic pc100.
> - /proc/mtrr output
(while in X, with geforce2 card, and AGP aperature set to 128)
reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
reg01: base=0xd8000000 (3456MB), size= 32MB: write-combining, count=1
reg05: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1
> - compiler used
gcc version 2.95.4 20010319 (Debian prerelease)
debian gcc package version 1:2.95.3-7
Is there any other information I can provide?
I also seem to have a problem running 2.4.3 (official and ac1-6) kernels
without K7 optimizations, it locks up under I/O using several interrupts (no
IDE involved). I'll post a message about it when I can keep it up long enough
to get debugging information.
Alan Cox wrote:
> Can the folks who are seeing crashes running athlon optimised kernels all mail
> me
>
> - CPU model/stepping
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 1009.002
cache size : 256 KB
> - Chipset
Asus A7V133/WOA
VIA Technologies, Inc. VT8363/8365
> - Amount of RAM
Mem: 525275136 469438464 55836672 0 179589120 221396992
-/+ buffers/cache: 68452352 456822784
Swap: 518180864 0 518180864
>
> - /proc/mtrr output
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0xe2000000 (3616MB), size= 32MB: write-combining, count=2
reg07: base=0xe4000000 (3648MB), size= 64MB: write-combining, count=1
>
> - compiler used
Tried both....
gcc-2.95.3
egcs-2.91.66
>
>
> Alan
>
> -
> 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/
--
Gary White Network Administrator
[email protected] Internet Pathway
Voice 601-776-3355 Fax 601-776-2314
>CPU model/stepping
AMD Duron, 800mhz
>chipset
VIA KT-133; motherboard is an ABIT KT7A-RAID
>amount of RAM
256M, single PC-133 SDRAM
>/proc/mtrr output
reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
reg05: base=0xd0000000 (3328MB), size= 64MB: write-combining, count=1
>compiler used
gcc version 2.95.2
It seems to blow up when I'm doing something which probably wants lots
of memory, ie running X and opening up several mozilla windows (though
it still crashes while just running X, Enlightenment, and w3m in an
Eterm...but it does take a little longer, though still < 30 min.).
I went back to 2.2.18 and the crashing stopped. I am using UDMA66 on
one of my drives, no DMA on the other two.
I haven't tried a non-Athlon optimised kernel, nor one with as few
options as possible; hopefully I will get the chance to do this soon.
--
--Ray
-----------------------------
Sotto la panca la capra crepa
sopra la panca la capra campa