[Bug 212460] kernels panic on boot

bugzilla at redhat.com bugzilla at redhat.com
Fri Apr 4 17:49:36 UTC 2008


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: kernels panic on boot


https://bugzilla.redhat.com/show_bug.cgi?id=212460


kb6ql at arrl.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Status Whiteboard| bzcl34nup                  |bzcl34nup




------- Additional Comments From kb6ql at arrl.net  2008-04-04 13:49 EST -------
i suppose that all of us who were affected by this bug have long since moved on
to newer releases of fedora, so it seems appropriate to close it.

however, what i think is missing here is the most important part of fixing a bug
-- even if you aren't going to.  and that is finding how something so
fundamental and so completely disastrous happened in the first place, AND
putting appropriate solutions in place to ensure that it can't happen again.

how could such a fundamental problem end up happening?  how could testing miss
it?  WAS it tested, or did someone bypass normal quality procedures?  HOW do we
be sure that it can't happen again?  that's pretty basic root cuase analysis,
you know.

frankly, i think that was the most important issue in this bug.  and it appears
to have been completely dropped on the floor.

i've worked waaay too much time in organizations which are swamped in bug
repor5ts.  the process of ignoring a bug, hoping that it will go away, and
waiting till it's old, then closing it, is symptomatic of organizations which
end up having it come back again.  it's not symptomatic of organizations which
end up providing high quality systems.

i'm rather disappointed that that happened to this bug.  and particularly
disappointed that it is being allowed to happen again.


-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the fedora-triage-list mailing list