Hi Rui, hi list,

On Wed, 14 Jun 2006, Rui Santos wrote:

> 
> elmar gerdes wrote:
>> hi folks,
>>
> Hi
>> I'm running a 2.6.16.16 kernel on a small Via Epia Nano N 10000E board
>> with a "Luke" processor.
>>
>> Running a bridge over one on-board ethernet interface (via-rhine) and a
>> USB-to-ethernet adaptor D-Link DUB-E100 (with asix AX88772 chip, drivers:
>> usbnet + asix), I occasionally get an oops like the one I append to this
>> mail.
>>

I just had another look at the D-Link DUB-E100: it has an Asix AX88172
chip, not AX88772.  sorry for that.  It worked right out-of-the box.  it
is already mentioned in the 2.6.14 sources I have lying around here.

> I've been trying to get that DUB-E100 with the asix AX8872 chip to work,
> and didn't succeed.
> Could you please share with this list how did you get it to work?
> I've tried adding a new ProductID and VendorID to drivers/usb/net/asix.c
> and use the ax88772_info driver_info struct. The kernel recognizes it as
> the correct network card but when I perform a ethtool eth0 the only
> output I get is:

I didn't change anything concerning the DUB-E100 in the kernel sources,
so it uses the dlink_dub_e100_info struct and original USB_DEVICE
(0x2001, 0x1a00).  Maybe you have a different revision (if there are
any), mine is 10.01 (taken from /proc/bus/usb/devices).

I haven't run ethtool on it.  it's not on the system that's running a
stress test using the adapter.

My problem with the VIA-based systems and USB-to-ethernet adaptors
oopsing after a while is still not solved.  I haven't seen it on
(large/fast) Intel/AMD-based systems, just on VIA-based systems (C3,
steppings 8 and 10), and only if such an adaptor is involved, not on
those with dual LAN on-board.  It appears with Linksys USB200M,
D-Link DUB-E100, and a Digitus adaptor, all of which use the asix driver.

>
> Settings for eth0:
>    Current message level: 0x00000007 (7)
>    Link detected: yes
>
> Can you give me a hint on this
>
>> the adaptor is running in high-speed mode under high load (about 65..75
>> Mbps, full-duplex).  the last occurrence of this error was when the board
>> had been running all night long, and then I logged in.
>>
>> since the first messages in the Oops are about ehci_hcd (scan_periodic
>> and ehci_work), I chose this mailing list to present the error to.  any
>> help would be warmly welcome.
>>
>> greetings from
>>              elmar
>>
> Thank you
> Rui Santos
>
>> PS: I'll give you more info about the system, just as you need it.
>>
>>
>>
>>
>> Unable to handle kernel NULL pointer dereference at virtual address 00000216
>>  printing eip:
>> cc86fde0
>> *pde = 00000000
>> Oops: 0002 [ #1 ]
>> Modules linked in: bridge padlock blowfish twofish cdc_subset asix usbnet 
>> sis190
>>  tg3 bnx2 r8169 sky2 e1000 8139too eepro100 3c59x via_rhine mii pcmcia 
>> pcmcia_co
>> re vfat fat mct_u232 pl2303 usbserial usblp ehci_hcd uhci_hcd ohci_hcd 
>> sd_mod us
>> b_storage scsi_mod usbcore
>> CPU:    0
>> EIP:    0060:[<cc86fde0>]      Not tainted VLI
>> EFLAGS: 00010202   (2.6.16.16 #1)
>> EIP is at scan_periodic+0x120/0x2f0 [ehci_hcd]
>> eax: 00000216   ebx: 00000000   ecx: c13af108   edx: cb95d0d0
>> esi: 00000000   edi: cb95d0d0   ebp: cb983108   esp: cb45be6c
>> ds: 007b   es: 007b   ss: 0068
>> Process sh (pid: 1192, threadinfo=cb45a000 task=cbfdd050)
>> Stack: <0>00000006 c13af108 cb95d000 00000000 00000800 00000216 00000216 
>> 0000004
>> 2
>>        cb95d0d0 cb45bfbc cb95d0d0 00000001 cc8700fc cb95d0d0 cb45bfbc 
>> 00000000
>>        00000000 cc870569 cb95d0d0 cb45bfbc cbd4ca00 cbbaa080 0807864a 
>> cbdfac3c
>> Call Trace:
>>  [<cc8700fc>] ehci_work+0x4c/0xd0 [ehci_hcd]
>>  [<cc870569>] ehci_irq+0xc9/0x160 [ehci_hcd]
>>  [<c012ed63>] find_get_page+0x13/0x30
>>  [<c012fb4b>] filemap_nopage+0x8b/0x320
>>  [<c013abf8>] do_no_page+0x58/0x1d0
>>  [<c013accd>] do_no_page+0x12d/0x1d0
>>  [<c013ae98>] __handle_mm_fault+0xb8/0x190
>>  [<c01cc7e1>] copy_to_user+0x31/0x40
>>  [<cc835958>] usb_hcd_irq+0x28/0x70 [usbcore]
>>  [<c012db08>] handle_IRQ_event+0x28/0x70
>>  [<c012db9f>] __do_IRQ+0x4f/0xa0
>>  [<c010475a>] do_IRQ+0x1a/0x30
>>  [<c0102ffa>] common_interrupt+0x1a/0x20
>> Code: f7 74 24 10 89 54 24 14 e9 4e ff ff ff 8b 54 24 08 f6 82 cc 00 00 00 
>> 01 74
>>  25 8b 54 24 34 8b 44 24 14 89 42 30 8b 42 04 8b 40 0c <00> 00 00 00 00 00 
>> 00 00
>>  24 14 89 54 24 18 0f 85 1c ff ff ff 83
>>  <0>Kernel panic - not syncing: Fatal exception in interrupt
>>

cheers,
        elmar



_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to