> On 28 Dec 2016, at 23:47, Jack Raats wrote:
>>
>> At this moment Iâll get the following error while compiling buildworld
>>
>>
>>
>> --- clang-tblgen.full ---
>>
>> c++ -O2 -pipe -I/usr/obj/usr/src/tmp/usr/src/lib/clang/libllvm
>> -I/
that is how it is done in the US.
The US is 2am -> 1am in the fall and 1am -> 2am in the spring.
See /usr/src/share/zoneinfo/northamerica
--
Jack O'NeillSystems Administrator / System
here so I can't fix them myself. If anyone would
Actually ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin IS correct,
the password is not checked for `ftp' or `anonymous'.
------
Jack O'Neill
wrote a
> little script that stuffs those annoying statistics dumps into an
> RRD. You could conceivably do the same thing with sendmail, although
> you would have to collect your own stats by analyzing the log files.
Or use mailstats(1).
-
ly when I'm
> computing serious problems. If FreeBSD's going to ever survive in this
> world, it needs to compete with Linux, Windows, OS X in desktop market!
>
>
> Sung N. Cho
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebs
were some major changes to CAM in
3.2-STABLE, IIRC.
--
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROTECTED] Crystal Wind Communications, Inc.
Finger [EMAIL PROTECTED]
ing my usual perogative of
> >inspecting all potential changes with a more jaundiced eye. :)
>
> What happened to every 4 months?
IIRC, that metamorphized into 4 releases per year.
--
Jack O'Neill
OS, not as
FreeBSD being broken.
--
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROTECTED] Crystal Wind Communications, Inc.
Finger [EMAIL PROTECTED] for my PGP key.
PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
w it down any
farther.
--
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROTECTED] Crystal Wind Communications, Inc.
Finger [EMAIL PROTECTED] for my PGP key.
PGP Key fingerprint = F6 C4 E6 D4 2F 15
or from
> a port which does the wrong thing and installs under /usr/sbin.
They're leftovers from the isdn4bsd upgrade from version 0.71 to
0.81 back in May. You'll find the source, and man pages, in the
src/usr.sbin/i4b/alawulaw directory in the Attic.
--
ones, and flashed older
ones, can be done with an xmodem upload.
--
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROTECTED] Crystal Wind Communications, Inc.
Finger [EMAIL PROTEC
have it scan my
> existing ports and the current index and tell me what's out of date
> version number wise?
pkg_version(1)
--
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROT
t-4.0-RELEASE technology.
------
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROTECTED] Crystal Wind Communications, Inc.
Finger [EMAIL PROTECTED] for my PGP key.
PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
x27;s blades
also have
this device, but testing on that has failed to repro the problem.
I was wondering if anyone else out there has this hardware, if so could you
let me
know your experience, have you had problems or not, etc etc?
Thanks much for any information!
.
Regards,
Jack
-Original Message-
From: TAKAHASHI Yoshihiro [mailto:n...@freebsd.org]
Sent: Friday, January 07, 2011 7:40 PM
To: jfvo...@gmail.com
Cc: freebsd-...@freebsd.org; freebsd-stable@freebsd.org; Vogel, Jack
Subject: Re: Supermicro Bladeserver
In article
Jack Vogel writes:
> I
NO, and i was rather irritated by a checkin that broke backward
compatibility without
even asking me first btw. That should be the only issue however, and it can
be fixed
by a define. I'll get there soon.
Jack
On Thu, Jan 20, 2011 at 9:00 AM, Mike Tancsa wrote:
> Hi Jack,
>
Jeremy is right, if you have a problem the first step is to try the latest code.
However, when I look at the interrupts below I don't see what the problem is?
The Broadcom seems to have about the same rate, it just doesn't have MSIX
(multiple vectors).
Jack
-Original Message
If you go to 8.2 and the latest driver you will get better stats also,
ahem...
Jack
On Thu, Jan 27, 2011 at 11:57 AM, Jeremy Chadwick
wrote:
> On Thu, Jan 27, 2011 at 08:39:40PM +0100, Damien Fleuriot wrote:
> >
> >
> > On 1/27/11 7:46 PM, Sergey Lobanov wrote:
> >
to-bound to a particular CPU.
The older version you are running had issues and hence multiqueue was
not enabled. So, do upgrade once 8.2 is finalized :)
Cheers,
Jack
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
I don't test POLLING, sounds like its broken, I don't understand
why you think you need you need it? This hardware supports
MSI why not use it?
Jack
2011/1/31 Lev Serebryakov
> Hello, Freebsd-stable.
> You wrote 1 февраля 2011 г., 10:24:16:
>
> > And all conn
Anyone in net and stable that wants it, limits blocked it, so send me
personal email and I'll send to you.
Jack
On Wed, Feb 23, 2011 at 9:47 AM, Jack Vogel wrote:
> Here is the 7.2.2 tarball. IMPORTANT: if you use this DO NOT try and put it
>
> into your kernel source tree, it w
On Tue, Mar 1, 2011 at 5:50 PM, Mike Tancsa wrote:
> I had a machine deadlock just now and the only thing on the serial
> console was
>
> CPU0: local APIC error 0x40
> CPU1: local APIC error 0x40
>
> prior to it hanging. Anyone know what that error is ? Googling didnt
> really show much definitiv
Missed packets just mean that some temporary resource shortage or error
caused
the packet to be dropped. I don't believe this is indicative of a problem,
just let it
keep running, 2 days is good but 2 weeks is better :)
Thanks for testing it!
Jack
On Sun, Mar 6, 2011 at 4:37 AM, Özkan
med[1048]: the working directory is not writable
Mar 9 04:59:01 jpr1 named[1048]: running0630AS 3.AAE> ATA-7 SATA 2.x device
Mar 9 05:00:20 jpr1 root: /etc/rc: WARNING: failed to start
apache22DMA5, PIO 8192bMar 9 05:00:31 jpr1 kernel: nfe0: promiscuous
mode enabled
Mar 9 05:00:44 jpr1 bandwidthd:
Mar 10 03:13:26 jpr1 kernel: Waiting (max 60 seconds) for system
process `syncer' to stop...
Mar 10 03:13:26 jpr1 kernel: Syncing disks, vnodes remaining...0 timed out
Mar 10 03:13:26 jpr1 kernel: All buffers synced.
On Thu, Mar 10, 2011 at 1:50 AM, Jack L. wrote:
> I just got the error ju
to
be the case that is testing this driver?
Jack
On Fri, Mar 11, 2011 at 6:57 AM, Özkan KIRIK wrote:
> Hi again,
>
> I wanna share state of test machine. em-7.2.2 driver runs as kld. No hangs.
> Altough em0 has about 200Mbps traffic, cpu usage of em0 is too high.
> Should I
If you get this message its only for one reason, you don't have enough mbufs
to
fill your rings. You must do one of two things, either reduce the number of
queues,
or increase the relevant mbuf pool.
Increase the 9K mbuf cluster pool.
Jack
On Thu, Apr 14, 2011 at 6:05 AM, Leon Meßner
So, what do you have in mind as the real problem then?
Jack
On Thu, Apr 14, 2011 at 11:55 AM, K. Macy wrote:
> That isn't guaranteed to work if he is KVA limited.
>
> On Thu, Apr 14, 2011 at 6:44 PM, Jack Vogel wrote:
> > If you get this message its only for one reason, y
dropping it
to 1K.
But, for 10G, I don't think its unreasonable to have enough memory around to
handle
this.
Cheers,
Jack
On Thu, Apr 14, 2011 at 12:44 PM, Leon Meßner wrote:
> On Thu, Apr 14, 2011 at 08:55:17PM +0200, K. Macy wrote:
> > That isn't guaranteed to work i
Notice this: em0: Using MSIX interrupts with 0 vectors
ZERO vectors are not a good sign :) You need to look at your system, you
have MSIX
disabled or something? Maybe some message in /var/log/messages??
Jack
On Thu, Apr 28, 2011 at 1:20 PM, Wiktor Niesiobedzki wrote:
> Hi,
>
Well, rebuild your kernel so the driver is not static, then you can load and
unload
the driver to see what happens. You only have one interface, no em1?
Jack
On Thu, Apr 28, 2011 at 2:17 PM, Wiktor Niesiobedzki wrote:
> Hi,
>
> I really don't know (I haven't done that in
data 128(256) link x0(x1)
> > cap 01[68] = powerspec 2 supports D0 D3 current D0
> > cap 05[70] = MSI supports 1 message, 64 bit, vector masks
> > cap 08[88] = HT MSI fixed address window disabled at 0xfee0
> > cap 0d[90] = PCI Bridge card=0x0004
> >
> > Though they mention that HT MSI windows is disabled. I'm not sure,
> > whether this matters.
>
> Yes, that is probably what breaks this.
>
> --
> John Baldwin
>
Opps, missed that, thanks John. So, disable MSIX and MSI using sysctl,
then the driver should use legacy when it loads.
Still, I'd get a different motherboard, sucks to not have MSIX :(
Jack
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Thanks John. Was gonna say... the code has been as it is forever, with
everyone else in the world working fine, figured something odd was going
on.
Jack
On Mon, May 2, 2011 at 7:01 AM, John Baldwin wrote:
> On Saturday, April 30, 2011 2:42:11 am Wiktor Niesiobedzki wrote:
> > 2011/4/
So, this happens EVERY time after an install of 8.2 ??
Give me details about the hardware please.
Jack
On Thu, May 5, 2011 at 11:11 AM, Zaphod Beeblebrox wrote:
> The motherboard in question is made by Intel and contains a Xeon 3440
> (4 core x 2 HT per core). 16 Gig of RAM is install
update the ports and to use make install
excuses for the bad english
thanks
Jack
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-uns
Er, so what if you get rid of ZFS, does your panic go away? It doesn't really
matter what type adapter it is, the igb driver only requests standard size
clusters, so memory is getting trashed somewhere I suspect.
Jack
From: Bartosz Stec [mailto:bartosz.s...@it4pro.pl]
Sent: Friday, Ju
I looked at the dmesg and I didn't see a panic that was igb related?
What I could see it looked like igb loaded normally, sounds like it's just a
victim of another problem perhaps? You certainly don't want to use it without
MSIX. So far I've seen no data that would help un
Whoops, ignore the last message, I saw your screen picture.
I have NEVER seen this particular message, I'm wondering if you're getting some
corrupt bits or something. Make sure you have a clean build of the kernel and
driver.
Jack
-Original Message-
From: Jerem
I have hardware now, am working on reproducing this. Just curious, do you
have
the em driver defined in the kernel, or as a module?
Jack
On Wed, Jun 15, 2011 at 2:09 AM, Joshua Boyd wrote:
> On Wed, Jun 15, 2011 at 3:57 AM, Jeremy Chadwick
> wrote:
>
> > On Wed, Jun 15, 201
when using the GENERIC
config then it would be interesting to see the diff between that and what does
cause the panic.
Regards,
Jack
-Original Message-
From: Bartosz Stec [mailto:bartosz.s...@it4pro.pl]
Sent: Friday, June 17, 2011 6:42 AM
To: Vogel, Jack
Cc: Jeremy Chadwick; FreeBSD S
I cannot repro this, I used your kernel config, this is on a Dell 1850 btw,
I ran netperf stress from 3 clients, and have seen no watchdogs :(
Jack
On Tue, Jun 21, 2011 at 7:59 PM, Joshua Boyd wrote:
> If needed, I can reproduce this on demand. Just need to know what sort of
> statisti
What OS release are you going to be using, 8.2 ? The driver in HEAD is the
latest code, the internal tarball goes thru release machinery so it is
lagging a
bit (2.3.8 vs 2.3.11), you should be OK in either case, but I'd recommend
the newer.
Jack
On Tue, Aug 23, 2011 at 12:39 AM, Sami H
-Original Message-
From: Jeremy Chadwick [mailto:free...@jdc.parodius.com]
Sent: Thursday, September 22, 2011 3:28 AM
To: David G Lawrence
Cc: Craig Leres; freebsd-stable@freebsd.org; John Baldwin; Vogel, Jack
Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest
Well, for a start I'd get both interfaces at the same speed, sounds like a
hardware
issue of some sort, cable or switch maybe?
Jack
On Mon, Oct 10, 2011 at 5:42 PM, Larry Rosenman wrote:
> On Mon, 10 Oct 2011, Jeremy Chadwick wrote:
>
> On Mon, Oct 10, 2011 at 04:15:25P
Oh, I see. So, did you have a previous working state?
Jack
On Tue, Oct 11, 2011 at 12:06 AM, Larry Rosenman wrote:
> ** They are not local to each other. See the diagram. They are across the
> internet from each other.
> --
> Sent from my Android phone with K-9 Mail. Please excus
using SIP, so no hardware attached.
It would be nice to see the minimum config I have to use from asterisk.
Thanks
Jack Raats
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
n't support MSI-X, and as
>> such get starved.
>>
>
> Upgraded to a new bios, but that does not help either.
>
> Now the trick question will be:
> IF I get a new servertype PCI-E ethernet card, would that get me
>an MSI-X ethernet device.
>
>
There is n
experience something like this? Is there solution? It is very
> inconvenient to have to down/up the interfaces manually via the IPMI
> console when such thing happens.
>
>
Ya, don't unplug the cable :)
Just a bit of holiday humor will look into the issue after the long
w
netmask 255.255.255.0 with gateway
192.168.178.1
Is this possible?
How to do it??
What kind of problems to expect?
Thanks for your time
Jack Raats
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
the drive has reallocated some sectors and normally drives should never
reallocate sectors unless it has trouble reading/writing to them. also,
that drive has known firmware problems so it sounds like the drive needs
replacing
On Feb 9, 2012 10:38 AM, "Mike Tancsa" wrote:
> On 2/9/2012 11:34 AM,
think the default calculation is dated and should be changed, but am not
sure the best way, so are
there suggestions/opinions about this, and might we get it fixed before 8.3
is baked?
Cheers,
Jack
___
freebsd-stable@freebsd.org mailing list
t; > In turn, i believe interfaces should do their part and by default
> > > never try to allocate more than a fraction of the total number
> > > of buffers,
> >
> > Well what fraction should that be? It surely depends on how many
> > interfaces are in the sy
Never rains but it pours, this is the second request today :)
Yes, I will do an MFC as soon as quickly as I am able.
Jack
On Tue, Mar 6, 2012 at 3:00 PM, Chris Forgeron wrote:
> I have a few systems with Intel X520-DA2 PCIe network cards (10 Gig).
>
> The problem I've been r
Yes, it is supported in the ixgbe driver.
Jack
On Fri, Jun 1, 2012 at 8:36 AM, Rick Miller wrote:
> Hi All,
>
> I did not see the Intel 82599ES chipset in the hardware release notes
> for 8.3 or 9.0. Are these controllers supported at this time?
>
> --
> Ta
Increase your system mbuf pool size, you do not want that failure to happen.
Jack
On Fri, Jun 22, 2012 at 2:01 PM, Rick Miller wrote:
> dmesg and ifconfig output below...
>
> On Fri, Jun 22, 2012 at 4:02 PM, Rick Miller
> wrote:
> > On Fri, Jun 22, 2012 at 3:54 PM, And
ups.
Hopefully, when you get rid of the rx ring setup failure you will get
things working.
Jack
On Fri, Jun 22, 2012 at 3:19 PM, Rick Miller wrote:
> On Fri, Jun 22, 2012 at 5:21 PM, Jack Vogel wrote:
> > Increase your system mbuf pool size, you do not want that failure to
> happen.
Glad you figured it out.
Cheers,
Jack
On Mon, Jun 25, 2012 at 3:52 PM, Rick Miller wrote:
> Turns out the gbic in the switch was bad...I didn't think there was a
> problem on the host, but you all still gave me some good info. I
> appreciate it!
>
>
>
> On 6/25/12,
Be patient, a new version will hit HEAD soon with the ID added.
Jack
On Fri, Jun 29, 2012 at 9:35 AM, Rick Miller wrote:
> On Fri, Jun 29, 2012 at 11:56 AM, Gary Palmer wrote:
> > On Fri, Jun 29, 2012 at 10:50:52AM -0400, Rick Miller wrote:
> >> Hi All,
> >>
>
vmstat -i ?
Custom kernel? If you use stock kernel do you still see this problem?
If you use 8 RELEASE do you see the problem?
Jack
On Wed, May 19, 2010 at 11:06 AM, Mark Stapper wrote:
> On 05/19/10 12:44, Jeremy Chadwick wrote:
> > On Wed, May 19, 2010 at 12:34:17PM +0200, Mar
Panic is due to a failure to get enough mbufs, when you make your ring that
big you
hit the problem, I have been experimenting with a change to fix it but am
not yet
completely confident, for the moment don't make your ring so big :)
Jack
On Thu, May 27, 2010 at 1:08 AM, Kirill Yeli
latest code with a simplified, more automatic approach.
Jack
On Thu, May 27, 2010 at 3:30 AM, Kirill Yelizarov wrote:
> Thank You Jack
>
> i'll keep it at 2048 now. I have plans to add two more igb interfaces.
> Should i decrease values to 1024 in case i will have four inter
Yes, the commits today are slated to get into 8.1, at least that's my
understanding.
Jack
On Fri, Jun 18, 2010 at 10:46 AM, Brandon Gooch wrote:
> On Tue, Jun 1, 2010 at 2:37 PM, Jeremy Chadwick
> wrote:
> > On Tue, Jun 01, 2010 at 03:18:39PM -0400, Brian A. Seklecki wrote:
I do not believe this is a problem, a bit hard to parse the numbers on that
netstat, but
missed packets will happen when an interface gets lots of traffic. Keep an
eye on things
though.
Thanks,
Jack
On Sat, Jun 19, 2010 at 12:23 PM, Jeremy Chadwick
wrote:
> Something I came across today o
I got the email, there are server outages around here today and people
leaving
for a long weekend, so not much getting done. I'll take some time and look
into
this after the weekend, ok?
Jack
On Fri, Jul 2, 2010 at 10:39 AM, Mike Tancsa wrote:
> Hi Jack,
>Just a followup t
The fact that I WISH it to be MFC'd doesn't mean that I am actually given
permission to do so.
Jack
On Thu, Jul 15, 2010 at 10:48 AM, Steve Polyack wrote:
> On 07/15/10 13:31, Michael Tuexen wrote:
>
>> On Jul 15, 2010, at 6:50 PM, Brian A. Seklecki wrote:
>>
&g
line, this is a critical fix for 82575: SVN rev 210968
Cheers,
Jack
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
's not the complete string,
use sysctl -a |grep blacklist to find it) and set that to 0. It needs
to be set at boot.
That should get you running.
Jack
On Tue, Aug 17, 2010 at 8:18 AM, pluknet wrote:
> On 1 July 2010 02:13, Jack Vogel wrote:
> > On Wed, Jun 30, 2010 at 2:50 PM,
Hmmm, interesting, I'll have to have some testing done, maybe for the 574 it
should automagically disable CSUM?
Jack
On Tue, Aug 17, 2010 at 11:52 AM, Pyun YongHyeon wrote:
> On Mon, Aug 16, 2010 at 05:07:11PM -0400, Mike Tancsa wrote:
> > Hi Jack,
> > FYI, I am st
I believe the requirement of a context descriptor for most frames in the igb
driver
is just the way the hardware works, I've looked over the Linux driver again
and it
looks like they require the same. I don't believe its a big deal, just the
added
descriptor for the frame.
Jack
On T
Well we do of course, i'll have my test engineer try it both ways and see
what
looks better. Let you know...
Jack
On Tue, Aug 17, 2010 at 12:35 PM, Pyun YongHyeon wrote:
> On Tue, Aug 17, 2010 at 12:05:56PM -0700, Jack Vogel wrote:
> > Hmmm, interesting, I'll have to hav
ng about igb. But hey, I'm willing to be proven wrong :)
Jack
On Tue, Aug 17, 2010 at 12:47 PM, Pyun YongHyeon wrote:
> On Tue, Aug 17, 2010 at 12:34:31PM -0700, Jack Vogel wrote:
> > I believe the requirement of a context descriptor for most frames in the
> igb
> > driv
sed to limit it is broken, so you are getting two
queues. For now near the top of if_igb.c set igb_num_queues = 1;
I believe that will get rid of the watchdogs.
Jack
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Hmmm, can you remove ALTQ from the mix and see if that eliminates it?
Jack
On Thu, Aug 26, 2010 at 2:56 PM, Philipp Wuensche wrote:
> Jeremy Chadwick wrote:
> >
> > CC'ing Jack Vogel of Intel and Yong-Hyeon PYUN who might have some
> > ideas. OP's ba
On Thu, Aug 26, 2010 at 3:15 PM, Jeremy Chadwick
wrote:
> On Thu, Aug 26, 2010 at 11:56:48PM +0200, Philipp Wuensche wrote:
> > Jeremy Chadwick wrote:
> > >
> > > CC'ing Jack Vogel of Intel and Yong-Hyeon PYUN who might have some
> > > ideas. O
On Fri, Aug 27, 2010 at 6:04 AM, Philipp Wuensche wrote:
> Jack Vogel wrote:
> >
> >
> > On Thu, Aug 26, 2010 at 3:15 PM, Jeremy Chadwick
> > mailto:free...@jdc.parodius.com>> wrote:
> >
> > On Thu, Aug 26, 2010 at 11:56:48PM +0200, Philipp Wu
LOL, if its the VF its pretty new code, PLEASE anyone, if this is the case
make it clear in the title somewhere, ok? Thanks.
Jack
On Wed, Sep 1, 2010 at 10:24 AM, John Baldwin wrote:
> On Wednesday, September 01, 2010 1:11:31 pm pluknet wrote:
> > On 1 September 2010 20:06, Joh
In the future make sure that you put E1000 or EM in the title otherwise I
might miss it,
fortunately I looked at this :)
I'm on a holiday weekend, I will investigate this tomorrow.
Jack
On Mon, Sep 6, 2010 at 8:53 AM, Gareth de Vaux wrote:
> Hi all, I moved from 8.0-RELEASE to las
more about the system please?
Jack
On Mon, Sep 6, 2010 at 11:36 AM, Jack Vogel wrote:
> In the future make sure that you put E1000 or EM in the title otherwise I
> might miss it,
> fortunately I looked at this :)
>
> I'm on a holiday weekend, I will investigate thi
some other
issues, and I have added a changed message that will be less confusing.
Regards,
Jack
On Tue, Sep 7, 2010 at 10:00 AM, Jack Vogel wrote:
> Email to Gareth de Vaux is bouncing :(
>
> First off, this device was not supported in 8.0 REL, what were you running
> that last
This is what'd I'd expect, the onboard is PCH chipset, support was not in
8.0,
but as I said, in 8.1 (and hence stable/8) it is supported, and it should
work.
I do not know why you don't have MSI support, but it should still work with
Legacy interrupts.
Jack
On Wed, Sep 8,
positive, the kernel restricts
> certain tasks; not even the superuser (i.e., root) is allowed to
> do them.
>
> There:
>
> # Write to kernel memory via /dev/mem and /dev/kmem.
>
> So I assume it also restricts reading /dev/kmem ?
>
>
OH YUCK, another root isn&#
On Thu, Sep 9, 2010 at 11:37 AM, John Baldwin wrote:
> On Thursday, September 09, 2010 12:41:07 pm Jack Vogel wrote:
> > On Thu, Sep 9, 2010 at 7:33 AM, Kurt Jaeger wrote:
> >
> > > Hi!
> > >
> > > > > Is this within a jail or something else alo
Gareth's email bouncing for anybody else or is it just me?
Gareth, set hw.pci.honor_msi_blacklist=0, you'll have to do that at boot
btw.
Tell me more exactly the make/model of the hardware so I might try to get
my hands on one?
Jack
On Thu, Sep 9, 2010 at 1:20 PM, John Baldwin wr
On Fri, Sep 10, 2010 at 1:41 AM, Gareth de Vaux wrote:
> On Thu 2010-09-09 (13:48), Jack Vogel wrote:
> > Gareth's email bouncing for anybody else or is it just me?
>
> Yes sorry I disabled this alias after picking up years of spam on the
> mailman archives. I assumed
failure is not because
your system is blacklisted.
You still have not given me what I need to help: the exact details
of the system, I don't need to see the pciconf of the NIC, I need
to know about the motherboard/chipset its on.
Jack
___
freebsd
We don't deal with desktop systems that much in my group, it was pointed out
by a coworker that the BIOS has settings that could disable MSI, please
check
out how yours is set.
Jack
On Mon, Sep 13, 2010 at 7:42 AM, Gareth de Vaux wrote:
> On Fri 2010-09-10 (10:43), Jack Vogel wrote
82574 just are a source
of problems without a lot of benefit, so it still uses MSIX but with only 3
vectors,
meaning it seperates TX and RX but has a single queue.
Its looking very stable, I hope it fixes everyone's issues.
Jack
On Tue, Sep 14, 2010 at 10:59 AM, Mike Tancsa wrote:
>
m what you show here. I will try to get the new
driver out shortly for you to try.
Jack
On Sun, Sep 26, 2010 at 2:57 PM, Mike Tancsa wrote:
> At 06:36 PM 9/24/2010, Jack Vogel wrote:
>
>> There is a new revision of the em driver coming next week, its going thru
>> some
>> st
The system I've had stress tests running on has 82574 LOMs, so I hope it
will solve the problem, will see tomorrow morning at how things have held
up...
Jack
On Sun, Sep 26, 2010 at 4:43 PM, Mike Tancsa wrote:
> At 06:19 PM 9/26/2010, Jack Vogel wrote:
>
>> Your em1 is using
in if_igb.c and setting it to something other
than
0 for now.
I am at work on a number of issues with igb and em right now which is why
there has not been an MFC yet.
Questions to me,
Jack
On Thu, Oct 14, 2010 at 3:26 PM, Terry Kennedy wrote:
> I've run across a strange problem with
The number of MSIX vectors it uses is the number of queues PLUS
one vector for link. I would use two or four rather than 3, but it should
be ok with that if that's what you wish.
Jack
On Thu, Oct 14, 2010 at 6:58 PM, Terry Kennedy wrote:
> > The problem is mbuf resources, th
pciconf -l
I need to know which hardware it is and that doesnt show me.
Jack
On Thu, Oct 21, 2010 at 3:28 PM, Randy Bush wrote:
> em0: port 0x2000-0x201f mem
> 0xe800-0xe801 irq 16 at device 0.0 on pci13
>
> randy
>
> Jeremy Chadwick wrote:
> >
> > On T
Odd, can you make any connection between this and the em complaints??
Jack
On Fri, Oct 22, 2010 at 6:59 PM, Mike Tancsa wrote:
> At 09:11 PM 10/22/2010, Mike Tancsa wrote:
>
>> At 08:01 PM 10/22/2010, Chris Morrow wrote:
>>
>>> Note, Warren and I attempted to test t
Try the code from HEAD, I've run that on a 82546 and it worked ok.
Jack
On Wed, Nov 10, 2010 at 5:55 AM, Kirill Yelizarov wrote:
>
>
> --- On Wed, 11/10/10, Jeremy Chadwick wrote:
>
> > From: Jeremy Chadwick
> > Subject: Re: icmp packets on em larger than 1
Did you mean the 7.1.7 version from HEAD ?
Jack
On Sat, Nov 20, 2010 at 11:18 AM, Naujikas Rolandas <
rolandas.nauji...@mif.vu.lt> wrote:
> I'm trying to test with newest version of /sys/dev/e1000 from FreeBSD
> 8-STABLE.
> For that I'm using loadable module option
tails.
Regards,
Jack
On Sat, Nov 20, 2010 at 1:53 PM, Naujikas Rolandas <
rolandas.nauji...@mif.vu.lt> wrote:
> I don't know about version, but I'm using RELENG_8 branch only. It is
> FreeBSD 8-STABLE also.
>
> Regards, Rolandas Naujikas
>
> P.S. I just go
I'm a bit dubious about this, if a descriptor still has an mbuf it was due
to a discard,
go look at em_rx_discard(), you will notice there that all these things are
already
being done at that point. So do you have a scenario where we can have an
unused
mbuf that didn't come thru that pa
It looks like that there may be a memory leak of my swap space with one of
the processes that is running.
Big question: How can I determine which process is responsible.
Any suggestions?
Thanks
Jack
___
freebsd-stable@freebsd.org mailing list
http
It looks like that there may be a memory leak of my swap space with one of
the processes that is running.
Big question: How can I determine which process is responsible.
Any suggestions?
Thanks
Jack
___
freebsd-stable@freebsd.org mailing list
http
ong? Where to look for?
Thanks
Jack Raats
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
1 - 100 of 436 matches
Mail list logo
