System reset message in /var/log/messages

2002-11-25 Thread Sal Torres/SBC Inc.
*** Reply to note of Fri, 22 Nov 2002 02:42:13 -0500 (EST/CDT)
*** by [EMAIL PROTECTED]

You could try to increase the number of server threads for the nfs server
in /etc/rc.config:

   #
   # the kernel nfs-server supports multiple server threads
   #
   USE_KERNEL_NFSD_NUMBER="16"

You can also use the nfsstat command (nfsstat -s for server and
nfsstat -c for the client) to gather more information.

sal

Michael MacIsaac <[EMAIL PROTECTED]> writes:
>Hi list,
>
>We're seeing network problems (especiallly NFS) under heavy loads.  The
>configuration is G6 with OSA Express Gigabit Ethernet.  Linux images are
>SLES-7 with patched (.8) qdio/qeth drivers sharing the OSA. In the NFS
>server's /var/log/messages we see constant:
>
>Nov 20 15:16:30 linuxnfs kernel: ch-0c71: System reset (remote)
>Nov 20 15:16:35 linuxnfs kernel: ch-0c21: System reset (remote)
>Nov 20 15:16:35 linuxnfs kernel: ch-0c41: System reset (remote)
>Nov 20 15:16:35 linuxnfs kernel: ch-0c31: System reset (remote)
>Nov 20 15:16:35 linuxnfs kernel: ch-0c51: System reset (remote)
>Nov 20 15:16:35 linuxnfs kernel: ch-0c61: System reset (remote)
>Nov 20 15:16:35 linuxnfs kernel: ch-0c81: System reset (remote)
>Nov 20 15:16:35 linuxnfs kernel: ch-0c11: System reset (remote)
>Nov 20 15:16:35 linuxnfs kernel: ch-0c71: System reset (remote)
>Nov 20 15:16:40 linuxnfs kernel: ch-0c21: System reset (remote)
>
>Any ideas? TIA
>
>  -Mike MacIsaac,  IBM   [EMAIL PROTECTED]   (845) 433-7061



Re: System reset message in /var/log/messages

2002-11-23 Thread Michael MacIsaac
Adam,

Thanks for the reply.

> do you mean via guest LANs, or do you mean each guest gets its own OSA
port?
own OSA ports.

I was in transit and offline most of yesterday and now I can't get to the
offending system from my dialup.  I'll do some digging Monday and try to
post with more meaningful description.

  -Mike MacIsaac,  IBM   [EMAIL PROTECTED]   (845) 433-7061



Re: System reset message in /var/log/messages

2002-11-22 Thread Adam Thornton
When you say "patched (.8) qdio/qeth drivers sharing the OSA," do you
mean via guest LANs, or do you mean each guest gets its own OSA port?
Or do you mean that one guest owns the OSA and talks to everyone else
with CTCs, which would at least explain why we're seeing a string that
only seems to occur in the CTC driver?

In any event, I don't understand why strings wouldn't make that string
pop out of the qdio/qeth driver if it were in there.

Adam



Re: System reset message in /var/log/messages

2002-11-22 Thread Adam Thornton
On Fri, Nov 22, 2002 at 10:47:56AM -0500, Post, Mark K wrote:
> Mike,
>
> Very few, if any.  I did a Google search on "System reset (remote)" and came
> up with a hit in the CTC driver, of all things:

H.

r2:~ # find /lib/modules/2.4.7-timer-SMP -type f | xargs grep -i "system reset"
Binary file /lib/modules/2.4.7-timer-SMP/kernel/drivers/s390/net/ctc.o matches

I *do* have the QDIO/QETH drivers installed here.  So it ain't in there.

Then:

r2:/usr/src/linux # find . -type f | xargs grep -i "system reset (remote)"
./drivers/s390/net/ctcmain.c:   printk(KERN_DEBUG "ch-%04x: System 
reset (remote)\n",

So it's your CTC driver.  Are you really using CTC to hook all this
together?

Adam



Re: System reset message in /var/log/messages

2002-11-22 Thread Post, Mark K
Mike,

Very few, if any.  I did a Google search on "System reset (remote)" and came
up with a hit in the CTC driver, of all things:
static void inline ccw_unit_check (channel *ch, unsigned char sense) {
   if (sense & SNS0_INTERVENTION_REQ) {
   if (sense & 0x01)  {
   printk(KERN_DEBUG
  "ch-%04x: Interface disc. or Sel. reset "
  "(remote)\n", ch->devno);
   fsm_event(ch->fsm, CH_EVENT_UC_RCRESET, ch);
   } else {
   printk(KERN_DEBUG "ch-%04x: System reset (remote)\n",
  ch->devno);
   fsm_event(ch->fsm, CH_EVENT_UC_RSRESET, ch);
   }

In the CTC driver at least, it looks like the device is returning an
Intervention Required sense code.  Assuming the guys in the lab re-used the
same code for the qdio/qeth stuff

I just got a call from one of our people yesterday where they were seeing a
bunch of network errors, and suspected that the Ethernet card in a
particular Intel Linux box was not set at 100mbs full-duplex as was the rest
of the systems in that network segment.  They were looking for advice on how
to check that.  Perhaps a very lame comparison, but maybe you'd want to
check that as well?

Mark Post

-Original Message-
From: Michael MacIsaac [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 22, 2002 2:42 AM
To: [EMAIL PROTECTED]
Subject: System reset message in /var/log/messages


Hi list,

We're seeing network problems (especiallly NFS) under heavy loads.  The
configuration is G6 with OSA Express Gigabit Ethernet.  Linux images are
SLES-7 with patched (.8) qdio/qeth drivers sharing the OSA. In the NFS
server's /var/log/messages we see constant:

Nov 20 15:16:30 linuxnfs kernel: ch-0c71: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c21: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c41: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c31: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c51: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c61: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c81: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c11: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c71: System reset (remote)
Nov 20 15:16:40 linuxnfs kernel: ch-0c21: System reset (remote)

Any ideas? TIA

  -Mike MacIsaac,  IBM   [EMAIL PROTECTED]   (845) 433-7061



System reset message in /var/log/messages

2002-11-21 Thread Michael MacIsaac
Hi list,

We're seeing network problems (especiallly NFS) under heavy loads.  The
configuration is G6 with OSA Express Gigabit Ethernet.  Linux images are
SLES-7 with patched (.8) qdio/qeth drivers sharing the OSA. In the NFS
server's /var/log/messages we see constant:

Nov 20 15:16:30 linuxnfs kernel: ch-0c71: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c21: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c41: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c31: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c51: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c61: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c81: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c11: System reset (remote)
Nov 20 15:16:35 linuxnfs kernel: ch-0c71: System reset (remote)
Nov 20 15:16:40 linuxnfs kernel: ch-0c21: System reset (remote)

Any ideas? TIA

  -Mike MacIsaac,  IBM   [EMAIL PROTECTED]   (845) 433-7061