[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#400372: marked as done (dpkg randomly craches on Sparc32 running HyperSPARC processor)



Your message dated Sun, 15 Jul 2007 10:47:14 +0200
with message-id <20070715084714.GB17820@wavehammer.waldi.eu.org>
and subject line sparc32 support retired
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: dpkg
Version: 1.13.24
Architecture: sparc
Severity: grave

	Hello,

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.

	Any idea ?

	Regards,

	JKB


--- End Message ---
--- Begin Message ---
sparc32 support has been retired.

Bastian

-- 
The sight of death frightens them [Earthers].
		-- Kras the Klingon, "Friday's Child", stardate 3497.2

--- End Message ---

Reply to: