Your message dated Wed, 19 Jun 2013 18:57:35 +0200
with message-id <20130619165735.GC5133@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #614326,
regarding Netgear FA-120 USB Ethernet asix driver fails with latest dist-upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
614326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base
Version: 2.6.37-1
The asix driver appears to be broken with the latest dist-upgrade code in the
sid repository.
The Netgear FA-120 USB ethernet adapter puts out these messages:
[ 7.188171] asix 1-1:1.0: eth1: register 'asix' at usb-0000:00:12.2-1, Netgear
FA-120 USB Ethernet, 00:0f:b5:82:65:39
[ 7.188199] usbcore: registered new interface driver asix
[ 83.864173] asix 1-1:1.0: eth1: Failed to enable software MII access
[ 88.864105] asix 1-1:1.0: eth1: Failed to enable hardware MII access
[ 101.398096] asix 1-1:1.0: eth1: Failed to enable hardware MII access
[ 106.398156] asix 1-1:1.0: eth1: Failed to enable software MII access
[ 126.894078] asix 1-1:1.0: eth1: Failed to enable software MII access
[ 131.894142] asix 1-1:1.0: eth1: Failed to enable hardware MII access
[ 136.894081] asix 1-1:1.0: eth1: Failed to enable software MII access
[ 147.895193] asix 1-1:1.0: eth1: Failed to enable software MII acces
The airlink101 adapter (asix 88178 chip) hangs the entire system.
And the Apple usb/ethernet adapter (also asix based) puts these stack dumps in
syslog:
[ 327.712025] ------------[ cut here ]------------
[ 327.712046] WARNING: at
/tmp/buildd/linux-aptosid-2.6-2.6.37/debian/build/source_amd64_none/net/sched/sch_generic.c:258
dev_watchdog+0x238/0x250()
[ 327.712053] Hardware name: System Product Name
[ 327.712058] NETDEV WATCHDOG: eth1 (asix): transmit queue 0 timed out
[ 327.712062] Modules linked in: vboxnetflt nf_nat_irc nf_conntrack_irc
nf_nat_ftp nf_conntrack_ftp ipt_REJECT ipt_ULOG xt_limit xt_state ipt_REDIRECT
xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4
iptable_filter ip_tables x_tables ppdev lp capifs sco bnep rfcomm l2cap crc16
bluetooth rfkill ntfs nls_utf8 nls_cp437 vfat fat ext3 jbd mbcache xfs exportfs
vboxdrv psmouse powernow_k8 freq_table mperf hwmon_vid eeprom fuse dm_crypt
lgdt330x cx88_dvb cx88_vp3054_i2c videobuf_dvb dvb_core ir_kbd_i2c rtc_isl1208
tuner_simple snd_hda_codec_hdmi tuner_types snd_hda_codec_realtek tda9887
tda8290 snd_hda_intel snd_hda_codec snd_hwdep cx88_alsa tuner ir_lirc_codec
snd_pcm_oss lirc_dev snd_mixer_oss snd_pcm snd_seq_dummy cx8802 ir_sony_decoder
radeon cx8800 snd_seq_oss ir_jvc_decoder cx88xx ir_rc6_decoder snd_seq_midi
v4l2_common snd_rawmidi ir_rc5_decoder videodev ir_nec_decoder
snd_seq_midi_event v4l1_compat ir_common v4l2_compat_ioctl32 ir_core snd_seq
ttm asix usbnet drm_kms_helper tveeprom drm videobuf_dma_sg btcx_risc tpm_tis
snd_timer tpm rtc_cmos videobuf_core i2c_algo_bit snd_seq_device tpm_bios
i2c_piix4 pcspkr rtc_core snd evdev rtc_lib parport_pc k8temp asus_atk0110
shpchp parport i2c_core soundcore amd64_edac_mod edac_core snd_page_alloc
pci_hotplug edac_mce_amd button processor wmi reiserfs raid1 md_mod dm_mirror
dm_region_hash dm_log dm_mod sg sr_mod sd_mod cdrom usbhid crc_t10dif
ata_generic pata_acpi hid ohci_hcd pata_atiixp ahci libahci libata ehci_hcd
usbcore ssb firewire_ohci firewire_core mmc_core pcmcia crc_itu_t floppy r8169
mii scsi_mod pcmcia_core nls_base [last unloaded: vboxnetadp]
core nls_base [last unloaded: vboxnetadp]
[ 327.712296] Pid: 0, comm: kworker/0:0 Not tainted
2.6.37-1.slh.1-aptosid-amd64 #1
[ 327.712301] Call Trace:
[ 327.712306] <IRQ> [<ffffffff8105093b>] ? warn_slowpath_common+0x7b/0xc0
[ 327.712326] [<ffffffff81050a35>] ? warn_slowpath_fmt+0x45/0x50
[ 327.712336] [<ffffffff811d12a2>] ? strlcpy+0x42/0x50
[ 327.712344] [<ffffffff812dd418>] ? dev_watchdog+0x238/0x250
[ 327.712353] [<ffffffff8105d2f3>] ? lock_timer_base+0x33/0x70
[ 327.712361] [<ffffffff8105d424>] ? mod_timer_pinned+0xf4/0x170
[ 327.712371] [<ffffffff810138e1>] ? native_sched_clock+0x11/0x60
[ 327.712379] [<ffffffff8105d049>] ? run_timer_softirq+0x139/0x250
[ 327.712386] [<ffffffff8104b0d9>] ? scheduler_tick+0xd9/0x2e0
[ 327.712393] [<ffffffff812dd1e0>] ? dev_watchdog+0x0/0x250
[ 327.712401] [<ffffffff81056ca6>] ? __do_softirq+0xa6/0x140
[ 327.712408] [<ffffffff8100bddc>] ? call_softirq+0x1c/0x30
[ 327.712416] [<ffffffff8100e0d5>] ? do_softirq+0x65/0xa0
[ 327.712422] [<ffffffff81056b55>] ? irq_exit+0x95/0xa0
[ 327.712431] [<ffffffff8102855a>] ? smp_apic_timer_interrupt+0x6a/0xa0
[ 327.712439] [<ffffffff8100b893>] ? apic_timer_interrupt+0x13/0x20
[ 327.712443] <EOI> [<ffffffff8102f762>] ? native_safe_halt+0x2/0x10
[ 327.712459] [<ffffffff81071ecc>] ? __atomic_notifier_call_chain+0x4c/0x70
[ 327.712467] [<ffffffff810140d3>] ? default_idle+0x23/0x40
[ 327.712474] [<ffffffff810141e4>] ? c1e_idle+0x54/0x120
[ 327.712484] [<ffffffff8100a0ce>] ? cpu_idle+0x5e/0xb0
[ 327.712490] ---[ end trace cbaaca18bc9cfcc2 ]---
This doesn't appear to be kernel specific...same behavior in the 2.6.36-2
kernel and the latest 2.6.37-1 kernel.
--- Begin Message ---
Your message didn't have a Package: line at the very first line of the
mail body (part of the pseudo-header), or didn't have a Package: line
at all. Unfortunatly, this means that your message has been ignored
completely.
Without this information we are unable to categorise or otherwise deal
with your problem report. Please _resubmit_ your report to
sub...@bugs.debian.org and tell us which package the
report is for. For help, check out
http://www.debian.org/Bugs/Reporting.
Your message was dated Sun, 20 Feb 2011 18:04:46 -0500 and had
message-id <20110220180446.31...@web011.roc2.bluetie.com>
and subject Netgear FA-120 USB Ethernet asix driver fails with latest
dist-upgrade.
The complete text of it is attached to this message.
If you need any assistance or explanation please contact
ow...@bugs.debian.org and include the the attached
message.
If you didn't send the attached message (spam was sent forging your
from address), we apologize; please disregard this message.
--
-1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
After the latest dist-upgrade, the Netgear adapter no longer works on my system.
What's puzzling is that it doesn't seem to be kernel dependent...the same error
messages happen whether the 2.6.36-2 kernel is used or the 2.6.27-1 kernel is
used.
[ 7.188171] asix 1-1:1.0: eth1: register 'asix' at usb-0000:00:12.2-1, Netgear
FA-120 USB Ethernet, 00:0f:b5:82:65:39
[ 7.188199] usbcore: registered new interface driver asix
[ 83.864173] asix 1-1:1.0: eth1: Failed to enable software MII access
[ 88.864105] asix 1-1:1.0: eth1: Failed to enable hardware MII access
[ 101.398096] asix 1-1:1.0: eth1: Failed to enable hardware MII access
[ 106.398156] asix 1-1:1.0: eth1: Failed to enable software MII access
[ 126.894078] asix 1-1:1.0: eth1: Failed to enable software MII access
[ 131.894142] asix 1-1:1.0: eth1: Failed to enable hardware MII access
[ 136.894081] asix 1-1:1.0: eth1: Failed to enable software MII access
[ 147.895193] asix 1-1:1.0: eth1: Failed to enable software MII acces
I've switched to an Apple USB ethernet adapter in the meantime without
problems. An Airlink 101 adapter (Asix 88178 chipset) also works fine.
ken
--- End Message ---
--- End Message ---
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by
sending
a mail to cont...@bugs.debian.org with the following three commands included in
the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
