B133 works perfectly (for the freeze/atge and wireless).
I'll see what b135 does, provided I can upgrade to that (upgrade uses too much
memory - known problem).
The swap on zfs on sd unreliability remains, removing compression makes
probability of unkillable process smaller but non-zero. Let's
There is something wrong with the atge driver, I think.
Disabling nwam ("manual network configuration") does not help for the freeze,
put plugging in ethernet cable does. As does removing atge driver.
However, the link does not work. The dmesg says "atge0 link up" but it does not
work ... or th
> d8db3dc0::threadlist -v
ADDR PROC LWP CLS PRIWCHAN
d8db3dc0 fec21dd80 0 60 d2bb902c
PC: _resume_from_idle+0xb1TASKQ: atge_mii0
stack pointer for thread d8db3dc0: d8db3c58
swtch+0x188()
cv_timedwait_hires+0xc5()
cv_reltimedwait+0x52()
_mii_task+0
Situation improves ... after I disabled compression on the swap Firefox no
longer hangs. At least yet.. Should I make a separate partition for it?
The kernel freeze I debugged with http://www.bruningsystems.com/runq.d and it
says:
(just a part here):
de7c4ac0 on run queue, execname = xscreensave
More info, sorry for spamming ...
> 1. The kernel freezes for a few hundred ms in b134
> (does not happen in b133).
More specifically when the kernel "freezes" nothing else works, mouse stops,
real time priority class processes stop, keyboard input stops, etc. Not sure
about network (wireless)
There are two problems now ... I bet I was a bit confusing, sorry.
1. The kernel freezes for a few hundred ms in b134 (does not happen in b133).
Number of running kernel threads jumps up suddenly - see the vmstat output. No
clue why.
2. Firefox dies/freezes and cannot be killed (kill -9 has no
The firefox freezes completely (unkillble process, must force shutdown) in b134.
Now I'm investigating if swap (on zfs on sd disk) might be part of problem.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-dis
My EeePC701 works quite nicely with b133 (from Masafumi Ohta), except some
reliability problems with Firefox (resulting in unkillable firefox process).
But after upgrade to 134 the kernel freezes about every ten seconds for very
long time (maybe 200-500ms?):
$ vmstat 1
kthr memory
I have Asus M3A78-VM motherboard (with RTL8111/8168B chip) and the '-14'
version works very nice indeed. Iperf gives ~900Mbits/sec.
Only "disappointmet" is nfs performance (I am sharing zfs and the client is
Linux), it is a bit low (~5Mbytes/s).
Thank you for fixing the driver!
BTW, the stock
