From owner-freebsd-net@FreeBSD.ORG Mon Jan 14 08:10:08 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63CC016A41A for ; Mon, 14 Jan 2008 08:10:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5FD5D13C44B for ; Mon, 14 Jan 2008 08:10:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0E8A2He023708 for ; Mon, 14 Jan 2008 08:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0E8A2ab023707; Mon, 14 Jan 2008 08:10:02 GMT (envelope-from gnats) Date: Mon, 14 Jan 2008 08:10:02 GMT Message-Id: <200801140810.m0E8A2ab023707@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: "Nagy Keve" Cc: Subject: Re: kern/112654: [pcn] Kernel panic upon if_pcn module load on a Netfinity 5000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Nagy Keve List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2008 08:10:08 -0000 The following reply was made to PR kern/112654; it has been noted by GNATS. From: "Nagy Keve" To: bug-followup@freebsd.org Cc: Subject: Re: kern/112654: [pcn] Kernel panic upon if_pcn module load on a Netfinity 5000 Date: Mon, 14 Jan 2008 09:06:42 +0100 An important update is that my earlier conclusion regarding the patch was f= lawed. The patch DOES WORK on RELENG_6, it gets rid of the kernel panic upon loadi= ng the module and it DOES FIND the appropriate cable media connected. I a= m still unable to explain what caused the "no carrier" issue during my ea= rlier attempts with this patch. So the concept is proved, this could be a proper fix if we can get the pcn = driver to use ns_phy instead of uk_phy. With the current patch both ns_ph= y and uk_phy shows up in dmesg, and I would rather see ns_phy only.