| Summary: | X restarting: Caught signal 11 (Segmentation fault). Server aborting | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Anonymous Helper <anonymous> | ||||||
| Component: | Server/Input/XKB | Assignee: | Daniel Stone <daniel> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | ||||||||
| Version: | git | ||||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
Created attachment 35517 [details]
xorg log
I have to join this report with mine xorg log. It happened while scrolling page within iceweasel. No messages on the seqfault in kern.log or dmesg.
Other possibly connecting symptoms:
- google IG page is for something scrolling really slow (but only this page, others are scrolling normally),
- today while scrolling google IG page, the cursor turned from arrow to a square composed of screen artifact and didn't dissapear after gdm restart. I had to restart the machine.
I'm running:
debian squeeze with vanilla 2.6.34-rc6 with mesa, drm, radeon driver updated yesterday from git.
One more thing: I'm guessing the scrolling problems relate to bug #27627 but not sure if it is connected with this segfault. (In reply to comment #1) > I have to join this report with mine xorg log. You absolutely didn't 'have to', in fact you shouldn't have: > It happened while scrolling page within iceweasel. No messages on the seqfault > in kern.log or dmesg. Which is completely different from what's written in this report. The backtrace doesn't look even remotely similar either. If your problem isn't fixed in newer Git snapshots of xserver and the radeon driver, please file a new report, preferably with a full gdb backtrace. The crash in this report looks XKB related, reassigning. I'm sorry if my report was totally unrelated with the original one. I just followed the symptoms (X closes and restarts itself without saying anything) and guessed it could be related since I'm not fluent in backtraces. In no way was "have to" reffered as something negative. Sorry again. (In reply to comment #4) > I'm sorry if my report was totally unrelated with the original one. I just > followed the symptoms (X closes and restarts itself without saying anything) > and guessed it could be related since I'm not fluent in backtraces. In no way > was "have to" reffered as something negative. Sorry again. don't worry about it. :) could you please file a new report on the radeon driver? (In reply to comment #0) > Created an attachment (id=35512) [details] > Xorg.0.log.old > > When playing video games, X closes and restarts itself. > > I use Ubuntu 10.04, xorg-edgers ppa (packages from 2010/05/04). KMS is on. > > Graphic card: rv420. > Radeon driver. hm. which games in particular? also, from looking at the backtrace, it happens just after you press a key. does this always happen at a specific time - e.g. just after a resolution change, right after the game starts, etc - or is it the first time you press a key, or? I switched back today to the xorg-edgers ppa, but I wasn't able to reproduce the bug. It happened with games like Warsow or Teeworlds, I don't recall any specific keys pressed as it was in middle of games. It seemed to me to be a bit random. I will reply later to confirm if the bug disappeared or not. No more sign of this bug, you can probably close it. (In reply to comment #9) > No more sign of this bug, you can probably close it. thanks. :) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 35512 [details] Xorg.0.log.old When playing video games, X closes and restarts itself. I use Ubuntu 10.04, xorg-edgers ppa (packages from 2010/05/04). KMS is on. Graphic card: rv420. Radeon driver.