All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26812] New: Radeon module causes hard reset on modprobe
Date: Sat, 15 Jan 2011 21:40:38 GMT	[thread overview]
Message-ID: <bug-26812-2300@https.bugzilla.kernel.org/> (raw)

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

           Summary: Radeon module causes hard reset on modprobe
           Product: Drivers
           Version: 2.5
    Kernel Version: 2.6.37-git9
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: mjevans1983@gmail.com
        Regression: No


I'm using the git snapshots between when Linus merged from drm-core-next and
when network drivers were merged (breaks build).

If there is a better patch relative to a released source I'll gladly test it
too; however the other sources I tried also had similar issues.

When radeon.ko (or build in init) starts the screens blank and a few seconds
later the system completely reboots.  This is 100% repeatable.

I have firmware from Arch's (AUR) linux-firmware-git package installed,
/lib/firmware pointed as the source, and the relevant blobs for the recent
ATI/AMD GPUs.

When built as a module I can modprobe radeon to trigger the exact same
behavior.

Problems debugging:
* It resets so hard there isn't a peep from netconsole.
* It resets so hard that my disks loose md raid sync and need to completely
rebuild (yeah, I know, I'll add a write-intent log before I test this again
next time...; it wasn't an issue before I got the brainwave of making it a
module to try to give netconsole/syslog time to get setup.)

How can I possibly approach isolating this?  Even a link to the correct
documentation would be helpful.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand 
malware threats, the impact they can have on your business, and how you 
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

             reply	other threads:[~2011-01-15 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15 21:40 bugzilla-daemon [this message]
2011-01-15 22:11 ` [Bug 26812] Radeon module causes hard reset on modprobe bugzilla-daemon
2011-01-16  1:42 ` bugzilla-daemon
2011-01-16  2:09 ` bugzilla-daemon
2011-01-16  5:57 ` bugzilla-daemon
2011-02-02 17:52 ` bugzilla-daemon
2011-03-08 18:06 ` [Bug 26812] [RADEON:KMS:BARTS:HD6850:FIRMWARE] radeon " bugzilla-daemon
2012-08-14 15: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-26812-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.