[ltp] ibmtr_cs 2.2.18 and DHCP
Friedemann Baitinger
linux-thinkpad@www.bm-soft.com
Mon, 18 Dec 2000 23:42:08 +0100 (CET)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have some updates with respect to this topic. Not only do I have
problems with the Token Ring driver on my TP770X but also on an IBM
Netfinity dual SMP server. With both, standard linux-2.2.17 and
linux-2.2.18 the driver is a veg. I keep getting "Transmitter
Busy" loops where the only cure is to reboot the machine. Plus I am
getting errors like:
Dec 18 16:38:17 tonto kernel: [read_mem+61/100] [sys_read+194/232]
[system_call+52/64]
Dec 18 16:38:17 tonto kernel: Code: f3 a5 89 c1 f3 a4 89 f6 89 c8 5b 5e
5f c3 89 f6 57 56 b8 00
Dec 18 16:38:17 tonto kernel: tr0: adapter error: ISRP_EVEN : 04
Dec 18 16:38:17 tonto kernel: NMI: IOCK error (debug interrupt?)
Dec 18 16:38:17 tonto kernel: CPU: 1
Dec 18 16:38:17 tonto
kernel: EIP: 0010:[__generic_copy_to_user+48/64]
Dec 18 16:38:17 tonto kernel: EFLAGS: 00010206
Dec 18 16:38:17 tonto kernel: eax: 00000000 ebx: 00000000
ecx: 00000055 edx: bffff7f4
Dec 18 16:38:17 tonto kernel: esi: c00dbeac edi: bffff6a0
ebp: f18a6000 esp: f18a7f7c
Dec 18 16:38:17 tonto kernel: ds: 0018 es: 0018 ss: 0018
Dec 18 16:38:17 tonto kernel: Process kdm (pid: 222, process nr: 15,
stackpage=f18a7000)
Dec 18 16:38:17 tonto kernel: Stack: 00002000 c01990d1 bfffd7f4 c00da000
00002000 f880e740 ffffffea 00000000
Dec 18 16:38:17 tonto kernel: c012967e f880e740 bfffd7f4 00002000
f880e754 f18a6000 6182870f bffff9a4
Dec 18 16:38:17 tonto kernel: bffff7f4 c01093d4 00000007 bfffd7f4
00002000 6182870f bffff9a4 bffff7f4
Dec 18 16:38:17 tonto kernel: Call Trace: [read_mem+61/100]
[sys_read+194/232] [system_call+52/64]
Dec 18 16:38:17 tonto kernel: Code: f3 a5 89 c1 f3 a4 89 f6 89 c8 5b 5e
5f c3 89 f6 57 56 b8 00
The error causes 10 to 20 of the above syslog sequences in a row and
makes the system completely unresponsive even at the console for about
1min.
I was using linux-2.2.12 since December 1999 on that machine and never
experienced any problem. Only since I changed to 2.2.17 about 2 weeks
ago I ran into this problem. So what now? Do I have bad hardware?
I doubt it. With all the problems I had with the TP770X I
figured it was worth a try to take the "ibmtr.[ch]" from linux-2.2.12
and put that into linux-2.2.18. The kernel compiled cleanly and the
machine runs like a champ since. I am currently on the ThinkPad also
running linux-2.2.18 and pcmcia-3.1.22, both unpatched. If I continue to
experience the transmitter busy with this code, I plan to also fall back
to the token ring driver from linux-2.2.12. Don't know yet what version
of the ibmtr_cs.c (from what pcmcia-3.2.xx package) I will use with it.
I will keep the list posted.
The _old_, good code from linux-2.2.12 reads:
Dec 18 17:48:22 tonto kernel: ibmtr.c: v1.3.57 8/ 7/94 Peter De
Schrijver and Mark Swanson
Dec 18 17:48:22 tonto kernel: v2.1.125 10/20/98 Paul Norton
<pnorton@ieee.org>
Dec 18 17:48:22 tonto kernel: v2.2.0 12/30/98 Joel Sloan
<jjs@c-me.com>
The _new_, bad (on my machine at least) code from linux-2.2.18 reads:
Dec 18 13:38:53 tonto kernel: ibmtr.c: v1.3.57 8/ 7/94 Peter De
Schrijver and Mark Swanson
Dec 18 13:38:53 tonto kernel: v2.1.125 10/20/98 Paul Norton
<pnorton@ieee.org>
Dec 18 13:38:53 tonto kernel: v2.2.0 12/30/98 Joel Sloan
<jjs@c-me.com>
Dec 18 13:38:53 tonto kernel: v2.2.1 02/08/00 Mike Sullivan
<sullivam@us.ibm.com>
Dec 18 13:38:53 tonto kernel: v2.2.2 07/27/00 Burt Silverman
<burts@us.ibm.com>
I'm sorry but I have to state that the changes, either v2.2.1 or v2.2.2
or both may not work so well.
On Mon, 18 Dec 2000, Markus Alt wrote:
> Hi all,
>
> lately I upgraded to ibmtr_cs-2.2.18 and pcmcia-cs-3.1.21 in order to
> get VMware to run again (base system config is SuSE 7.0 with 2.2.16).
> There should be quite a few messages in the archives with regard to that
> topic.
>
> This has worked fine so far. Even more, the Token Ring driver looks more
> stable to me now, although others have reported problems. Unfortunately,
> I can join them now ...
>
> Usually, I use a fixed IP address for my machine. Last week I had to
> connect my TP to another location's LAN and therefore use DHCP for the
> IP configuration. To my surprise, this wasn't working, although I had
> used DHCP without problems before. Today, I double-checked it in our LAN
> with the same unsatisfying result.
>
> It looks like the adapter isn't opened correctly and the tr0 interface
> receives a lot of packages, but is not able to send some. Here are the
> lines from /var/log/messages:
>
>
> Dec 18 10:46:00 altmark cardmgr[4082]: initializing socket 0
> Dec 18 10:46:00 altmark cardmgr[4082]: socket 0: IBM Token Ring Adapter
> Dec 18 10:46:00 altmark cardmgr[4082]: executing: 'modprobe ibmtr_cs
> mmiobase=0xd6000 srambase=0xd8000 ringspeed=16 sramsize=16 irq_list=9'
> Dec 18 10:46:00 altmark kernel:
> Dec 18 10:46:00 altmark kernel: ibmtr_cs.c 1.10 1996/01/06 05:19:00
> (Steve Kipisz)
> Dec 18 10:46:00 altmark kernel: 2.2.7 1999/05/03 12:00:00
> (Mike Phillips)
> Dec 18 10:46:00 altmark kernel: 2.2.18 2000/10/15 Midnight
> (Burt Silverman)
> Dec 18 10:46:00 altmark kernel: tr0: ISA P&P 16/4 Adapter/A (short) |
> 16/4 ISA-16 Adapter found
> Dec 18 10:46:00 altmark kernel: tr0: using irq 9, PIOaddr a20, 16K
> shared RAM.
> Dec 18 10:46:00 altmark kernel: tr0: Hardware address :
> 00:20:35:55:11:01
> Dec 18 10:46:00 altmark kernel: tr0: Shared RAM paging enabled. Page
> size: 16K Shared Ram size 63K
> Dec 18 10:46:00 altmark kernel: tr0: Maximum Receive Internet Protocol
> MTU 16Mbps: 16344, 4Mbps: 6104
> Dec 18 10:46:03 altmark kernel: tr0: Initial interrupt : 16 Mbps, shared
> RAM base 000d8000.
> Dec 18 10:46:03 altmark kernel: tr0: port 0xa20, irq 9, mmio 0xd4d1c000,
> sram 0xd8000,
> Dec 18 10:46:03 altmark kernel: hwaddr=002035551101
> Dec 18 10:46:03 altmark cardmgr[4082]: executing: './network start tr0'
> Dec 18 10:46:03 altmark kernel: tr0: Opening adapter: Xmit bfrs: 2 X
> 16384, Rcv bfrs: 16 X 1032
> Dec 18 10:46:04 altmark dhclient: Internet Software Consortium DHCP
> Client 2.0pl3
> Dec 18 10:46:04 altmark dhclient: Copyright 1995, 1996, 1997, 1998, 1999
> The Internet Software Consortium.
> Dec 18 10:46:04 altmark dhclient: All rights reserved.
> Dec 18 10:46:04 altmark dhclient:
> Dec 18 10:46:04 altmark dhclient: Please contribute if you find this
> software useful.
> Dec 18 10:46:04 altmark dhclient: For info, please visit
> http://www.isc.org/dhcp-contrib.html
> Dec 18 10:46:04 altmark dhclient:
> Dec 18 10:46:05 altmark dhclient: Listening on Socket/tr0
> Dec 18 10:46:05 altmark dhclient: Sending on Socket/tr0
> Dec 18 10:46:06 altmark kernel: tr0: Adapter is closed.
> Dec 18 10:46:06 altmark kernel: tr0: Opening adapter: Xmit bfrs: 2 X
> 16384, Rcv bfrs: 16 X 1032
> Dec 18 10:46:09 altmark dhclient: DHCPDISCOVER on tr0 to 255.255.255.255
> port 67 interval 5
> Dec 18 10:46:09 altmark dhclient: send_packet: No such device
> Dec 18 10:46:14 altmark dhclient: DHCPDISCOVER on tr0 to 255.255.255.255
> port 67 interval 7
> Dec 18 10:46:14 altmark dhclient: send_packet: No such device
> Dec 18 10:46:21 altmark dhclient: DHCPDISCOVER on tr0 to 255.255.255.255
> port 67 interval 8
> Dec 18 10:46:21 altmark dhclient: send_packet: No such device
> Dec 18 10:46:29 altmark dhclient: DHCPDISCOVER on tr0 to 255.255.255.255
> port 67 interval 10
> Dec 18 10:46:29 altmark dhclient: send_packet: No such device
> Dec 18 10:46:39 altmark dhclient: DHCPDISCOVER on tr0 to 255.255.255.255
> port 67 interval 18
> Dec 18 10:46:39 altmark dhclient: send_packet: No such device
> Dec 18 10:46:57 altmark dhclient: DHCPDISCOVER on tr0 to 255.255.255.255
> port 67 interval 7
> Dec 18 10:46:57 altmark dhclient: send_packet: No such device
> Dec 18 10:47:04 altmark dhclient: DHCPDISCOVER on tr0 to 255.255.255.255
> port 67 interval 1
> Dec 18 10:47:04 altmark dhclient: send_packet: No such device
> Dec 18 10:47:05 altmark dhclient: No DHCPOFFERS received.
> Dec 18 10:47:05 altmark dhclient: No working leases in persistent
> database - sleeping.
>
>
> Another item: As you may have seen above, I have *not* disabled (i.e.
> commented out) the options for the ibmtr_cs module within
> /etc/pcmcia/config.opts, although some time ago Burt told us to do so
> and let the driver pick the values. The reason is that my machine hung
> from time to time when not specifying these options for ibmtr_cs.
> Regardless whether I tried DHCP or was using a fixed IP address.
>
> Burt, could you shed some light on any (preferably both ;-) ) of these
> items? TIA.
>
> Regards,
> Markus
> ----- The Linux ThinkPad mailing list -----
> The linux-thinkpad mailing list home page is at:
> http://www.bm-soft.com/~bm/tp_mailing.html
>
- --
Friedemann Baitinger fb@baiti.net http://baiti.net/fb/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6PpLD8ZparKdkcvIRAuoUAJ4pmD0uRCKzeP4EM8XWseKtZ7oXRACfUPwu
acsg2ym3krwX+ARIwjdF37U=
=SNpo
-----END PGP SIGNATURE-----
----- The Linux ThinkPad mailing list -----
The linux-thinkpad mailing list home page is at:
http://www.bm-soft.com/~bm/tp_mailing.html