All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99989] random crashes during boot
Date: Mon, 27 Feb 2017 20:05:25 +0000	[thread overview]
Message-ID: <bug-99989-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 99989
           Summary: random crashes during boot
           Product: Mesa
           Version: unspecified
          Hardware: x86 (IA32)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/r200
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: anonymissimus@arcor.de
        QA Contact: dri-devel@lists.freedesktop.org

Maybe 30% of the time, the system hangs during boot. There are 2 possible
points in the boot sequence where it occurs: Immediately before the login
screen appears, or immediately before my desktop is there. I'd love to provide
a dmesg log or something, but neither ctrl+alt+Fx nor SysRq keys work anymore
if it happens, I have to reset. (How do I get a log from the last boot ?)
Behavior of the machine and occasional stack traces I get displayed (but cannot
save) suggest to me the problem is graphics drivers related. System is Lubuntu
16.04. I can always boot to command line without problems, and it also never
happens afterwards, after it reached the desktop successfully.

lspci -v:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV280
[Radeon 9200] (rev 01) (prog-if 00 [VGA controller])
        Subsystem: PC Partner Limited / Sapphire Technology RV280 [Radeon 9200]
        Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        I/O ports at c000 [size=256]
        Memory at e9000000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at e8000000 [disabled] [size=128K]
        Capabilities: [58] AGP version 3.0
        Capabilities: [50] Power Management version 2
        Kernel driver in use: radeon
        Kernel modules: radeonfb, radeon

01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV280
[Radeon 9200] (Secondary) (rev 01)
        Subsystem: PC Partner Limited / Sapphire Technology RV280 [Radeon 9200]
(Secondary)
        Flags: bus master, 66MHz, medium devsel, latency 32
        Memory at e0000000 (32-bit, prefetchable) [size=128M]
        Memory at e9010000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [50] Power Management version 2

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

[-- Attachment #1.2: Type: text/html, Size: 3805 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

                 reply	other threads:[~2017-02-27 20:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-99989-502@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 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.