[driver-discuss] Driver trouble on Nevada...

[Kyle McDonald]

minskey guo wrote:
> Kyle McDonald 写道:
>> minskey guo wrote:
>>>
>>> Probably, it is a bug in e1000g driver. You can try to use early
>>> e1000g driver, or compile it by yourself, if s10 works for your
>>> hardware.
>> Why the e1000g driver?
>>
>> I'm pretty sure these blades only have bge interfaces. I'll have to 
>> double check.
>
> I thought you have an intel 8257x series like NIC. What's the
> hardware model ?  I know little about BCMxx hardware, Is the
> nic shared by OS driver and bmc firmware ?
>
Yes, the BMC and the Motherboard share the bge0 port.

The blade part is an HS20 model 8843 (I believe), the bge chip is 
BCM57xx (07 maybe?). I'm not sure what the BMC hardware is.

Thanks for thinking about this... It's driving me bonkers!

  -Kyle



> -minskey
>
>
>>
>>  -Kyle
>>
>>>
>>> -minskey
>>>
>>>
>>> Kyle McDonald 写道:
>>>> Hi,
>>>>
>>>> I have several types of IBM BladeCenter blades (mostly HS20 and LS20.)
>>>> The BladeCenter manages these blades through a BMC with IPMI, and
>>>> provides access to the serial console (ttyb) of the blades through the
>>>> Serial Over LAN (SOL) feature of the BMC.
>>>>
>>>> When I user Solaris10 on these blades, Access to the serial console 
>>>> is fine.
>>>> When I install SXCE (sNVb120 through 125 at least,) the console
>>>> connection is terminated (not gibberish - The BMC stops sending the 
>>>> SOL
>>>> data) shortly after the kernel boots, and the management module for 
>>>> the
>>>> BladeCenter reports that 'SOL is not ready' for the blade I'm using,
>>>> until I reboot it.
>>>>
>>>> I've played a bit with the BMC BIOS Settings, but I don't think that's
>>>> the problem since this works fine in s10.
>>>>
>>>> How can I collect more info, or narrow this problem down further so 
>>>> that
>>>> I can file a useful bug report?
>>>>
>>>> The output from booting SXCE sNV b125, as you can see it disconnects
>>>> after loading the sysidcfg info, previous builds used to disconnect
>>>> while 'Configuring /dev' if I recall.
>>>>
>>>>> SunOS Release 5.11 Version snv_125 64-bit
>>>>> Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
>>>>> Use is subject to license terms.
>>>>> NOTICE: Invalid iBFT table 0x1
>>>>> Configuring /dev
>>>>> WARNING: emlxs: ddi_modopen drv/fct failed: err 2
>>>>> Custom JumpStart
>>>>> Reading ZFS config: done.
>>>>> Setting up Java. Please wait...
>>>>> Serial console, reverting to text install
>>>>> Beginning system identification...
>>>>> Searching for configuration file(s)...
>>>>> Using sysid configuration file 
>>>>> 172.30.171.30:/ex/Inst/SysID/Def/sysidcfg
>>>>> Search complete.
>>>>> Discoveri
>>>>> system> console -T blade[3]
>>>>> SOL is not ready
>>>>> system>
>>>> The 'system>' prompt is the CLI for the mmanagement module. The 
>>>> 'console
>>>> -T blade[3]' command is me trying to reconnect to the SOL console.
>>>>
>>>> Anyone know of any changes in sNV that might have triggered this?
>>>> It's making all of these blades useless for OpenSolaris.
>>>>
>>>> -Kyle
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> driver-discuss mailing list
>>>> driver-discuss at opensolaris.org
>>>> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>>>>
>>>
>>> _______________________________________________
>>> driver-discuss mailing list
>>> driver-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>>
>>
>>
>
> _______________________________________________
> driver-discuss mailing list
> driver-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/driver-discuss