dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104608] [r600, RV635] Removing radeon module results in BUG: unable to handle kernel NULL pointer dereference at 0000000000000258
Date: Tue, 16 Jan 2018 13:37:18 +0000	[thread overview]
Message-ID: <bug-104608-502-s473ymOx7g@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104608-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 609 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104608

--- Comment #3 from Vedran Miletić <vedran@miletic.net> ---
(In reply to Michel Dänzer from comment #2)
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> ?id=e97f12f359775de4fabfb507f836ebffa20f4986 should help for this.

Thanks. imirkin warned me on IRC (wrt similar bug 104609 in nouveau) not to
expect machine to reboot cleanly, so I'll be able to test it in a few weeks,
which is when 4.15.x is expected to come to Fedora 27 anyway.

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

[-- Attachment #1.2: Type: text/html, Size: 1931 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-01-16 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 19:00 [Bug 104608] [r600, RV635] Removing radeon module results in BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 bugzilla-daemon
2018-01-12 19:05 ` bugzilla-daemon
2018-01-15 10:10 ` bugzilla-daemon
2018-01-16 13:37 ` bugzilla-daemon [this message]
2018-01-16 16:37 ` bugzilla-daemon
2018-01-16 21:22 ` bugzilla-daemon
2018-03-05 17:06 ` 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-104608-502-s473ymOx7g@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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