I'm also having the same exact issues across several systems on
13-BETA3 and 14-CURRENT as of last week.
I recently upgraded everything to the latest 13-STABLE and 14-CURRENT
but uptime is only a day or so and not sure if it's still a problem.
On Mon, Feb 22, 2021 at 12:07 PM Florian Smeets via
I've noticed for Dells, you have to set the performance setting to
"Custom" and OS Control to be able to change the EST.
On Tue, Feb 16, 2021 at 7:12 PM Eugene Grosbein wrote:
>
> Hi!
>
> We use leased server Dell PowerEdge R640 with latest firmware (BIOS/UEFI)
> that does not export ACPI _PSS ta
I bought a new a PC and now eager waiting for the new release to arrive!!!
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Yes, I upgraded 2 systems and both experience the same behavior
Dell R610 and Dell 7010 here. Afraid to upgrade any others
On Tue, Sep 10, 2019 at 8:25 PM Terry Kennedy wrote:
>
> I have a system I updated from r352025 (which worked fine) to r352200.
> Any attempt to boot r352200 results in th
I use crontab @daily (/sbin/gmirror status | grep -q COMPLETE) || mail
-s "gmirror failure" email addy
On Tue, May 8, 2018 at 4:41 PM, Vincent Hoffman-Kazlauskas
wrote:
>
>
> On 08/05/2018 08:28, Andrea Brancatelli wrote:
>> Hi,
>>
>> out of curiosity, does any kind of GMirror-failure notificatio
I went from 9 to 11 without issue with the make work/kernel method and
rebuilt all the ports.
On Tue, Jun 20, 2017 at 10:31 AM, Miroslav Lachman <000.f...@quip.cz> wrote:
> Zoran Kolic wrote on 2017/06/20 17:12:
>>>
>>> Generally (and previously) the advice is to go via the next major version
>>>
I have a few still sitting in a corner with FreeBSD 7 or 8 on them. Someday i
might put them back on with FreeBSD but not anytime soon
Sent from far away...
> On Mar 25, 2017, at 11:02 AM, Andriy Gapon wrote:
>
>
> Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors with
>
Problem SOLVED. I copied libpthread.a from a jail on that server to the right
directory and could compile the source.
It seemed that the library was somehow damaged.
Grtz.,
Jack
Op 29-12-16 16:06 heeft Dimitry Andric geschreven:
On 28 Dec 2016, at 23:47, Jack Raats wrote:
>
&
> 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/
> 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/
ined reference to
`__sys_fdatasync'
c++: error: linker command failed with exit code 1 (use -v to see invocation)
*** [clang-tblgen.full] Error code 1
Systeem: FreeBSD 11.0-STABLE At revision 310725.
Can anyone give me a clue?
Thanks
Jack
___
Adding FreeBSD stable to see if they can provide some insight on this since
it affects everything from 11 and beyond
>
> On Sat, Nov 26, 2016 at 7:01 AM, Bertram Scharpf > wrote:
>
>> On Friday, 25. Nov 2016, 20:06:55 -0800, Jack L. wrote:
>> > On Fri, Nov 25, 2016
If you look at the ftp.freebsd.org than you can see that the 10.3-RELEASE
can be downloaded.
The strange thing is that there is no announcement yet.
Also the newvers.sh still has PRERELEASE in stead of STABLE.
Can anyone explain why this hasn¹t happened yet???
Thanks!
Jack
Op 01-04-16 00
You missed the all-important details: OS version, driver version.
And another question I can think of, do these interfaces watchdog if they
are not configured with lagg?
Cheers,
Jack
On Fri, Oct 2, 2015 at 10:37 AM, Frank de Bot (lists)
wrote:
> On a server I have 2 interfaces configured
Should give someone a clue, something in the usb code that 10.2 didn't get
perhaps...
Thanks,
Jack
On Sat, Aug 8, 2015 at 6:37 PM, Paul Mather <
freebsd-li...@gromit.dlib.vt.edu> wrote:
> On Aug 3, 2015, at 2:15 PM, Paul Mather
> wrote:
>
> > On Aug 3, 2015, at 1
Have you tried it on HEAD, and have you tried it on the same system with
some
recent flavor of Linux?
Jack
On Mon, Aug 3, 2015 at 8:35 AM, Paul Mather <
freebsd-li...@gromit.dlib.vt.edu> wrote:
> On Aug 3, 2015, at 11:09 AM, Alban Hertroys wrote:
>
> > On 3 August 2015 at
Set the storm threshold to 0, that way you disable the check and don't have
to wonder
if its a problem :)
Given everything you've told me I'd suspect the switch... easy enough to
test, remove it
from the equation, run two systems back-to-back and see how that effects
the numbers.
Make sure you are in slots with enough lanes/bandwidth, the driver should
complain when loaded
if you aren't though. Make sure you aren't getting interrupts throttled,
and that you have sufficient
mbuf resources so you aren't waiting on those, that can make a BIG
difference.
Jack
sysctl dev.ix.0 etc...
Jack
On Thu, Oct 3, 2013 at 12:35 PM, Rumen Telbizov wrote:
> Hello everyone,
>
> I am trying to tweak some of the sysctl tunables for the ix (ixgbe) driver
> in FreeBSD 9.2 since I am experiencing less than ideal performance and it
> seems like I
Thanks for the investigation, I guess what I'm wondering the most right now
is if the patch from
Oleg is a good change in general, so any others that can test and give me
results would be appreciated.
Thanks,
Jack
On Wed, Sep 25, 2013 at 11:14 AM, Rumen Telbizov wrote:
> Hi Jack,
&g
will check it out and have my validation
engineer do some tests and
we'll get to the bottom of this.
Jack
On Wed, Sep 25, 2013 at 9:57 AM, Rumen Telbizov wrote:
> Thanks for the patch Oleg.
> I'll give it a try but I would also like to hear back from Jack.
>
> Oleg,
I will look into this.
Jack
On Tue, Sep 24, 2013 at 5:16 PM, Rumen Telbizov wrote:
> Hello Jack, list,
>
> I've been dealing with a nagging problem for a day now and decided to ask a
> quick question here.
>
> Basically I am building a brand new FreeBSD 9.1-RELEASE ro
ixgb is the old PCI-X based adapter, ixgbe is for all pci express hardware.
The latter is almost certainly what you want :)
Jack
On Tue, Sep 3, 2013 at 6:24 AM, Daniel Braniss wrote:
> hi,
> I have a hard time figuring this out, the kernel says:
> ...
> ix0: port
> 0x
r you will be ready to send the whole chain to the stack.
Its good that you are using ONEBUF since packet split has hardware issues
on 82599.
Are you developing a new driver, or simply having issues using mine?
Regards,
Jack
On Sun, Jul 7, 2013 at 2:24 AM, Kaushal Bhandankar wrote:
> In 82
roblem at
times with those that is corrected in recent shared code, this is why you
should try the
latest code.
Cheers,
Jack
On Wed, May 15, 2013 at 2:00 AM, dennis berger wrote:
> Hi list,
> since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now
> on 9.1 we recog
link:
http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-controller-statement
Any questions or concerns may be sent to me.
Cheers,
Jack
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman
Hi,
In this mailinglist I'm reading a lot about problems (re)compiling the system.
At this moment I'm running:
"FreeBSD 9.1-PRERELEASE (ORAC) #0 r244047: Sun Dec 9 15:33:19 CET 2012"
without problems.
Is it save to recompile the system with all patches
Try putting the driver from 9.1 back onto 8.3 and see if you still
see a problem. That will indicate if its in the driver or the stack/OS.
If you have any question about doing this send me email.
Is NFS using UDP or TCP?
Regards,
Jack
On Thu, Dec 13, 2012 at 8:05 AM, Daniel Braniss wrote
On Tue, Nov 27, 2012 at 4:04 PM, Zaphod Beeblebrox wrote:
> To Jack Vogel's comment, this problem only seems to occur on systems
> that are exceedingly lightly loaded (in this case, not yet in
> production and I'm the only one using it).
>
> On Tue, Nov 27, 2012 at
Something in your environment, have lots of users with this driver in very
demanding
environments and I have not been seeing reports of this sort.
Jack
On Tue, Nov 27, 2012 at 2:27 PM, Zaphod Beeblebrox wrote:
> I've got an Intel server motherboard with 4x igb (and 1x em) on i
broken design??
There is nothing you can do about this because the issue is in the host,
not the guest,
well getting the host code fixed is the solution :)
Hope this helps,
Jack
On Tue, Oct 23, 2012 at 2:12 PM, Marius Strobl wrote:
> On Tue, Oct 23, 2012 at 11:49:45AM +0200, Harald Schmalzba
On Wed, Sep 12, 2012 at 1:51 PM, Freddie Cash wrote:
> On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel wrote:
> > On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash
> wrote:
> >> Thanks for checking. I've used lagg(4) with igb, just not on 9.x.
> >>
> >>
gt; ifconfig_lagg0_alias0="inet 192..."
> >>
> >> I've had problems in the past with cloned interfaces not working right
> >> if you do everything in one ifconfig line. Never spent much time
> >> debugging it, though, as the split
On Fri, Sep 7, 2012 at 10:44 AM, Harald Schmalzbauer <
h.schmalzba...@omnilan.de> wrote:
> schrieb Jack Vogel am 07.09.2012 18:53 (localtime):
> > OH, now things are clearer, this is a client part, and it is supported
> > by the em driver,
> > I don't know why l
hipset
that are not being given to the guest, b) there is no real gain with this
hardware doing this,
you can get performance using the normal virtual device connection.
Bottom line, its possible this could be made to work, but I've not done it,
and its not
something I'm able to support.
nvironment.
Widely spread, uh ya, but not virtualized, so tell me more about the
environment.
Jack
On Thu, Sep 6, 2012 at 3:05 PM, Harald Schmalzbauer <
h.schmalzba...@omnilan.de> wrote:
> Hello,
>
> I'm playing with releng_9_1 on a neat intel server, pre-production.
> Since E
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,
> >>
>
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,
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.
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
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
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
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
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
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,
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
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
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
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
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
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
-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
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
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
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 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
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 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
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
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
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
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/
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"
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
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,
>
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
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
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
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
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
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:
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
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
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
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
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"
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:
> >
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
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,
>
.
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
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!
- Original Message -
From: "Jack Raats"
Subject: Old system keeps coming back
At this moment I hiring a FreeBSD server running FreeBSD 7.2.
After running cvsup, updating sources and ports, compiling the complete
system, installing kernel and the "new world",
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"
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
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
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
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
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
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
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
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
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 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
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
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:
>
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
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
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
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
1 - 100 of 436 matches
Mail list logo
