Hi Stuart, Remove the following line: e1000g "pci8086,1011" >From /etc/driver_aliases
Intel screwed up and made there device ID the same for both there GbE cards and there WiFi chipsets. When the system comes up it tries to attach the e1000g driver which of course would fail as its not that card. The driver did not check for this condition (prob did not think of this at the time of coding it) and thus we had the panic. On http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/io/e1000g/e1000g_main.c#562 We should be checking that devi_node is valid before setting the structure member priv_devi_node of Adapter else Adapter->priv_devi_node should remain NULL. The problem has been fixed by Kerry Shu from Sun so thanks to Kerry is due ! Here is the Bug report: http://bugs.opensolaris.org/view_bug.do?bug_id=6816786 Hopeful this fix goes into the next build from Kerry ASAP ! Hope this extra info helps. Best Regards, Edward O'Callaghan. >> >From Linux so it looks like I indeed have a e1000g >> NIC. Are you sure >> you lads have the exact same trace? > > Edward, > > No I'm not sure and I don't know how to trap the > trace as I'm basically a user who programs a bit > in C and Fortran. ?However, I was able to install > to my T43p today by adding the following to the > Grub boot entry for the snv_109 DVD: > > -B disable-e1000g=true -kv > > The install went OK after that (no panic). ?The > notebook does NOT have an e1000g interface > but rather an iwi interface that many versions > of Solaris 10/Nevada try to bind e1000g to. > > The relevant output of scanpci -v for the iwi interface: > > pci bus 0x000b cardnum 0x02 function 0x00: vendor 0x8086 device 0x4224 > ?Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection > ?CardVendor 0x8086 card 0x1010 (Intel Corporation, Card unknown) > ?STATUS ? ?0x0290 ?COMMAND 0x0006 > ?CLASS ? ? 0x02 0x80 0x00 ?REVISION 0x05 > ?BIST ? ? ?0x00 ?HEADER 0x00 ?LATENCY 0x40 ?CACHE 0x08 > ?BASE0 ? ? 0xb4001000 SIZE 4096 ?MEM > ?BASEROM ? 0x00000000 ?addr 0x00000000 > ?MAX_LAT ? 0x18 ?MIN_GNT 0x03 ?INT_PIN 0x01 ?INT_LINE 0x0b > > The notebook has a Broadcom gigE interface: > > pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x14e4 device 0x167d > ?Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express > ?CardVendor 0x1014 card 0x0577 (IBM, ThinkPad Z60t) > ?STATUS ? ?0x0010 ?COMMAND 0x0046 > ?CLASS ? ? 0x02 0x00 0x00 ?REVISION 0x11 > ?BIST ? ? ?0x00 ?HEADER 0x00 ?LATENCY 0x00 ?CACHE 0x08 > ?BASE0 ? ? 0xb0200000 SIZE 65536 ?MEM > ?BASEROM ? 0x00000000 ?addr 0x00000000 > ?MAX_LAT ? 0x00 ?MIN_GNT 0x00 ?INT_PIN 0x01 ?INT_LINE 0x0b > > I see a lurking problem as /etc/path_to_inst now has: > > "/pci at 0,0/pci8086,2448 at 1e/pci8086,1010 at 2" 0 "iwi" > "/pci at 0,0/pci8086,2448 at 1e/pci8086,1010 at 2" 0 "e1000g" > > The e1000g entry is incorrect. ?There are two entries in > /etc/driver_aliases that might cause the issue on my > IBM/Lenovo T43p (and other similar vintage Lenovo > machines with iwi): > > [t43p : /etc : 21 ] grep e1000g driver_aliases | grep 1010 > e1000g "pci8086,1010" > [t43p : /etc : 22 ] grep iwi driver_aliases | grep 1010 > iwi "pci8086,4224.8086.1010" > > Only the second line is correct for my T43p. > > Stuart > -- > This message posted from opensolaris.org > _______________________________________________ > laptop-discuss mailing list > laptop-discuss at opensolaris.org > -- All Documents adhered to the ISO/IEC 26300 standard file format for electronic office documents, such as spreadsheets, charts, presentations and word processing documents from this email address. The author does not take responsibility of the recipients inability to read international standards and who use proprietary products such as MS Office. See: http://www.openoffice.org/ Edward O'Callaghan. -- http://fedoraproject.org/wiki/EdwardOcallaghan http://moonshine.opn4.org/ http://www.pcbsd.org/
