Date: Tue, 2 Oct 2007 11:41:17 +0800 From: "Kudo Chien" <ckchien@gmail.com> To: pyunyh@gmail.com Cc: freebsd-current@freebsd.org Subject: Re: msk watchdog timeout Message-ID: <8bebfc960710012041h205216ecl75d44e0c9ba69068@mail.gmail.com> In-Reply-To: <20071002004521.GH18658@cdnetworks.co.kr> References: <8bebfc960710010039q3ae744b9h71f785f6e3a4634d@mail.gmail.com> <20071001080058.GE18658@cdnetworks.co.kr> <8bebfc960710010707o4b7e9b2cif086e35b4f8f736d@mail.gmail.com> <20071002004521.GH18658@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
2007/10/2, Pyun YongHyeon <pyunyh@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. -- Best Regards, Kudo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8bebfc960710012041h205216ecl75d44e0c9ba69068>