All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62541] New: Kernel oops/panic during system boot with systemd - "Unable to handle kernel NULL pointer dereference"
Date: Sat, 05 Oct 2013 06:50:50 +0000	[thread overview]
Message-ID: <bug-62541-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=62541

            Bug ID: 62541
           Summary: Kernel oops/panic during system boot with systemd -
                    "Unable to handle kernel NULL pointer dereference"
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.11
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: a.byszuk@elka.pw.edu.pl
        Regression: No

Created attachment 110251
  --> https://bugzilla.kernel.org/attachment.cgi?id=110251&action=edit
dmesg, lswh, .config outputs

Hello,

I have a bug (100 % repeatable) that prevents booting Linux when systemd is
used as an init system. However, booting with traditional init works fine.
I'm posting this bug to the DRI subsystem because I was (barely) able to
capture to capture kernel message before the screen becomes blank.
I can verify that this problem happens in all 3.11.x kernels and in Debian's
3.10 kernel.
The hardware is Dell Vostro 3560 - Intel Ivy Bridge, hybrid graphics (Intel +
Radeon), OCZ Vertex 4 SSD.
My suspicion is that maybe the system bootup is too fast for the kernel; I was
able to boot kernel once even with systemd, but that was when I turned on all
the debugging messages which flooded console a bit.

Photo of captured BUG message: http://s23.postimg.org/qgk843rzv/vga1.png
dmesg, lshw and .config outputs attached.

Kind regards,
Adrian

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2013-10-05  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05  6:50 bugzilla-daemon [this message]
2013-10-05  6:51 ` [Bug 62541] Kernel oops/panic during system boot with systemd - "Unable to handle kernel NULL pointer dereference" bugzilla-daemon
2013-10-05  8:14 ` bugzilla-daemon
2014-06-20  4:11 ` bugzilla-daemon
2017-03-06 20:22 ` bugzilla-daemon
2017-03-08 11:21 ` bugzilla-daemon
2017-08-03  9:40 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-62541-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.