From: "=?ISO-8859-2?Q?Pawe=B3_Ma=B3achowski?=" <pawmal@unia.3lo.lublin.pl> To: Ian Dowse <iedowse@maths.tcd.ie>, freebsd-bugs@FreeBSD.org Subject: Re: kern/42260: 4.6-STABLE kernel panic, fxp related Message-ID: <20020903221718Z2129491-22726%2B13@mx1.lublin.pl> In-Reply-To: <200209031622.aa49142@salmon.maths.tcd.ie> References: Your message of "Tue, 03 Sep 2002 06:40:04 PDT." <200209031340.g83De4dj012795@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3 Sep 02, at 16:22, Ian Dowse wrote: > > So, it looks as if the problem was introduced beetween > > 2002.08.09 00:00 and 2002.08.10 12:35. > > > > This could by interesting: > > Edit src/sys/dev/fxp/if_fxp.c > > Add delta 1.110.2.24 2002.08.09.02.04.20 luigi > > Edit src/sys/kern/uipc_mbuf.c > > Add delta 1.51.2.17 2002.08.09.02.11.08 luigi > > Add delta 1.51.2.18 2002.08.10.12.34.31 iedowse > > Could you try using the latest 4.6-STABLE source, but with the old > version of if_fxp.c? Grab it from cvsweb at Well, I cvsupped RELENG_4 and but I cannot compile it. (/usr/src/sys/netinet/tcp_input.c #ifdefs ;)) But let's go back to this PR. Todays RELENG_4, 4.7-PRERELASE with older version of if_fxp.c (1.110.2.23) looks stable for me. I'm happy. What now? Problem is specific only to one combination of my machines. I have no idea, how this combinaction could affect the newer fxp driver and cause a kernel panic... PM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020903221718Z2129491-22726%2B13>