From pete@silver.he.iki.fi  Sun Jun  1 02:49:25 2003
Return-Path: <pete@silver.he.iki.fi>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 421C837B401
	for <FreeBSD-gnats-submit@freebsd.org>; Sun,  1 Jun 2003 02:49:25 -0700 (PDT)
Received: from silver.he.iki.fi (silver.he.iki.fi [193.64.42.241])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E691E43FEA
	for <FreeBSD-gnats-submit@freebsd.org>; Sun,  1 Jun 2003 02:48:03 -0700 (PDT)
	(envelope-from pete@silver.he.iki.fi)
Received: from silver.he.iki.fi (localhost.he.iki.fi [127.0.0.1])
	by silver.he.iki.fi (8.12.9/8.11.4) with ESMTP id h519m1k8003023
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 1 Jun 2003 12:48:01 +0300 (EEST)
	(envelope-from pete@silver.he.iki.fi)
Received: (from pete@localhost)
	by silver.he.iki.fi (8.12.9/8.12.5/Submit) id h519m0ZL003022;
	Sun, 1 Jun 2003 12:48:00 +0300 (EEST)
Message-Id: <200306010948.h519m0ZL003022@silver.he.iki.fi>
Date: Sun, 1 Jun 2003 12:48:00 +0300 (EEST)
From: Petri Helenius <pete@he.iki.fi>
Reply-To: Petri Helenius <pete@he.iki.fi>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: em driver does not work with mobile-chipset
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         52835
>Category:       i386
>Synopsis:       [em] em driver does not work with mobile-chipset
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    linimon
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jun 01 02:50:06 PDT 2003
>Closed-Date:    Sun Jun 18 21:18:09 GMT 2006
>Last-Modified:  Sun Jun 18 21:18:09 GMT 2006
>Originator:     Petri Helenius
>Release:        FreeBSD 5.1-BETA i386
>Organization:
>Environment:
>Description:
I installed 5.0-RELEASE on an X31 IBM laptop and em0 worked. (1.4.x driver) Then
I cvsupped -CURRENT two days ago and now the em0 probe only displays:
em0: <Intel(R) PRO/1000 Network Connection, Version - 1.5.31> port 0x8000-0x803f
mem 0xc0200000-0xc020ffff, 0xc0220000-0xc023ffff irq 11 at device 1.0 on pci2
em0: The EEPROM Checksum Is Not Valid
em0: Unable to initialize the hardware

The chip is supposedly Intel mobile GE, and the machine has Win XP as dual booth with FreeBSD.
>How-To-Repeat:
Update to latest -CURRENT with Intel Mobile Gigabit ethernet.

>Fix:
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-i386->pdeuskar 
Responsible-Changed-By: dwmalone 
Responsible-Changed-When: Sun Jun 8 02:53:58 PDT 2003 
Responsible-Changed-Why:  
em driver is pdeuskar's. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=52835 

From: Benjamin Howell <bhowell@iglou.com>
To: freebsd-gnats-submit@FreeBSD.org, pete@he.iki.fi
Cc:  
Subject: Re: i386/52835: em driver does not work with mobile-chipset
Date: Wed, 1 Oct 2003 23:30:14 -0400

 This problem only occurs if you compile with CardBus bridge support
 (yenta) -- device cbb.
 
 If both "device em" and "device cbb" are present, then the checksum is
 listed as invalid and the device fails to work properly.
 
 If "device em" is present and "device cbb" is NOT present, then the em
 driver works fine and does not display the checksum error.
 
 
 - Benjamin Howell

From: Petri Helenius <pete@he.iki.fi>
To: Benjamin Howell <bhowell@iglou.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: i386/52835: em driver does not work with mobile-chipset
Date: Thu, 02 Oct 2003 11:03:35 +0300

 Benjamin Howell wrote:
 
 >This problem only occurs if you compile with CardBus bridge support
 >(yenta) -- device cbb.
 >  
 >
 I can confirm that. It would be useful to have this though, because laptops
 generally have cardbus slots. Is there a workaround to get both?
 
 >If both "device em" and "device cbb" are present, then the checksum is
 >listed as invalid and the device fails to work properly.
 >
 >If "device em" is present and "device cbb" is NOT present, then the em
 >driver works fine and does not display the checksum error.
 >
 >  
 >
 Does this require changes to cbb or em driver to get them to co-exist?
 
 Pete
  
 

