On Wed, Nov 03, 2010 at 07:27:20PM -0400, Rick Macklem wrote:
> >
> > I'm more interested in number of dropped frames. See below how to
> > extract that information.
> >
>
> I've attached the stats. I'm guessing that the
> Rx missed frames : 14792
> is the culprit.
>
Because that counter is 16
>
> I'm more interested in number of dropped frames. See below how to
> extract that information.
>
I've attached the stats. I'm guessing that the
Rx missed frames : 14792
is the culprit.
This was for a read of a fairly large file via NFS over TCP,
getting a read rate of about 450Kbytes/sec. (N
Alexander Kojevnikov wrote:
> The site now features Atom feeds for the following files:
>
> * ports/UPDATING
> * head/UPDATING
> * stable/7/UPDATING
> * stable/8/UPDATING
>
> Hope you find the feeds useful.
Useful indeed! Also, this is probably a nice thread to point out that a
commit log feed e
> On 11/3/10 2:56 PM, Rick Macklem wrote:
> >>> Is there any documentation on best practices for writing a FreeBSD
> >>> driver?
> >> Not really. :-/
> >>
> > Just a dumb obvious suggestion. Imho, there is no better doc. than
> > some
> > well written code, so maybe someone familiar with the driver
On 11/3/10 2:56 PM, Rick Macklem wrote:
Is there any documentation on best practices for writing a FreeBSD
driver?
Not really. :-/
Just a dumb obvious suggestion. Imho, there is no better doc. than some
well written code, so maybe someone familiar with the drivers can suggest
one (or two) that
On 11/3/10 10:52 AM, Julian Elischer wrote:
On 11/3/10 10:17 AM, John Baldwin wrote:
On Wednesday, November 03, 2010 1:04:13 pm m...@freebsd.org wrote:
So a MTX_DEF is okay in that environment?
Yes. In fact, the reason to have threads for interrupt handlers is
to allow
interrupt handlers to
>
> > Is there any documentation on best practices for writing a FreeBSD
> > driver?
>
> Not really. :-/
>
Just a dumb obvious suggestion. Imho, there is no better doc. than some
well written code, so maybe someone familiar with the drivers can suggest
one (or two) that they consider well writte
So, here is the next version of the patch:
http://people.freebsd.org/~avg/amd64-minidump.4.diff
Changes since the last version:
1. libkvm - try to support both the new and the previous formats/versions of
amd64 minidump. I am not entirely sure about style in which I handled handling
of version 1
On Wed, Nov 03, 2010 at 07:28:15PM +0100, Olivier Smedts wrote:
> > http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2
>
> Hello,
>
> Any status update on this ? I regularly check
> http://people.freebsd.org/~pjd/patches/ to see if there's an updated
> version of your patch. 2 m
Been working on getting this machine serviceable under FreeBSD with HP,
I need to try out some patches for other problems, but I wanted to link
folks to the pciconf output first.
Most importantly, I see an unsupported ethernet controller in this box,
but other's may find other devices of interest
on 03/11/2010 20:44 Alan Cox said the following:
[snip]
Thank you for the confirmation!
> Andriy Gapon wrote:
>> P.S. is there a macro for extracting frame address from PDPE?
> To a lower level page table page or to a 1GB physical page? For the latter,
> you
> can use PG_PS_FRAME.
To a 1GB pag
2010/8/31 Pawel Jakub Dawidek :
> Hello.
>
> I'd like to give you ZFS v28 for testing. If you are neither brave nor
> mad, you can stop here.
>
> The patchset is very experimental. It can eat your cookie and hurt your
> teddy bear, so be warned. Don't try it for anything except testing.
>
> This pa
on 08/10/2010 10:46 Alan Cox said the following:
> Andriy Gapon wrote:
>> Here's an updated patch:
>> http://people.freebsd.org/~avg/amd64-minidump.3.diff
>
> The kernel part of the patch looks good. That said, I have one suggestion.
> The
> current generation of AMD and Intel processors has su
On 11/3/10 10:17 AM, John Baldwin wrote:
On Wednesday, November 03, 2010 1:04:13 pm m...@freebsd.org wrote:
So a MTX_DEF is okay in that environment?
Yes. In fact, the reason to have threads for interrupt handlers is to allow
interrupt handlers to use non-spin locks that block when the lock i
on 03/11/2010 19:11 Kostik Belousov said the following:
> On Wed, Nov 03, 2010 at 10:04:13AM -0700, m...@freebsd.org wrote:
>> Is there any documentation on best practices for writing a FreeBSD driver?
> Not that I am aware of. You can read locking(9) in HEAD to get the answer
> on your question ab
On Wednesday, November 03, 2010 1:04:13 pm m...@freebsd.org wrote:
> On Wed, Nov 3, 2010 at 9:42 AM, Andriy Gapon wrote:
> > on 03/11/2010 18:27 m...@freebsd.org said the following:
> >> It's not clear to me from the man pages (perhaps I didn't look at the
> >> right one?) in which environments I
On Wed, Nov 03, 2010 at 10:04:13AM -0700, m...@freebsd.org wrote:
> On Wed, Nov 3, 2010 at 9:42 AM, Andriy Gapon wrote:
> > on 03/11/2010 18:27 m...@freebsd.org said the following:
> >> It's not clear to me from the man pages (perhaps I didn't look at the
> >> right one?) in which environments I n
On Wed, Nov 3, 2010 at 12:27 PM, wrote:
> It's not clear to me from the man pages (perhaps I didn't look at the
> right one?) in which environments I need a spinlock. For example, I
> wouldn't think it's safe to use a MTX_DEF in a hard interrupt handler
> (i.e one that was registered with BUS_SE
on 03/11/2010 19:04 m...@freebsd.org said the following:
> On Wed, Nov 3, 2010 at 9:42 AM, Andriy Gapon wrote:
>> on 03/11/2010 18:27 m...@freebsd.org said the following:
>>> It's not clear to me from the man pages (perhaps I didn't look at the
>>> right one?) in which environments I need a spinlo
On Wed, Nov 3, 2010 at 9:42 AM, Andriy Gapon wrote:
> on 03/11/2010 18:27 m...@freebsd.org said the following:
>> It's not clear to me from the man pages (perhaps I didn't look at the
>> right one?) in which environments I need a spinlock. For example, I
>> wouldn't think it's safe to use a MTX_D
on 03/11/2010 18:27 m...@freebsd.org said the following:
> It's not clear to me from the man pages (perhaps I didn't look at the
> right one?) in which environments I need a spinlock. For example, I
> wouldn't think it's safe to use a MTX_DEF in a hard interrupt handler
> (i.e one that was registe
It's not clear to me from the man pages (perhaps I didn't look at the
right one?) in which environments I need a spinlock. For example, I
wouldn't think it's safe to use a MTX_DEF in a hard interrupt handler
(i.e one that was registered with BUS_SETUP_INTR), but I see some code
lying around here t
On 10/30/2010 19:19, David Rhodus wrote:
> I haven't seen much of this since 5.x days. Anyone else see calcru
> messages lately ?
I only get them right after boot due to ntpd_sync_on_start=YES.
Cheers,
--
Thomas E. Spanjaard
t...@netphreax.net
t...@deepbone.net
signat
2010/10/30 David Rhodus :
> I haven't seen much of this since 5.x days. Anyone else see calcru
> messages lately ?
The following was performed on my Xen-powered VPS by RootBSD:
$ grep calcru /var/log/messages | wc -l
125
$ grep calcru /var/log/messages | head -n3
Oct 26 18:05:59 vps-1 kerne
On Wed, Nov 3, 2010 at 12:44 PM, Ed Schouten wrote:
> * Renato Botelho , 20101103 15:36:
>> On Wed, Nov 3, 2010 at 11:44 AM, Ed Schouten wrote:
>> > Garga!
>> >
>> > * Renato Botelho , 20101103 13:36:
>> >> For now i solve my problem adding
* Renato Botelho , 20101103 15:36:
> On Wed, Nov 3, 2010 at 11:44 AM, Ed Schouten wrote:
> > Garga!
> >
> > * Renato Botelho , 20101103 13:36:
> >> For now i solve my problem adding this to /etc/src.conf
> >>
> >> .if ${.CURDIR} == "/usr/sr
Just for the records: After applying the patch for net/kdenetwork3 from
Ed (thanks again for this), the port x11/kde3 (3.5.10_6) compiled fine
on -CURRENT without further tweakings; and it comes up fine too :-)
I've two smaller problems to investigate
1) I can't zapp the Xorg server with CTRL-AL
On Wed, Nov 3, 2010 at 11:44 AM, Ed Schouten wrote:
> Garga!
>
> * Renato Botelho , 20101103 13:36:
>> For now i solve my problem adding this to /etc/src.conf
>>
>> .if ${.CURDIR} == "/usr/src/gnu/lib/libgcc"
>> CC=cc
>> CXX=c++
>> .endif
&
on 03/11/2010 12:06 Sam Fourman Jr. said the following:
> On Wed, Nov 3, 2010 at 4:36 AM, Aragon Gouveia wrote:
>> I recently saw these on a Dell server. It was caused by power saving being
>> enabled in the BIOS in a mode where the BIOS takes control instead of
>> handing it off to the OS. Disa
On Fri, Oct 22, 2010 at 8:54 AM, Renato Botelho wrote:
> I have a 9.0-current (r214167) amd64, kernel and world built
> with clang and all ports built with gcc, and i cannot start
> openoffice anymore, it shows splash, start to go up and die.
>
> If I reinstall world+kernel built with gcc openoffi
On Wed, Nov 03, 2010 at 08:27:02AM +0100, Bernhard Schmidt wrote:
> ...
> There is ieee80211_notify_radio(), granted iwn(4) misses the calls.. that
> function is supposed to notify upper layers about the radio state (0 = off, 1
> = on). Anyways, once wpa_supplicant import/update is done, I'll pro
On Wed, Nov 3, 2010 at 4:36 AM, Aragon Gouveia wrote:
> I recently saw these on a Dell server. It was caused by power saving being
> enabled in the BIOS in a mode where the BIOS takes control instead of
> handing it off to the OS. Disable power saving or set it such that the OS
> has control (an
I recently saw these on a Dell server. It was caused by power saving
being enabled in the BIOS in a mode where the BIOS takes control instead
of handing it off to the OS. Disable power saving or set it such that
the OS has control (and then enable powerd(8) if you like).
Regards,
Aragon
O
On Tuesday, November 02, 2010 22:55:18 David Wolfskill wrote:
> On Tue, Nov 02, 2010 at 06:30:10PM +0100, Bernhard Schmidt wrote:
> >
> > Thanks. I had quick look into that and I currently do not see an easy
> > way to address that issue, as in tell wpa_supplicant about the device's
> > state.
On Tue, Nov 02, 2010 at 07:33:50PM +, Bruce Cran wrote:
> On Tuesday 02 November 2010 19:12:14 Bruce Cran wrote:
> > I've noticed in recent months that I appear to be getting silent corruption
> > of my UFS filesystems - and I think it may be linked to using md(4) or
> > creating sparse files.
35 matches
Mail list logo
