[Bug 738547] New: network card only detected without cable; plugging in cable causes kernel bug
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c0 Summary: network card only detected without cable; plugging in cable causes kernel bug Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: suse-beta@cboltz.de QAContact: qa@suse.de Found By: --- Blocker: --- I have a very strange issue on a system with two network cards. One of them (eth2, the one on the mainboard) works without problems, but the other (eth3) is only detected if no cable is plugged in (no, I'm not joking ;-) To make it even more interesting, I get a kernel bug logged (see attachment) when I plug in a network cable in the non-working card. lspci: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev ff) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) hwinfo --network 39: None 00.0: 10700 Loopback [Created at net.124] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 40: None 03.0: 10701 Ethernet [Created at net.124] Unique ID: GP_i.ndpeucax6V1 Parent ID: DkES.+0uqx5FUcb7 SysFS ID: /class/net/eth3 SysFS Device Link: /devices/pci0000:00/0000:00:04.0/0000:02:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "r8169" Driver Modules: "r8169" Device File: eth3 HW Address: 00:0a:cd:1b:ac:7b Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #24 (Ethernet controller) 41: None 02.0: 10701 Ethernet [Created at net.124] Unique ID: pDke.ndpeucax6V1 Parent ID: mY_N.sJMQtADpSK3 SysFS ID: /class/net/eth2 SysFS Device Link: /devices/pci0000:00/0000:00:05.0/0000:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "r8169" Driver Modules: "r8169" Device File: eth2 HW Address: 8c:89:a5:66:f8:80 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> 2011-12-25 21:30:55 CET --- Created an attachment (id=468913) --> (http://bugzilla.novell.com/attachment.cgi?id=468913) /v/l/messages, bz2-compressed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c3 Benjamin Poirier <bpoirier@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jlee@suse.com, | |trenn@novell.com InfoProvider| |suse-beta@cboltz.de --- Comment #3 from Benjamin Poirier <bpoirier@suse.com> 2012-03-23 13:34:16 UTC --- Initialization of the card is failing. From the driver: r8169 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 r8169 0000:02:00.0: cache line size of 64 is not supported r8169 0000:02:00.0: (unregistered net_device): Mem-Wr-Inval unavailable Those last two messages are printed as a result of: \ rtl8169_init_one (pci probe function) \ pci_set_mwi \ pci_set_cacheline_size not fatal since 87aeec7 r8169: failure to enable mwi should not be fatal r8169 0000:02:00.0: (unregistered net_device): region #2 not an MMIO resource, aborting if !pci_resource_flags(pdev, region) & IORESOURCE_MEM): return -ENODEV r8169 0000:02:00.0: PCI INT A disabled Given the boot log we can see a problem at pci enumeration time for device 0000:02:00.0. A working 8168 card has three pci BARs/regions, like so: pci 0000:03:00.0: [10ec:8168] type 0 class 0x000200 pci 0000:03:00.0: reg 10: [io 0xc800-0xc8ff] pci 0000:03:00.0: reg 18: [mem 0xfdfff000-0xfdffffff 64bit pref] pci 0000:03:00.0: reg 20: [mem 0xfdff8000-0xfdffbfff 64bit pref] whereas the failing card has none: pci 0000:02:00.0: [10ec:8168] type 0 class 0x000200 The driver is accessing region 2, hardcoded. So it expects it to be there pretty strongly... I've had a chat with Thomas here and he suggested to try the pci=nocrs boot option. It disables the use of ACPI for pci resource enumeration. Christian, please try to add the pci=nocrs option. You may do so 1) manually at boot when the grub menu with "Startup option" shows up 2) OR you can edit '/boot/grub/menu.lst' and add 'pci=nocrs' to the end of the 'kernel' line for the default entry (determined by the 0 base indexed 'default' configuration statement, usually just the first entry). Please check you kernel logs afterwards, they should contain one XID line per r8169 interface, like: r8169 0000:03:00.0: eth0: RTL8168evl/8111evl at 0xffffc9000060e000, 8c:89:a5:66:f8:80, XID 0c900800 IRQ 42 and the interface should be functionnal. If this works around the problem, it suggests a bug in the BIOS. Please provide the output of `dmidecode` and `acpidump` to help us get the problem fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c4 --- Comment #4 from Joey Lee <jlee@suse.com> 2012-03-23 16:03:46 UTC --- Please kindly also provide the following information for compare: + lspci -xxxnnvv + lspci -t Sometimes BIOS's POST fill-in wrong value to pci configuration area. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c5 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #5 from Christian Boltz <suse-beta@cboltz.de> 2012-03-26 21:35:10 CEST --- Created an attachment (id=483291) --> (http://bugzilla.novell.com/attachment.cgi?id=483291) tarball with the requested information This tarball contains the output of the following commands: without pci=nocrs: mkdir /tmp/bnc738547 lspci -xxxnnvv > /tmp/bnc738547/lspci-xxxnnvv lspci -t > /tmp/bnc738547/lspci-t dmidecode > /tmp/bnc738547/dmidecode acpidump > /tmp/bnc738547/acpidump old /var/log/messages rebooting with pci=nocrs: (the included "/var/log/messages" starts here) cat /proc/cmdline > /tmp/bnc738547/cmdline-nocrs lspci -xxxnnvv > /tmp/bnc738547/lspci-xxxnnvv-nocrs lspci -t > /tmp/bnc738547/lspci-t-nocrs echo "plugging in network cable..." | logger -t bnc738547 plugging in a network cable (still with pci=nocrs), then: lspci -xxxnnvv > /tmp/bnc738547/lspci-xxxnnvv-nocrs-with-cable lspci -t > /tmp/bnc738547/lspci-t-nocrs-with-cable cp /var/log/messages /tmp/bnc738547/ tar cjf /tmp/bnc738547.tar.bz2 /tmp/bnc738547/* -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c6 Joey Lee <jlee@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #6 from Joey Lee <jlee@suse.com> 2012-03-27 11:14:12 UTC --- I saw there have link up in your messages after applied pci=nocrs : Mar 27 04:48:48 linux kernel: [ 26.967008] r8169 0000:03:00.0: eth2: link up Mar 27 04:48:48 linux kernel: [ 26.967499] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready Does that mean 'pci=nocrs' can workaround this issue on your machine? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c7 Benjamin Poirier <bpoirier@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rjw@suse.com InfoProvider|suse-beta@cboltz.de |rjw@suse.com --- Comment #7 from Benjamin Poirier <bpoirier@suse.com> 2012-03-28 01:22:45 UTC --- Thank you for providing this information Christian. So with pci=nocrs there are now some resources, but the card still isn't working properly. 0000:02:00.0: [10ec:8168] type 0 class 0x000200 0000:02:00.0: reg 10: [io 0x0000-0x00ff] 0000:02:00.0: reg 18: [mem 0x00000000-0x00000fff 64bit] 0000:02:00.0: reg 20: [mem 0x00000000-0x00003fff 64bit pref] 0000:02:00.0: reg 30: [mem 0x00000000-0x0001ffff pref] 0000:02:00.0: supports D1 D2 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold 0000:02:00.0: PME# disabled 0000:00:04.0: PCI bridge to [bus 02-02] 0000:00:04.0: bridge window [io 0xb000-0xbfff] 0000:00:04.0: bridge window [mem 0xfde00000-0xfdefffff 64bit pref] [...] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded r8169 0000:02:00.0: Refused to change power state, currently in D3 r8169 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 r8169 0000:02:00.0: cache line size of 64 is not supported r8169 0000:02:00.0: (unregistered net_device): Mem-Wr-Inval unavailable r8169 0000:02:00.0: (unregistered net_device): unknown MAC, using family default r8169 0000:02:00.0: no MSI. Back to INTx. r8169 0000:02:00.0: eth0: RTL8168b/8111b at 0xffffc9000060e000, ff:ff:ff:ff:ff:ff, XID 9cf0f8ff IRQ 16 Both the mac and XID are read from pci region 2 for this card. In this case, the mac address is made up of only 1's and I'm willing to bet it's the same for the XID. 0x9cf0f8ff is the mask used in the driver when printing it. Unless I'm mistaken, unconnected addresses read out as 1's... Rafael, I have it on good authority that you're a pci geek ;) Could you please shed some light on what may be going on here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c8 --- Comment #8 from Thomas Renninger <trenn@novell.com> 2012-03-28 08:34:10 UTC --- If both pci=nocrs and pci=use_crs are failing to retrieve the correct resources..., I have no idea what is going on there. I expect this card has been explicitly added and was not installed when the system was bought? Is the latest BIOS installed? Possibly a PCI part is disabled via BIOS or another PCI related BIOS setting may cause this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c9 --- Comment #9 from Joey Lee <jlee@suse.com> 2012-03-29 04:55:41 UTC --- I didn't see the second realtek ethernet (02:00.0) in lspci-xxxnnvv log, that the first strange thing didn't see it. But, there have the following strange realtek ethernet (02:00.0) in lspci-xxxnnvv-nocrs: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: r8169 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Whole pci config area fill-in to 'ff' (11111111). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c10 --- Comment #10 from Joey Lee <jlee@suse.com> 2012-03-29 05:07:30 UTC --- Hi Christian, Could you please try the following testing ? + add "pci=earlydump" kernel paramter to /boot/grub/menu.lst, reboot system, then please attached /var/log/messages? Please boot with and without cable plug-in. + add "pci=earlydump,assign-busses,realloc" kernel paramter to /boot/grub/menu.lst, reboot system. Then, please attach 'lspci -vt' and 'lspci -xxxnnvv'. Another strange thing is the issue card' power state is in D3 when r8169 initial: Mar 27 04:48:45 linux kernel: [ 10.900388] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Mar 27 04:48:45 linux kernel: [ 10.912073] r8169 0000:02:00.0: Refused to change power state, currently in D3 <=== strange Mar 27 04:48:45 linux kernel: [ 10.912162] r8169 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 I have no idea for why it's in D3 state when system boot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c Joey Lee <jlee@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|rjw@suse.com |suse-beta@cboltz.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c11 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #11 from Christian Boltz <suse-beta@cboltz.de> 2012-04-16 22:19:13 CEST --- Created an attachment (id=486320) --> (http://bugzilla.novell.com/attachment.cgi?id=486320) tarball with information for comment #10 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c12 --- Comment #12 from Joey Lee <jlee@suse.com> 2012-04-23 17:13:52 UTC --- Created an attachment (id=487516) --> (http://bugzilla.novell.com/attachment.cgi?id=487516) bnc738547-highlight-comment11.txt The above is my simple summary for the log in comment#11 (In reply to comment #11)
Created an attachment (id=486320) --> (http://bugzilla.novell.com/attachment.cgi?id=486320) [details] tarball with information for comment #10
There have 5 times boot in the log in comment#11, all added 'pci=earlydump', means those pci register dump log is before kernel touch pci devices. I extract the 0000:02:00.0 pci device, it's must be extra NIC: The FIRST BOOT: Apr 16 20:41:45 linux kernel: [ 0.000000] pci 0000:02:00.0 config space: Apr 16 20:41:45 linux kernel: [ 0.000000] 00: ec 10 68 81 00 00 10 00 03 00 00 02 00 00 00 00 Apr 16 20:41:45 linux kernel: [ 0.000000] 10: 01 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 Apr 16 20:41:45 linux kernel: [ 0.000000] 20: 0c 00 00 00 ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:41:45 linux kernel: [ 0.000000] f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff The SECOND BOOT: Apr 16 20:47:24 linux kernel: [ 0.000000] pci 0000:02:00.0 config space: Apr 16 20:47:24 linux kernel: [ 0.000000] 00: ec 10 68 81 07 01 10 00 03 00 00 02 10 00 00 00 Apr 16 20:47:24 linux kernel: [ 0.000000] 10: 01 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 Apr 16 20:47:24 linux kernel: [ 0.000000] 20: 0c 00 00 00 00 00 00 00 00 00 00 00 ec 10 68 81 Apr 16 20:47:24 linux kernel: [ 0.000000] 30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 01 00 00 Apr 16 20:47:24 linux kernel: [ 0.000000] 40: 01 50 c3 ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 20:47:24 linux kernel: [ 0.000000] f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff The THIRD BOOT: Apr 16 20:52:21 linux kernel: [ 0.000000] pci 0000:02:00.0 config space: Apr 16 20:52:21 linux kernel: [ 0.000000] 00: ec 10 68 81 07 01 10 00 03 00 00 02 10 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] 10: 01 b8 00 00 00 00 00 00 04 b0 af fe 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] 20: 0c c0 ef fd 00 00 00 00 00 00 00 00 ec 10 68 81 Apr 16 20:52:21 linux kernel: [ 0.000000] 30: 00 00 ac fe 40 00 00 00 00 00 00 00 0a 01 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] 40: 01 50 c3 ff 08 00 00 00 00 00 00 00 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] 50: 05 70 80 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] 70: 10 ac 02 02 c0 8c 64 00 00 20 19 00 11 3c 07 00 Apr 16 20:52:21 linux kernel: [ 0.000000] 80: 40 00 11 10 00 00 00 00 00 00 00 00 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] 90: 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] a0: 00 00 00 00 00 00 00 00 00 00 00 00 11 cc 03 00 Apr 16 20:52:21 linux kernel: [ 0.000000] b0: 04 00 00 00 04 08 00 00 00 00 00 00 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] c0: 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 16 20:52:21 linux kernel: [ 0.000000] f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The FOURTH BOOT: NONE, yes, 0000:02:00.0 disappear, I am not sure the NIC is really in machine... The FIFTH BOOT: Apr 16 21:04:58 linux kernel: [ 0.000000] pci 0000:02:00.0 config space: Apr 16 21:04:58 linux kernel: [ 0.000000] 00: ec 10 68 81 00 00 10 00 03 00 00 02 00 00 00 00 Apr 16 21:04:58 linux kernel: [ 0.000000] 10: 01 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 Apr 16 21:04:58 linux kernel: [ 0.000000] 20: 0c 00 00 00 00 00 00 00 00 00 00 00 ec 10 68 81 Apr 16 21:04:58 linux kernel: [ 0.000000] 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00 Apr 16 21:04:58 linux kernel: [ 0.000000] 40: 01 50 c3 ff 08 00 00 00 00 00 00 00 00 00 00 00 Apr 16 21:04:58 linux kernel: [ 0.000000] 50: 05 70 80 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 16 21:04:58 linux kernel: [ 0.000000] 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Apr 16 21:04:58 linux kernel: [ 0.000000] 70: 10 ac 02 02 c0 8c 64 00 10 20 11 00 11 3c 07 00 Apr 16 21:04:58 linux kernel: [ 0.000000] 80: 00 00 11 10 00 00 00 00 00 00 00 00 00 00 00 00 Apr 16 21:04:58 linux kernel: [ 0.000000] 90: 00 00 00 00 10 00 00 00 ff ff ff ff ff ff ff ff Apr 16 21:04:58 linux kernel: [ 0.000000] a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 21:04:58 linux kernel: [ 0.000000] b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 21:04:58 linux kernel: [ 0.000000] c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 21:04:58 linux kernel: [ 0.000000] d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 21:04:58 linux kernel: [ 0.000000] e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Apr 16 21:04:58 linux kernel: [ 0.000000] f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Look at the above pci register dump of 0000:02:00.0 before kernel touch it, looks the ff write to pci register is not fully cover whole pci registers. It's random. Those information were return from BIOS, that means BIOS didn't do right job in BIOS post stage. Or the hardware actually have problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c13 Joey Lee <jlee@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |rjw@suse.com --- Comment #13 from Joey Lee <jlee@suse.com> 2012-04-23 17:17:26 UTC --- I agreed this is a hardware issue. Still need info to Rafael, need his comment on PCI power management side. Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c14 Rafael Wysocki <rjw@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|rjw@suse.com |suse-beta@cboltz.de --- Comment #14 from Rafael Wysocki <rjw@suse.com> 2012-04-25 22:23:40 UTC --- Is the /sys/devices/.../power/control file present for the affected device and if so, what's its contents? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c15 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #15 from Christian Boltz <suse-beta@cboltz.de> 2012-05-06 16:32:04 CEST --- To avoid I missed the correct device: # head -n1000 /sys/devices/*/power/control ==> /sys/devices/breakpoint/power/control <== auto ==> /sys/devices/cpu/power/control <== auto ==> /sys/devices/LNXSYSTM:00/power/control <== auto ==> /sys/devices/pci0000:00/power/control <== auto ==> /sys/devices/platform/power/control <== auto ==> /sys/devices/pnp0/power/control <== auto ==> /sys/devices/rapidio/power/control <== auto ==> /sys/devices/software/power/control <== auto ==> /sys/devices/tracepoint/power/control <== auto -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c16 Rafael Wysocki <rjw@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #16 from Rafael Wysocki <rjw@suse.com> 2012-05-08 21:56:04 UTC --- What happens if you change that setting to "on" for the affected device? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c17 --- Comment #17 from Benjamin Poirier <bpoirier@suse.com> 2012-07-30 19:50:19 UTC --- Christian, could you please try the experiment in comment 16? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c18 --- Comment #18 from Benjamin Poirier <bpoirier@suse.com> 2012-08-20 20:04:07 UTC --- Ping Christian, do you still experience this issue. If so, can you try the experiment in comment 16? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c19 --- Comment #19 from Christian Boltz <suse-beta@cboltz.de> 2012-08-20 22:36:34 CEST --- Sorry for the delay. This is a friend's machine, and he was too busy in the last months to test it. On the positive side, he promised to test it in the next days. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c20 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #20 from Christian Boltz <suse-beta@cboltz.de> 2012-10-14 22:55:31 CEST --- Created an attachment (id=509478) --> (http://bugzilla.novell.com/attachment.cgi?id=509478) /var/log/messages - setting /sys/devices/*/power/control to on (In reply to comment #16)
What happens if you change that setting to "on" for the affected device?
My friend finally tested this, and I don't see any changes in the log (search for "setting.*to on", those lines were added by logger). I'm attaching the log nevertheless in case I overlooked something. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738547 https://bugzilla.novell.com/show_bug.cgi?id=738547#c21 Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #21 from Jeff Mahoney <jeffm@suse.com> 2014-08-08 16:26:30 EDT --- This report is against openSUSE 12.1 which is no longer under maintenance. If you are able to reproduce it with openSUSE 13.1 or openSUSE Factory, please re-open and reset the the "Product" field to the appropriate release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com