dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201035] New: I2C bus probing crash on OpenChrome DRM
Date: Thu, 06 Sep 2018 18:34:52 +0000	[thread overview]
Message-ID: <bug-201035-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 201035
           Summary: I2C bus probing crash on OpenChrome DRM
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19 rc1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: kevinbrace@gmx.com
        Regression: No

OpenChrome DRM was working fine (i.e., able to normally boot Xubuntu 16.04)
until DRM maintainer's version of Linux 4.18 rc4.
When I upgraded to Linux 4.18 rc7, it stopped working.
I also upgraded to Linux 4.19 rc1, but it crashes for a similar reason.
It appears that there is a NULL pointer reference when probing for I2C bus.
The bug was observed on HP 2133 mini-note and VIA Embedded EPIA-M830 mainboard.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-09-06 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 18:34 bugzilla-daemon [this message]
2018-09-06 18:37 ` [Bug 201035] I2C bus probing crash on OpenChrome DRM bugzilla-daemon
2018-09-06 18:38 ` 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-201035-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox