uevent from a mount command

English Network/Internet
#1

The following script to mount a disk on a W98 computer yielded the following message:

hu360:/home/mcair/hbcoc # cat …/bin/hbcoc
#!/bin/bash
clear
echo run as root
mkdir /home/mcair/hbcoc
mount -t cifs -o sec=lanman,servern=HBCO,user=yyyyyy,password=xxxxxxx //192.168.3.5/C /home/mcair/hbcoc
cd /home/mcair/hbcoc
echo HBCO Drive C Mount successful
hu360:/home/mcair/hbcoc # cd …

hu360:/home/mcair/bin # . ./hbcoc

run as root

Message from syslogd@hu360 at Apr 21 21:02:46 …
kernel: 3142.600843] Oops: 0002 #1] SMP

Message from syslogd@hu360 at Apr 21 21:02:46 …
kernel: 3142.600850] last sysfs file: /sys/devices/virtual/bdi/cifs-1/uevent

Message from syslogd@hu360 at Apr 21 21:02:46 …
kernel: 3142.601052] Process mount.cifs (pid: 8382, ti=f4c4c000 task=f7232f30 task.ti=f4c4c000)

Message from syslogd@hu360 at Apr 21 21:02:46 …
kernel: 3142.601058] Stack:

Message from syslogd@hu360 at Apr 21 21:02:46 …
kernel: 3142.601102] Call Trace:

Message from syslogd@hu360 at Apr 21 21:02:46 …
kernel: 3142.601373] Code: d0 00 00 00 f6 82 34 01 00 00 02 89 04 24 89 d8 0f 95 c1 81 c2 5a 01 00 00 e8 2b d2 ff ff 66 83 4e 36 08 8b 44 24 5c 8b 54 24 48 <89> 10 8b 54 24 4c 89 50 04 8b 54 24 50 89 50 08 8b 54 24 54 89

Message from syslogd@hu360 at Apr 21 21:02:46 …
kernel: 3142.601442] EIP: <f90b0452>] CIFS_SessSetup+0x322/0xca0 [cifs] SS:ESP 0068:f4c4dd8c

Message from syslogd@hu360 at Apr 21 21:02:46 …
kernel: 3142.601458] CR2: 00000000024e45dc
HBCO Drive C Mount successful

System: Dell 3000 Computer, 1GB memory, P4 CPU, Intel 845 chipset.
Linux kernel 2.6.37.1-1.2-default

Bill
hbco2@sbcglobal.net

#2

This may be a red herring. An application called JOS was running in another terminal. I am not sure of the affect, but JNOS was terminated, the uevent disappeared. JNOS is an amateur radio bulletin board/subnet application that supports X25 and packet communications over radio.

Bill

#3

Nice you think you have solved it.

But please, next time you want us to read computer in/output, put it between CODE tags to make it as readable as it was on your terminal: Posting in Code Tags - A Guide. Thanks in advance.

#4

On 04/22/2011 04:06 AM, hcvv wrote:
>
> Nice you think you have solved it.
>
> But please, next time you want us to read computer in/output, put it
> between CODE tags to make it as readable as it was on your terminal:
> ‘Posting in Code Tags - A Guide’ (http://tinyurl.com/2wwx7l9). Thanks in
> advance.

In addition, when you get a kernel oops (which is what you saw), do not post the
console output. Use the dmesg command to get the full dump and post it.