All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 61811] kms mode breaks when using radeon.agpmode=-1
Date: Tue, 24 Sep 2013 20:58:27 +0000	[thread overview]
Message-ID: <bug-61811-2300-wW9Dqf8QBZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-61811-2300@https.bugzilla.kernel.org/>

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

--- Comment #12 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
(In reply to Alex Deucher from comment #10)
> (In reply to Dieter Nützel from comment #8)
> > (In reply to Alex Deucher from comment #6)
> > > Can you bisect?
> > 
> > Hello Alex,
> > 
> > I'll try 'cause I get the same with clean 3.12-rc2 +
> > 0001-drm-radeon-avoid-UVD-corruption-on-AGP-cards-using-G.patch
> > 
> > radeon.agpmode=8 works as before, but
> > radeon.agpmode=-1 gave
> > 
> > [-]
> > [   10.958649] radeon: `-1' invalid for parameter `agpmode'
> > [   11.515274] radeon: `-1' invalid for parameter `agpmode'
> > FATAL: Error inserting radeon
> > (/lib/modules/3.12.0-rc2-1-desktop/kernel/drivers/gpu/drm/radeon/radeon.ko):
> > Invalid argument
> > 
> 
> We haven't touched anything AGP related in radeon in years.

I know. ;-)

>  Maybe some general kernel module parsing change?

That was my thought, too.

> > 
> > Any point to start without git-tree?
> 
> You really need a git tree to bisect.

I know, second time, but...
...I'll see what I can find in Linus 3.12-rc1 (maybe before) patch file(s)
(logs).
For several git trees this system is to small...

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

  parent reply	other threads:[~2013-09-24 20:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-61811-2300@https.bugzilla.kernel.org/>
2013-09-24 17:47 ` [Bug 61811] kms mode breaks when using radeon.agpmode=-1 bugzilla-daemon
2013-09-24 19:07 ` bugzilla-daemon
2013-09-24 19:24 ` bugzilla-daemon
2013-09-24 20:27 ` bugzilla-daemon
2013-09-24 20:29 ` bugzilla-daemon
2013-09-24 20:39 ` bugzilla-daemon
2013-09-24 20:40 ` bugzilla-daemon
2013-09-24 20:52 ` bugzilla-daemon
2013-09-24 20:58 ` bugzilla-daemon [this message]
2013-09-24 21:14 ` bugzilla-daemon
2013-09-26 12:25 ` bugzilla-daemon
2013-09-27 12:38 ` bugzilla-daemon
2013-09-27 15:07 ` bugzilla-daemon
2013-09-27 15:44 ` bugzilla-daemon
2013-09-27 17:53 ` bugzilla-daemon
2013-09-28  0:00 ` bugzilla-daemon
2013-09-28  0:23 ` bugzilla-daemon
2013-09-30  3:14 ` bugzilla-daemon
2013-10-14 22:01 ` bugzilla-daemon
2013-10-15  1:52 ` 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-61811-2300-wW9Dqf8QBZ@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.