Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751244AbWAVAV7 (ORCPT ); Sat, 21 Jan 2006 19:21:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751248AbWAVAV7 (ORCPT ); Sat, 21 Jan 2006 19:21:59 -0500 Received: from xenotime.net ([66.160.160.81]:35983 "HELO xenotime.net") by vger.kernel.org with SMTP id S1751246AbWAVAV5 (ORCPT ); Sat, 21 Jan 2006 19:21:57 -0500 Date: Sat, 21 Jan 2006 16:22:03 -0800 From: "Randy.Dunlap" To: "J.A. Magallon" Cc: akpm@osdl.org, linux-kernel@vger.kernel.org Subject: Re: SMP+nosmp=hang [was: Re: 2.6.15-rc5-mm2] Message-Id: <20060121162203.16afe24d.rdunlap@xenotime.net> In-Reply-To: <20060122004636.0837de67@werewolf.auna.net> References: <20051211041308.7bb19454.akpm@osdl.org> <20051214095459.3912d59e@werewolf.auna.net> <20060120192259.4460af42.akpm@osdl.org> <20060122004636.0837de67@werewolf.auna.net> Organization: YPO4 X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.3; x86_64-unknown-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: 3535 Lines: 81 On Sun, 22 Jan 2006 00:46:36 +0100 J.A. Magallon wrote: > On Fri, 20 Jan 2006 19:22:59 -0800, Andrew Morton wrote: > > > "J.A. Magallon" wrote: > > > > > > On Sun, 11 Dec 2005 04:13:08 -0800, Andrew Morton wrote: > > > > > > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm2/ > > > > > > > > > > Booting a SMP built kernel with 'nosmp' just hangs at the VFS layer, with > > > the message about 'not being able to find root device sda1'. > > > sda is a SATA drive on an Intel ICH5 controller: > > > > > > libata version 1.20 loaded. > > > ata_piix 0000:00:1f.2: version 1.05 > > > ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16 > > > PCI: Setting latency timer of device 0000:00:1f.2 to 64 > > > ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16 > > > ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16 > > > ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f > > > ata1: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48 > > > ata1: dev 0 configured for UDMA/133 > > > scsi0 : ata_piix > > > ATA: abnormal status 0x7F on port 0xC807 > > > scsi1 : ata_piix > > > Vendor: ATA Model: ST3200822AS Rev: 3.01 > > > Type: Direct-Access ANSI SCSI revision: 05 > > > SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB) > > > SCSI device sda: drive cache: write back > > > SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB) > > > SCSI device sda: drive cache: write back > > > sda: sda1 sda2 sda3 > > > sd 0:0:0:0: Attached scsi disk sda > > > > > > I would have to double check, but I think it even missed the USB keyboard. > > > > > > > Is this still happening? > > Yes. I have just tried with 2.6.16-rc1-mm2, and the result is the same. > No root device. > > The nosmp-booted kernel looks much much slow than the SMP one, it takes > ages to detect devices like usb ones, and even spent about 20 seconds here: > > [ 0.431601] libata version 1.20 loaded. > [ 0.431652] ata_piix 0000:00:1f.2: version 1.05 > [ 0.431670] ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16 > [ 0.431792] PCI: Setting latency timer of device 0000:00:1f.2 to 64 > [ 0.431852] ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 16 > [ 0.431950] ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD008 irq 16 > >>>>>>>>>>>>> here <<<<<<<<<<<<<<<<<< > [ 0.690451] ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f > [ 0.690456] ata1: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48 > [ 0.696278] ata1: dev 0 configured for UDMA/133 > [ 0.701627] scsi0 : ata_piix > [ 1.937443] scsi1 : ata_piix > > and it did not detect any drive, so the no-root-device error. This one can be > a detection timeout, but as I say also the USB detection is dog slooow. > > Need some info ? .config, or the like ? Hi, I've been testing this also. I also see the problem. I don't yet know what to do about it, but it's easy to reproduce. I'll continue to look at it. For a temporary workaround, booting with "irqpoll" might help, but that's not the real solution IMO. --- ~Randy - 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/