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

Bug#659410: marked as done ([memtest86] Ignores keyboard input in certain (most) parts, such as keypress on c (configuration))

Your message dated Fri, 02 Sep 2022 17:32:23 +0000
with message-id <[🔎] E1oUAWl-00AN1t-PH@fasolo.debian.org>
and subject line Bug#1016189: Removed package(s) from unstable
has caused the Debian Bug report #659410,
regarding [memtest86] Ignores keyboard input in certain (most) parts, such as keypress on c (configuration)
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 owner@bugs.debian.org
immediately.)


-- 
659410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659410
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: memtest86
Version: 4.0a-0.1
Severity: important
I had the impression that I couldn't access to configuration. I found out that in fact, most of the time, keypresses are ignored. This includes "c", which is supposed to bring up the configuration dialog, Escape, Space and Ctrl+Alt+Del.
My machine is a Gateway NV5909, using an Intel Core i3 and 6 GB of RAM. The CPU has 2 cores and hyperthreading, which shows as 4 CPUs in Linux. memtest86 detects that fine. It gives the state of each core, either as a turning bar, presumably showing the "CPU" is working, or as a "W", presumably showing the "CPU" is waiting.
When "CPU 1" is working, keypresses are ignored. When only "CPU 0" is working, keyboards work fine. I haven't deeply investigated when each "CPU" works, but apparently tests 1 and 3 switch between "CPU" 0 and 1 at 50%. Tests 2 and 4 and perhaps all others use both "CPUs" all the time. It is therefore possible to control memtest86 during at least the first half of test 1 and the first half of test 3.
This happens whether or not a USB keyboard is plugged in, on both the laptop's keyboard and the external keyboard. 

--- System information. ---
Architecture: i386
Kernel: Linux 3.1.0-1-amd64

Debian Release: wheezy/sid
990 testing security.debian.org
990 testing ftp.ca.debian.org
500 unstable ftp.ca.debian.org
1 experimental ftp.ca.debian.org

--- Package information. ---
Depends (Version) | Installed
==========================-+-===========
debconf (>= 0.5) | 1.5.41
OR debconf-2.0 |


Package's Recommends field is empty.

Suggests (Version) | Installed
=============================================-+-======================
hwtools |
memtester |
kernel-patch-badram |
memtest86+ | 4.20-1
grub2 (>= 1.96+20090523-1) |
OR grub (>= 0.95+cvs20040624) |
mtools | 4.0.12-1

--- End Message ---
--- Begin Message --- 
Version: 4.3.7-4+rm

Dear submitter,

as the package memtest86 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1016189

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---
Reply to: