rt28600: Ralink RT2790 PCIe mem 0xf7f0-0xf7f0 irq 17 at
device 0.0 on pci3
rt28600: invalid EEPROM LNA gain #2: 0x00
rt28600: invalid EEPROM LNA gain #3: 0x00
rt28600: invalid EEPROM powersave level
rt28600: MAC/BBP RT2860 (rev 0x28720200), RF RT3022 2.4G 2T2R
Wow, your
On Thu, 31 Mar 2011 23:44:03 -0700 (PDT)
PseudoCylon moonlightak...@yahoo.ca wrote:
rt28600: Ralink RT2790 PCIe mem 0xf7f0-0xf7f0 irq 17 at
device 0.0 on pci3
rt28600: invalid EEPROM LNA gain #2: 0x00
rt28600: invalid EEPROM LNA gain #3: 0x00
rt28600: invalid EEPROM
Here is a larger patch:
Index: kern/kern_ktrace.c
===
--- kern/kern_ktrace.c (revision 220190)
+++ kern/kern_ktrace.c (working copy)
@@ -882,7 +882,8 @@
nfound = 0;
LIST_FOREACH(p,
Yes, you may hit it only on hast devices creation. The workaround is to avoid
using 'hastctl role primary all', start providers one by one instead.
Interesting to note that I just hit a lockup in hast (the discs froze
up - could not run hastctl or zpool import, and could not kill
them). I have
On 1 April 2011 01:03, Alexander Best arun...@freebsd.org wrote:
hi there,
devstat_buildmatch(3) crashes with certain strings. you can test this by
doing one of:
iostat -t ,
iostat -t ,,
iostat -t da,
iostat -t ,da,
iostat -t ,da
iostat -t da,scsi,
iostat -t ,da,scsi
iostat -t
On 1 April 2011 15:37, Sergey Kandaurov pluk...@freebsd.org wrote:
On 1 April 2011 01:03, Alexander Best arun...@freebsd.org wrote:
hi there,
devstat_buildmatch(3) crashes with certain strings. you can test this by
doing one of:
iostat -t ,
iostat -t ,,
iostat -t da,
iostat -t ,da,
On Fri Apr 1 11, Sergey Kandaurov wrote:
On 1 April 2011 01:03, Alexander Best arun...@freebsd.org wrote:
hi there,
devstat_buildmatch(3) crashes with certain strings. you can test this by
doing one of:
iostat -t ,
iostat -t ,,
iostat -t da,
iostat -t ,da,
iostat -t ,da
On 03/31/11 22:39, Daniel O'Connor wrote:
On 01/04/2011, at 5:09, Nathan Whitehorn wrote:
On 03/29/11 20:50, Daniel O'Connor wrote:
Hi,
I noticed that the entry widgets in the bsdinstaller label editor don't understand
various emacs keys (eg C-a, C-d, C-e).
Here's a patch which adds the
On Fri, 01 Apr 2011 11:40:11 +0100 Pete French wrote:
Yes, you may hit it only on hast devices creation. The workaround is to
avoid
using 'hastctl role primary all', start providers one by one instead.
PF Interesting to note that I just hit a lockup in hast (the discs froze
PF up -
On Thursday, March 31, 2011 6:33:39 pm Alexander Best wrote:
hi there,
i think there are multiple issues with devstat. i found the following in
devicestat.h:
/*
* These types are intended to aid statistics gathering/display programs.
* The first 13 types (up to the 'target' flag) are
The other 5% of the time, the hastd crashes occurred either when
importing the ZFS pool, or when running multiple parallel rsyncs to
the pool. hastd was always shown as the last running process in the
backtrace onscreen.
This is what I am seeing - did you manage to reproduce this with the
This looks like a different problem. If you have this again please provide the
output of 'procstat -kka'.
Will do...
-pete.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
On Fri, Apr 1, 2011 at 4:22 AM, Pete French petefre...@ingresso.co.uk wrote:
The other 5% of the time, the hastd crashes occurred either when
importing the ZFS pool, or when running multiple parallel rsyncs to
the pool. hastd was always shown as the last running process in the
backtrace
On Apr 1, 2011, at 5:40 AM, Sergey Kandaurov wrote:
if (++tempstr = tstr[5])
BTW,
this game with pointers might prevent devstat(3) from work on big-endian.
I'm very curious about your reasoning here.
Warner
On 1 April 2011 18:50, Warner Losh i...@bsdimp.com wrote:
On Apr 1, 2011, at 5:40 AM, Sergey Kandaurov wrote:
if (++tempstr = tstr[5])
BTW,
this game with pointers might prevent devstat(3) from work on big-endian.
I'm very curious
On Fri, Mar 25, 2011 at 03:41:53PM +0300, Alexander Pyhalov wrote:
Hello.
I'm just implementing the following network scheme on our freebsd hosts:
1) physical interface
2) for each vlanN on physical interface I create bridgeN and connect
interface to the bridge
3) for each vnet jail which
On 3/31/11 2:31 PM, John Baldwin wrote:
On Thursday, March 31, 2011 4:54:53 pm Julian Elischer wrote:
http://svn.freebsd.org/viewvc/base/head/sys/kern/kern_fork.c?annotate=83366
FreeBSD has always used this process to find a free PID. SVN and CVS history
does not lie.
yep
it's possible
17 matches
Mail list logo