linux-kernel - Re: [Bug #14294] kernel BUG at drivers/ide/ide-disk.c:187

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 29 Nov 2009 00:54:00 +0100
From:	Santiago Garcia Mantinan <manty@...ty.net>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	David Miller <davem@...emloft.net>
Subject: Re: [Bug #14294] kernel BUG at drivers/ide/ide-disk.c:187

> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14294

Hi!

Sorry for not answering before, I've been running 2.6.31 patched for all
this time and the results are a bit dissapointing...

The first run was for almost a month and ended up with half a hang, I could
read on the console that there had been an error on one of the disks, dma
error, the keyboard was working, getty seemed to work but then login didn't
show up when entering the username even though the disks led was flashing
when I operated the console entering usernames and all that. This hang was
not like the hangs I had before, don't know if it was due to the patch and
the unknown operation arriving to the IDE disk, but the message that the
patch was supposed to display was not displayed at all.

The second run is current run I believe, currently it has an uptime of 18
days and not problem was showed over this time.

So... I'm afraid I'm not able to reproduce this and maybe the whole problem
is hardware related, even though the machine had been running with 2.6.30 in
a stable way, it is an old machine, so maybe it is not as healthy as I
believed, and even though memtest doesn't show any errors there could be
some dma problems or other weird things happening around :-(

So... I'd say you can close the bug and if I happen to find it again... I'll
report it again.

Sorry for all the noise.

Regards...
-- 
Manty/BestiaTester -> http://manty.net
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/