dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83505] AMD A4-5300 APU : only radeon.dpm=1 prevents random reboots with 3.16.1 kernel.
Date: Sat, 06 Sep 2014 10:40:34 +0000	[thread overview]
Message-ID: <bug-83505-502-DEOFje8Eug@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83505-502@http.bugs.freedesktop.org/>


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

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

Rpnpif <rpnpif@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rpnpif@free.fr

--- Comment #1 from Rpnpif <rpnpif@free.fr> ---
I have now two consecutive reboot : I describe.

1. I worked on Iceweasel 24.8.0 with two opened windows. One editing a SPIP
site.
The second with editing a Wikipedia article, more one other tab with Wikipedia.
Claws-mail was also opened.

2. A reboot occurred without any log.

3. The system reboots on 3.16.1 kernel with always radeon.dpm=1.

4. I reopened a session on Xfce.

5. I rerun Iceweasel only. All the tab and windows are restored.

6. I opened this bug report and begun this new comments.

7. After writing two or three lines in the text area, the system rebooted
again!

8. I replaced radeon.dpm=1 with radeon.dpm=0, rerun update-grub.I rebooted.

9. I rerun again Iceweasel with restored tabs and I can now fill this comment !

To conclude. The reboot problem is not fixed by a radeon.dpm=1 in grub. So the
summary of this bug is not exact. I expect that no new reboot happened again.
I'll follow with dpm=0 to see.

Note that about 2 two seconds before a reboot, xorg freezes (a watchdog effect
?).
I have also a little doubt with a kernel network side-effect.

My question : how get a debug log when an immediate reboot happened?

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

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

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

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

  reply	other threads:[~2014-09-06 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 16:54 [Bug 83505] New: AMD A4-5300 APU : only radeon.dpm=1 prevents random reboots with 3.16.1 kernel bugzilla-daemon
2014-09-06 10:40 ` bugzilla-daemon [this message]
2014-09-11 14:51 ` [Bug 83505] " bugzilla-daemon
2014-09-11 14:51 ` [Bug 83505] AMD A4-5300 APU : only radeon.dpm=1 get " bugzilla-daemon
2014-09-11 14:52 ` [Bug 83505] AMD A4-5300 APU : " bugzilla-daemon
2014-09-11 15:03 ` bugzilla-daemon
2014-09-11 15:08 ` bugzilla-daemon
2014-09-11 15:14 ` bugzilla-daemon
2014-09-17  8:01 ` bugzilla-daemon
2014-09-19 14:02 ` bugzilla-daemon
2014-09-22  6:39 ` 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-83505-502-DEOFje8Eug@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;
as well as URLs for NNTP newsgroup(s).