mii related fallout

So there was some fallout from my mii push. Elxl devices had a nasty panic, which I fixed in time for build 119. Some older i82557 (iprb) devices had problems as well. The push for this fix went into build 120. To everyone affected, please accept my apologies. Build 120 should be stable for these devices.

Comments

Anonymous said…
I've noticed another "fall out" when I upgraded to snv_126. the pci8086:10f0 was stolen from the iprb driver by e1000g.

Someone at intel thought it would be cool to have

pci8086:10f0 EtherExpress PRO/100+ Dual Port Adapter

and

pciex8086:10f0 82578DC Gigabit Network Connection

could you please get pci8086:10f0 back to iprb in /etc/driver_aliases?

Thanks
November 24, 2009 at 9:28 AM
Unknown said…
I'll look into this... it certainly sounds like an unfortunate bug. I bet the problem is conflicting subsystem ids vs. vendor ids. Unfortunately, the two numbering spaces are supposed to be distinct, but Solaris treats them as a single space (per IEEE 1275, which is mis-specified, IMO.)
November 24, 2009 at 10:00 AM
Anonymous said…
In my driver_aliases I have changed the lines to

e1000g "pciex8086,10f0"
iprb "pci8086,10f0"

you sound as if this is unsupported.

So the main problem is that "Solaris treats them as a single space"

If you can get yourself a 82578DC I could supply a PRO/100+ Dual Port so that you can plug both ids into a single machine and see which driver gets loaded.
November 25, 2009 at 1:11 AM
Post a Comment

Popular posts from this blog

An important milestone

Yesterday, with very little fanfare, illumos passed an important milestone. This milestone was the integration of  195 Need replacement for nfs/lockd+klm This is work that I originally tasked Gordon Ross and Dan Kruchinin to work while we were colleagues at  Nexenta .  Gordon started the work, picking up bits from FreeBSD as a starting point and gluing it to the illumos entry points.  Dan continued with it, and fleshed out a lot of the skeleton that Gordon had started.  It was subsequently picked up by the engineers at Delphix , and -- after some important bug fixing work was completed -- was integrated into their product quite some time ago -- reportedly its been stable since December in their product. The reason this is such an important milestone, is two fold: First, this represents a substantial collaborative effort, involving contributions from parties across several organizational boundaries.  The level of collaboration achieved here is a win for the greater good of th
Read more

GNU grep - A Cautionary Tale About GPLv3

My company, DEY Storage Systems , is in the process of creating a new product around the illumos operating system.  As you might imagine, this product includes a variety of open and proprietary source code.  The product itself is not delivered as a separate executable, but as a complete product.  We don't permit our customers to crack it open, both from the sense of protecting our IP, but also to protect our support and release engineering organizations -- our software releases consist only of a single file and we don't supply tools or source for other parties to modify that file. One of the pieces that we wanted to integrate into the tree is an excellent little piece of software called Zookeeper , produced by the Apache organization.  Like illumos, Zookeeper has a nice non-viral copyleft license, which makes it nice for integration into our product. However, I discovered that as part of our integration, one of my engineers had decided to integrate GNU grep.  Why? Becaus
Read more

The Hand May Be Forced

Well, as you may have read , Oracle has decided that at some point very soon, we're going to lose normal regular access to the source code for OS/Net. (I.e. the Solaris kernel and supporting programs.) While I would have vastly preferred for Illumos to have a cooperative and collaborative relationship with Oracle , it appears that Oracle doesn't value this. In fact, the exact words were from the management at Oracle were as follows: Solaris is not something we outsource to others, it is not the assembly of someone else’s technology, and it is not a sustaining-only product. While I understand the need to own the technology, there are few things that could be stated that show a stronger NIH attitude than this. Its unlikely that there will ever be a way for Oracle and the greater community to have a collaborative relationship. This is a dark day for OpenSolaris -- its effectively dead now. (Its parent, Solaris, lives on however.) How unfortunate. For Oracle that is. Because
Read more