On Sat, 8 Dec 2007 12:24:14 -0800, Steve Langasek wrote:

> On Sat, Dec 08, 2007 at 09:57:00PM +0900, Atsuhito Kohda wrote:
> > Hi all, (please keep Cc to me)
> 
> > recently, libc6.1 2.7-3 got into testing but it caused
> > segfault with my all/two alpha machines so I don't understand
> > why it got into testing.
> 
> Because no one reported such a bug while the package was in unstable.

Okay, so dropped [EMAIL PROTECTED]

> It doesn't happen on my alpha or on the Debian buildd.  Please provide more
> information about your system's hardware and kernel. (uname -a and cat
> /proc/cpuinfo would be a start.)

Here are outputs:

$ uname -a
Linux nsx 2.6.22-3-alpha-generic #1 Mon Oct 22 20:57:06 UTC 2007 alpha GNU/Linux
$ cat /proc/cpuinfo
cpu                     : Alpha
cpu model               : EV56
cpu variation           : 7
cpu revision            : 0
cpu serial number       :
system type             : EB164
system variation        : LX164
system revision         : 0
system serial number    :
cycle frequency [Hz]    : 666466480 est.
timer frequency [Hz]    : 1024.00
page size [bytes]       : 8192
phys. address bits      : 40
max. addr. space #      : 127
BogoMIPS                : 1321.80
kernel unaligned acc    : 0 (pc=0,va=0)
user unaligned acc      : 31523 (pc=12001fc74,va=12102a59b)
platform string         : Digital AlphaPC 164LX 666 MHz
cpus detected           : 1
L1 Icache               : 8K, 1-way, 32b line
L1 Dcache               : 8K, 1-way, 32b line
L2 cache                : 96K, 3-way, 64b line
L3 cache                : 2048K, 1-way, 64b line

Another machine is almost the same but its kernel is older
than the above by some reason:

$ uname -a
Linux torneo 2.6.12-1-alpha-generic #1 Tue Sep 27 10:23:27 UTC 2005 alpha 
GNU/Linux

Thanks for your advice.             2007-12-9(Sun)

-- 
 Debian Developer & Debian JP Developer - much more I18N of Debian
 Atsuhito Kohda <kohda AT debian.org>
 Department of Math., Univ. of Tokushima


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to