Package: linux-2.6
Version: 2.6.32-3
Severity: normal

Hi.

Since linux-image-2.6.32-3 (and also at least with -4) (tested with the
-486 version of the image) my ATL1E network of the EEE PC 900A does not
longer work.
The module is automatically loaded, dmesg shows the usual info about the
network card, but when brining the iface up I get:
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device

There is not MAC address problem with udev persistent-net-rules.

Going back to the linux-image-2.6.30-2-486... and everything works
again.


Any ideas?

Cheers,
Chris.


-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-fermat (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

On Thu, 2010-04-01 at 14:41 +0200, Christoph Anton Mitterer wrote:
> Package: linux-2.6
> Version: 2.6.32-3
> Severity: normal
>
> Hi.
>
> Since linux-image-2.6.32-3 (and also at least with -4) (tested with the
> -486 version of the image) my ATL1E network of the EEE PC 900A does not
> longer work.
> The module is automatically loaded, dmesg shows the usual info about the
> network card,

Show me.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Hi Ben


On Thu, 01 Apr 2010 14:22:43 +0100, Ben Hutchings <ben@decadent.org.uk>
wrote:
>> The module is automatically loaded, dmesg shows the usual info about
the
>> network card,
> Show me.
I've attached dmesg output (also the one of the old 2.6.30 kernel) and
loaded modules.

Thx,
Chris.Module Size Used by
acpi_cpufreq 3614 0
cpufreq_stats 1592 0
cpufreq_userspace 1300 0
cpufreq_powersave 602 0
cpufreq_conservative 3902 0
binfmt_misc 4719 1
uinput 4664 1
fuse 42747 1
ip6table_filter 1912 1
ip6_tables 8168 1 ip6table_filter
iptable_filter 1794 1
ip_tables 7326 1 iptable_filter
x_tables 8283 2 ip6_tables,ip_tables
joydev 6599 0
snd_hda_codec_realtek 163122 1
snd_hda_intel 16363 0
snd_hda_codec 45794 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 4022 1 snd_hda_codec
snd_pcm 46210 2 snd_hda_intel,snd_hda_codec
snd_seq 35413 0
snd_timer 12292 2 snd_pcm,snd_seq
snd_seq_device 3661 1 snd_seq
eeepc_laptop 9351 0
snd 34102 8 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec, snd_hwdep,snd_pcm,snd_seq,snd_timer,snd_seq_device
uvcvideo 45162 0
rfkill 10658 1 eeepc_laptop
soundcore 3294 1 snd
videodev 25417 1 uvcvideo
snd_page_alloc 5017 2 snd_hda_intel,snd_pcm
rng_core 2162 0
psmouse 48174 0
pcspkr 1235 0
v4l1_compat 10246 2 uvcvideo,videodev
pci_hotplug 18013 1 eeepc_laptop
battery 3774 0
ac 1628 0
processor 23235 2 acpi_cpufreq
evdev 5520 17
serio_raw 2912 0
aes_i586 6816 2
aes_generic 25738 1 aes_i586
xts 1701 1
gf128mul 5106 1 xts
ext4 237427 1
mbcache 3482 1 ext4
jbd2 48327 1 ext4
crc16 1027 1 ext4
dm_crypt 9023 1
raid10 16377 0
usb_storage 29677 0
raid456 39925 0
async_raid6_recov 4042 1 raid456
async_pq 2639 2 raid456,async_raid6_recov
raid6_pq 77468 2 async_raid6_recov,async_pq
async_xor 1974 3 raid456,async_raid6_recov,async_pq
xor 12418 1 async_xor
async_memcpy 846 2 raid456,async_raid6_recov
async_tx 1310 5 raid456,async_raid6_recov,async_pq,async_xor,async _memcpy
raid1 15863 0
raid0 5529 0
multipath 4899 0
linear 2999 0
md_mod 65915 6 raid10,raid456,raid1,raid0,multipath,linear
sd_mod 25733 2
crc_t10dif 1012 1 sd_mod
ide_pci_generic 1920 0
ide_core 64230 1 ide_pci_generic
i915 212244 1
ata_generic 2011 0
drm_kms_helper 17275 1 i915
ata_piix 16625 1
drm 106715 2 i915,drm_kms_helper
uhci_hcd 16017 0
i2c_algo_bit 3489 1 i915
intel_agp 20135 1
libata 115918 2 ata_generic,ata_piix
i2c_core 12600 4 videodev,i915,drm,i2c_algo_bit
atl1e 22784 0
ehci_hcd 27716 0
agpgart 19100 2 drm,intel_agp
scsi_mod 102173 3 usb_storage,sd_mod,libata
usbcore 98034 5 uvcvideo,usb_storage,uhci_hcd,ehci_hcd
video 14557 1 i915
output 1204 1 video
nls_base 4445 1 usbcore
button 3578 1 i915
thermal 9210 0
fan 2590 0
thermal_sys 9346 4 processor,video,thermal,fan
dm_mirror 9731 0
dm_region_hash 5443 1 dm_mirror
dm_log 6257 2 dm_mirror,dm_region_hash
dm_mod 45901 5 dm_crypt,dm_mirror,dm_log

On Thu, 2010-04-01 at 22:23 +0000, calestyo@scientia.net wrote:
> Hi Ben
>
>
> On Thu, 01 Apr 2010 14:22:43 +0100, Ben Hutchings <ben@decadent.org.uk>
> wrote:
> >> The module is automatically loaded, dmesg shows the usual info about
> the
> >> network card,
> > Show me.
> I've attached dmesg output (also the one of the old 2.6.30 kernel) and
> loaded modules.

If you add 'blacklist eeepc-laptop' to /etc/modprobe.d/blacklist and
then reboot, does the atl1e driver work again?

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

On Sat, 03 Apr 2010 01:30:52 +0100, Ben Hutchings <ben@decadent.org.uk>
wrote:
> If you add 'blacklist eeepc-laptop' to /etc/modprobe.d/blacklist and
> then reboot, does the atl1e driver work again?
Yes That works.

Just removing eeepc-laptop or removing + removing/reinstalling atl1e does
not work by the way (I mean without adding it to blacklist+rebooting)

Thanks so far

Cheers,
Chris.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: e2d4e2509e67eee45b13f457fb01a983@imap.dd24.net">ht tp://lists.debian.org/e2d4e2509e67eee45b13f457fb01a983@imap.dd24.net

On Sat, 2010-04-03 at 01:32 +0000, Christoph Anton Mitterer wrote:
> On Sat, 03 Apr 2010 01:30:52 +0100, Ben Hutchings <ben@decadent.org.uk>
> wrote:
> > If you add 'blacklist eeepc-laptop' to /etc/modprobe.d/blacklist and
> > then reboot, does the atl1e driver work again?
> Yes That works.
>
> Just removing eeepc-laptop or removing + removing/reinstalling atl1e does
> not work by the way (I mean without adding it to blacklist+rebooting)
[...]

It looks like this is yet another Eee model where eeepc-laptop is
hotplugging the wired network controller (similar to bug #573607)
instead of the wireless network controller.

eeepc-laptop should use a whitelist of those models where 01:00.0 is the
correct address, or some other method to find the correct address. What
it's doing now is dangerously wrong.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Hi Ben.

On Sat, 2010-05-15 at 14:34 +0100, Ben Hutchings wrote:
> Version: 2.6.32-11
>
> This was fixed in the above version.
Should this already work with the linux-image-2.6.32-5-amd64 kernel?

If so, we'll have to reopen the bug, as it does not longer work, when I
disable the blacklisting of the eee module.


Cheers,
Chris.

On Wed, 2010-06-09 at 16:10 +0200, Christoph Anton Mitterer wrote:
> Hi Ben.
>
> On Sat, 2010-05-15 at 14:34 +0100, Ben Hutchings wrote:
> > Version: 2.6.32-11
> >
> > This was fixed in the above version.
> Should this already work with the linux-image-2.6.32-5-amd64 kernel?
>
> If so, we'll have to reopen the bug, as it does not longer work, when I
> disable the blacklisting of the eee module.

I'm sorry, I was confused. Only the 1005HA, 1201N and 1005PE models
were fixed in 2.6.32-11. I never got confirmation from the eeepc-laptop
maintainer that the same change should be applied to the 900A. I have
reopened this bug.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

On Thu, 2010-06-10 at 01:01 +0100, Ben Hutchings wrote:
> On Wed, 2010-06-09 at 16:10 +0200, Christoph Anton Mitterer wrote:
> > Hi Ben.
> >
> > On Sat, 2010-05-15 at 14:34 +0100, Ben Hutchings wrote:
> > > Version: 2.6.32-11
> > >
> > > This was fixed in the above version.
> > Should this already work with the linux-image-2.6.32-5-amd64 kernel?
> >
> > If so, we'll have to reopen the bug, as it does not longer work, when I
> > disable the blacklisting of the eee module.
>
> I'm sorry, I was confused. Only the 1005HA, 1201N and 1005PE models
> were fixed in 2.6.32-11. I never got confirmation from the eeepc-laptop
> maintainer that the same change should be applied to the 900A. I have
> reopened this bug.

I've found the change that Corentin Chary said should cover the 900A.
This will be included in 2.6.32-16. Please let us know if this doesn't
fix the problem for you. Again, sorry for wrongly claiming it was fixed
already.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

On Thu, 2010-06-10 at 01:20 +0100, Ben Hutchings wrote:
> I've found the change that Corentin Chary said should cover the 900A.
> This will be included in 2.6.32-16. Please let us know if this doesn't
> fix the problem for you.
Will test it as soon as the package is out.

> Again, sorry for wrongly claiming it was fixed
> already.
No problem

Cheers,
Chris.