Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1
Hi,
On 11/24/18 2:19 AM, Cesare Leonardi wrote:
>
> On Sat, 24 Nov 2018 01:08:56 +0100 Hans van Kranenburg
> <hans@knorrie.org> wrote:
>> You didn't share any part of your logging. Can you share a part of dmesg
>> logging that shows Oops in it?
>
> Here it is, attached to this message.
> Previously I didn't attached it because to me it looks substantially the
> same as the one I attached in the opening message of this bug (#913119).
Thanks. Your logging indeed also only shows the 'task [...] blocked for
more than 120 seconds', and no actual OOPS messages.
>> If a task hangs while doing disk IO, it might cause messages like these
>> in dmesg:
>>
>> INFO: task kthxbye:1157 blocked for more than 120 seconds.
>> Not tainted blah #1 Debian someversion
>> [...]
>> <Some stack trace thing>
>>
>> These are 'just' informational messages. The process will still wait
>> until it can continue.
>>
>> A kernel Oops is something really different. It usually means that some
>> data structures or code to be executed are corrupt and there's a real
>> problem going on, it's not just stalled and waiting.
>
> Thank you very much for this explanation: I didn't know this difference
> and indeed I realized that I didn't know what a oops really is.
I'm unfortunately not the person who can fix this issue. Anyway, it's
good to confirm there is no actual real oops in your log. :)
Hans
Reply to: