mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Holger Birkmeyer <holger.birkmeyer@ebee.berlin>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: ASIX USB dongle problem: asix_rx_fixup() Bad Header Length
Date: Tue, 28 Nov 2017 13:40:28 +0100	[thread overview]
Message-ID: <51e9790a-364c-782d-cd81-721dcba52d78@ebee.berlin> (raw)
In-Reply-To: <20171128084351.wcdzcp7m43iijsun@pengutronix.de>


[-- Attachment #1.1.1: Type: text/plain, Size: 9299 bytes --]

Dear Sascha,

the ASIX USB dongle is working on the same hardware running a 4.4
vanilla kernel. The dongle also works on my Linux PC with a 4.13 kernel.

I added memory_display(buf, 0, len, 4, 0) to asix_rx_fixup(). Here are
the logs:

barebox@Atmel at91sam9260-ek:/ usb
usb: USB: scanning bus for devices...
usb: Bus 001 Device 001: ID 0000:0000 OHCI Root Hub
usb: Bus 001 Device 002: ID 0b95:7720 AX88772A
mdio_bus: miibus1: probed
eth1: got preset MAC address: 8c:ae:4c:eb:1f:83
usb: 2 USB Device(s) found
barebox@Atmel at91sam9260-ek:/ eth1.ipaddr=192.168.10.120
barebox@Atmel at91sam9260-ek:/ ethact eth1
barebox@Atmel at91sam9260-ek:/ ping 192.168.10.55
eth1: 100Mbps full duplex link detected
00000000: ffffffc3 ffffffff eaa82a80 06088d6a               
.........*..j...
00000010: 00080100 01000406 eaa82a80 a8c08d6a               
.........*..j...
00000020: 0000020a 00000000 6b0aa8c0 00000000               
...........k....
00000030: 00000000 00000000 00000000 00b90000               
................
00000040: ffffff46 ffffffff eaa82a80 00088d6a               
F........*..j...
00000050: ab000045 00400000 986f1140 020aa8c0               
E.....@.@.o.....
00000060: ffffffff 1127d7b5 af4b9700 8b000602               
......'...K.....
00000070: 800a0002 6aeaa82a 0aa8c08d 06000102               
....*..j........
00000080: eaa82a80 000a8d6a c1130004 04000b2a               
.*..j.......*...
00000090: 544e4255 4203000c 0003325a 2e5a4222               
UBNT...BZ2.."BZ.
000000a0: 32377261 762e3034 2e372e33 362e3535               
ar7240.v3.7.55.6
000000b0: 2e383033 34303731 312e3331 16363535               
308.170413.1556.
000000c0: 2e330b00 35352e37 3033362e 03001538               
..3.7.55.6308...
000000d0: 17325a42 18000100 19000100 1a000100               
BZ2.............
000000e0: 13000100 2a800600 8d6aeaa8 00040012               
.......*..j.....
000000f0: 1beff801 2e320500 9d342e34 ffc3003c               
......2.4.4.<...
00000100: ffffffff 2a80ffff 8d6aeaa8 01000608               
.......*..j.....
00000110: 04060008 2a800100 8d6aeaa8 020aa8c0               
.......*..j.....
00000120: 00000000 a8c00000 00006b0a 00000000               
.........k......
00000130: 00000000 00000000 00000000 ff4300bc               
..............C.
00000140: ffffffff 2a80ffff a88bb2a8 00450008               
.......*......E.
00000150: 0000ae00 11400040 a8c0926f ffff050a               
....@.@.o.......
00000160: 01adffff 9a001127 0602ccad 00028e00               
....'...........
00000170: a82a800a c0b9bb13 01050aa8 2a800600               
..*............*
00000180: b9bb13a8 0004000a 0b6d6f1a 42550400               
.........om...UB
00000190: 000c544e 4c375504 23000354 712e5a42               
NT...U7LT..#BZ.q
000001a0: 35396163 762e7836 2e372e33 362e3535               
ca956x.v3.7.55.6
000001b0: 2e383033 34303731 312e3331 16303136               
308.170413.1610.
000001c0: 2e330b00 35352e37 3033362e 04001538               
..3.7.55.6308...
000001d0: 544c3755 00010017 00010018 00010019               
U7LT............
000001e0: 0001001a 80060013 bb13a82a 040012b9               
........*.......
000001f0: 44a40200 3305001b 312e342e ffc3003c               
...D...3.4.1<...
00000200: ffffffff 0bd4ffff 7490591a 01000608               
.........Y.t....
00000210: 04060008 0bd40200 7490591a a90aa8c0               
.........Y.t....
00000220: ffffffff a8c0ffff 0000010a 00000000               
................
00000230: 00000000 00000000 00000000 ffc3003c               
............<...
00000240: ffffffff c000ffff 116d95ca 00450008               
..........m...E.
00000250: d3b52600 11400040 a8c023ba ffff280a               
.&..@.@..#...(..
00000260: 46e0ffff 12002ffd be002fd9 a8c042ac               
...F./.../...B..
00000270: 8206280a 00000000 00000000 ffc3003c               
.(..........<...
00000280: eb4cae8c 973c831f 2b08590e 01000608               
..L...<..Y.+....
00000290: 04060008 973c0200 2b08590e 370aa8c0               
......<..Y.+...7
000002a0: eb4cae8c a8c0831f 0000780a 00000000               
..L......x......
000002b0: 00000000 00000000 00000000                         ............
eth1: asix_rx_fixup() Bad Header Length 0xffffffc3, offset 4
00000000: ff4600b9 ffffffff 2a80ffff 8d6aeaa8               
..F........*..j.
00000010: 00450008 0000ab00 11400040 a8c0986f               
..E.....@.@.o...
00000020: ffff020a c5b9ffff 97001127 0602c13c               
........'...<...
00000030: 00028b00 a82a800a c08d6aea 01020aa8               
......*..j......
00000040: 2a800600 8d6aeaa8 0004000a 0b34c113               
...*..j.......4.
00000050: 42550400 000c544e 325a4203 42220003               
..UBNT...BZ2.."B
00000060: 72612e5a 30343237 2e33762e 35352e37               
Z.ar7240.v3.7.55
00000070: 3033362e 37312e38 33313430 3535312e               
.6308.170413.155
00000080: 0b001636 2e372e33 362e3535 15383033               
6...3.7.55.6308.
00000090: 5a420300 01001732 01001800 01001900               
..BZ2...........
000000a0: 01001a00 06001300 eaa82a80 00128d6a               
.........*..j...
000000b0: f8010004 05001bf0 2e342e32 16364434                ........2.4.4D
00000000: ffc3003c ffffffff 2a80ffff a88bb2a8               
<..........*....
00000010: 01000608 04060008 2a800100 a88bb2a8               
...........*....
00000020: 050aa8c0 00000000 a8c00000 00006d0a               
.............m..
00000030: 00000000 00000000 00000000 00000000               
................
T 00000000: ffc3003c eb4cae8c 973c831f 2b08590e               
<.....L...<..Y.+
00000010: 01000608 04060008 973c0200 2b08590e               
..........<..Y.+
00000020: 370aa8c0 eb4cae8c a8c0831f 0000780a               
...7..L......x..
00000030: 00000000 00000000 00000000 00000000               
................
00000000: ffc3003c eb4cae8c 973c831f 2b08590e               
<.....L...<..Y.+
00000010: 00450008 43392500 01400000 a8c095ab               
..E..%9C..@.....
00000020: a8c0370a 0000780a 0000f443 877c0000               
.7...x..C.....|.
00000030: 000c8388 00ab0000 00000000 00000000               
................

Regards,
Holger

On 28.11.2017 09:43, Sascha Hauer wrote:
> HI Holger,
>
> +Cc Lucas who has also some patches in the Asix driver.
>
> On Mon, Nov 27, 2017 at 06:01:15PM +0100, Holger Birkmeyer wrote:
>> Dear all,
>>
>> I am struggling to get networking up and running on my Atmel at91sam9260-ek.
>>
>> I am trying to use an ASIX USB dongle. I got pretty far. Here is the
>> console log:
>>
>> ...snip...
>>
>> barebox 2017.11.0-gdf1d493-dirty #50 Mon Nov 27 17:20:57 CET 2017
>>
>> ...snip...
>>
>> Board: Atmel at91sam9260-ek
>> AT91: Detected soc type: at91sam9260
>> AT91: Detected soc subtype: Unknown
>>
>> ...snip...
>>
>> usb: USB: scanning bus for devices...
>> usb: Bus 001 Device 001: ID 0000:0000 OHCI Root Hub
>> usb: Bus 001 Device 002: ID 0b95:7720 AX88772A
>> mdio_bus: miibus1: probed
>> eth1: got preset MAC address: 8c:ae:4c:eb:1f:83
>> usb: 2 USB Device(s) found
>>
>> But as soon as I start using the device eth1, the following error
>> messages appear in the serial console and the dongle LEDs will turn dark.
>>
>> ping 8.8.8.8
>> eth1: 100Mbps full duplex link detected
>> eth1: asix_rx_fixup() Bad Header Length 0xffffffc3, offset 4
>> eth1: asix_rx_fixup() Bad Header Length 0xd526003c, offset 514
>> eth1: asix_rx_fixup() Bad Header Length 0x97001127, offset 4
>> eth1: asix_rx_fixup() Bad Header Length 0xffffffc3, offset 4
>> T ERROR: OHCI Unrecoverable Error, controller usb-ohci disabled
>> ERROR: sohci_submit_job failed with -32
> I have a AX88772A running here and it works fine on an i.MX53 board.
> There are some things you could try. Do you have some other hardware
> you can test? Like another board or another USB dongle? I do not really
> trust the OHCI driver.
> The Asix code is directly derived from the kernel. the asix_rx_fixup()
> looks quite different there now, so it could be that the barebox code
> has a bug in this area.
> If that doesn't help, could you add a
>
> memory_display(buf, 0, len, 4, 0)
>
> to the top of asix_rx_fixup_internal() and post the result?
>
> Also maybe Lucas has an idea.
>
> Sascha
>

-- 
Holger Birkmeyer
Ebee Smart Technologies GmbH
Torgauer Str. 12-15
10829 Berlin
Phone: +49 30 6098371-52
Mail: holger.birkmeyer@ebee.berlin


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-11-28 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 17:01 Holger Birkmeyer
2017-11-28  8:43 ` Sascha Hauer
2017-11-28 12:40   ` Holger Birkmeyer [this message]
2017-11-28 13:20     ` Sascha Hauer
2017-11-28 13:32       ` Holger Birkmeyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51e9790a-364c-782d-cd81-721dcba52d78@ebee.berlin \
    --to=holger.birkmeyer@ebee.berlin \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox