All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 109230] [crash] Xorg is crashing on startup with enabled xinerama
Date: Mon, 07 Jan 2019 07:42:07 +0000	[thread overview]
Message-ID: <bug-109230-8800-T8jYW4D6Cc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109230-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #4 from Mariusz Białończyk <manio-RFXG7K41k5GsTnJN9+BGXg@public.gmane.org> ---
Hi Ilia,
> Do you have a debug symbols package you could install? Or perhaps build
> xf86-video-nouveau yourself?
yes - I installed it, but the line:
"unw_get_proc_name failed: no unwind info found"
was still there, so I compiled nouveau myself and installed with debug symbols
but it doesn't help to full unwind, so finally I compiled whole xorg+debug
symbols and complete unwind still doesn't happen.
Isn't it that this unwind is for some libc calls which is irrelevant?
I am attaching new backtrace from console output.

> Also, to eliminate some potential complications -- try commenting out the
> RADEON bit and ensure that it keeps failing. (Not that that shouldn't work,
> but good to know for debugging purposes.)
No, it is not failing with nouveau alone (and commented radeon driver).

I was also trying to disable xinerama (with radeon+nouveau) - then it is also
not failing. It seems this is triggering only with enabled xinerama and both
radeon and nouveau drivers loaded.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-01-07  7:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 11:29 [Bug 109230] New: [crash] Xorg is crashing on startup with enabled xinerama bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-109230-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-01-06 11:29   ` [Bug 109230] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-06 11:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-06 17:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-07  7:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-01-07  7:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-07  7:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-07  7:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-07  8:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-07  8:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-109230-8800-T8jYW4D6Cc@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.