kern/38234: Bugfix for Report No. 38172

[J.Karpinski%ape-net.com@localhost]

>Number:         38234
>Category:       kern
>Synopsis:       Bugfix for Report No. 38172
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 13 09:05:00 +0000 2008
>Originator:     JRK
>Release:        netbsd-4
>Organization:
A.P.E.
>Environment:
NetBSD SSP_FW_Client 4.0_STABLE NetBSD 4.0_STABLE (GEN_LAP_IPSEC) #0: Thu Mar  6
 11:19:40 CET 2008  admin@SSP_CLap:/cur_src/src/sys/arch/i386/compile/obj/GEN_LA
P_IPSEC i386
>Description:
I got the same Speed issue described in Report No. 38172.
After applying the provided patch and installing the new kernel,
the network interface configured for pppoe throws "re0: bad phy register" every 
second on the console as long as the network cable is 
inserted (unplugging the network cable stops the Spam).  

I hope this is the right way to report this, I dont know the proper way to 
reopen a ticket.


JRK


console output:

re0 at pci0 dev 11 function 0: RealTek 8139C+ 10/100BaseTX (rev. 0x20)
re0: interrupting at irq 5
re0: Ethernet address 00:90:0b:0b:39:5f
rlphy0 at re0 phy 0: Realtek internal PHY
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re1 at pci0 dev 12 function 0: RealTek 8139C+ 10/100BaseTX (rev. x20)
re1: interrupting at irq 12
re1: Ethernet address 00:90:0b:0b:39:5e
rlphy1 at re1 phy 0: Realtek internal PHY
rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re2 at pci0 dev 13 function 0: RealTek 8139C+ 10/100BaseTX (rev. x20)
re2: interrupting at irq 10
re2: Ethernet address 00:90:0b:0b:39:5d
rlphy2 at re2 phy 0: Realtek internal PHY
rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re3 at pci0 dev 14 function 0: RealTek 8139C+ 10/100BaseTX (rev. x20)
re3: interrupting at irq 11
re3: Ethernet address 00:90:0b:0b:39:5c
rlphy3 at re3 phy 0: Realtek internal PHY
rlphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
uhci0 at pci0 dev 16 function 0: VIA Technologies VT83C572 USB Controller (rev. 
0x80)
uhci0: interrupting at irq 5
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 16 function 1: VIA Technologies VT83C572 USB Controller (rev. 
0x80)
uhci1: interrupting at irq 12
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 16 function 2: VIA Technologies VT83C572 USB Controller (rev. 
0x80)
uhci2: interrupting at irq 10
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 16 function 3: VIA Technologies VT8237 EHCI USB Controller 
(rev. 0x82)
ehci0: interrupting at irq 11
ehci0: BIOS has given up ownership
ehci0: EHCI version 1.0
ehci0: companion controllers, 2 ports each: uhci0 uhci1 uhci2
usb3 at ehci0: USB revision 2.0
uhub3 at usb3
uhub3: VIA Technologies EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: 6 ports with 6 removable, self powered
pcib0 at pci0 dev 17 function 0
pcib0: VIA Technologies VT8235 (Apollo KT400) PCI-ISA Bridge (rev. 0x00)
viaide0 at pci0 dev 17 function 1
viaide0: VIA Technologies VT8235 ATA133 controller
viaide0: bus-master DMA support present
viaide0: primary channel configured to compatibility mode
viaide0: primary channel interrupting at irq 14
atabus0 at viaide0 channel 0
viaide0: secondary channel configured to compatibility mode
viaide0: secondary channel interrupting at irq 15
atabus1 at viaide0 channel 1
isa0 at pcib0
lpt0 at isa0 port 0x378-0x37b irq 7
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com0: console
pckbc0 at isa0 port 0x60-0x64
attimer0 at isa0 port 0x40-0x43: AT Timer
pcppi0 at isa0 port 0x61
pcppi0: children must have an explicit unit
midi0 at pcppi0: PC speaker (CPU-intensive output)
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff
pcppi0: attached to attimer0
isapnp0: no ISA Plug 'n Play devices found
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
Kernelized RAIDframe activated
IPsec: Initialized Security Association Processing.
wd0 at atabus0 drive 0: <CF CARD 2GB>
wd0: drive supports 1-sector PIO transfers, LBA addressing
wd0: 1935 MB, 3933 cyl, 16 head, 63 sec, 512 bytes/sect x 3964464 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2
wd0(viaide0:0:0): using PIO mode 4, DMA mode 2 (using DMA)
boot device: wd0
root on wd0e dumps on wd0b
root file system type: ffs
Wed Mar 12 15:43:54 CET 2008
Checking for botched superblock upgrades: done.
Starting file system checks:
/dev/rwd0e: file system is clean; not checking
/dev/rwd0f: file system is clean; not checking
Setting tty flags.
Installing ipsec manual keys/policies.
Enabling ipfilter.
Setting sysctl variables:
Starting network.
Hostname: FW
IPv6 mode: host
Configuring network interfaces: re1 re2 pppoe0.
Adding interface aliases:
pppoe0: connected to RGBC01-10k

re0: bad phy register

re0: bad phy register

Enabling pf firewall.
Building databases...
re0: bad phy register

wsdisplay0: screen 0 added (80x25, vt100 emulation)

wsdisplay0: screen 1 added (80x25, vt100 emulation)

wsdisplay0: screen 2 added (80x25, vt100 emulation)

wsdisplay0: screen 3 added (80x25, vt100 emulation)

wsdisplay0: screen 4 added (80x25, vt100 emulation)

encoding -> de
Starting syslogd.
Starting ifwatchd.
Mar 12 15:43:59 /usr/sbin/ifwatchd[308]: watching interface pppoe0 Installing 
NAT rules ... Mar 12 15:43:59 /usr/sbin/ifwatchd[247]: calling: /etc/ppp/ip-up 
pppoe0 /dev/null 9600 91.11.119.231 217.0.118.30
 0 entries flushed from NAT table
Mounting all filesystems...
re0: bad phy register

Clearing /tmp.
Creating a.out runtime link editor directory cache.
Checking quotas: done.
Starting virecover.
Starting local daemons:.
Updating motd.
re0: bad phy register

Starting sshd.
Starting inetd.
Starting cron.
Wed Mar 12 15:44:01 CET 2008
re0: bad phy register

re0: bad phy register

 NetBSD/i386 (FW) (console)  login: re0: bad phy register

re0: bad phy register
re0: bad phy register
re0: bad phy register
re0: bad phy register

ping re0: bad phy register

goore0: bad phy register

glere0: bad phy register

.de
PING google.de (72.14.221.104): 56 data bytes
re0: bad phy register

64 bytes from 72.14.221.104: icmp_seq=0 ttl=246 time=57.847 ms
re0: bad phy register

64 bytes from 72.14.221.104: icmp_seq=1 ttl=246 time=56.079 ms
re0: bad phy register

64 bytes from 72.14.221.104: icmp_seq=2 ttl=246 time=56.079 ms
re0: bad phy register
 

my ifconfig.pppoe0 :
> 
>       create
>       ! /sbin/ifconfig re0 up
>       ! /sbin/pppoectl -e re0 $int
>       ! /sbin/pppoectl $int myauthproto=pap 'myauthname=xxx' 
> 'myauthsecret=xxx'
>       0.0.0.0 0.0.0.1 up
> 

>How-To-Repeat:
configure a pppoe connection over a Realtek 8139C+ Network Interface.
Use a kernel compiled with the patch from Report No. 38172.  

startup with inserted network cable.
>Fix: