2002-09-12 16:27:12

by Joel Votaw

[permalink] [raw]
Subject: Oops, maybe smbfs on SMP system? Kernel is RedHat's 2.4.18-10smp


[ ksymoops output at the bottom. ]


Hello Urban and other kernel developers,


I'm having a semi-reproducible Oops which seems to be related to smbfs on
an SMP system. I'm using smbfs and rsync to back up data from about 60
Windows machines to our Linux file server. These oopses are fairly
reproducible: I've been using smbfs on this system for about two weeks and
have seen the oops twice (had to power cycle the machine both times).

When I first encountered the bug, my scripts were written to back up as
many machines as possible in parallel, so I thought the problem might be
aggravated by multiple smbfs filesystems running in parallel, or possibly
two such filesystems being unmounted at the same time. Just before the
Oops, I saw this in syslog:

--

smb_retry: no connection process
last message repeated 2 times
smb_delete_inode: could not close inode 2
VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice
day...
Unable to handle kernel paging request at virtual address 740a6279
printing eip:
c01588d3
*pde = 00000000

--

The second time I saw the Oops I had rewritten my scripts to only backup
one Windows machine at a time; there should only be one smbfs filesystem
mounted at a time. This time I did not see the VFS-related entries in
syslog, but there was a reference to BUG which I did not see the first
time. However the rest of the Oops looks more or less the same.

I've run scripts which are almost identical to these on another system
and haven't had these problems -- but that system only has one CPU.


The hardware:

Intel server board using Serverworks III low-end chipset, dual Pentium
III/1.26GHz, 1GB RAM, 3com 3C996B-T (tigon3-based) gigabit Ethernet,
hardware RAID 5 on four Maxtor 160GB drives. (I can forward the output
from dmesg if you need it.)


The software:

RedHat 7.3, fairly minimal install, latest patches, and their
2.4.18-10smp kernel.


At home I like to replace the kernel with one custom compiled from the
mainstream source code. However at work I'm using the stock RedHat kernel
so that the system will be (hopefully) more maintainable by other admins.
Nonetheless I'm going to give a generic 2.4.19 kernel a try and see if
that clears up the problem.

I've filed a bug report with RedHat on this (tracking #73526).

Has anyone seen this crash before? Is it specific to the RedHat kernel,
or is it possibly in the mainstream kernels as well?

Let me know what I can do on my end to track this down and I'll gladly do
it. Is there any additional information you need?


Thanks for your help,

-Joel


-------------------- ksymoops of first crash --------------------------

[[email protected] root]# ksymoops -V -k /proc/ksyms -l /proc/modules -o
/lib/modules/2.4.18-10smp/ -m /boot/System.map-2.4.18-10smp oops.log
ksymoops 2.4.4 on i686 2.4.18-10smp. Options used
-V (specified)
-k /proc/ksyms (specified)
-l /proc/modules (specified)
-o /lib/modules/2.4.18-10smp/ (specified)
-m /boot/System.map-2.4.18-10smp (specified)

Error (expand_objects): cannot stat(/lib/ext3.o) for ext3
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/jbd.o) for jbd
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/raid5.o) for raid5
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/xor.o) for xor
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/aic7xxx.o) for aic7xxx
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod
ksymoops: No such file or directory
/usr/bin/find: /lib/modules/2.4.18-10smp/build: No such file or directory
Error (pclose_local): find_objects pclose failed 0x100
Warning (map_ksym_to_module): cannot match loaded module ext3 to a unique
module object. Trace may not be reliable.
Oops: 0000
CPU: 0
EIP: 0010:[<c01588d3>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 740a6269 ebx: c9111da0 ecx: f4bfcbd0 edx: c9111db0
esi: c26cc400 edi: 740a6269 ebp: 00000041 esp: f7ed3f5c
ds: 0018 es: 0018 ss: 0018
Process kswapd (pid: 7, stackpage=f7ed3000)
Stack: f4bfcbb8 f4bfcba0 c9111da0 c0155fa6 c9111da0 00000375 000000c3 ffffffff
c02f3c28 00000375 00000185 00000493 c01381e8 000001d0 00000556 00000000
00000185 c01563d0 0000230c c0138b3c 00000006 000001d0 000001d0 f7ed2000
Call Trace: [<c0155fa6>] prune_dcache [kernel] 0xe6
[<c01381e8>] page_launder [kernel] 0x168
[<c01563d0>] shrink_dcache_memory [kernel] 0x20
[<c0138b3c>] do_try_to_free_pages [kernel] 0x1c
[<c0138e31>] kswapd [kernel] 0x101
[<c0105000>] stext [kernel] 0x0
[<c0107286>] kernel_thread [kernel] 0x26
[<c0138d30>] kswapd [kernel] 0x0
Code: 8b 47 10 85 c0 74 04 53 ff d0 58 68 bc 49 2f c0 8d 43 2c 50

>>EIP; c01588d3 <iput+43/290> <=====
Trace; c0155fa6 <prune_dcache+e6/1c0>
Trace; c01381e8 <page_launder+168/300>
Trace; c01563d0 <shrink_dcache_memory+20/30>
Trace; c0138b3c <do_try_to_free_pages+1c/180>
Trace; c0138e31 <kswapd+101/2d0>
Trace; c0105000 <_stext+0/0>
Trace; c0107286 <kernel_thread+26/30>
Trace; c0138d30 <kswapd+0/2d0>
Code; c01588d3 <iput+43/290>
00000000 <_EIP>:
Code; c01588d3 <iput+43/290> <=====
0: 8b 47 10 mov 0x10(%edi),%eax <=====
Code; c01588d6 <iput+46/290>
3: 85 c0 test %eax,%eax
Code; c01588d8 <iput+48/290>
5: 74 04 je b <_EIP+0xb> c01588de
<iput+4e/290>
Code; c01588da <iput+4a/290>
7: 53 push %ebx
Code; c01588db <iput+4b/290>
8: ff d0 call *%eax
Code; c01588dd <iput+4d/290>
a: 58 pop %eax
Code; c01588de <iput+4e/290>
b: 68 bc 49 2f c0 push $0xc02f49bc
Code; c01588e3 <iput+53/290>
10: 8d 43 2c lea 0x2c(%ebx),%eax
Code; c01588e6 <iput+56/290>
13: 50 push %eax


1 warning and 8 errors issued. Results may not be reliable.





-------------------- ksymoops of second crash --------------------------

[[email protected] root]# ksymoops -V -k /proc/ksyms -l /proc/modules -o
/lib/modules/2.4.18-10smp/ -m /boot/System.map-2.4.18-10smp oops2.log

ksymoops 2.4.4 on i686 2.4.18-10smp. Options used
-V (specified)
-k /proc/ksyms (specified)
-l /proc/modules (specified)
-o /lib/modules/2.4.18-10smp/ (specified)
-m /boot/System.map-2.4.18-10smp (specified)

Error (expand_objects): cannot stat(/lib/ext3.o) for ext3
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/jbd.o) for jbd
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/raid5.o) for raid5
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/xor.o) for xor
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/aic7xxx.o) for aic7xxx
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod
ksymoops: No such file or directory
/usr/bin/find: /lib/modules/2.4.18-10smp/build: No such file or directory
Error (pclose_local): find_objects pclose failed 0x100
Warning (map_ksym_to_module): cannot match loaded module ext3 to a unique
module object. Trace may not be reliable.
kernel BUG at inode.c:1066!
invalid operand: 0000
CPU: 1
EIP: 0010:[<c01588bf>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 0000001c ebx: d94fe420 ecx: c02f25e0 edx: 00008f60
esi: f7d1c000 edi: 00000000 ebp: 00000051 esp: f7ed3f54
ds: 0018 es: 0018 ss: 0018
Process kswapd (pid: 7, stackpage=f7ed3000)
Stack: c024a65f 0000042a ddd49e58 ddd49e40 d94fe420 c0155fa6 d94fe420 0000038e
00000098 ffffffff c02f3c28 0000038e 0000016c 000003cd c01381e8 000001d0
00000465 00000000 0000016c c01563d0 000020a0 c0138b3c 00000006 000001d0
Call Trace: [<c0155fa6>] prune_dcache [kernel] 0xe6
[<c01381e8>] page_launder [kernel] 0x168
[<c01563d0>] shrink_dcache_memory [kernel] 0x20
[<c0138b3c>] do_try_to_free_pages [kernel] 0x1c
[<c0138e31>] kswapd [kernel] 0x101
[<c0105000>] stext [kernel] 0x0
[<c0107286>] kernel_thread [kernel] 0x26
[<c0138d30>] kswapd [kernel] 0x0
Code: 0f 0b 5a 59 85 f6 74 08 8b 46 20 85 c0 0f 45 f8 85 ff 74 0b

>>EIP; c01588bf <iput+2f/290> <=====
Trace; c0155fa6 <prune_dcache+e6/1c0>
Trace; c01381e8 <page_launder+168/300>
Trace; c01563d0 <shrink_dcache_memory+20/30>
Trace; c0138b3c <do_try_to_free_pages+1c/180>
Trace; c0138e31 <kswapd+101/2d0>
Trace; c0105000 <_stext+0/0>
Trace; c0107286 <kernel_thread+26/30>
Trace; c0138d30 <kswapd+0/2d0>
Code; c01588bf <iput+2f/290>
00000000 <_EIP>:
Code; c01588bf <iput+2f/290> <=====
0: 0f 0b ud2a <=====
Code; c01588c1 <iput+31/290>
2: 5a pop %edx
Code; c01588c2 <iput+32/290>
3: 59 pop %ecx
Code; c01588c3 <iput+33/290>
4: 85 f6 test %esi,%esi
Code; c01588c5 <iput+35/290>
6: 74 08 je 10 <_EIP+0x10> c01588cf
<iput+3f/290>
Code; c01588c7 <iput+37/290>
8: 8b 46 20 mov 0x20(%esi),%eax
Code; c01588ca <iput+3a/290>
b: 85 c0 test %eax,%eax
Code; c01588cc <iput+3c/290>
d: 0f 45 f8 cmovne %eax,%edi
Code; c01588cf <iput+3f/290>
10: 85 ff test %edi,%edi
Code; c01588d1 <iput+41/290>
12: 74 0b je 1f <_EIP+0x1f> c01588de
<iput+4e/290>


1 warning and 8 errors issued. Results may not be reliable.


---------------------------------------------



2002-09-12 22:23:45

by Urban Widmark

[permalink] [raw]
Subject: Re: Oops, maybe smbfs on SMP system? Kernel is RedHat's 2.4.18-10smp

On Thu, 12 Sep 2002, Joel Votaw wrote:

> smb_retry: no connection process

This means that your smbmount process has terminated (crashed?). You could
try some things with that, eg upgrading samba to the latest 2.2.x, running
it with a higher debug level (4, check your smbmount.log), add more debug
printouts to the smbmount main loop, getting a core dump from it.

The mount should become unusble at this point because smbfs no longer has
a connection and it can't contact it's smbmount daemon to get a new one.

> last message repeated 2 times
> smb_delete_inode: could not close inode 2

I believe this is at umount time. And if smb_delete_inode wants to
actually close something and smb_retry is failing it won't be able to.

I need to find out if/why that would cause the busy message. When the
connection closes any open files are closed, so closing shouldn't be a
problem.

Did you get either of these the second time?

> VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice
> day...

Kabooom!

/Urban

2002-09-13 20:14:43

by Joel Votaw

[permalink] [raw]
Subject: Re: Oops, maybe smbfs on SMP system? Kernel is RedHat's 2.4.18-10smp

On Fri, 13 Sep 2002, Urban Widmark wrote:

> On Thu, 12 Sep 2002, Joel Votaw wrote:
>
> > smb_retry: no connection process
>
> This means that your smbmount process has terminated (crashed?). You could
> try some things with that, eg upgrading samba to the latest 2.2.x, running
> it with a higher debug level (4, check your smbmount.log), add more debug
> printouts to the smbmount main loop, getting a core dump from it.

I upped the debug level from 1 to 5, which appears to give a ton of
information. I didn't see any interesting messages from debug=1; the
relevant areas from smbmount.log are below. I enabled core dumps just
now -- RedHat 7.3 has them disabled for bash by default. So with luck
I should have more information if this happens again.

I upgraded to kernel 2.4.19 just in case that was the problem, and I'll
upgrade Samba in the next few days.


> I believe this is at umount time.

That's what I thought too. Interestingly, however, I think the log file
of my backup script from the second crash indicated that that crash
happened when the filesystem was first mounted. I accidently deleted
that log though so I can't check it.... :-(


> And if smb_delete_inode wants to
> actually close something and smb_retry is failing it won't be able to.
>
> I need to find out if/why that would cause the busy message. When the
> connection closes any open files are closed, so closing shouldn't be a
> problem.
>
> Did you get either of these the second time?

No. I've included more of /var/log/messages (and also
/var/log/samba/smbmount.log) below, in case there's something useful
in them that I overlooked.


> > VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice
> > day...
>
> Kabooom!

Yup! It's actually nice to have a bit of humor in the middle of one's
server crashing.

-Joel




======================= Crash #1 ===================================

----------------------- /var/log/samba/smbmount.log #1 -------------

[2002/09/05 11:58:47, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc22\usr, pid=17752
[2002/09/05 11:58:47, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc15\c$, pid=17762
[2002/09/05 11:58:47, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc52\c$, pid=17770
[2002/09/05 11:58:48, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc96\c$, pid=17787
[2002/09/05 11:58:48, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc34\c$, pid=17796
[2002/09/05 11:58:48, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc23\user, pid=17804


----------------------- /var/log/messages #1 -----------------------

Sep 4 20:46:13 files2 kernel: smb_proc_readdir_long: name=\usr\usr\???????\*, result=-2, rcls=1, err=123
Sep 4 20:46:13 files2 kernel: smb_proc_readdir_long: name=\usr\usr\sch\*, result=-13, rcls=1, err=5
Sep 4 20:46:13 files2 kernel: smb_proc_readdir_long: name=\usr\mentor_guide\*, result=-13, rcls=1, err=5
Sep 5 06:59:05 files2 kernel: raid5: multiple 0 requests for sector 196608024
Sep 5 06:59:25 files2 kernel: raid5: multiple 0 requests for sector 256464264
Sep 5 11:56:35 files2 kernel: smb_retry: no connection process
Sep 5 11:56:37 files2 last message repeated 2 times
Sep 5 11:56:37 files2 kernel: smb_delete_inode: could not close inode 2
Sep 5 11:56:37 files2 kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
Sep 5 11:58:50 files2 kernel: Unable to handle kernel paging request at virtual address 740a6279
Sep 5 11:58:50 files2 kernel: printing eip:
Sep 5 11:58:50 files2 kernel: c01588d3
Sep 5 11:58:50 files2 kernel: *pde = 00000000
Sep 5 11:58:50 files2 kernel: Oops: 0000
Sep 5 11:58:50 files2 kernel: smbfs nfs lockd sunrpc tg3 eepro100 ide-cd cdrom st usb-ohci usbcore ext3 jbd
Sep 5 11:58:50 files2 kernel: CPU: 0
Sep 5 11:58:50 files2 kernel: EIP: 0010:[<c01588d3>] Not tainted
Sep 5 11:58:50 files2 kernel: EFLAGS: 00010206
Sep 5 11:58:50 files2 kernel:
Sep 5 11:58:50 files2 kernel: EIP is at iput [kernel] 0x43 (2.4.18-10smp)
Sep 5 11:58:50 files2 kernel: eax: 740a6269 ebx: c9111da0 ecx: f4bfcbd0 edx: c9111db0
Sep 5 11:58:50 files2 kernel: esi: c26cc400 edi: 740a6269 ebp: 00000041 esp: f7ed3f5c
Sep 5 11:58:51 files2 kernel: ds: 0018 es: 0018 ss: 0018
Sep 5 11:58:51 files2 kernel: Process kswapd (pid: 7, stackpage=f7ed3000)
Sep 5 11:58:51 files2 kernel: Stack: f4bfcbb8 f4bfcba0 c9111da0 c0155fa6 c9111da0 00000375 000000c3 ffffffff
Sep 5 11:58:51 files2 kernel: c02f3c28 00000375 00000185 00000493 c01381e8 000001d0 00000556 00000000
Sep 5 11:58:51 files2 kernel: 00000185 c01563d0 0000230c c0138b3c 00000006 000001d0 000001d0 f7ed2000
Sep 5 11:58:51 files2 kernel: Call Trace: [<c0155fa6>] prune_dcache [kernel] 0xe6
Sep 5 11:58:51 files2 kernel: [<c01381e8>] page_launder [kernel] 0x168
Sep 5 11:58:51 files2 kernel: [<c01563d0>] shrink_dcache_memory [kernel] 0x20
Sep 5 11:58:51 files2 kernel: [<c0138b3c>] do_try_to_free_pages [kernel] 0x1c
Sep 5 11:58:51 files2 kernel: [<c0138e31>] kswapd [kernel] 0x101
Sep 5 11:58:52 files2 kernel: [<c0105000>] stext [kernel] 0x0
Sep 5 11:58:52 files2 kernel: [<c0107286>] kernel_thread [kernel] 0x26
Sep 5 11:58:52 files2 kernel: [<c0138d30>] kswapd [kernel] 0x0
Sep 5 11:58:52 files2 kernel:
Sep 5 11:58:58 files2 kernel:
Sep 5 11:58:59 files2 kernel: Code: 8b 47 10 85 c0 74 04 53 ff d0 58 68 bc 49 2f c0 8d 43 2c 50
Sep 5 12:40:28 files2 syslogd 1.4.1: restart.
Sep 5 12:40:28 files2 syslog: syslogd startup succeeded
Sep 5 12:40:28 files2 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Sep 5 12:40:28 files2 kernel: Linux version 2.4.18-10smp ([email protected]) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 SMP Wed Aug 7 11:17:48 EDT 2002



======================= Crash #2 ===================================

----------------------- /var/log/samba/smbmount.log #2 -------------

[2002/09/12 04:58:19, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc43\c$, pid=3230
[2002/09/12 04:59:07, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc74\c$, pid=3274
[2002/09/12 04:59:43, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc74\c$, pid=3311
[2002/09/12 05:03:23, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc67\c$, pid=3361
[2002/09/12 05:04:07, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc67\c$, pid=3398
[2002/09/12 05:07:14, 0] client/smbmount.c:send_fs_socket(386)
mount.smbfs: entering daemon mode for service \\pc3\c$, pid=3442


----------------------- /var/log/messages #2 -----------------------

Sep 12 03:47:23 files2 kernel: smb_proc_readdir_long: name=\usr\usr\???????\*, result=-2, rcls=1, err=123
Sep 12 03:47:23 files2 kernel: smb_proc_readdir_long: name=\usr\usr\sch\*, result=-13, rcls=1, err=5
Sep 12 03:47:23 files2 kernel: smb_proc_readdir_long: name=\usr\mentor_guide\*, result=-13, rcls=1, err=5
Sep 12 03:55:52 files2 kernel: smb_proc_readdir_long: name=\Cygwin\home\tim\Mail\*, result=-13, rcls=1, err=5
Sep 12 04:01:22 files2 kernel: smb_proc_readdir_long: name=\Projects\sahara30\production\production\production\*, result=-13, rcls=1, err=5
Sep 12 05:00:35 files2 kernel: smb_open: Mail/Inbox.snm open failed, result=-26
Sep 12 05:00:37 files2 kernel: smb_open: Mail/Inbox.snm open failed, result=-26
Sep 12 05:00:37 files2 kernel: smb_readpage_sync: Mail/Inbox.snm open failed, error=-26
Sep 12 05:37:05 files2 kernel: ------------[ cut here ]------------
Sep 12 05:37:05 files2 kernel: kernel BUG at inode.c:1066!
Sep 12 05:37:05 files2 kernel: invalid operand: 0000
Sep 12 05:37:05 files2 kernel: smbfs nfs lockd sunrpc tg3 eepro100 ide-cd cdrom st usb-ohci usbcore ext3 jbd
Sep 12 05:37:05 files2 kernel: CPU: 1
Sep 12 05:37:05 files2 kernel: EIP: 0010:[<c01588bf>] Not tainted
Sep 12 05:37:05 files2 kernel: EFLAGS: 00010286
Sep 12 05:37:05 files2 kernel:
Sep 12 05:37:05 files2 kernel: EIP is at iput [kernel] 0x2f (2.4.18-10smp)
Sep 12 05:37:05 files2 kernel: eax: 0000001c ebx: d94fe420 ecx: c02f25e0 edx: 00008f60
Sep 12 05:37:05 files2 kernel: esi: f7d1c000 edi: 00000000 ebp: 00000051 esp: f7ed3f54
Sep 12 05:37:05 files2 kernel: ds: 0018 es: 0018 ss: 0018
Sep 12 05:37:05 files2 kernel: Process kswapd (pid: 7, stackpage=f7ed3000)
Sep 12 05:37:13 files2 kernel: Stack: c024a65f 0000042a ddd49e58 ddd49e40 d94fe420 c0155fa6 d94fe420 0000038e
Sep 12 05:37:13 files2 kernel: 00000098 ffffffff c02f3c28 0000038e 0000016c 000003cd c01381e8 000001d0
Sep 12 05:37:13 files2 kernel: 00000465 00000000 0000016c c01563d0 000020a0 c0138b3c 00000006 000001d0
Sep 12 05:37:13 files2 kernel: Call Trace: [<c0155fa6>] prune_dcache [kernel] 0xe6
Sep 12 05:37:13 files2 kernel: [<c01381e8>] page_launder [kernel] 0x168
Sep 12 05:37:13 files2 kernel: [<c01563d0>] shrink_dcache_memory [kernel] 0x20
Sep 12 05:37:14 files2 kernel: [<c0138b3c>] do_try_to_free_pages [kernel] 0x1c
Sep 12 05:37:14 files2 kernel: [<c0138e31>] kswapd [kernel] 0x101
Sep 12 05:37:14 files2 kernel: [<c0105000>] stext [kernel] 0x0
Sep 12 05:37:14 files2 kernel: [<c0107286>] kernel_thread [kernel] 0x26
Sep 12 05:37:14 files2 kernel: [<c0138d30>] kswapd [kernel] 0x0
Sep 12 05:37:14 files2 kernel:
Sep 12 05:37:14 files2 kernel:
Sep 12 05:37:14 files2 kernel: Code: 0f 0b 5a 59 85 f6 74 08 8b 46 20 85 c0 0f 45 f8 85 ff 74 0b
Sep 12 10:21:30 files2 syslogd 1.4.1: restart.
Sep 12 10:21:30 files2 syslog: syslogd startup succeeded
Sep 12 10:21:30 files2 syslog: klogd startup succeeded
Sep 12 10:21:30 files2 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Sep 12 10:21:30 files2 kernel: Linux version 2.4.18-10smp ([email protected]) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 SMP Wed Aug 7 11:17:48 EDT 2002



2002-09-24 21:15:49

by Joel Votaw

[permalink] [raw]
Subject: Re: Oops, maybe smbfs on SMP system? Kernel is RedHat's 2.4.18-10smp


Just wanted to let people know, in case they ran into this same bug -- I
haven't had any more crashes since upgrading to a standard 2.4.19 kernel.

-Joel