Your message dated Sat, 15 Feb 2014 10:45:08 +0100
with message-id
<cagnkunehes2nda49dmzmxpkz4rqq+p9axqyrbgxghwh7hrg...@mail.gmail.com>
and subject line read-edid: get-edid harms interrupt management
has caused the Debian Bug report #81776,
regarding read-edid: get-edid harms interrupt management
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.)
--
81776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81776
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: read-edid
Version: 1.4.0-2
Severity: important
The problem is quite serious, but I do not have many details. I'll try
to describe it.
I did
get-edid | parse-edid
(I suppose this is the right way to use it, but the package comes with no
documentation at all, not even a readme.)
After doing that a couple of times, the system exhibited strange
behaviour. The beeps were longer than normal, the system was slow, the
X server did not work well. Specifically, the X display went black and,
in order to make it appear again, I had to press a key or move the
mouse. After a couple of seconds it went black again. In the meantime,
the image was not perfectly normal, as if the video driver lost some
interrupts while refreshing. In text mode, everything looked normal,
apart from the beep and the slowness. But the clock was much slower
than normal. In 12 hours (more or less) the clock advanced by less than
three hours. I looked at the timer interrupts (cat /proc/interrupts),
and it seemed to me that the interrupts were much less than 100 per
second, as I suppose they should be. After reboot everything was okay.
This sort of behaviour is particularly bad for my box, which is a
server.
the process it does some harm to the interrupt handling (I don't know
how). The most evident result was that the clock went on much more
slowly than due. As a matter of fact, when I cam back to the office in
the morning, the clock was showing midnight of the previous day, and the
cron jobs scheduled for the night were not started. I rebooted and
everything should be fine now.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux pot 2.2.13 #17 Tue May 9 13:12:19 CEST 2000 i686 unknown
Versions of the packages read-edid depends on:
ii libc6 2.2-6 GNU C Library: Shared libraries and Timezone
--- End Message ---
--- Begin Message ---
This bug is not longer present in 3.X branch, due to the new I2C
interface, please update.
--
Pozdrawiam,
Dariusz Dwornikowski, Assistant
Institute of Computing Science, Poznań University of Technology
www.cs.put.poznan.pl/ddwornikowski/
room 2.7.2 BTiCW | tel. +48 61 665 29 41
--- End Message ---
