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 problem record with the IBM support center to get it looked at. Does he have to buy an IBM maintenance license to do that? (Here we go again, I can see it now...) Or is his only option to try to get some help from the Boeblingen folks who subscribe to the mailing list? This is something I need clarified for myself for future reference. (And if anyone in Boeblingen is reading, 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 giving me difficulty about providing support, as they say I need an additional contract for the OCO. Craig ----- Original Message ----- From: Post, Mark K To: 'Craig J. Yasuna' Sent: Wednesday, January 23, 2002 2:18 PM Subject: RE: QETH Driver failure Craig, I wouldn't say you missed something if you're getting segfaults. That really looks like a code problem. You should be able to open a problem via the IBM Support Center, just as you would with an OS/390 or VM problem. Mark -----Original Message----- From: Craig J. Yasuna [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 23, 2002 2:07 PM To: Post, Mark K Subject: Re: QETH Driver failure Mark, Thanks for the reply, did I miss anything on the install, and it does not seem to initialize at boot time? How do I open a problem records with IBM on the Linux side? thanks - craig ----- Original Message ----- From: Post, Mark K To: 'Superlink' Sent: Wednesday, January 23, 2002 1:51 PM Subject: RE: QETH Driver failure Craig, Since you're getting a segfault in an IBM OCO module, I would suggest you open up a problem record with IBM. They do take those, so you shouldn't have a major problem getting help there. Most people who have been having problems with the OCO modules have not been reporting segfaults, so this looks like something different/new. Your other (less attractive) option would be to run that kernel oops through ksymoops, and report the results on the mailing list. The only people on the list who are going to be able to help you with are are the IBM developers, which is why I made my other recommendation first. Mark -----Original Message----- From: Superlink [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 23, 2002 1:38 PM To: [EMAIL PROTECTED] Subject: QETH Driver failure Mark, Sorry to bother you, but you seem to be the OCO person on the list. I am running RH/390(Enigma) Linux in an IFL. It was originally installed using CTCs to another LPAR. I've installed the OCO modules, updated the chandev.conf, updated modules.conf, done a chown, a depmod -ae, and it still does not work. The card is shared among several LPARS, the portname is the same on all. The insmod of QDIO works fine, the INSMOD of QETH gets a segmentation fault. IFCONFIG will then config the card, but I cannot get I/O through it. lsmod inditactes the QETH module is initializing. QDIO indicates QETH is using it. A boot does not load anything (toher than the CTC) automatically. OSASF indicates that the card is initialized. Any suggestions? Thanks - Craig chandev.conf: ctc0,0xc372,0xc373 add_parms,0x10,0xb800,0xb802,portname:OSAFE7A,no_router qeth0,0xb800,0xb801,0xb802 modules.conf alias parport_lowlevel parport_pc alias eth0 qeth alias tr0 lcs segmentation exception: Oops: 0011 CPU: 0 Process insmod (pid: 1138, stackpage=3D4F1000) Kernel PSW: 07082000 c0831ab8 Tainted: P task: 3d4f0000 ksp: 3d4f1a38 pt_regs: 3d4f19a0 Kernel GPRS: 3d058f84 00000000 00000000 0000004f c0831ac8 3d048800 4087c000 00000001 000000f4 00003d00 00000000 40884300 00003d00 c083192c c0831ac8 3d4f1a38 Kernel ACRS: 00000000 00000000 00000000 00000000 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Kernel BackChain CallChain 3d4f1a38 [<40831ac8>] 3d4f1aa8 [<408397da>] 3d4f1b30 [<4083a000>] 3d4f1b98 [<00112ee6>] 3d4f1cc0 [<00113772>] 3d4f1d70 [<00115990>] 3d4f1dd0 [<4083db98>] 3d4f1e38 [<0002138e>]
