[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#704767: linux-image-2.6.32-5-amd64: kernel crashes when task block for more than 120 seconds



On Fri, Apr 5, 2013 at 4:55 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> Control: reopen -1
> Control: retitle -1 Kernel soft-lockup when running doxygen
>
> On Fri, Apr 05, 2013 at 03:16:06PM -0400, Olivier Diotte wrote:
>> Hi Ben,
>>
>> I am pretty sure that running doxygen (high load) is related to this
>> lockup, but based on your comment, maybe I am wrong.
>
> So you're actually reporting the soft-lockup, not the response to it.
>
Hum, seems like I reported this bug really messily. I am not so
familiar with kernel lockup terminology.
The computer locks up and it is most likely a software problem, so I
suppose the correct term would be soft-lockup, yes.

> [...]
>> root@Debianosaur:~# sysctl -a | grep lockup
>> kernel.softlockup_panic = 0
>> kernel.softlockup_thresh = 60
>>
>> I don't remember ever changing this parameter, so I assume
>> softlockup_panic was never enabled.
>
> Indeed, this is not enabled by default as an uninterruptible sleep
> for 120 seconds is sometimes OK.
>
> [...]
>> > Here is an example of what appears in kern.log when the system crashes:
> [...]
>
> The thing is, the kernel doesn't write to kern.log; the syslog daemon
> does.  If you get a soft-lockup message in kern.log then it proves
> the system was still somewhat responsive.
>
Hum, I tried to correlate the lockup with the logs, but maybe this
thing gets written before or even is unrelated to the lockup.
There also seems be a few issues with the WiFi USB dongle as can be
seen in the kernel log output from my bug report, but I remember
seeing something that looked like crashes also. I will look into this
monday when I have access to the machine.

> Please send the contents of /proc/meminfo.
>
Yes, I suppose a filled memory could be related. I will try to get the
contents of this file, but I am not sure if that will be possible if
the system is locked up (magic keys don't seem to work either, though
I will confirm that monday).

> Also, what filesystem and storage device were you using for the
> doxygen source and output files?
>
Both are in my /home which is an ext4 filesystem, / is also ext4 and
so is /boot if I decided to make a separate partition for the latter
on this system.

I haven't confirmed this yet, but I am pretty sure the disk is a
conventional rotational SATA drive.

> Ben.
>
> --
> Ben Hutchings
> We get into the habit of living before acquiring the habit of thinking.
>                                                               - Albert Camus

Olivier


Reply to: