On 29/11/2013 02:02, Nilton Jose Rizzo wrote:
in the near past, when I update ports repository via svn, I always use
pkg2ng to upgrade (or update?) the database, but today I can not do it.
Uh? pkg2ng is a one time thing. Its only use is when converting a
system that had previously used
Edit the Makefile to include USE_GCC= yes - sans quotation marks - with
nvi or another editor.
Some programs will not compile with the new Clang default.
On Sat, Nov 23, 2013 at 7:48 AM, Ajtim lum...@gmail.com wrote:
Hi!
I tried to build some programs on FreeBSD 10.0-BETA3 and as they told
On Sunday 24 November 2013 11:41:30 Joe Nosay wrote:
Edit the Makefile to include USE_GCC= yes - sans quotation marks - with
nvi or another editor.
Some programs will not compile with the new Clang default.
On Sat, Nov 23, 2013 at 7:48 AM, Ajtim lum...@gmail.com wrote:
Hi!
I tried
Give me a moment
On Sun, Nov 24, 2013 at 12:31 PM, Ajtim lum...@gmail.com wrote:
On Sunday 24 November 2013 11:41:30 Joe Nosay wrote:
Edit the Makefile to include USE_GCC= yes - sans quotation marks - with
nvi or another editor.
Some programs will not compile with the new Clang default.
You need to have thew output in a text such as make output.txt in
order for others to know what is going on with your system.
On Sun, Nov 24, 2013 at 2:11 PM, Joe Nosay superbisq...@gmail.com wrote:
Give me a moment
On Sun, Nov 24, 2013 at 12:31 PM, Ajtim lum...@gmail.com wrote:
On
On Sunday 24 November 2013 14:14:46 Joe Nosay wrote:
You need to have thew output in a text such as make output.txt in
order for others to know what is going on with your system.
On Sun, Nov 24, 2013 at 2:11 PM, Joe Nosay superbisq...@gmail.com wrote:
Give me a moment
On Sun, Nov
-- Forwarded Message --
Subject: Re: problems
Date: Sunday 24 November 2013, 17:02:32
From: Ajtim lum...@gmail.com
To: Stefan Esser s...@freebsd.org
On Sunday 24 November 2013 21:21:29 you wrote:
The linker does no longer automatically load indirectly required
libraries
Em Mon, 16 Sep 2013 17:53:06 -0700, John-Mark Gurney escreveu
Nilton Jose Rizzo wrote this message on Mon, Sep 16, 2013 at 20:26 -0300:
Em Mon, 16 Sep 2013 16:07:28 -0700, John-Mark Gurney escreveu
Nilton Jose Rizzo wrote this message on Sun, Sep 15, 2013 at 13:14 -0300:
Last
Nilton Jose Rizzo wrote this message on Sun, Sep 15, 2013 at 13:14 -0300:
Last night, I has tried to put in my kernel config the libiconv with this
knobs from LINT:
options CD9660_ICONV
options MSDOSFS_ICONV
options UDF_ICONV
options LIBICONV
but this
On Wed, 21 Aug 2013 21:49+0200, Dimitry Andric wrote:
Hi,
While packaging my just-rebuilt ports today, I noticed a strange message
occurring during the package creation stage:
$ sudo make -C /usr/ports/ports-mgmt/pkg repackage
=== Building package for pkg-1.1.4_1
Creating package for
On 8/21/2013 2:49 PM, Dimitry Andric wrote:
Hi,
While packaging my just-rebuilt ports today, I noticed a strange message
occurring during the package creation stage:
$ sudo make -C /usr/ports/ports-mgmt/pkg repackage
=== Building package for pkg-1.1.4_1
Creating package for pkg-1.1.4_1
On Sat, Mar 28, 2009 at 11:00:32AM +0100, Hans Petter Selasky wrote:
On Saturday 28 March 2009, Lars Engels wrote:
Hi all,
yesterday I bought a shiny new hama usb bluetooth dongle but I am having
some problems using it:
before loading ng_ubt:
usb2_alloc_device:1480: set address 2
Hi YongHyeon,
Without natd this seems to work fine (both on RELEASE and CURRENT).
Both my Hong-Kong no-name and Edimax EU-4208 seem to behave the same.
This works with natd on RELEASE as well, but just for a limited time.
I've yet to establish if it's time or #packets that cause the
processing
Hello, Lev.
You wrote 17 мая 2013 г., 0:03:30:
LS Problem is, that when WITHOUT_CLANG is set, all warning-suppression
LS options are set as fro GCC. What is plainly wrong. buildworld fails:
Setting COMPILER_TYPE=clang seems to help (build is not finished
yet, but passes first fail point).
On Sat, May 11, 2013 at 12:04:09AM +0400, Gleb Smirnoff wrote:
Spil,
On Fri, May 10, 2013 at 09:06:35AM +0200, Spil Oss wrote:
S There seems to be quite a bit of overhaul on the firewall code, pf and
S ipfw have been moved to sys/netpfil? Can there be some regressions in
S there that I
Hi,
There seems to be quite a bit of overhaul on the firewall code, pf and
ipfw have been moved to sys/netpfil? Can there be some regressions in
there that I hit?
Just upgraded to r250404 but that does not help. Should I file a PR?
Kind regards,
Spil.
On Thu, May 9, 2013 at 10:56 AM, Spil Oss
Spil,
On Fri, May 10, 2013 at 09:06:35AM +0200, Spil Oss wrote:
S There seems to be quite a bit of overhaul on the firewall code, pf and
S ipfw have been moved to sys/netpfil? Can there be some regressions in
S there that I hit?
Yes, a regression is possible there. However, the issue seems to
Hi all,
So I bought another AX88772B part, this time an Edimax UE-4208 and it
behaved exactly like the no-name part I bought on eBay.
Looking at YongHyeong's feedback on his engineering sample I decided
to revert back to 9.1-RELEASE and try again, this works like expected.
(see my post
Problems
On Sat, Apr 13, 2013 at 03:25:11PM +0200, Spil Oss wrote:
Hi YongHyeon,
Will post on freebsd-ipfw@ as well...
Does your engineering sample function normally with rxcsum/txcsum disabled?
Yes.
Kind regards,
Spil.
On Thu, Apr 11, 2013 at 3:11 AM, YongHyeon PYUN pyu...@gmail.com
Hi YongHyeon,
Will post on freebsd-ipfw@ as well...
Does your engineering sample function normally with rxcsum/txcsum disabled?
Kind regards,
Spil.
On Thu, Apr 11, 2013 at 3:11 AM, YongHyeon PYUN pyu...@gmail.com wrote:
On Wed, Apr 10, 2013 at 07:48:00PM +0200, Spil Oss wrote:
Hi
Hi YongHyeon,
With the original unmodified .ko...
ifconfig output as requested at bottom
Static IP-configuration does not make a difference with the ipfw behaviour.
ipfw ruleset (based on /etc/rc.firewall simple ruleset)
00010 allow ip from any to me dst-port 22 recv ue0
00010 allow tcp from
On Wed, Apr 10, 2013 at 07:48:00PM +0200, Spil Oss wrote:
Hi YongHyeon,
With the original unmodified .ko...
ifconfig output as requested at bottom
Static IP-configuration does not make a difference with the ipfw behaviour.
ipfw ruleset (based on /etc/rc.firewall simple ruleset)
00010
On Mon, Apr 08, 2013 at 08:45:58PM +0200, Spil Oss wrote:
Hi YongHyeon,
output from verbose boot
ugen3.2: vendor 0x0b95 at usbus3
axe0: vendor 0x0b95 product 0x772b, rev 2.00/0.01, addr 2 on usbus3
axe0: PHYADDR 0xe0:0x10
miibus1: MII bus on axe0
ukphy0: Generic IEEE 802.3u media
On Sun, Apr 07, 2013 at 09:14:16PM +0200, Spil Oss wrote:
Hi all,
With checksum offloading enabled I cannot use my axe NIC (ASIX AX88772B).
ifconfig ue0 -txcsum -rxcsum
will make dhclient ue0 return
if I re-enable txcsum and rxcsum I get an immediate response from the dhcp
server.
Hi YongHyeon,
output from verbose boot
ugen3.2: vendor 0x0b95 at usbus3
axe0: vendor 0x0b95 product 0x772b, rev 2.00/0.01, addr 2 on usbus3
axe0: PHYADDR 0xe0:0x10
miibus1: MII bus on axe0
ukphy0: Generic IEEE 802.3u media interface PHY 16 on miibus1
ukphy0: OUI 0x007063, model 0x0008, rev. 1
... ath_ahb is only needed for MIPS platforms. Why are you building it for x86?
Also, do you have the 5416 support option in your kernel?
adrian
On 4 January 2013 20:37, Super Bisquit superbisq...@gmail.com wrote:
In sys/modules/svr4 needs machine/_align.h to read
X86/include/_align.h, if
I did not know that ath_ahb was MIPS only. Why? I wanted the most/best
performance for my system's wireless.
Support for 5416 is there but the card is a 2413.
On Sat, Jan 5, 2013 at 12:03 AM, Adrian Chadd adr...@freebsd.org wrote:
... ath_ahb is only needed for MIPS platforms. Why are you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2012 09:29, Dimitry Andric wrote:
On 2012-12-07 17:43, Mark Atkinson wrote:
On 12/7/2012 6:08 AM, Dimitry Andric wrote:
...
With this patch (placed in /usr/ports/devel/dbus-qt4/files),
qdbus starts up and exits normally for me. I did
On Mon, Dec 10, 2012 at 09:35:29AM -0800, Mark Atkinson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2012 09:29, Dimitry Andric wrote:
On 2012-12-07 17:43, Mark Atkinson wrote:
On 12/7/2012 6:08 AM, Dimitry Andric wrote:
...
With this patch (placed in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2012 10:25, Konstantin Belousov wrote:
On Mon, Dec 10, 2012 at 09:35:29AM -0800, Mark Atkinson wrote: On
12/07/2012 09:29, Dimitry Andric wrote:
On 2012-12-07 17:43, Mark Atkinson wrote:
On 12/7/2012 6:08 AM, Dimitry Andric wrote:
...
On Mon, Dec 10, 2012 at 12:29:20PM -0800, Mark Atkinson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2012 10:25, Konstantin Belousov wrote:
On Mon, Dec 10, 2012 at 09:35:29AM -0800, Mark Atkinson wrote: On
12/07/2012 09:29, Dimitry Andric wrote:
On 2012-12-07 17:43,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2012 12:33, Konstantin Belousov wrote:
Hmm. Since I took out -O2 and added -g in rebuilding
libthr/libc/rtld, I figured I needed to reproduce a new segfault,
but the rtld side of things seems broken:
Use e.g. cd src/libexec/rtld-elf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2012 12:45, Mark Atkinson wrote:
On 12/10/2012 12:33, Konstantin Belousov wrote:
Hmm. Since I took out -O2 and added -g in rebuilding
libthr/libc/rtld, I figured I needed to reproduce a new
segfault, but the rtld side of things seems
On Mon, Dec 10, 2012 at 01:13:23PM -0800, Mark Atkinson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2012 12:45, Mark Atkinson wrote:
On 12/10/2012 12:33, Konstantin Belousov wrote:
Hmm. Since I took out -O2 and added -g in rebuilding
libthr/libc/rtld, I figured I
On Mon, Dec 10, 2012 at 12:35 PM, Mark Atkinson atkin...@gmail.com wrote:
vex x86-IR: unhandled instruction bytes: 0xF 0xB 0x90 0x90
==33074== valgrind: Unrecognised instruction at address 0x380434e9.
==33074==at 0x380434E9: ??? (in
/usr/local/lib/valgrind/memcheck-x86-freebsd)
==33074==
On 2012-12-06 18:12, Mark Atkinson wrote:
Short backstory, I had recently upgraded my workstation to the latest
current which included clang as default cc now.
...
qdbus under kde segfaults in malloc with a huge recursion stack:
[...]
#44740 0x282f7bd4 in QObject::QObject () from
On 2012-12-07 13:59, Dimitry Andric wrote:
On 2012-12-06 18:12, Mark Atkinson wrote:
Short backstory, I had recently upgraded my workstation to the latest
current which included clang as default cc now.
...
qdbus under kde segfaults in malloc with a huge recursion stack:
...
This is a bug
On 12/7/2012 6:08 AM, Dimitry Andric wrote:
On 2012-12-07 13:59, Dimitry Andric wrote:
On 2012-12-06 18:12, Mark Atkinson wrote:
Short backstory, I had recently upgraded my workstation to the latest
current which included clang as default cc now.
...
qdbus under kde segfaults in malloc
On 2012-12-07 17:43, Mark Atkinson wrote:
On 12/7/2012 6:08 AM, Dimitry Andric wrote:
...
With this patch (placed in /usr/ports/devel/dbus-qt4/files), qdbus
starts up and exits normally for me. I did not do any other rigorous
testing, though. :)
Thanks for the awesome analysis. I will
Dimitry Andric wrote:
On 2012-12-07 13:59, Dimitry Andric wrote:
On 2012-12-06 18:12, Mark Atkinson wrote:
Short backstory, I had recently upgraded my workstation to the latest
current which included clang as default cc now.
...
qdbus under kde segfaults in malloc with a huge recursion
It may have been the media I used. I was able to install from the
releases on your FreeBSD repo page.
I have an iMac G4 800MHz that is being used.
Also, the firmware is at 3.X if that means anything.
On 2/19/12, Nathan Whitehorn nwhiteh...@freebsd.org wrote:
On 02/19/12 04:28, Super Bisquit
On 02/19/12 04:28, Super Bisquit wrote:
I decided to try burning an image from Index of
ftp://ftp.freebsd.org/pub/FreeBSD/releases/powerpc/powerpc/ISO-IMAGES/9.0/
And here are the following errors:
1.) The usb image doesn't boot. From following Whitehorn and others on
the FreeBSD PowerPC
On Sun, Jan 22, 2012 at 05:19:11PM -0500, Michael Butler wrote:
On 01/22/12 12:46, Super Bisquit wrote:
No dice, people. It isn't doing diddly.
You did, of course, reboot after adding the license ack to
/boot/loader.conf ..
No need to reboot:
# kenv legal.intel_iwi.license_ack=1
Sets the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/12 09:51, Super Bisquit wrote:
# sysctl legal.intel_iwi.license_ack=1
sysctl: unknown oid 'legal.intel_iwi.license_ack'
On 9.0, the XML type input does not include the intel license.
I switched to 8.2 thinking that it was the
No dice, people. It isn't doing diddly.
# ifconfig -a
iwi0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290
ether 00:0e:35:53:a9:fe
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
fwe0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/12 12:46, Super Bisquit wrote:
No dice, people. It isn't doing diddly.
You did, of course, reboot after adding the license ack to
/boot/loader.conf ..
imb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (FreeBSD)
Comment:
On 01/22/12 15:51, Super Bisquit wrote:
# sysctl legal.intel_iwi.license_ack=1
sysctl: unknown oid 'legal.intel_iwi.license_ack'
You should put it in your loader.conf.
[t43:~] andreast% cat /boot/loader.conf
legal.intel_iwi.license_ack=1
Given that your were looking on how to make iwi
Yes, it is corrected now. I was missing the firmware ko.
Thanks.
On 1/22/12, Michael Butler i...@protected-networks.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/12 12:46, Super Bisquit wrote:
No dice, people. It isn't doing diddly.
You did, of course, reboot after
On Tue, Oct 25, 2011 at 05:01:31PM +0200, Jason Edwards wrote:
On Tue, Oct 25, 2011 at 4:35 PM, Nikolay Denev nde...@gmail.com wrote:
I was struck with this problem too yesterday.
I was able to import the pool by specifying the directory where zpool
should look for devices.
Like : zpool
On Oct 25, 2011, at 4:38 PM, Jason Edwards wrote:
Hello list,
I'm working on ZFSguru, a FreeNAS-like distribution based on FreeBSD
that focuses on NAS or Network Attached Storage functionality,
sporting a web-interface et al.
I've been building FreeBSD 9.0-RC1, and put together a LiveCD
On Tue, Oct 25, 2011 at 4:35 PM, Nikolay Denev nde...@gmail.com wrote:
I was struck with this problem too yesterday.
I was able to import the pool by specifying the directory where zpool should
look for devices.
Like : zpool import -d /dev/gptid
Alternatively you can try putting
on 02/09/2011 01:29 Nathan Whitehorn said the following:
On 09/01/11 17:23, Matt Thyer wrote:
Probably the real solution is to use MBR and have BSDinstall and the install
kernel support UFS labels. Space on the memstick is not an issue.
Both support that. The issue is makefs(8).
Here's a
Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
We won't need larger than 2TiB installation media for many decades!
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
On Sep 1, 2011, at 12:00 PM, Matt Thyer wrote:
Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
They aren't exclusive. Anything which doesn't understand GPT should
fall back to the 'protective' MBR kept inside the GPT format...
Regards,
--
-Chuck
On 09/01/11 14:00, Matt Thyer wrote:
Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
We won't need larger than 2TiB installation media for many decades!
It uses GPT so that the partition can be labeled, and fstab will not
need e.g. da0 hard-coded into it. makefs,
On Sep 1, 2011, at 12:00 PM, Matt Thyer wrote:
Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
We won't need larger than 2TiB installation media for many decades!
Or just don't use a backup partition? Maybe dd conv=sync would help?
Thanks,
-Garrett
On Sep 2, 2011 4:35 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote:
On 09/01/11 14:00, Matt Thyer wrote:
Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
We won't need larger than 2TiB installation media for many decades!
It uses GPT so that the partition can
On Thu, 1 Sep 2011, Garrett Cooper wrote:
On Sep 1, 2011, at 12:00 PM, Matt Thyer wrote:
Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
We won't need larger than 2TiB installation media for many decades!
Or just don't use a backup partition? Maybe dd
On Thu, Sep 1, 2011 at 12:25 PM, Matt Thyer matt.th...@gmail.com wrote:
On Sep 2, 2011 4:35 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote:
On 09/01/11 14:00, Matt Thyer wrote:
Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
We won't need larger than 2TiB
On Sep 2, 2011 5:25 AM, Warren Block wbl...@wonkity.com wrote:
On Thu, 1 Sep 2011, Garrett Cooper wrote:
On Sep 1, 2011, at 12:00 PM, Matt Thyer wrote:
Shouldn't we use MBR partitioning instead of GPT for the memstick image
?
It seems wrong to have gptboot just ignore backup GPT data, but
On 09/01/11 17:23, Matt Thyer wrote:
On Sep 2, 2011 5:25 AM, Warren Blockwbl...@wonkity.com wrote:
On Thu, 1 Sep 2011, Garrett Cooper wrote:
On Sep 1, 2011, at 12:00 PM, Matt Thyer wrote:
Shouldn't we use MBR partitioning instead of GPT for the memstick image
?
It seems wrong to have
On Sep 2, 2011 7:59 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote:
On 09/01/11 17:23, Matt Thyer wrote:
On Sep 2, 2011 5:25 AM, Warren Blockwbl...@wonkity.com wrote:
On Thu, 1 Sep 2011, Garrett Cooper wrote:
On Sep 1, 2011, at 12:00 PM, Matt Thyer wrote:
Shouldn't we use MBR
On Tue, 30 Aug 2011, Jason Campbell wrote:
Downloaded FreeBSD-9.0-BETA1-amd64-memstick.img and verified the image
with md5sum. I wrote the image (from Linux):
dd if=FreeBSD.img of=/dev/sde bs=512
Rebooted and get gptboot: Invalid backup GPT header
Same here, although it ran normally. The
On 07/03/2011 03:51 PM, Stephen Montgomery-Smith wrote:
On 07/02/2011 10:25 PM, jhell wrote:
Use csup(1) in base. This is in 7, 8 9. cvsup has been deprecated for
much longer than it really needed to be and should probably be removed
from use as a client entirely and links generated for
On 02/07/2011 17:07, Garrett Cooper wrote:
On Sat, Jul 2, 2011 at 8:33 AM, Vassilis Laganakos
vassilis.lagana...@yahoo.com wrote:
Hello,
I am facing the same problems as Holger here:
http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025205.html
although CVSup dies in gmtime_r in
On 02/07/2011 17:54, Kurt Jaeger wrote:
Hi!
Any quick ideas on how to correct this, or if someone else is seeing
this issue?
Does csup work ?
Yeah! That works!
I see that csups is part of the build system. So is this to replace the
cvsup port?
Thanks,
Vassilis L.
On 03/07/2011 04:25, jhell wrote:
On Sat, Jul 02, 2011 at 04:33:39PM +0100, Vassilis Laganakos wrote:
Hello,
I am facing the same problems as Holger here:
http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025205.html
although CVSup dies in gmtime_r in libc.so.7:
...
On 07/02/2011 10:25 PM, jhell wrote:
Use csup(1) in base. This is in 7, 8 9. cvsup has been deprecated for
much longer than it really needed to be and should probably be removed
from use as a client entirely and links generated for installation of
cvsup - csup.
Only drawback for you may be
W dniu 2011-06-15 14:23, Holger Kipp pisze:
Dear all,
I had installed FreeBSD 9 amd64 from snapshot (ISO-image) located here:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201101/FreeBSD-9.0-CURRENT-201101-amd64-dvd1.iso
Today I wanted to cvsup to a later date to upgrade to ZFS v28
and compiled
W dniu 2011-06-15 14:23, Holger Kipp pisze:
Have now used csup instead of cvsup (which seems to have worked fine), and started cvsup
once again (seems cvsup only gives Illegal Instruction when a file needs to
be changed...).
Any ideas?
Whoops, I read your message too fast, apologize. Please
On 6/15/11 8:23 AM, Holger Kipp wrote:
Dear all,
I had installed FreeBSD 9 amd64 from snapshot (ISO-image) located here:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201101/FreeBSD-9.0-CURRENT-201101-amd64-dvd1.iso
Today I wanted to cvsup to a later date to upgrade to ZFS v28
and compiled
On Wed, Jun 15, 2011 at 10:24:46AM -0400, Eric McCorkle wrote:
On 6/15/11 8:23 AM, Holger Kipp wrote:
Dear all,
I had installed FreeBSD 9 amd64 from snapshot (ISO-image) located here:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201101/FreeBSD-9.0-CURRENT-201101-amd64-dvd1.iso
Today I
On 6/15/11 10:46 AM, Holger Kipp wrote:
Ah, ok.
Do we have a compiler switch to force stack alignment to 16-Byte-boundaries?
Otherwise I am really concerned that we might have similar wrong pieces of code
lurking unnoticed in other binaries as well :-/
My cvsup binary is:
# file
On 6/15/11 10:58 AM, Kostik Belousov wrote:
On Wed, Jun 15, 2011 at 10:24:46AM -0400, Eric McCorkle wrote:
On 6/15/11 8:23 AM, Holger Kipp wrote:
Dear all,
I had installed FreeBSD 9 amd64 from snapshot (ISO-image) located here:
Hi,
On Thu, May 5, 2011 at 1:20 AM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, May 4, 2011 at 5:38 PM, Jack Vogel jfvo...@gmail.com wrote:
I have had my validation engineer busy all day, we have tried both
a 9 kernel as well as 8.2, using the code from HEAD, and we
cannot
OK, but what this does not explain is why I do not see this if
its so easily reproduced, what causes the failure case, any idea?
As I said, given the code was not feasible for igb anyway I would not
be unhappy about returning to the old way of doing things.
Jack
On Wed, May 4, 2011 at 11:03
Hello,
2011/5/4 Arnaud Lacombe lacom...@gmail.com:
Hi,
On Wed, May 4, 2011 at 3:58 AM, Olivier Smedts oliv...@gid0.org wrote:
em0: Using an MSI interrupt
em0: Ethernet address: d4:85:64:b2:aa:f5
em0: Could not setup receive structures
em0: Could not setup receive structures
What can we
Hello,
(sorry for dual posting)
2011/5/4 Jack Vogel jfvo...@gmail.com:
I have had my validation engineer busy all day, we have tried both
a 9 kernel as well as 8.2, using the code from HEAD, and we
cannot reproduce this problem.
The data your netstat -m shows suggests to me that what's
Hi,
On Thu, May 5, 2011 at 2:59 AM, Jack Vogel jfvo...@gmail.com wrote:
OK, but what this does not explain is why I do not see this if
its so easily reproduced, what causes the failure case, any idea?
It is completely random as it depends on the content of the stack. I
spent 3 or 4 hours
Hi,
On Wed, May 4, 2011 at 3:00 AM, Alastair Hogge a...@fastmail.fm wrote:
[.]
I also tried 2x, 4x 25600 for max mbuff clusters via kern.ipc.nmbclusters.
This didn't help.
For the record, I did the math yestarday, checked the code. By
default, a machine with 6 82574L-backed em(4) interfaces,
On Thu, May 5, 2011 at 7:21 AM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Thu, May 5, 2011 at 2:59 AM, Jack Vogel jfvo...@gmail.com wrote:
OK, but what this does not explain is why I do not see this if
its so easily reproduced, what causes the failure case, any idea?
It is
2011/5/5 Jack Vogel jfvo...@gmail.com:
Anyway, I see the problematic code path, its only when
you skip the while loop altogether. I'm surprised the compiler
did not complain about this, its usually so anal.
Could it be related to the compiler (clang) or some optimization flags ?
--
Olivier
Not sure, I wondered if those seeing this had some special sequence of
actions they took for granted that is different than what we do in house...
In any case, the init really is ultimately a correctness thing, so let's
just
call it good :)
Jack
On Thu, May 5, 2011 at 11:16 AM, Olivier Smedts
2011/5/4 Jack Vogel jfvo...@gmail.com:
It has nothing to do with load, it has to do with the prerequisites to init
your interfaces.
The amount you need is fixed, it doesn't vary with load. Every RX descriptor
needs one,
so its simple math, number-of-interfaces X number-of-queues X size of the
On Tue, May 03, 2011 at 11:50:53PM +0200, Michael Schmiedgen wrote:
On 03.05.2011 23:24, Jack Vogel wrote:
If you get the setup receive structures fail, then increase the nmbclusters.
If you use standard MTU then what you need are mbufs, and standard size
clusters (2K).
Only when you
Hi,
On Wed, May 4, 2011 at 3:58 AM, Olivier Smedts oliv...@gid0.org wrote:
em0: Using an MSI interrupt
em0: Ethernet address: d4:85:64:b2:aa:f5
em0: Could not setup receive structures
em0: Could not setup receive structures
What can we do to help you debug this ?
At some point in time, in
Hi,
On Tue, May 3, 2011 at 7:25 PM, Olivier Smedts oliv...@gid0.org wrote:
2011/5/4 Arnaud Lacombe lacom...@gmail.com:
A more rude version might be Why the frak my network adapter stopped
working with the default setting ? :)
...on a -STABLE branch
Maybe you should not have picked the rude
No, I do not Arnaud. But I refuse to rise to rude and uncivil behavior. Its
your
behavior again and again which causes you to not get responses, not my
willingness to help and respond to those that behave like respectful
customers
and adults.
Jack
On Wed, May 4, 2011 at 10:20 AM, Arnaud
Hi,
On Wed, May 4, 2011 at 1:24 PM, Jack Vogel jfvo...@gmail.com wrote:
No, I do not Arnaud. But I refuse to rise to rude and uncivil behavior. Its
your
behavior again and again which causes you to not get responses, not my
willingness to help and respond to those that behave like respectful
2011/5/4 Arnaud Lacombe lacom...@gmail.com:
Obviously, I am no longer the only one finding that em(4) has
unacceptable issue, this thread is the proof.
Right, and Jack seems to be willing to help, he asked something (I'll
reply tomorrow when I'll be in front of the hardware) and is trying to
I have had my validation engineer busy all day, we have tried both
a 9 kernel as well as 8.2, using the code from HEAD, and we
cannot reproduce this problem.
The data your netstat -m shows suggests to me that what's happening
is somehow setup of the receive ring is running more than once maybe??
Hi,
On Wed, May 4, 2011 at 5:38 PM, Jack Vogel jfvo...@gmail.com wrote:
I have had my validation engineer busy all day, we have tried both
a 9 kernel as well as 8.2, using the code from HEAD, and we
cannot reproduce this problem.
The data your netstat -m shows suggests to me that what's
Hi,
On Wed, May 4, 2011 at 5:38 PM, Jack Vogel jfvo...@gmail.com wrote:
I have had my validation engineer busy all day, we have tried both
a 9 kernel as well as 8.2, using the code from HEAD, and we
cannot reproduce this problem.
Actually, it can be trivially reproduced by tainting `error'.
Hello,
2011/4/27 Jack Vogel jfvo...@gmail.com:
If you get cannot setup receive structures you cannot go on and try to
use the thing :) It means you have inadequate mbuf clusters to setup
your receive side, you simply have to increase it and reload the driver.
I tried increasing
If you get the setup receive structures fail, then increase the nmbclusters.
If you use standard MTU then what you need are mbufs, and standard size
clusters (2K).
Only when you use jumbo frames will you need larger.
You must configure enough, its that simple.
Jack
On Tue, May 3, 2011 at 2:13
Hi,
I have the very same problem.
- GENERIC 9.0-CURRENT (April 28)
- em0 PRO/1000 7.2.3
- em0: Could not setup receive structures
On 03.05.2011 10:58, Olivier Smedts wrote:
I tried increasing kern.ipc.nmbjumbo* (is it what you suggested ?).
Values doubled :
kern.ipc.nmbjumbo16: 6400
On 03.05.2011 23:24, Jack Vogel wrote:
If you get the setup receive structures fail, then increase the nmbclusters.
If you use standard MTU then what you need are mbufs, and standard size
clusters (2K).
Only when you use jumbo frames will you need larger.
You must configure enough, its that
It has nothing to do with load, it has to do with the prerequisites to init
your interfaces.
The amount you need is fixed, it doesn't vary with load. Every RX descriptor
needs one,
so its simple math, number-of-interfaces X number-of-queues X size of the
ring.
If you have other network interfaces
2011/5/4 Arnaud Lacombe lacom...@gmail.com:
A more rude version might be Why the frak my network adapter stopped
working with the default setting ? :)
...on a -STABLE branch
--
Olivier Smedts _
ASCII
Hi Jack,
On Tue, May 3, 2011 at 6:00 PM, Jack Vogel jfvo...@gmail.com wrote:
It has nothing to do with load, it has to do with the prerequisites to init
your interfaces.
The amount you need is fixed, it doesn't vary with load. Every RX descriptor
needs one,
so its simple math,
101 - 200 of 668 matches
Mail list logo
