Hi, On Sat, 2006-11-25 at 19:19:58 +0100, BERTRAND Joël wrote: > Package: dpkg > Version: 1.13.24 > Architecture: sparc > Severity: grave
> I have some SparcSTATION 20 with one or two SuperSPARC-II and 448 MB > of memory (thus, HIGHMEM is used). On these workstations, dpkg works fine. > If I replace SuperSPARC-II by one, two or four ROSS RT-626, I cannot use > dpkg because it craches with a random error when it tries to configure > the package (it cannot read the configuration script due to a data > corruption. Sometimes, an EOF in the middle of the script...). > > I have tested dpkg on three SS20 that perfectly work with SuperSPARC > and with four different HyperSPARC modules, and with and without HIGHMEM. > > Results : in all configurations (with and without HIGHMEM), dpkg > crashes with HyperSPARC and works with SuperSPARC. I don't understand > this memory corruption because the workstations work fine in all > configurations I have tested ! Kernels are 2.6.18.x. Given that this happens when changing the CPU, and that this does not happen anywhere else, I'd say it's a hw or kernel problem. Also given the mails[0] in debian-sparc about past state of HyperSparc support I would say this is not related to dpkg, and the bug would need closing or to be reassigned. But I've CCed debian-sparc for comments. [0] <http://lists.debian.org/debian-sparc/2006/04/msg00003.html> <http://lists.debian.org/debian-sparc/2006/04/msg00018.html> <http://lists.debian.org/debian-sparc/2006/06/msg00030.html> regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
