cksum failed" and
> "[drm2:pid:hangcheck_hung]...GPU hung" issues to track/report, but since
> finding Xorg's secret about "MatchIsKeyboard" took me too much time,
> this is postponed.
>
> -harry
>
--
[image: Limelight Networks] <http://www.
PM, but 21:49...
> So I think it's most likely any UTC+>2 time, so the revision I tested
> was probably Diff 42294 <https://reviews.freebsd.org/B16487>.
>
> Just tell me if it was useful for you to test the latest revision again.
>
> -harry
>
--
0xfe008fe183f0
> ether_output_frame() at ether_output_frame+0xaa/frame 0xfe008fe18420
> ether_output() at ether_output+0x68b/frame 0xfe008fe184c0
> arprequest() at arprequest+0x474/frame 0xfe008fe185c0
> arp_ifinit() at arp_ifinit+0x58/frame 0xfe008fe18600
>
Eric van Gyzen wrote:
Twice a day, my router hits an LOR in iflib_timer when it jumps to the
"hung" label. It's running r325049 (head 3 days ago).
lock order reversal:
1st 0xfef36068 igb1:tx(0):call (igb1:tx(0):call) @
/usr/src/sys/kern/kern_mutex.c:182
2nd 0xf80003b0c150 igb1 (
Kevin Bowling wrote:
I have heard from several vendors the need for a NIC configuration
tool. Chelsio ships a cxgb/cxgbetool in FreeBSD as one example.
There is precedence for some nod toward a basic unified tool in Linux
ethtool.
From your perspective,
1) What are the common requirements?
> is there any chance this patch will be commited soon to the -STABLE
> tree? i'm
> having a similar problems and it's driving me crazy. my log is full
> with all
> the arp movement messages.
As I understand it, there's a very good change... possibly so good that it's
already done. ;-)
Alfred P
