Bug 106697 - LTC4843-fake_ll not working for QETH device
LTC4843-fake_ll not working for QETH device
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
s390 Linux
medium Severity medium
: ---
: ---
Assigned To: Pete Zaitcev
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-10-09 14:00 EDT by Duane Beyer
Modified: 2008-08-13 17:06 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-13 17:06:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Fully working, but with P3s (6.94 KB, patch)
2003-10-09 17:59 EDT, Pete Zaitcev
no flags Details | Diff

  None (edit)
Description Duane Beyer 2003-10-09 14:00:14 EDT
The following has be reported by IBM LTC:  
fake_ll not workingfor QETH device
Hardware Environment:z/900

Software Environment:RHEL-3 RC1

Steps to Reproduce:
1. Add the fake_ll to the parm in chandev.conf
     Followed the directions in Linux For zSeries and S/390 Device Drivers and 
Installation Commands July 25, 2003 Chapter 19, Enabling OSA-Express QDIO 
devices in Linux for DHCP and tcpdump.
eth0 is the interface used in this case. 

2. Reboot the system
3. Start "ethereal" and capture packets for eth0  

Actual Results: 
Capturing on eth0
  0.000000 40:00:40:06:3e:d1 -> 45:10:00:4c:20:99 0x090c Ethernet II
  0.132967 40:00:7d:06:52:a3 -> 45:00:00:28:cf:fa 0x0938 Ethernet II
  0.159949 40:00:40:06:3e:58 -> 45:10:00:c4:20:9a 0x090c Ethernet II
  0.333547 40:00:7d:06:52:a2 -> 45:00:00:28:cf:fb 0x0938 Ethernet II
  0.333580 40:00:40:06:3e:9f -> 45:10:00:7c:20:9b 0x090c Ethernet II

Expected Results:
Packets should have been valid TCP packets.  It appears that the LLC headers 
are still not on the packets.  

Additional Information: I get the same results on both 31 and 64 bit systems.
Comment 1 Pete Zaitcev 2003-10-09 17:57:33 EDT
It's Boeblingen's fault, but I fixed it (*beaming* :-)
See the attached patch.
Comment 2 Pete Zaitcev 2003-10-09 17:59:25 EDT
Created attachment 95089 [details]
Fully working, but with P3s
Comment 3 Duane Beyer 2003-10-10 16:28:52 EDT
Peter,  Not sure what you mean by P3's.   Is that a 390 box. Also, will this be 
picked up in the next release of Red Hat or do I need to go back to Boeblingen.
Comment 4 Pete Zaitcev 2003-10-10 17:23:34 EDT
Duane, please look at the patch - "P3" is a tag for debugging messages.
Final version won't have them, naturally.

I think I can get this into U1.

I also sumbitted it to Utz Bacher for inclusion into DeveloperWorks.
If you are interested helping it to happen, you might want to poke
him for opinion/rejection/acception.
Comment 5 Pete Zaitcev 2003-10-10 17:25:45 EDT
I observe that Utz made himself an account in RH Bugzilla,
let me try to add him to cc: for this bug...
Comment 6 Duane Beyer 2003-10-14 16:51:43 EDT
Thanks for the update, I applied the patch and it is working fine.  I'll nudge 
Comment 7 Pete Zaitcev 2003-10-23 00:30:31 EDT
Ernie approved, I'm resending for commit now.
I dropped all unrelated fixes (such as dst_link_failure removal).
Comment 8 Pete Zaitcev 2003-11-09 01:28:14 EST
Modified 2.4.21-4.11.EL
Duane, please test and reopen or close, according to results.

Note You need to log in before you can comment on or make changes to this bug.