From: Randy Dunlap <randy.dunlap@oracle.com>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19 does not boot, while 2.6.19-rc4 does
Date: Sat, 9 Dec 2006 10:39:54 -0800 [thread overview]
Message-ID: <20061209103954.868f818a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20061209152859.GA14037@gamma.logic.tuwien.ac.at>
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
next prev parent reply other threads:[~2006-12-09 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 15:28 Norbert Preining
2006-12-09 18:39 ` Randy Dunlap [this message]
2006-12-10 11:12 ` Norbert Preining
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061209103954.868f818a.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®