linux-kernel - Re: 2.6.19 does not boot, while 2.6.19-rc4 does

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: <20061209103954.868f818a.randy.dunlap@oracle.com>
Date:	Sat, 9 Dec 2006 10:39:54 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Norbert Preining <preining@...ic.at>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.19 does not boot, while 2.6.19-rc4 does

On Sat, 9 Dec 2006 16:28:59 +0100 Norbert Preining wrote:

> Hi all!
> 
> [Please Cc]
> 
> I copied my old config-2.6.19-rc4 to a clean linux-2.6.19 tree, called
> make oldconfig; make, installed the kernel and modules, but the kernel
> cannot find the root file system.
> 
> I diffed the two config files and the only not-comment diff is:
> -# CONFIG_SYSCTL_SYSCALL is not set
> +CONFIG_SYSCTL_SYSCALL=y
> (how did this happen?)

The default changed from n to y.

> a part of the dmesg is included here (from -rc4):
> 
> libata version 2.00 loaded.
> ata_piix 0000:00:1f.2: version 2.00ac6
> ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
> ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 20
> PCI: Setting latency timer of device 0000:00:1f.2 to 64
> ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x18B0 irq 14
> ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18B8 irq 15
> scsi0 : ata_piix
> PM: Adding info for No Bus:host0
> ata1.00: ATA-7, max UDMA/133, 195371568 sectors: LBA48 NCQ (depth 0/32)
> ata1.00: ata1: dev 0 multi count 16
> ata1.00: configured for UDMA/133
> scsi1 : ata_piix

That didn't help (me).

> Hardware: Acer TravelMate 3012
> 
> 
> Any suggestions what to do next?

Test 2.6.19-rc5, 2.6.19-rc6, and then use git snapshots or
git bisect to focus in on the breakage.

And post more complete boot logs.

---
~Randy
-
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/