Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030245AbWALEeH (ORCPT ); Wed, 11 Jan 2006 23:34:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030235AbWALEeG (ORCPT ); Wed, 11 Jan 2006 23:34:06 -0500 Received: from smtp.osdl.org ([65.172.181.4]:47832 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S965013AbWALEeE (ORCPT ); Wed, 11 Jan 2006 23:34:04 -0500 Date: Wed, 11 Jan 2006 20:33:32 -0800 From: Andrew Morton To: Reuben Farrelly Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com, Greg KH , linux-usb-devel@lists.sourceforge.net, Neil Brown , linux-acpi@vger.kernel.org Subject: Re: 2.6.15-mm3 Message-Id: <20060111203332.50c45031.akpm@osdl.org> In-Reply-To: <43C5D537.7020800@reub.net> References: <20060111042135.24faf878.akpm@osdl.org> <43C5D537.7020800@reub.net> X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3784 Lines: 99 Reuben Farrelly wrote: > > > > On 12/01/2006 1:21 a.m., Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm3/ > > > > - New config options (VMSPLIT_*) to permit non-standard user/kernel > > splitting on x86. Needs testing please. > > > > - Lots of updates to the USB, PCI, driver and I2C trees. This is usually a > > worry. > > > > - Multiblock allocation speedup for ext3. This is only used by direct-IO at > > present. > > > > - Reminder: -mm kernel commit activity can be reviewed by subscribing to the > > mm-commits mailing list. > > > > echo "subscribe mm-commits" | mail marordomo@vger.kernel.org > > > > - If you hit a bug in -mm and it's not obvious which patch caused it, it is > > most valuable if you can perform a bisection search to identify which patch > > introduced the bug. Instructions for this process are at > > > > http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt > > > > But beware that this process takes some time (around ten rebuilds and > > reboots), so consider reporting the bug first and if we cannot immediately > > identify the faulty patch, then perform the bisection search. > > I'm not sure if this is new to -mm3, but it's the first time I have seen it. > > The sequence of events leading up to this was to reboot the machine, it came up > and crashed: > > Call Trace: > [] show_stack+0x9b/0xc0 > [] show_registers+0x162/0x1e7 > [] die+0x126/0x231 > [] do_page_fault+0x271/0x5b9 > [] error_code+0x4f/0x54 > [] class_device_del+0xa3/0x156 > [] class_device_unregister+0xb/0x15 > [] scsi_remove_host+0xb4/0xef > There's some trace missing here. I assume it's the same ata_device_add() thing. > uhci_hcd 0000:00:1d.2: irq 185, io base 0x0000d400 > usb usb4: configuration #1 chosen from 1 choice > hub 4-0:1.0: USB hub found > hub 4-0:1.0: 2 ports detected > ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 169 > uhci_hcd 0000:00:1d.3: UHCI Host Controller > uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5 > uhci_hcd 0000:00:1d.3: irq 169, io base 0x0000d800 > usb usb5: configuration #1 chosen from 1 choice > hub 5-0:1.0: USB hub found > hub 5-0:1.0: 2 ports detected > Initializing USB Mass Storage driver... > irq 193: nobody cared (try booting with the "irqpoll" option) > [] dump_stack+0x17/0x19 > [] __report_bad_irq+0x27/0x83 > [] note_interrupt+0x7e/0x21d > [] __do_IRQ+0xd3/0xef > [] do_IRQ+0x3d/0x57 > ======================= > [] common_interrupt+0x1a/0x20 > [] cpu_idle+0x63/0x78 > [] rest_init+0x23/0x2e > [] start_kernel+0x2ca/0x34b > [] 0xc0100210 > handlers: > [] (usb_hcd_irq+0x0/0x56) > Disabling IRQ #193 USB lost its interrupt. Could be USB, more likely ACPI. > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block > 2, size 4096) > ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block > 16, size 4096) > EXT3-fs: unable to read superblock > EXT2-fs: unable to read superblock > isofs_fill_super: bread failed, dev=md0, iso_blknum=16, block=32 > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0) > Looks like RAID0 keeled over. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/