From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3ED49EB8.1080506@aitel.hist.no> Date: Wed, 28 May 2003 13:34:16 +0200 From: Helge Hafting MIME-Version: 1.0 Subject: Re: 2.5.70-mm1 bootcrash, possibly IDE or RAID References: <20030408042239.053e1d23.akpm@digeo.com> <3ED49A14.2020704@aitel.hist.no> <20030528111345.GU8978@holomorphy.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: William Lee Irwin III Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: William Lee Irwin III wrote: > On Wed, May 28, 2003 at 01:14:28PM +0200, Helge Hafting wrote: > >>2.5.69-mm8 is fine, 2.5.67-mm1 dies before mounting anything read-write. Argh. I meant 2.5.70-mm1. Followup to the wrong message. :-( The early kernel boot is fine, the penguin appear, a bunch of the usual messages scroll by too fast to read, and then it hangs. The kernel is UP, with preempt & devfs. All filesystems are ext2. This kernel has no module support. Root is on raid-1, there are two ide disks connected to this controller on separate cables: 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] Here's the decoded crash, written down by hand: bio_endio _end_that_request_first ide_end_request ide_dma_intr ide_intr ide_dma_intr handle_IRQ_event do_IRQ default_idle default_idle common_interrupt default_idle default_idle default_idle cpu_idle rest_init start_kernel unknown_bootoption <0>Kwrnel Panic fatal exception in interrupt in interrupt - not syncing -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org