Date: Fri, 01 Nov 2019 06:26:28 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239352] kernel panic - cause as yet undetermined Message-ID: <bug-239352-227-k7U8SRL9R4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239352-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239352-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #11 from Ronald F. Guilmette <rfg-freebsd@tristatelogic.com> --- Is anybody ever going to fix this? I am frankly kind of shocked that apparently there is no manpower available to even fix kernel panics. I've already posted all of the information that was requested of me, twice. I've had three or four more kernel panics since then, and the only reason that I haven't posted that additional info is that it is starting to seem like an utter waste of my time to do so. Is it? Time was when kernel panics were treated like minor national emergencies. I guess not so much these day. A suggestion: If nobody is going to fix the kernel bugs that already exist, some or all of which may possibly have security implications, then perhaps it would be best to freeze all further kernel development, thereby at least insuring that the probem won't be made any worse than it already is. Don't get me wrong. New kernel features are great and always appreciated... at least right up until the moment when the console suddently goes black. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239352-227-k7U8SRL9R4>