Your message dated Sat, 15 Feb 2014 10:57:06 +0100
with message-id 
<cagnkund19cmde-djo5q1qq+rljmzecczaw2trdevvyspzka...@mail.gmail.com>
and subject line read-edid: get-edid goes into a loop on vm86old
has caused the Debian Bug report #111666,
regarding read-edid: get-edid goes into a loop on vm86old
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.)


-- 
111666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=111666
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: read-edid
Version: 1.4.0-2
Severity: important

get-edid is shown in Running state and never exits. See attached strace.

Video card:
(--) PCI:*(1:0:0) NVidia Riva Ultra 64 rev 21, Mem @ 0xd8000000/24, 
0xda000000/25
chipset: "RIVATNT2 M64"


write(2, "\tFunction unsupported\n", 22) = 22
write(2, "\tCall failed\n\n", 14)       = 14
write(2, "The EDID data should not be trus"..., 59) = 59
write(2, "Reading next EDID block\n", 24) = 24
write(2, "\nVBE/DDC service about to be cal"..., 36) = 36
write(2, "\tRead EDID\n", 11)           = 11
write(2, "\n\tPerforming real mode VBE call\n", 32) = 32
write(2, "\tInterrupt 0x10 ax=0x4f15 bx=0x1"..., 44) = 44
vm86old(0x804c5ac)                      = -1 ENOSYS (Function not implemented)
write(2, "\tCall successful\n\n", 18)   = 18
write(2, "Reading next EDID block\n", 24) = 24
write(2, "\nVBE/DDC service about to be cal"..., 36) = 36
write(2, "\tRead EDID\n", 11)           = 11
write(2, "\n\tPerforming real mode VBE call\n", 32) = 32
write(2, "\tInterrupt 0x10 ax=0x4f15 bx=0x1"..., 44) = 44
vm86old(0x804c5ac)                      = -1 ENOSYS (Function not implemented)
write(2, "\tCall successful\n\n", 18)   = 18
write(2, "EDID claims 255 more blocks left"..., 33) = 33
write(2, "EDID keeps on claiming same numb"..., 63) = 63
write(2, "Reading next EDID block\n", 24) = 24
write(2, "\nVBE/DDC service about to be cal"..., 36) = 36
write(2, "\tRead EDID\n", 11)           = 11
write(2, "\n\tPerforming real mode VBE call\n", 32) = 32
write(2, "\tInterrupt 0x10 ax=0x4f15 bx=0x1"..., 44) = 44
      0:00 sh /var/lib/dpkg/info/xserver-xfree86.config configur 6255 tty1     
S      0:00 parse-edid
 6273 ?        S      0:00 nmbd -a
 6277 tty3     S      0:00 vim get-edid.bug
 6254 tty1     R      3:04 get-edid

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux sunone 2.2.20pre8 #2 Wed Aug 1 18:35:07 CEST 2001 i686 
unknown

Versions of the packages read-edid depends on:
ii  libc6          2.2.4-1        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 ---

Reply via email to