DragonFlyBSD

After adding "-ht" parameter to ifconfig string I have not seen a
firmware error anymore, but the X console still freezes when using a
browser (tried with firefox and midori).

messages contains the following log (starting with drm initialization):

Nov 13 12:24:46 MisterX kernel: info: [drm] Initialized drm 1.1.0 20060810
Nov 13 12:24:46 MisterX kernel: drm0 on vgapci0
Nov 13 12:24:46 MisterX kernel: info: [drm] AGP at 0xe0000000 256MB
Nov 13 12:24:46 MisterX kernel: iicbus0: <Philips I2C bus> on iicbb0
addr 0xff
Nov 13 12:24:46 MisterX kernel: iicbus2: <Philips I2C bus> on iicbb1
addr 0xff
Nov 13 12:24:46 MisterX kernel: iicbus4: <Philips I2C bus> on iicbb2
addr 0xff
Nov 13 12:24:46 MisterX kernel: iicbus6: <Philips I2C bus> on iicbb3
addr 0xff
Nov 13 12:24:46 MisterX kernel: iicbus8: <Philips I2C bus> on iicbb4
addr 0xff
Nov 13 12:24:46 MisterX kernel: iicbus10: <Philips I2C bus> on iicbb5
addr 0xff
Nov 13 12:24:46 MisterX kernel: info: [drm] Supports vblank timestamp
caching Rev 1 (10.10.2010).
Nov 13 12:24:46 MisterX kernel: info: [drm] Driver supports precise
vblank timestamp query.
Nov 13 12:24:46 MisterX kernel: drm0: taking over the fictitious range
0xe0000000-0xf0000000
Nov 13 12:24:46 MisterX kernel: info: [drm] initialized overlay support
Nov 13 12:24:46 MisterX kernel: info: [drm] Initialized i915 1.6.0 20080730
Nov 13 12:25:27 MisterX kernel: error: [drm:pid-1:i915_hangcheck_hung]
ERROR Hangcheck timer elapsed... GPU hung
Nov 13 12:25:27 MisterX kernel: error: [drm:pid-1:init_ring_common]
ERROR render ring initialization failed ctl 00000000 head 00000000
tail 00000000 start 00000000
Nov 13 12:25:39 MisterX syslogd: exiting on signal 15

As you can see in the last log lines, there is still something wrong
with drm.

Now I thought that this is an xorg issue, searched the Internet for
fixes and found a few for Linux that modify the "AccelMethod" parameter
in the graphics card section (change it to "XAA", "EXA", ...). Tried
them all, but nothing helped.

Regards
Matthias

Am 12.11.2014 um 23:36 schrieb bugtracker-admin@leaf.dragonflybsd.org:

Issue #2733 has been updated by swildner.

Can you try adding "-ht" to your ifconfig_wlan0 line in rc.conf? This disables "high throughput". It seems there are issues with 802.11n (which we don't support for iwn(4) anyway, afaik).

----------------------------------------
Bug #2733: iwn firmware error rendering xserver unusable
http://bugs.dragonflybsd.org/issues/2733#change-12278

• Author: masu
• Status: New
• Priority: Normal
• Assignee:
• Category:
• Target version:
  ----------------------------------------
  Hi,

a firmware error of the wifi nic occurrs right after drm is started when starting xserver on my machine.
The nic is automatically reset afterwards and drm becomes initialized.

But then during the X session the nic error occurrs again resulting in an unsuccessful restart that causes also drm to fail which in effect leaves the X console unresponsive.
Strangely this effect appears when browsing the Internet and not when e.g., installing packages from remote locations that also generates network traffic over the wifi nic.

Does someone has a Lenovo X61 and experiences the same problems?

An excerpt from /var/log/messages is attached.

Regards
Matthias

---Files--------------------------------
messages (26.1 KB)

The firmware error does not seem anything to do with the X server freeze.

Found the X server error to be introduced with the following commit:
http://gitweb.dragonflybsd.org/dragonfly.git/commit/d1c259eee6a290aadce1c78a746e131034aba76a

Please can somebody have a look into this who knows i915 drm internals?

Regards
Matthias

Could you switch back to master and apply this additional commit with git am ? It's a revert of the first wrong subcommit.

The partial revert has been pushed to master, as commit# 7e793f0f65ddb0079aff564e23816504c945f876.

Thanks for testing !