Bug#490156: linux-image-2.6.24-1-686: SMP (2*hyperthreading xeon) machine wedged in loop saying 'BUG: soft lockup - CPU#N stuck for 11s'
maximilian attems wrote:
> On Thu, Jul 10, 2008 at 11:57:36AM +0100, Simon A. Boggis wrote:
>> Package: linux-image-2.6.24-1-686
>> Version: 2.6.24-7
>> Severity: critical
>> Justification: breaks the whole system
>
> overflated severity, learn to set them.
> one or two broken boxes doesn't mean the kernel is unusable on the
> whole. but everybody like to play selfish oh my bug is that important.
Whoa, steady, there's really no need for that! Isn't it evident that I
took a great deal of care in compiling and submitting my report?
There are a very limited number of choices for severity in reportbug and
I did my best to choose the most appropriate one according to the help
available. Unfortunately the help does not suggest how one ought to
modify the correct level according to whether one, two or a thousand
boxes are broken. The help does however say something along the lines of
"if you are not sure, don't worry, the maintainer will assign the
correct level for you". Since I gather from your sparkling sarcasm that
you seem to think you do know better, why not simply change the level
for me if you can, or politely suggest that I do so if you cannot?
If you believe that the help given in reportbug and the debian bug
reporting web page is unclear or wrong, it would be much more
constructive for you to take it up with the respective maintainers.
>
> try out newer 2.6.26-rc9 snapshots, see trunk apt lines
> -> http://wiki.debian.org/DebianKernel
>
Thank you, that's a constructive suggestion and more like the kind of
thing I hoped for.
As I said in my report, I'm not sure from reading other problem reports
whether the problem is one which has already been addressed, and I
appreciate some indication that it might be. I will therefore have a
look at a newer version as you suggest.
Thanks for taking the time to answer, and best wishes to you.
Simon
Reply to: