> I put in the workarounds referenced at > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6432894
Warning: Rant ahead. This is probably not the right place to bring it up, but this sort of bug is a demonstration of one of the WORST ways to run a bug reporting system. Let's go through a couple of issues: State: 11-Closed:Duplicate -- Ok, I understand that bugs with the same underlying cause can have different reported symptoms, so let's see if my bug matches up. Keywords: boston-reviewed | boston-rr-doc | boston-waiver-approved | e1000g | seabos-res-plan | seabos-rp-fix-s10u3 | seabos-sqo-reviewed | seattle-rr-doc | seattle-waiver-list -- Other than "e1000g", all of the keywords appear to be documenting the workflow of moving this bugfix into Solaris, rather than OpenSolaris, and certainly nothing that would match any sane keyword search for a problem I'm having. Duplicate of: 6453554 -- Unfortunately, that bug is not available at bugs.opensolaris.org, so I have no idea if the problem I'm seeing is a duplicate of this bug. Introduced in: solaris_nevada -- Wow, that's a very large place to start looking for the bug. I guess the duplicate-of would probably narrow this down. Commit to Fix, Fixed In, Release Fixed, all blank. -- So it's closed as a duplicate of a bug that I can only assume was fixed somewhere. Related bugs: 6428335 , 6450683 , 6453554 , 6458708 -- While they might be related in some code sense, two of the four involve kernel panics (on hardware codenamed boston), one is a placeholder bug to replace the older IPGE driver with e1000g, and the other is not available on bugs.opensolaris.org And finally, the crowning achievement of bug clarity: Description: See Comments -- Is there somewhere else I'm supposed to be looking? Does this mean figure out what mercurial changeset corresponded to this bugfix and look at the source comments? </rant> --Joe _______________________________________________ networking-discuss mailing list [email protected]
