linux-kernel - Re: Kernel BUG at fs/mpage.c:489

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]

Message-ID: <20080212215006.170ade88@core>
Date:	Tue, 12 Feb 2008 21:50:06 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Bart Dopheide <dopheide@....nl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Kernel BUG at fs/mpage.c:489

> Feb 12 19:55:08 butterfly kernel: hde: dma timeout error: status=0xd0 { Busy }
> Feb 12 19:55:08 butterfly kernel: ide: failed opcode was: unknown

Your drive stopped responding.

> Feb 12 19:55:08 butterfly kernel: hde: DMA disabled
> Feb 12 19:55:08 butterfly kernel: PDC202XX: Primary channel reset.
> Feb 12 19:55:08 butterfly kernel: PDC202XX: Secondary channel reset.

We gave it a good kicking and it stayed offline

> Feb 12 19:55:08 butterfly kernel: hde: set_drive_speed_status: status=0xd0 { Busy }
> Feb 12 19:55:08 butterfly kernel: ide: failed opcode was: unknown
> Feb 12 19:55:47 butterfly kernel: ide2: reset timed-out, status=0xd0
> Feb 12 19:55:47 butterfly kernel: hde: status timeout: status=0xd0 { Busy }

And we gave up.

Almost certainly a hardware fail of some sort.
--
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/