Re: msk watchdog timeout

From: Pyun YongHyeon <pyunyh_at_gmail.com>
Date: Tue, 2 Oct 2007 12:58:14 +0900
On Tue, Oct 02, 2007 at 11:41:17AM +0800, Kudo Chien wrote:
 > 2007/10/2, Pyun YongHyeon <pyunyh_at_gmail.com>:
 > >
 > > On Mon, Oct 01, 2007 at 10:07:34PM +0800, Kudo Chien wrote:
 > > > Hi,
 > > >
 > > > I've applied the patch. But it seems not solve the problem.
 > > > After applied patch, mskc0 boot message changes from 'mskc0: [ITHREAD]'
 > > to
 > > > 'mskc0: [FILTER]'.
 > > It just means it uses fast interrupt handler now. Previously you may
 > > have disabled it.(hw.msk.legacy_intr=1)
 > 
 > 
 > Oh I see.
 > 
 > > And one thing I forgot to provide before is that a line in boot message
 > > > "mskc0: <Marvell Yukon 88E8056 Gigabit Ethernet> port 0xa000-0xa0ff mem
 > > > 0xf1000000-0xf1003fff irq 16 at device 0.0 on pci3"
 > > >
 > > >
 > > > I'm not sure if it could be helpful. But if you need any infomation, I
 > > could
 > > > provide it.
 > > > Thanks for your help.
 > > >
 > > As I said I don't have this hardware to experiment so it would take
 > > long time to fix it. I'd like to know chaging PHY driver has any
 > > effect in your case. Edit /usr/src/sys/dev/mii/e1000phy.c with
 > > the following.
 > >
 > > Save and rebuild kernel. This makes ukphy(4) serve 88E1149 PHY.
 > > Do you still see the same error from msk(4) after above change?
 > 
 > 
 > Yes, the error message is the same after making ukphy(4) serve 88E1149 PHY.
 > Thanks for your help.
 > 

Thanks for testing. Would you sumbit a PR for the issue and assign
it to me? I'll let you know when I manage to find a clue.

-- 
Regards,
Pyun YongHyeon
Received on Tue Oct 02 2007 - 02:01:56 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:18 UTC