2.4.2 kernel mount crash

2.4.2 kernel mount crash

[Jie Zhou]

Hi, Folks,

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. 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.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.
Any kind of suggestions are appreciated..

-Jie

Re: 2.4.2 kernel mount crash

[Remco B. Brink]

"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

Re: 2.4.2 kernel mount crash

[Alan Cox]

> > During the "make bzImage"step, I got bunch of this warning:
> > "pasting would not give a valid preprocessing token". then I just ignored

The pasting warning is harmless

> 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.

kgcc or gcc 2.96-69  (2.96-74 for DAC960 due to a structure packing assumption
in DAC960)

> 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.

Its certainly worth building with kgcc as well to make sure, and in this case
it looks like the problem is really in the kernel proper

Re: 2.4.2 kernel mount crash

[Remco B. Brink]

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> > 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.
> 
> Its certainly worth building with kgcc as well to make sure, and in this case
> it looks like the problem is really in the kernel proper

Actually the mount process behaves in exactly the same way as my emacs process
as mentioned in an earlier post (topic: "process with connection in CLOSE_WAIT won't 
die in 2.4.2").

It'll stay in the proceslist regardless of what kill signal is sent to it
and appears to be (and very much _stay_) in un-interuptable sleep.

The same can be said for the various mount processes, both when mounting
loopback and scsi devices.

Another thing that struck me as weird was that after all the problems
with the mount and emacs process, trying to unmount a NFS share was not
possible even though the NFS server had no problems whatsoever mounting
new shares.

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

In most countries selling harmful things like drugs is punishable.
Then howcome people can sell Microsoft software and go unpunished?
(By hasku@rost.abo.fi, Hasse Skrifvars)