linux-kernel - Re: Decoding an oops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wiK0Mmo-9qkuoBj4Syx_q9Lbn-ZZLb8BGpvuCf8OHjMgQ@mail.gmail.com>
Date:   Mon, 7 Oct 2019 12:37:47 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Francis M <fmcbra@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Decoding an oops

On Mon, Oct 7, 2019 at 7:58 AM Francis M <fmcbra@...il.com> wrote:
>
> Attached is a JPEG of what I've been able to capture from the console.
> I'm guessing it's probably not enough to go on, but hoping someone
> might have an 'ahh, that looks familiar' moment.

That is an awkwardly small snippet and not showing any of the real
oops state at all (the code/rip dump is actually the user space state
at the time of the system call that then causes the problem).

Can you make your VM use a bigger terminal so that it shows more of
the oops? Assuming your virtual environment supports the usual VESA
VGA modes, it might be as easy as just booting with "vga=775" to get a
1280x1024 console.

See

     https://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers

for more commentary.

That *might* work, and get you more of the dump.

              Linus