James Jones wrote:
I decided I shouldn't ignore the blinky exclamation point any more,
and fired up up2grade. It upgraded the kernel to 2.4.18-27.8.0, among
other things, and I rebooted...
...only to get a kernel panic, complaining about not being able to
mount the root fs.
If I choose to boo
ot
into the old kernel if necessary.
> -Original Message-
> From: James Jones [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 8:44 PM
> To: [EMAIL PROTECTED]
> Subject: Re: kernel panic after kernel upgrade
>
>
> Dave Tibbals wrote:
>
> >Ta
Dave Tibbals wrote:
Take a look at /boot/grub/menu.lst It should look like the following:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd path
Take a look at /boot/grub/menu.lst It should look like the following:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /bo
On Sat, 2002-12-21 at 05:57, Arjan van de Ven wrote:
> > To be clear: specifying "rootflags=data=writeback" causes the kernel
> > panic.
>
> it's also the wrong thing to do: the initrd mounts your root filesystem,
> not the kernel. So the mount flag need to be set within the initrd, and
> afaik
On Sat, 2002-12-21 at 00:32, Tom Ball wrote:
> On Fri, 2002-12-20 at 12:05, Bill Rugolsky Jr. wrote:
> > On Fri, Dec 20, 2002 at 09:12:26AM -0800, Tom Ball wrote:
> > > title Red Hat Linux (2.4.18-18.8.0) - Home
> > > root (hd0,5)
> > > kernel /boot/vmlinuz-2.4.18-18.8.0 ro root=LABEL=/ rootfla
On Fri, Dec 20, 2002 at 09:12:26AM -0800, Tom Ball wrote:
> On Thu, 2002-12-19 at 23:26, Kevin McConnell wrote:
> BTW, the writeback option support is in (search for "writeback"):
>
> file:///usr/src/linux-2.4/fs/ext3/super.c
>
> and its use is in:
>
> file:///usr/src/linux-2.4/fs/ext3/fsy
On Fri, Dec 20, 2002 at 03:32:01PM -0800, Tom Ball wrote:
> On Fri, 2002-12-20 at 12:05, Bill Rugolsky Jr. wrote:
> > On Fri, Dec 20, 2002 at 09:12:26AM -0800, Tom Ball wrote:
> > > title Red Hat Linux (2.4.18-18.8.0) - Home
> > > root (hd0,5)
> > > kernel /boot/vmlinuz-2.4.18-18.8.0 ro root=LA
On Fri, 2002-12-20 at 12:05, Bill Rugolsky Jr. wrote:
> On Fri, Dec 20, 2002 at 09:12:26AM -0800, Tom Ball wrote:
> > title Red Hat Linux (2.4.18-18.8.0) - Home
> > root (hd0,5)
> > kernel /boot/vmlinuz-2.4.18-18.8.0 ro root=LABEL=/ rootflags=mode=writeback
> > initrd /boot/initrd-2.4.1
On Fri, Dec 20, 2002 at 09:12:26AM -0800, Tom Ball wrote:
> title Red Hat Linux (2.4.18-18.8.0) - Home
> root (hd0,5)
> kernel /boot/vmlinuz-2.4.18-18.8.0 ro root=LABEL=/ rootflags=mode=writeback
> initrd /boot/initrd-2.4.18-18.8.0.img
>
> As someone previously suggested, I also
On Thu, 2002-12-19 at 23:26, Kevin McConnell wrote:
> --- Tom Ball <[EMAIL PROTECTED]> wrote:
> > Has anyone been able to boot Red Hat 8.0 with an
> > ext3 root device with
> > it set to writeback mode? When I add
> > bootflags=mode=writeback to my
> > kernel line in Grub, the kernel panics becaus
On 20 Dec 2002, Chris Kloiber wrote:
> Wouldn't this be something to be put in /etc/fstab where you normally
> see "defaults"? Yep, check out 'man mount', it's in the 'Mount options
> for ext3' section. data=writeback. Before you actually do this however,
> I've heard this option is fast, but not
Wouldn't this be something to be put in /etc/fstab where you normally
see "defaults"? Yep, check out 'man mount', it's in the 'Mount options
for ext3' section. data=writeback. Before you actually do this however,
I've heard this option is fast, but not always safe in the event of a
crash. YMMV.
On
--- Tom Ball <[EMAIL PROTECTED]> wrote:
> Has anyone been able to boot Red Hat 8.0 with an
> ext3 root device with
> it set to writeback mode? When I add
> bootflags=mode=writeback to my
> kernel line in Grub, the kernel panics because it
> doesn't recognize the
> option.
Where did you read ab
Rigoberto Spake:
>Andrew
>
> Hello Andrew.. thanks for your response... I did not
> express what I wanted to know.. the problem is that
> I'm getting a kernel panic... unfortunately I'm using
> X, so I can not see anything except for the blinking
> lights... I was wondering if I could get any
> i
>On Wed, 2002-12-11 at 10:14, Rigoberto de la Cruz
>wrote:
>> I was wondering what a kernel panic code means...
CAPS
>> LOCK and SCROLL LOCK are flashing (at the same
time).
>> Does anyone know what that means? does anyone know
>> here to find any info... thanks...
>
>Hello Rigoberto,
>
>A kernel
On Wed, 2002-12-11 at 10:14, Rigoberto de la Cruz wrote:
> I was wondering what a kernel panic code means... CAPS
> LOCK and SCROLL LOCK are flashing (at the same time).
> Does anyone know what that means? does anyone know
> here to find any info... thanks...
Hello Rigoberto,
A kernel panic is es
17 matches
Mail list logo
