public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: remco@solbors.no (Remco B. Brink)
To: "Jie Zhou" <jiezhou@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.2 kernel mount crash
Date: 08 Mar 2001 15:13:34 +0100	[thread overview]
Message-ID: <m3itlkuz5d.fsf@localhost.localdomain> (raw)
In-Reply-To: <OF586830F9.6A70047B-ON85256A09.004D1EC7@somers.hqregion.ibm.com>
In-Reply-To: <OF586830F9.6A70047B-ON85256A09.004D1EC7@somers.hqregion.ibm.com> ("Jie Zhou"'s message of "Thu, 8 Mar 2001 09:03:27 -0500")

"Jie Zhou" <jiezhou@us.ibm.com> writes:
> I did an upgrade from  kernel-2.2.16 to the latest version-2.4.2.
> During the "make bzImage"step, I got bunch of this warning:
> "pasting would not give a valid preprocessing token". then I just ignored
> it and after all done rebooted the linux and got into the new kernel successfully. 

The above message is related to the version of gcc that you get with
your copy of RedHat7. You might just want to use kgcc instead of gcc
to compile your kernel.

> However, when I tried to mount my DVD RAM using the command mount -t udf /dev/hdb /mnt/dvd
> (I did choose the support for udf filesystem), the command completed with a
> promp appears.but after the 'busy' light on the DVD catridge gets on, it never gets off any
> more, and the computer froze then. I thought it might be because I haven't unmount
> the DVD , so I restarted the computer and use the 'dmesg' command to see what
> happens, then I found a lot of "Unable to identify CD-ROM Format" messages in it. so I did a 'mount'
> command to check whether it's mounted or not, and the result shows that the /dev/hdb(which is the DVD on
> my computer) is not mounted yet.

Same problem here, albeit not with a DVD drive.

After mounting anything with the loopback device (I know it's not working
that well in 2.4.2) all future mounts of my SCSI writer and SCSI cdrom don't 
even return a prompt. The mount just 'hangs' and the mount process can't be killed 
either.

> So I did the mount -t udf /dev/hdb /mnt/dvd again, same thing happens
> again-the computer froze with the DVD light on.
> I read in the book "Running Linux", the author said
> "If any errors or warnings occur while compiling, you cannot expect the
> resulting kernel to work correctly..." I'm wondering if it's because of the the
> warning I got during the process of compiling the image file-"pasting would not give a valid
> preprocessing token" that the mount command fails.

No, probably not.

I used kgcc to compile the kernel, did not get any of the RH7 gcc warning messages
and still am left with a not-so-stable mount.

> Any kind of suggestions are appreciated..

Very much appreciated even ;)

regards,
Remco

-- 
Remco B. Brink                                  Norge-iNvest AS
Kung foo                            http://www.norge-invest.com
        PGP/GnuPG key at http://remco.xgov.net/rbb.pgp

panic("Oh boy, that early out of memory?");
	2.2.16 /usr/src/linux/arch/mips/mm/init.c

  reply	other threads:[~2001-03-08 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08 14:03 2.4.2 kernel mount crash Jie Zhou
2001-03-08 14:13 ` Remco B. Brink [this message]
2001-03-08 14:27   ` Alan Cox
2001-03-08 14:41     ` Remco B. Brink

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=m3itlkuz5d.fsf@localhost.localdomain \
    --to=remco@solbors.no \
    --cc=jiezhou@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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