The Linux system is a Pentium machine with an Intel EtherExpress Pro network
card running RedHat 5.0, 2.0.32 kernel.
I have 3 smbmount on the same Win95 machine that hang at random times.
When I do a df -k or a ls of the mounted directory, it block. The
process is in the D state and is not killable. I reboot the machine
and all go fine... to the next time (maybe 15 days after or less).
Here is some of the /var/log/messages errors:
First, the kernel errors:
Boot - dmesg
------------
eepro100.c:v0.36 10/20/97 Donald Becker linux-eepro100@cesdis.gsfc.nasa.gov
eth0: Intel EtherExpress Pro 10/100 at 0xd000, 00:A0:C9:23:45:C1, IRQ 11.
Board assembly 352509-003, Physical connectors present: RJ45
Primary interface chip DP83840 PHY #1.
DP83840 specific setup, setting register 23 to 8462.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x49caa8d6).
Receiver lock-up workaround activated.
Problem, first time
-------------------
May 27 07:31:38 wserver kernel: smb_put_inode: could not close
May 27 07:31:38 wserver kernel: general protection: 0000
May 27 07:31:38 wserver kernel: CPU: 0
May 27 07:31:38 wserver kernel: EIP: 0010:[eepro100:eepro100_init+-18765/8070]
May 27 07:31:38 wserver kernel: EFLAGS: 00010246
May 27 07:31:38 wserver kernel: eax: 002f2adc ebx: 002f2adc ecx: 0139060c edx: a0002adc
May 27 07:31:38 wserver kernel: esi: 0139060c edi: 356aadb2 ebp: 002f2810 esp: 00722f5c
May 27 07:31:38 wserver kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
May 27 07:31:38 wserver kernel: Process view-order.pl (pid: 3520, process nr: 19, stackpage=00722000)
May 27 07:31:38 wserver kernel: Stack: 0197ed00 02814601 0139060c 0197ed00 0197ed00 0197ed00 bffffa00 00123b65
May 27 07:31:38 wserver kernel: 0197ed00 0136e7b4 001229d2 0197ed00 00000000 0136e7b4 00122a24 0136e7b4
May 27 07:31:38 wserver kernel: 0197ed00 fffffff7 080ef700 08055a1c 00122a78 0136e7b4 018a4810 0010a92d
May 27 07:31:38 wserver kernel: Call Trace: [eepro100:eepro100_init+-23043/8070] [iput+209/408] [__fput+58/64] [close_fp+76/92] [sys_close+68/80] [system_call+85/124]
May 27 07:31:38 wserver kernel: Code: 89 42 0c 51 e8 a8 95 90 fd 83 c4 04 85 db 74 0b 8b 43 04 48
Problem, second time
--------------------
Jun 7 07:49:54 wserver kernel: smb_put_inode: could not close
Jun 7 07:49:54 wserver kernel: general protection: 0000
Jun 7 07:49:54 wserver kernel: CPU: 0
Jun 7 07:49:54 wserver kernel: EIP: 0010:[eepro100:eepro100_init+-18765/8070]
Jun 7 07:49:54 wserver kernel: EFLAGS: 00010246
Jun 7 07:49:54 wserver kernel: eax: 002f2adc ebx: 002f2adc ecx: 01390214 edx: a0000dfc
Jun 7 07:49:54 wserver kernel: esi: 01390214 edi: 35798bce ebp: 002f2810 esp: 019f2f48
Jun 7 07:49:54 wserver kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Jun 7 07:49:54 wserver kernel: Process sort (pid: 7630, process nr: 36, stackpage=019f2000)
Jun 7 07:49:54 wserver kernel: Stack: 005ad600 02814601 01390214 005ad600 005ad600 005ad600 01076018 00123b65
Jun 7 07:49:54 wserver kernel: 005ad600 011c23fc 001229d2 005ad600 00000000 011c23fc 00122a24 011c23fc
Jun 7 07:49:54 wserver kernel: 005ad600 00000001 00000003 00000001 00116df5 011c23fc 01542810 400a4214
Jun 7 07:49:54 wserver kernel: Call Trace: [eepro100:eepro100_init+-23043/8070] [iput+209/408] [__fput+58/64] [close_fp+76/92] [do_exit+273/488] [sys_exit+14/16] [system_call+85/124]
Jun 7 07:49:54 wserver kernel: Code: 89 42 0c 51 e8 a8 95 90 fd 83 c4 04 85 db 74 0b 8b 43 04 48
I encountered this errors two times only. The process being run
(view-order.pl and sort) are called from Apache httpd when a client use the
CGI and access files stored on a Win95 machine via a mounted smb filesystem
(the Win95 is the first released one, no patch applied).
There is other errors, more frequent, but I don't know if it is related to
the previous kernel problems:
Jun 17 16:11:43 wserver kernel: smb_dont_catch_keepalive: server->data_ready == NULL
Jun 17 16:12:54 wserver kernel: smb_dont_catch_keepalive: server->data_ready == NULL
Jun 17 16:13:00 wserver kernel: smb_dont_catch_keepalive: server->data_ready == NULL
Jun 18 12:07:56 wserver kernel: smb_dont_catch_keepalive: server->data_ready == NULL
Jun 19 07:10:52 wserver kernel: smb_dont_catch_keepalive: server->data_ready == NULL
There is anyone that have an idea of the origin of the error?
Thanks for your help. (I hope I post this mail to the right mailing list).
______________________________________
Sylvain Falardeau
sfalardeau@qbc.clic.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu