Mailinglist Archive: opensuse-bugs (5757 mails)

[bugzilla_noreply@xxxxxxxxxx]

http://bugzilla.novell.com/show_bug.cgi?id=615761

http://bugzilla.novell.com/show_bug.cgi?id=615761#c34


--- Comment #34 from Camaleon -- <noelamac@xxxxxxxxx> 2010-08-04 19:35:47 CEST 
---
(In reply to comment #33)
> Does the BIOS on the system allow ASPM to be disabled?  If so can you try
> disabling it and give it a try?  

BIOS capabilities are very limited. No, I'm afraid there is none related with
ASPM (I only can enable/disable the ethernet adapter but nothing more).

I've also tried passing "pcie_aspm=off" parameter to the kernel but seems to
have no effect:

(with kernel 2.6.34)

test@linux-5qwj:~> dmesg | grep aspm; dmesg | grep e1000e
[    0.000000] Kernel command line:
root=/dev/disk/by-id/usb-SAMSUNG_VG38404A__8.4_0-0:0-part2
resume=/dev/disk/by-id/usb-SAMSUNG_VG38404A__8.4_0-0:0-part1 splash=silent
quiet vga=0x317 pcie_aspm=off
[    0.619891] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device.  You
can enable it with 'pcie_aspm=force'
[    0.620212] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device.  You
can enable it with 'pcie_aspm=force'
[    0.620848] pci 0000:05:00.0: disabling ASPM on pre-1.1 PCIe device.  You
can enable it with 'pcie_aspm=force'
[   13.266572] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.8-NAPI
[   13.266576] e1000e: Copyright(c) 1999 - 2010 Intel Corporation.
[   13.266631] e1000e 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   13.266656] e1000e 0000:02:00.0: setting latency timer to 64
[   13.267015] e1000e 0000:02:00.0: irq 29 for MSI/MSI-X
[   13.267035] e1000e 0000:02:00.0: Disabling ASPM L0s 
[   13.531569] e1000e 0000:02:00.0: (unregistered net_device): NVM Read Error
while reading MAC address
[   13.531876] e1000e 0000:02:00.0: (unregistered net_device): Invalid MAC
Address: 00:00:00:00:00:00
[   13.542407] e1000e 0000:02:00.0: PCI INT A disabled
[   13.542417] e1000e: probe of 0000:02:00.0 failed with error -5

(with kernel 2.6.35)

test@linux-5qwj:~> dmesg | grep aspm; dmesg | grep e1000e
[    0.000000] Kernel command line:
root=/dev/disk/by-id/usb-SAMSUNG_VG38404A__8.4_0-0:0-part2
resume=/dev/disk/by-id/usb-SAMSUNG_VG38404A__8.4_0-0:0-part1 splash=silent
quiet vga=0x317 pcie_aspm=off
[    0.607913] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device.  You
can enable it with 'pcie_aspm=force'
[    0.608232] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device.  You
can enable it with 'pcie_aspm=force'
[    0.608860] pci 0000:05:00.0: disabling ASPM on pre-1.1 PCIe device.  You
can enable it with 'pcie_aspm=force'
[   16.238851] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k4
[   16.238854] e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
[   16.238911] e1000e 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   16.238937] e1000e 0000:02:00.0: setting latency timer to 64
[   16.239141] e1000e 0000:02:00.0: irq 45 for MSI/MSI-X
[   16.239316] e1000e 0000:02:00.0: Disabling ASPM L0s 
[   16.294535] e1000e 0000:02:00.0: (unregistered net_device): NVM Read Error
while reading MAC address
[   16.294551] e1000e 0000:02:00.0: (unregistered net_device): Invalid MAC
Address: 00:00:00:00:00:00
[   16.304777] e1000e 0000:02:00.0: PCI INT A disabled
[   16.304784] e1000e: probe of 0000:02:00.0 failed with error -

> Is this still happening on 2.6.35 now that it's released?  

Yes, it is still happening (see my comment #32 on Novell's bugzilla)

https://bugzilla.novell.com/show_bug.cgi?id=615761#c32

> We need to narrow this down more than it is so we can see what
> has changed.  It does seem that this is broken on 2.6.34 but since we don't
> have one of these systems (and haven't seen this for some time now) it's going
> to be very hard for us to narrow down the actual changes that could be causing
> the problem.

I know, it's hard to diagnose... what puzzles me most is not seeing more
reports/complaints about this, as this should a very common NIC chipset :-?

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.