re weird bug

[Pyun YongHyeon]

On Fri, Oct 31, 2008 at 10:29:55AM +0100, Milan Obuch wrote:
 > On Friday 31 October 2008 02:11:25 Pyun YongHyeon wrote:
 > > On Thu, Oct 30, 2008 at 10:41:01PM +0100, Milan Obuch wrote:
 > >  > On Thursday 30 October 2008 11:26:56 Pyun YongHyeon wrote:
 > >  > > On Thu, Oct 30, 2008 at 08:29:35AM +0100, Milan Obuch wrote:
 > >  > >  > Hi,
 > >  > >  > yesterday I csup'ped my 8-current sources on my MSI Wind netbook
 > >  > >  > (again) and tried to build new kernel. There is again a problem
 > >  > >  > with re interface. It just does not work, with following
 > >  > >  >
 > >  > >  > re0: <RealTek 8101E/8102E/8102EL PCIe 10/100baseTX> port
 > >  > >  > 0xc000-0xc0ff mem 0xffd10000-0xffd10fff,0xffd00000-0xffd0ffff irq
 > >  > >  > 16 at device 0.0 on pci1 re0: Chip rev. 0x34800000
 > >  > >  > re0: MAC rev. 0x00200000
 > >  > >  > re0: PHY write failed
 > >  > >  > re0: PHY write failed
 > >  > >  > re0: MII without any phy!
 > >  > >  > device_attach: re0 attach returned 6
 > >  > >  >
 > 
 > [ snip ]
 > 
 > >  > >
 > >  > > That's known issue for newer RealTek PCIe controllers. Would you
 > >  > > please try the patch at the following URL?
 > >  > > http://people.freebsd.org/~yongari/re/re.ephy.patch.20081021
 > >  > >
 > >  > > Since it's not easy to reproduce this issue please make sure to
 > >  > > (cold and warm) reboot several times until you can put confidence
 > >  > > in the patch.
 > >  >
 > >  > I tried, but no change - with patch applied re still does not work
 > >  > unless I boot with verbose logging, no matter whether I boot cold or
 > >  > warm.
 > >
 > > Thanks for testing. If you look into patched if_re.c you can see a
 > > "#if 1" in function re_ephy_config(). How about changing it to
 > > "#if 0" to enable more aggresive reprogramming for EPHY register?
 > 
 > I tried. Again, no change - rlphy not working normally, but everything works 
 > when booting with verbose logging.
 > 

Hmm, I have no idea how verbosed booting can hide the issue.

 > If there is anything else I could test, let me know. Booting with verbose 
 > logging is acceptable for me for now, so do not feel any pressure from my 
 > side. I just like to test when something will be available for test.
 > 

I vaguely guess hardware was not properly initialized. How about
this one?
http://people.freebsd.org/~yongari/re/re.phy.patch.20081103

-- 
Regards,
Pyun YongHyeon