From: Benjamin Howell <bhowell@iglou.com>
To: freebsd-gnats-submit@FreeBSD.org, pete@he.iki.fi
Cc:  
Subject: Re: i386/52835: em driver does not work with mobile-chipset
Date: Thu, 2 Oct 2003 10:32:14 -0400

 On Thu, Oct 02, 2003 at 11:03:35AM +0300, Petri Helenius wrote:
 > Benjamin Howell wrote:
 > >This problem only occurs if you compile with CardBus bridge support
 > >(yenta) -- device cbb.
 >
 > I can confirm that. It would be useful to have this though, because laptops
 > generally have cardbus slots. Is there a workaround to get both?
 
 Indeed, I did not mean to imply disregarding that disregarding the
 problem was the best thing to do. It was meant to add some further
 insight as to where the problem lies. I am not a committer, I just
 wished to add some information to the problem report.
 
 > >If both "device em" and "device cbb" are present, then the checksum is
 > >listed as invalid and the device fails to work properly.
 > >
 > >If "device em" is present and "device cbb" is NOT present, then the em
 > >driver works fine and does not display the checksum error.
 >
 > Does this require changes to cbb or em driver to get them to co-exist?
 
 It very well may. I have been attempting to determine which change
 introduced the problem over the past few days and what is causing it.
 There were significant changes to both the cbb driver and the em driver
 between 5.0-RELEASE and 5.1-RELEASE. I am inclined to believe it is a
 change in the cbb driver that broke if_em on mobile chipsets/Thinkpads.
 
 
 - Benjamin Howell

From: Petri Helenius <pete@he.iki.fi>
To: Benjamin Howell <bhowell@iglou.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: i386/52835: em driver does not work with mobile-chipset
Date: Fri, 03 Oct 2003 22:21:44 +0300

 Benjamin Howell wrote:
 
 >It very well may. I have been attempting to determine which change
 >introduced the problem over the past few days and what is causing it.
 >There were significant changes to both the cbb driver and the em driver
 >between 5.0-RELEASE and 5.1-RELEASE. I am inclined to believe it is a
 >change in the cbb driver that broke if_em on mobile chipsets/Thinkpads.
 >
 >  
 >
 I can confirm this because taking the old em driver (as a loadable 
 module) from a time when
 it worked does not resolve the issue.
 
 Pete
 
 

From: Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw>
To: freebsd-gnats-submit@FreeBSD.org
Cc: pete@he.iki.fi
Subject: Re: i386/52835: em driver does not work with mobile-chipset
Date: Wed, 14 Jan 2004 18:42:24 +0800 (CST)

 I guess this bug may not be directly related to the em driver. On my
 Thinkpad T40, 5.1-RELEASE/5.2-RELEASE kernel always panics unless I set
 hw.pci.allow_unsupported_io_range=1 in /boot/loader.conf.
 
 Perhaps you would like to give that tunable a try.
 
 >Benjamin Howell wrote:
 >
 > >It very well may. I have been attempting to determine which change
 > >introduced the problem over the past few days and what is causing it.
 > >There were significant changes to both the cbb driver and the em driver
 > >between 5.0-RELEASE and 5.1-RELEASE. I am inclined to believe it is a
 > >change in the cbb driver that broke if_em on mobile chipsets/Thinkpads.
 > >
 > >
 > >
 > I can confirm this because taking the old em driver (as a loadable
 > module) from a time when
 > it worked does not resolve the issue.
 >
 > Pete
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Wed Apr 5 00:06:21 UTC 2006 
State-Changed-Why:  
Is this still a problem with recent versions of FreeBSD? 


Responsible-Changed-From-To: pdeuskar->linimon 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Wed Apr 5 00:06:21 UTC 2006 
Responsible-Changed-Why:  
Reset PR assigned to inactive committer who has not responded to email. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=52835 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Sun Jun 18 21:17:47 UTC 2006 
State-Changed-Why:  
Feedback timeout (> 2 months). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=52835 
>Unformatted:
