Your message dated Tue, 25 Oct 2022 12:27:48 +0200
with message-id <[email protected]>
and subject line Re: memtest86+: Bullseye version freezes, buster version was
okay
has caused the Debian Bug report #994515,
regarding memtest86+: Bullseye version freezes, buster version was okay
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
994515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994515
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: memtest86+
Version: 5.01-3.1
Severity: normal
Dear Maintainer,
The memtest86+ package shipping with Bullseye (5.01-3.1) freezes during
Test #2 (Address test, own address Parallel) on my machine.
If I downgrade to the package from Buster (5.01-3), it works perfectly
fine.
This is on an older machine (ASUS P5Q-EM DO with Core2 Duo E7400, 6 GB
DDR2).
Let me know if you need further details.
-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages memtest86+ depends on:
ii debconf [debconf-2.0] 1.5.77
memtest86+ recommends no packages.
Versions of packages memtest86+ suggests:
ii grub-pc 2.04-20
pn hwtools <none>
pn kernel-patch-badram <none>
pn memtest86 <none>
pn memtester <none>
pn mtools <none>
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Thu, 3 Mar 2022 18:03:27 +0100 Stefan Ott <[email protected]> wrote:
> This new version does indeed seem to fix the problem for me.
>
> Thank you.
>
Thanks for reporting back.
Fully closing the bug then
--- End Message ---
