I've got the following kernel panic seemingly at random.
I have been using the kernel for about a week without any issues and I wasn't
doing anything special when the panic occurred.
Does this panic ring any bells? Could the problem be already fixed by more
recent changes?
r286985
panic: Stray
On 30/08/2015 21:37, Oliver Pinter wrote:
You have a running Xorg with radeonkms driver, and this issue
occurrence under high load (for example parallel buildworld)?
I use radonkms indeed and judging from ta_func = ttm_bo_delayed_workqueue it was
involved. But there was no steady system load
On 30/08/2015 19:16, Konstantin Belousov wrote:
This is strange, I do not think that could be a right explanation of this
issue. The taskqueue callout is initialized with the mutex, which means
that the callout_stop() caller
- must own the mutex;
- is synchronous with the callout.
In other
Slawa Olhovchenkov wrote on 08/30/2015 20:50:
On Sun, Aug 30, 2015 at 04:06:04PM +0300, Slawa Olhovchenkov wrote:
On Sat, Aug 29, 2015 at 11:15:53PM +0300, Ruslan Makhmatkhanov wrote:
Hello,
I'm getting tons of this in /var/log/messages:
error: [drm:pid9:i915_gem_object_unbind] *ERROR*
On 8/30/15, Andriy Gapon a...@freebsd.org wrote:
I've got the following kernel panic seemingly at random.
I have been using the kernel for about a week without any issues and I
wasn't
doing anything special when the panic occurred.
Does this panic ring any bells? Could the problem be
On Sun, Aug 30, 2015 at 09:58:31PM +0300, Ruslan Makhmatkhanov wrote:
I think this is not root of cause, this is only cause of other error:
=== dmesg
info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer
On Sun, Aug 30, 2015 at 11:59:26PM +0300, Ruslan Makhmatkhanov wrote:
Slawa Olhovchenkov wrote on 08/30/2015 22:17:
On Sun, Aug 30, 2015 at 09:58:31PM +0300, Ruslan Makhmatkhanov wrote:
No doubt that this is not the root cause, but frankly I haven't that
GPU hung messages in my system. I
Slawa Olhovchenkov wrote on 08/30/2015 22:17:
On Sun, Aug 30, 2015 at 09:58:31PM +0300, Ruslan Makhmatkhanov wrote:
No doubt that this is not the root cause, but frankly I haven't that
GPU hung messages in my system. I have others like this one triggered
on shutdown:
error:
On Sun, Aug 30, 2015 at 04:06:04PM +0300, Slawa Olhovchenkov wrote:
On Sat, Aug 29, 2015 at 11:15:53PM +0300, Ruslan Makhmatkhanov wrote:
Hello,
I'm getting tons of this in /var/log/messages:
error: [drm:pid9:i915_gem_object_unbind] *ERROR* Attempting to unbind
pinned buffer
On Sat, Aug 29, 2015 at 11:15:53PM +0300, Ruslan Makhmatkhanov wrote:
Hello,
I'm getting tons of this in /var/log/messages:
error: [drm:pid9:i915_gem_object_unbind] *ERROR* Attempting to unbind
pinned buffer
As far I understand [1], this case is harmless and there is no point to
print
On my laptop I am using LAGG(4) as explained in
Example 30.3. Failover Mode Between Ethernet and Wireless Interfaces in
the Handbook.
In rc.conf i have:
# LAGG
ifconfig_re0=up
ifconfig_ath0=ether 18:67:b0:39:bd:23
wlans_ath0=wlan0
ifconfig_wlan0=WPA
cloned_interfaces=lagg0
ifconfig_lagg0=laggproto
hi,
don'tr set ath0 to the MAC of your ethernet device, set your ethernet
MAC to the MAC of your atheros device.
(But I keep telling people, failover between ethernet/wifi isn't
supported by the wifi code...)
-a
On 30 August 2015 at 05:52, Ranjan1018 . 21474...@gmail.com wrote:
On my laptop
Hi,
has anyone asked dumbbell directly about it?
-a
On 30 August 2015 at 14:25, Slawa Olhovchenkov s...@zxy.spb.ru wrote:
On Sun, Aug 30, 2015 at 11:59:26PM +0300, Ruslan Makhmatkhanov wrote:
Slawa Olhovchenkov wrote on 08/30/2015 22:17:
On Sun, Aug 30, 2015 at 09:58:31PM +0300, Ruslan
13 matches
Mail list logo
