clone 629506 -1 reassign -1 memtest86 retitle -1 memtest86.bin crashes if loader ends up putting it not at 9000:0000 tags -1 + patch thanks
On Sat, Feb 28, 2015 at 08:24:02PM +0000, Al Viro wrote: > > FWIW, the effects described in this bug report are 100% reproducible > > on any version, as long as the loader (lilo, grub, whatever) ends up putting > > the bootsect+setup in any location below 9000:0000. > > ... and the problem actually predates the fork of memtest86 and memtest86+; > IOW, the same crap is present in memtest86 as well - it triggers on the same > boxen, the same patch applies[*] and gets the damn thing working. > > How does one normally deal with that kind of shared bugs? Two packages > with identical bugs; same setups trigger those, same fix, code actually > predates the fork that produced one of those packages from another. > Opening a matching bug report in memtest86 and refering to this one > in it? At least memtest86 and memtest86+ have the same maintainer... Well, since the maintaince is a bit separate (despite using the same codebase for the 2 packages as well), I'm cloning the bug. BTW, memtest86 as an OpenSource package is now discontinued, the guys at PassMark Software, who have apparently acquired rights about it and released the last 4.x versions, choose to release 5.x and later (UEFI version, not BIOS-compatible any more) as closed source (citing dev costs and lack of contribution as reason). > [*] except that there setup.S has CRLF for EOL, so applying it requires > either converting the sucker into normal text file first, or applying via > sed -e 's/$/\r/' | patch -p1 -E --binary OK, thanks. I'll upload this to experimental to avoid interfering with the jessie release process. Did you contact upstream about this issue already ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
