Bug 9387

Summary: ipxe booted install fails to establish networking with r8169 driven network card.
Product: Mageia Reporter: marcin kowalski <yoshi314>
Component: InstallerAssignee: Thomas Backlund <tmb>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: dvgevers, thierry.vignaud
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description marcin kowalski 2013-03-14 14:57:29 CET 
Description of problem:

I boot mageia's installer kernel+initrd through ipxe. The process works fine until i have to setup the network with DHCP, it stalls indefinitely trying to acquire ip address.

This happens on Dell Vostro 320 AIO computer. Any other distribution i tried booting through ipxe seems to work with the network card correctly (tested Centos, debian, fedora, opensuse, arch linux). Tested distributions have kernels ranging from 2.6.32 to current.

The installation image works fine under qemu or on other hardware.

Version-Release number of selected component (if applicable):

Latest available kernel+initrd of mageia from 'cauldron' subdir on mirrors. Tested numerous times during mageia 3's development, so kernel version changed with time.

How reproducible:
Attempt booting through ipxe on Vostro 320, observe dhcp stall. Static configuration also stalls the installer, and makes it impossible to proceed with "Network is unreachable".

Attempt booting on non r8169 machine, installation proceeds through network configuration without issues, regardless of setup method.

Steps to Reproduce:
1. Obtain Dell Vostro 320 (or possibly another machine with r8169 network card)
2. Attempt booting kernel + initrd over PXE
3. installer cannot negotiate ip address over dhcp

ipxe configuration is available here : https://raw.github.com/yoshi314/multi-live-usb-configs/master/pxe/menu

lspci : 
====================================================================================================================
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 01)
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
01:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. Device 3401
01:00.1 Mass storage controller: VIA Technologies, Inc. Device 401a
01:00.2 SD Host controller: VIA Technologies, Inc. Device 401b
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
====================================================================================================================

lspci -vv (only the network device)
====================================================================================================================
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
	Subsystem: Dell Device 02f5
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 42
	Region 0: I/O ports at e800 [size=256]
	Region 2: Memory at fdfff000 (64-bit, prefetchable) [size=4K]
	Region 4: Memory at fdff8000 (64-bit, prefetchable) [size=16K]
	Expansion ROM at febe0000 [disabled] [size=128K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee0300c  Data: 4169
	Capabilities: [70] Express (v2) Endpoint, MSI 01
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 4096 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB
	Capabilities: [ac] MSI-X: Enable- Count=4 Masked-
		Vector table: BAR=4 offset=00000000
		PBA: BAR=4 offset=00000800
	Capabilities: [cc] Vital Product Data
		Unknown small resource type 00, will not decode more.
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [140 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Capabilities: [160 v1] Device Serial Number 07-00-00-00-68-4c-e0-00
	Kernel driver in use: r8169
	Kernel modules: r8169
====================================================================================================================

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-03-15 01:48:56 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => tmb

Comment 1 Thierry Vignaud 2013-03-15 06:37:25 CET 
What's displayed on tty3 & tty4?

Keywords: (none) => NEEDINFO

Comment 2 marcin kowalski 2013-03-18 14:43:04 CET 
after selecting DHCP in installer, there is nothing on the screen for at least a minute.

tty4 has usual messages indicating module r8169 loading and starting up the hardware.

after that minute the "Sending DHCP request" message appears on tty1, tty3 shows : 

DHCP: sending DISCOVER
<sleep>

and that's it for tty3.

tty4 mentions "unable to load firmware patch rtl_nic/rtl8168d-1.fw (-2)" , followed by link down and link up message.

If i wait long enough, DHCP will eventually failm sometimes. Similarily static address config will wait for quite a while, eventually declaring network not responding/available.

Rebooting into any other system makes the card work instantly.
Comment 3 marcin kowalski 2013-03-18 14:43:28 CET 
Is there a way to open a shell in the installer environment so that i can capture the system logs ?
Comment 4 marcin kowalski 2013-03-18 14:57:20 CET 
one more thing, with 3.8.3-desktop-1.mgs3 kernel in the installation image, the usb keyboard no longer works  - i have error about module hid_generic not being able to load.  keyboard works fine in bios/ipxe.

i have to use ps/2 keyboard.
Comment 5 Dick Gevers 2014-12-02 16:40:33 CET 
The 'NEEDINFO' label is outdated.

@tmb and/or tv: anything to be done? old? relevant for M5?

thanks for reviewing it...

Keywords: NEEDINFO => (none)
CC: (none) => dvgevers

Comment 6 Thierry Vignaud 2014-12-02 17:20:09 CET 
Probably a missing firmware.
He should try using boot-nonfree.iso instead of boot.iso
We should really warn about missing firmwares in stage1 and advertize using boot-nonfree.iso in such cases
Comment 7 Thierry Vignaud 2016-06-17 12:43:54 CEST 
Is this still valid?

Keywords: (none) => NEEDINFO

Comment 8 Thierry Vignaud 2016-06-18 15:12:11 CEST 
The real issue is tracked in 9193

*** This bug has been marked as a duplicate of bug 9193 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE