Hi Aubrey,
This is because the device id of 0x10be is changed to 0x10f5 since
e1000g Ver 5.2.8 (CR*6687947.*).
So this is not a bug of e1000g.
Because of some reasons Intel has decided to retire id 10be entirely and
0x10f5 is the correct one.
But some systems did go out into the world with the 10be device id.
E1000g driver since 5.2.8 will not work on this chip 0x10be.
As Intel's suggestion, the right thing to do is upgrading the NVM image.
Milan,
Thank you for forwarding this mail.
Thanks
Chenlu
On 09/18/08 00:57, Milan Jurik wrote:
Hi Ted, hi Chenlu,
in Opensolaris community there are new and new reports that in last
e1000g builds there is something wrong. See attached and
opensolaris-discuss@ and driver-discuss@
Best regards,
Milan
------------------------------------------------------------------------
------------------------------------------------------------------------
Subject:
Re: [indiana-discuss] e1000g0 disappear after update to B97(e1000 Ver
5.2.11 bug?)
From:
Al Slater <[EMAIL PROTECTED]>
Date:
Wed, 17 Sep 2008 09:52:43 +0100
To:
Aubrey Li <[EMAIL PROTECTED]>
To:
Aubrey Li <[EMAIL PROTECTED]>
CC:
Indiana Discuss <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aubrey Li wrote:
My network works okay under b95 but it doesn't work after update to B97
<snip>
The interesting is, when I copied the driver (e1000g) from b95 to b97, it works.
So I guess the driver is the root cause.
# modinfo | grep e1000g <================B95
167 fffffffff7e5d000 2f7e8 223 1 e1000g (Intel PRO/1000 Ethernet 5.2.6)
# modinfo | grep e1000g <================B97
157 fffffffff7d86000 32f88 223 1 e1000g (Intel PRO/1000 Ethernet 5.2.11)
Similarly I upgraded a v880 (sparc) box last week from sxce b82 to sxce
96 and had problems with the e1000g interfaces; they would stop working
under NFS load. My solution was the same as yours (restore the previous
drivers).
It looks like a regression has been introduced in b96 (and still present
in b97)
- --
Al Slater
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkjQxVsACgkQz4fTOFL/EDasxACghxKHtjR7th/CNCLrxgHWnsVw
jpgAn3NWnsNtGoo96PI12jlhXl/podo5
=HFxL
-----END PGP SIGNATURE-----
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
------------------------------------------------------------------------
------------------------------------------------------------------------
Subject:
[indiana-discuss] e1000g0 disappear after update to B97(e1000 Ver
5.2.11 bug?)
From:
Aubrey Li <[EMAIL PROTECTED]>
Date:
Wed, 17 Sep 2008 11:10:29 +0800
To:
Indiana Discuss <[email protected]>
To:
Indiana Discuss <[email protected]>
My network works okay under b95 but it doesn't work after update to B97
On B95:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS>
mtu 1500 index 2
inet 10.239.12.36 netmask ffffff00 broadcast 10.239.12.255
ether 0:13:20:f6:a3:af
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
# modinfo | grep e1000g
167 fffffffff7e5d000 2f7e8 223 1 e1000g (Intel PRO/1000 Ethernet 5.2.6)
On B97:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
# ifconfig e1000g0 plumb
ifconfig: cannot open link "e1000g0": No such device or address
# modinfo | grep e1000g
157 fffffffff7d86000 32f88 223 1 e1000g (Intel PRO/1000 Ethernet 5.2.11)
# prtconf -vp
----snip----
Node 0x000008
assigned-addresses:
8200c810.00000000.90500000.00000000.00020000.8200c814.00000000.90520000.00000000.00001000.8100c818.00000000.000020e0.0000000
0.00000020
reg:
0000c800.00000000.00000000.00000000.00000000.0200c810.00000000.00000000.00000000.00020000.0200c814.00000000.00000000.00000000.00001000.0100
c818.00000000.00000000.00000000.00000020
compatible: 'pci8086,10be.8086.0.3' +
'pci8086,10be.8086.0' + 'pci8086,0' + 'pci8086,10be.3' +
'pci8086,10be' + 'pciclass,020000' + 'pciclass,020
0'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00008086
subsystem-id: 00000000
unit-address: '19'
class-code: 00020000
revision-id: 00000003
vendor-id: 00008086
device-id: 000010be
name: 'pci8086,0
----snip----
# cat /etc/driver_aliases | grep e1000g
e1000g "pci8086,10be"
# rem_drv e1000g
# add_drv -i "pci8086,10be" e1000g
devfsadm: driver failed to attach: e1000g
Warning: Driver (e1000g) successfully added to system but failed to attachlsls
The interesting is, when I copied the driver (e1000g) from b95 to b97, it works.
So I guess the driver is the root cause.
# modinfo | grep e1000g <================B95
167 fffffffff7e5d000 2f7e8 223 1 e1000g (Intel PRO/1000 Ethernet 5.2.6)
# modinfo | grep e1000g <================B97
157 fffffffff7d86000 32f88 223 1 e1000g (Intel PRO/1000 Ethernet 5.2.11)
Thanks,
-Aubrey
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
