All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: v2.6.22.1-rt5
Date: Tue, 24 Jul 2007 21:42:09 -0400	[thread overview]
Message-ID: <200707242142.09407.gene.heskett@gmail.com> (raw)
In-Reply-To: <20070724191027.GA13268@elte.hu>

On Tuesday 24 July 2007, Ingo Molnar wrote:
>* Gene Heskett <gene.heskett@gmail.com> wrote:
>> The above stanza still needs some tlc.  I built a 2.6.22.1-rt6 (rt5
>> wouldn't build) using the same old config that a make oldconfig didn't
>> fuss about, but the reboot never completed, see the attached, heavily
>> smunched camera shot of the panic.
>>
>> Kinda looks like hda/sda confusion, with rt3 (this boot), its hda*,
>> what is it now?  fstab or kernel config error?
>
>yeah, as long as your filesystems are created with a proper label, all
>that you need to do is to change all 'hda' to 'sda' in the new kernel's
>/etc/grub.conf entry. (or enable the old IDE code in the .config, under
>CONFIG_IDE)
>
>	Ingo

I believe it is on:

[root@coyote linux-2.6.22.1-rt6]# grep CONFIG_IDE .config
CONFIG_IDE=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y
CONFIG_IDE_GENERIC=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_IVB is not set


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Computer programmers never die, they just get lost in the processing.

  parent reply	other threads:[~2007-07-25  1:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 12:04 v2.6.22.1-rt5 Ingo Molnar
2007-07-24 13:18 ` v2.6.22.1-rt5 Andi Kleen
2007-07-24 12:27   ` v2.6.23-rc1-rt0 Ingo Molnar
2007-07-24 15:56 ` v2.6.22.1-rt5 Gene Heskett
2007-07-24 19:10   ` v2.6.22.1-rt5 Ingo Molnar
2007-07-25  1:29     ` v2.6.22.1-rt5 Gene Heskett
2007-07-25  1:36     ` v2.6.22.1-rt5 Gene Heskett
2007-07-25  7:52       ` v2.6.22.1-rt5 Ingo Molnar
2007-07-25  1:42     ` Gene Heskett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23 21:02 v2.6.22.1-rt5 Ingo Molnar
2007-07-23 21:29 ` v2.6.22.1-rt5 Rui Nuno Capela
2007-07-23 21:30   ` v2.6.22.1-rt5 Daniel Walker
2007-07-23 22:05     ` v2.6.22.1-rt5 Thomas Gleixner
2007-07-23 22:11       ` v2.6.22.1-rt5 Thomas Gleixner
2007-07-24  7:39   ` v2.6.22.1-rt5 Ingo Molnar
2007-07-24 19:34     ` v2.6.22.1-rt5 Fernando Lopez-Lezcano
2007-07-24 19:35       ` v2.6.22.1-rt5 Fernando Lopez-Lezcano
2007-07-24 20:05         ` v2.6.22.1-rt5 Ingo Molnar
2007-07-24 20:23           ` v2.6.22.1-rt5 Fernando Lopez-Lezcano
2007-07-24 20:34             ` v2.6.22.1-rt5 Ingo Molnar
2007-07-24 20:38               ` v2.6.22.1-rt5 Fernando Lopez-Lezcano
2007-07-25  7:34               ` v2.6.22.1-rt5 Alessio Igor Bogani

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=200707242142.09407.gene.heskett@gmail.com \
    --to=gene.heskett@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.