> > rt28600: 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 device h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a similar issue. I have:
ifconfig_re0_ipv6="inet6 accept_rtadv"
And after boot, I get:
% ping6 www.google.com
PING6(56=40+8+8 bytes) 2001:470:::::: -->
2a00:1450:8005::68
^C
- --- www.l.google.com ping6 statistics ---
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 basics.. Unfortunately dialog d
On Thu, 31 Mar 2011, Jung-uk Kim wrote:
On Thursday 31 March 2011 02:27 pm, Alexander Best wrote:
i just noticed the WWW links in pkg-descr of boths nspluginwrapper
and nspluginwrapper-devel are broken. i believe [1] is the current
location.
cheers.
alex
[1] https://github.com/davidben/nsplu
TB --- 2011-03-31 23:35:30 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 23:35:30 - starting HEAD tinderbox run for ia64/ia64
TB --- 2011-03-31 23:35:30 - cleaning the object tree
TB --- 2011-03-31 23:35:43 - cvsupping the source tree
TB --- 2011-03-31 23:35:43 - /usr/bin/c
TB --- 2011-03-31 22:40:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 22:40:00 - starting HEAD tinderbox run for i386/i386
TB --- 2011-03-31 22:40:00 - cleaning the object tree
TB --- 2011-03-31 22:40:26 - cvsupping the source tree
TB --- 2011-03-31 22:40:26 - /usr/bin/c
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 identical numerically
* to the SCSI device type numbers. The next 3 t
On Thursday, March 31, 2011 4:54:53 pm Julian Elischer wrote:
> On 3/31/11 11:37 AM, John Baldwin wrote:
> > On Thursday, March 31, 2011 2:20:11 pm Attilio Rao wrote:
> >> 2011/3/31 John Baldwin:
> >>> On Thursday, March 31, 2011 12:34:31 pm Attilio Rao wrote:
> 2011/3/31 John Baldwin:
> >
On 3/31/11 11:37 AM, John Baldwin wrote:
On Thursday, March 31, 2011 2:20:11 pm Attilio Rao wrote:
2011/3/31 John Baldwin:
On Thursday, March 31, 2011 12:34:31 pm Attilio Rao wrote:
2011/3/31 John Baldwin:
On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
Hi,
I've got a page
On Thu, 31 Mar 2011 16:50:16 +0100
"Sevan / Venture37" wrote:
> On 31 March 2011 10:07, Aleksandr Rybalko wrote:
> > Now good peoples help me with rework of driver, then this driver
> > will be available under ral(4). So you need to wait some time.
>
> Excellent, I'm happy to be a tester for pa
2011/3/31 John Baldwin :
> On Thursday, March 31, 2011 2:20:11 pm Attilio Rao wrote:
>> 2011/3/31 John Baldwin :
>> > On Thursday, March 31, 2011 12:34:31 pm Attilio Rao wrote:
>> >> 2011/3/31 John Baldwin :
>> >> > On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
>> >> >> Hi,
>> >> >>
On Thursday 31 March 2011 02:27 pm, Alexander Best wrote:
> On Thu Mar 31 11, Jung-uk Kim wrote:
> > On Thursday 31 March 2011 01:58 am, Jung-uk Kim wrote:
> > > I wrote an ugly but very simple workaround. Drop the attached
> > > patch in www/nspluginwrapper-devel/files and replaces old one,
> > >
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 basics.. Unfortunately dialog doesn't have a
"key" for delete all, delete left or delete right
On Thursday, March 31, 2011 2:20:11 pm Attilio Rao wrote:
> 2011/3/31 John Baldwin :
> > On Thursday, March 31, 2011 12:34:31 pm Attilio Rao wrote:
> >> 2011/3/31 John Baldwin :
> >> > On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
> >> >> Hi,
> >> >>
> >> >> I've got a page fault
On Thursday, March 31, 2011 12:21:45 pm Svatopluk Kraus wrote:
> On Thu, Mar 31, 2011 at 3:58 PM, John Baldwin wrote:
> > On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
> >> Hi,
> >>
> >> I've got a page fault (because of NULL td_lock) in
> >> thread_lock_flags() called from sched
On Thu Mar 31 11, Jung-uk Kim wrote:
> On Thursday 31 March 2011 01:58 am, Jung-uk Kim wrote:
> > I wrote an ugly but very simple workaround. Drop the attached
> > patch in www/nspluginwrapper-devel/files and replaces old one,
> > rebuild, reinstall, redo plugin wrappers, etc., etc...
>
> I just
2011/3/31 John Baldwin :
> On Thursday, March 31, 2011 12:34:31 pm Attilio Rao wrote:
>> 2011/3/31 John Baldwin :
>> > On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
>> >> Hi,
>> >>
>> >> I've got a page fault (because of NULL td_lock) in
>> >> thread_lock_flags() called from sched
On Thursday, March 31, 2011 12:34:31 pm Attilio Rao wrote:
> 2011/3/31 John Baldwin :
> > On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
> >> Hi,
> >>
> >> I've got a page fault (because of NULL td_lock) in
> >> thread_lock_flags() called from schedcpu() in /sys/kern/sched_4bsd.c
>
On Thursday 31 March 2011 01:58 am, Jung-uk Kim wrote:
> I wrote an ugly but very simple workaround. Drop the attached
> patch in www/nspluginwrapper-devel/files and replaces old one,
> rebuild, reinstall, redo plugin wrappers, etc., etc...
I just went ahead and committed slightly improved versio
This problem happens for only one reason, you have insufficient mbufs to
fill your rx ring. Its odd that it would differ when its static versus a
loadable
module though!
With the 7.2.2 driver you also will use different mbuf pools depending on
the MTU you are using. If you use jumbo frames it will
2011/3/31 John Baldwin :
> On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
>> Hi,
>>
>> I've got a page fault (because of NULL td_lock) in
>> thread_lock_flags() called from schedcpu() in /sys/kern/sched_4bsd.c
>> file. During process fork, new thread is linked to new process which
On Thu, Mar 31, 2011 at 3:58 PM, John Baldwin wrote:
> On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
>> Hi,
>>
>> I've got a page fault (because of NULL td_lock) in
>> thread_lock_flags() called from schedcpu() in /sys/kern/sched_4bsd.c
>> file. During process fork, new thread is
On 3/31/2011 11:20 AM, Olivier Smedts wrote:
> Hello,
>
> I've got a problem under FreeBSD 9.0-CURRENT amd64 with the em driver.
> It's loaded as a module. I was previously using r219710 (2011-03-17)
> without any problem, but with latest HEAD I can't even send a ping.
> Here's what appears in dme
On 31 March 2011 10:07, Aleksandr Rybalko wrote:
> Now good peoples help me with rework of driver, then this driver will be
> available under ral(4).
> So you need to wait some time.
Excellent, I'm happy to be a tester for patches, the card is a
Azurewave RT2700E out of a EEPC if I remember righ
Hello,
I've got a problem under FreeBSD 9.0-CURRENT amd64 with the em driver.
It's loaded as a module. I was previously using r219710 (2011-03-17)
without any problem, but with latest HEAD I can't even send a ping.
Here's what appears in dmesg. I tried unloading / loading the module,
did not help.
2011/3/31 Andriy Gapon :
> on 29/03/2011 23:29 Baptiste Daroussin said the following:
>> ok let's try to say it simpler :) the main goal is to keep it simple
>> for now, simple and rock solid, so that we can replace pkg_install and
>> do some cleanup in the ports tree, add the "must have" features
on 29/03/2011 23:29 Baptiste Daroussin said the following:
> ok let's try to say it simpler :) the main goal is to keep it simple
> for now, simple and rock solid, so that we can replace pkg_install and
> do some cleanup in the ports tree, add the "must have" features while
> doing that. And only w
TB --- 2011-03-31 12:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 12:00:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2011-03-31 12:00:00 - cleaning the object tree
TB --- 2011-03-31 12:00:25 - cvsupping the source tree
TB --- 2011-03-31 12:00:25 - /usr/bin
On Thu, Mar 31, 2011 at 4:10 PM, Andriy Gapon wrote:
> on 31/03/2011 14:32 Svatopluk Kraus said the following:
>> Hi,
>>
>> I've got a page fault (because of NULL td_lock) in
>> thread_lock_flags() called from schedcpu() in /sys/kern/sched_4bsd.c
>> file. During process fork, new thread is linke
TB --- 2011-03-31 12:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 12:00:00 - starting HEAD tinderbox run for i386/i386
TB --- 2011-03-31 12:00:00 - cleaning the object tree
TB --- 2011-03-31 12:00:26 - cvsupping the source tree
TB --- 2011-03-31 12:00:26 - /usr/bin/c
on 31/03/2011 14:32 Svatopluk Kraus said the following:
> Hi,
>
> I've got a page fault (because of NULL td_lock) in
> thread_lock_flags() called from schedcpu() in /sys/kern/sched_4bsd.c
> file. During process fork, new thread is linked to new process which
> is linked to allproc list and both
TB --- 2011-03-31 12:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 12:00:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2011-03-31 12:00:00 - cleaning the object tree
TB --- 2011-03-31 12:00:21 - cvsupping the source tree
TB --- 2011-03-31 12:00:21 - /usr/bin/c
On Thursday, March 31, 2011 7:32:26 am Svatopluk Kraus wrote:
> Hi,
>
> I've got a page fault (because of NULL td_lock) in
> thread_lock_flags() called from schedcpu() in /sys/kern/sched_4bsd.c
> file. During process fork, new thread is linked to new process which
> is linked to allproc list and
.. I fixed it by just disabling building the ath_ahb module for now.
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org
Hi,
I've got a page fault (because of NULL td_lock) in
thread_lock_flags() called from schedcpu() in /sys/kern/sched_4bsd.c
file. During process fork, new thread is linked to new process which
is linked to allproc list and both allproc_lock and new process lock
are unlocked before sched_fork() i
TB --- 2011-03-31 10:04:18 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 10:04:18 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2011-03-31 10:04:18 - cleaning the object tree
TB --- 2011-03-31 10:04:32 - cvsupping the source tree
TB --- 2011-03-31 10:04:32 - /u
TB --- 2011-03-31 09:51:30 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 09:51:30 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2011-03-31 09:51:30 - cleaning the object tree
TB --- 2011-03-31 09:51:44 - cvsupping the source tree
TB --- 2011-03-31 09:51:44 - /usr
TB --- 2011-03-31 10:22:11 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 10:22:11 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2011-03-31 10:22:11 - cleaning the object tree
TB --- 2011-03-31 10:22:22 - cvsupping the source tree
TB --- 2011-03-31 10:22:22 - /usr/b
TB --- 2011-03-31 10:05:21 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-03-31 10:05:21 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2011-03-31 10:05:21 - cleaning the object tree
TB --- 2011-03-31 10:05:32 - cvsupping the source tree
TB --- 2011-03-31 10:05:32 - /usr
Hi Sevan,
On Thu, 31 Mar 2011 01:49:04 +0100
"Sevan / Venture37" wrote:
>> On 20 March 2011 13:36, Aleksandr Rybalko wrote:
>> > Hi folks,
>> >
>> > new version of patch for wireless card based on Ralink RT2860 plus
>> > RT3090 that required testing.
>> >
>> > Main part:
>> > http://my.ddteam.n
Quoting Jung-uk Kim (from Wed, 30 Mar 2011 12:50:04 -0400):
Seriously, this problem is very well known. There were several
work-arounds suggested but the most popular one is setting
GDK_NATIVE_WINDOWS environment variable. Try "GDK_NATIVE_WINDOWS
Flash" on Google and you will see tons of them
41 matches
Mail list logo
