From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: REVISED: Experimentation with Athlon and fast_page_copy
Date: Sat, 5 May 2001 04:28:03 +0200 [thread overview]
Message-ID: <01050504280300.03550@SunWave1> (raw)
> What still stands out is that exactly _zero_ people have reported the same
> problem with non VIA chipset Athlons.
Sorry Alan, but...
My (very) old Athlon 550 (model 1, stepping 2) show it on my MSI MS-6167 (AMD
Irongate C4) with your 2.4.4-ac5, now :-(
Even with or without apm/acpi enabled.
It freezes during "Freeing unused kernel memory: 172k freed".
Never saw this before.
I am open for any test fixes...
-Dieter
SuSE 7.1 (glibc-2.2, gcc-2.95.2)
Linux version 2.4.4 (root@SunWave1) (gcc version 2.95.2 19991024 (release))
#1 Sun Apr 29 02:30:34 CEST 2001
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000013ff0000 (usable)
BIOS-e820: 0000000013ff0000 - 0000000013ff3000 (ACPI NVS)
BIOS-e820: 0000000013ff3000 - 0000000014000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Scan SMP from c0000000 for 1024 bytes.
Scan SMP from c009fc00 for 1024 bytes.
Scan SMP from c00f0000 for 65536 bytes.
Scan SMP from c009f800 for 4096 bytes.
On node 0 totalpages: 81904
zone(0): 4096 pages.
zone(1): 77808 pages.
zone(2): 0 pages.
mapped APIC to ffffe000 (01555000)
SunWave1>cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 1
model name : AMD-K7(tm) Processor
stepping : 2
cpu MHz : 548.950
cache size : 512 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 mmx syscall mmxext 3dnowext 3dnow
bogomips : 1094.45
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Kölln-Straße 30
D-22527 Hamburg, Germany
email: nuetzel@kogs.informatik.uni-hamburg.de
@home: Dieter.Nuetzel@hamburg.de
next reply other threads:[~2001-05-05 2:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 2:28 Dieter Nützel [this message]
2001-05-05 7:13 ` REVISED: Experimentation with Athlon and fast_page_copy Alan Cox
2001-05-09 23:56 ` Dieter Nützel
-- strict thread matches above, loose matches on Subject: below --
2001-05-05 17:34 Jeremy
2001-05-04 19:14 Manfred Spraul
2001-05-04 19:30 ` Seth Goldberg
2001-05-04 21:43 ` Alan Cox
2001-05-08 21:15 ` Arjan van de Ven
2001-05-04 17:22 Seth Goldberg
2001-05-04 19:48 ` Brian Gerst
2001-05-04 21:09 ` Alan Cox
2001-05-04 22:26 ` Aaron Tiensivu
2001-05-04 18:10 ` Bobby D. Bryant
2001-05-05 6:43 ` John R Lenton
2001-05-05 7:20 ` Alan Cox
2001-05-07 1:26 ` John R Lenton
2001-05-07 1:30 ` Jeremy
2001-05-05 0:26 ` Joseph Carter
2001-05-05 3:51 ` Chris Wedgwood
2001-05-05 4:08 ` Seth Goldberg
2001-05-05 5:45 ` Joseph Carter
2001-05-09 2:11 ` Tom Leete
2001-05-09 8:49 ` Alan Cox
2001-05-09 11:38 ` Tom Leete
2001-05-09 12:38 ` Alan Cox
2001-05-09 13:02 ` Tom Leete
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01050504280300.03550@SunWave1 \
--to=dieter.nuetzel@hamburg.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox