* kernel panic in virt-manager
@ 2016-11-01 20:59 Joël Krähemann
2016-11-02 10:35 ` Sebastian Andrzej Siewior
0 siblings, 1 reply; 3+ messages in thread
From: Joël Krähemann @ 2016-11-01 20:59 UTC (permalink / raw)
To: linux-rt-users
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
Hi
There is a screenshot of a kernel panic in the attachment.
The last thing I did was:
apt-get install gdb valgrind make gcc automake autoconf on TTY2
Bests,
Joël
[-- Attachment #2: kernel-panic.png --]
[-- Type: image/png, Size: 34798 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kernel panic in virt-manager
2016-11-01 20:59 kernel panic in virt-manager Joël Krähemann
@ 2016-11-02 10:35 ` Sebastian Andrzej Siewior
2016-11-08 5:02 ` Joël Krähemann
0 siblings, 1 reply; 3+ messages in thread
From: Sebastian Andrzej Siewior @ 2016-11-02 10:35 UTC (permalink / raw)
To: jkraehemann-guest; +Cc: linux-rt-users
On 2016-11-01 21:59:49 [+0100], Joël Krähemann wrote:
> Hi
Hi,
> There is a screenshot of a kernel panic in the attachment.
> The last thing I did was:
>
> apt-get install gdb valgrind make gcc automake autoconf on TTY2
I see. So there is no backtrace and IP points to "doublefault". If you
can reproduce it then you could redirect ttyS0 somewhere and log
kernel's output there.
> Bests,
> Joël
Sebastian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kernel panic in virt-manager
2016-11-02 10:35 ` Sebastian Andrzej Siewior
@ 2016-11-08 5:02 ` Joël Krähemann
0 siblings, 0 replies; 3+ messages in thread
From: Joël Krähemann @ 2016-11-08 5:02 UTC (permalink / raw)
To: Sebastian Andrzej Siewior; +Cc: linux-rt-users
Hi
This happend as virtualization support was disabled by BIOS. And
occured multiple times, as
enabling hardware virtualization support there were no more problems.
Bests,
Joël
On Wed, Nov 2, 2016 at 11:35 AM, Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
> On 2016-11-01 21:59:49 [+0100], Joël Krähemann wrote:
>> Hi
> Hi,
>
>> There is a screenshot of a kernel panic in the attachment.
>> The last thing I did was:
>>
>> apt-get install gdb valgrind make gcc automake autoconf on TTY2
>
> I see. So there is no backtrace and IP points to "doublefault". If you
> can reproduce it then you could redirect ttyS0 somewhere and log
> kernel's output there.
>
>> Bests,
>> Joël
>
> Sebastian
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-11-08 5:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-01 20:59 kernel panic in virt-manager Joël Krähemann
2016-11-02 10:35 ` Sebastian Andrzej Siewior
2016-11-08 5:02 ` Joël Krähemann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).