,0xc374,0x
ctc0,0xc372,0xc373
add_parms,0x10,0xb800,0xb802,portname:OSAFE7A,no_router
qeth0,0xb800,0xb801,0xb802
- Original Message -
From: "Post, Mark K" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 24, 2002 10:32 AM
Subject: Re: QETH Driver failure
On Thursday, 01/24/2002 at 10:32 EST, "Post, Mark K" <[EMAIL PROTECTED]>
wrote:
> Except when dealing with an OCO module, IBM is the only one capable of
> working on the problem, so most of those options aren't applicable.
While that's true, it doesn't mean that you can only get OCO service by
ha
27;ll know
better. :(
Mark Post
-Original Message-
From: Alan Altmark [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 24, 2002 9:55 AM
To: [EMAIL PROTECTED]
Subject: Re: QETH Driver failure
On Wednesday, 01/23/2002 at 10:19 EST, "Post, Mark K" <[EMAIL PROTECTED
On Wednesday, 01/23/2002 at 10:19 EST, "Post, Mark K" <[EMAIL PROTECTED]>
wrote:
> I must have misunderstood something that was being said in the past
about
> IBM support of Linux/390. If someone like Craig is getting segfaults in
the
> QETH OCO driver for Linux/390, I thought he could open up a
, the
raw kernel oops is at the bottom. Craig can run it through ksymoops for you
if you contact him.)
Mark Post
-Original Message-
From: Craig J. Yasuna [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 23, 2002 5:26 PM
To: Post, Mark K
Subject: Re: QETH Driver failure
Mark,
IBM is
