Kernel panic: Need help debugging

Hi! I can get the kernel to panic when I try to run virtualbox (selecting the amd64 ubuntu iso and attaching to virtual machine and starting it up.). The kernel: 12.0-ALPHA3 FreeBSD 12.0-ALPHA3 #0 r338359: Wed Aug 29 21:49:53 EDT 2018 someone@somebox:/usr/obj/usr/src/amd64.amd64/sys/GENERIC

Re: need help using ng_patch to modify src/dst packets or alternative way

17.12.2017 17:59, Sami Halabi wrote: > Hi Eugene, > I'm looking for a solution for IP traffic. in linux iptables its possible but > I couldn't find freebsd way yet. > bkuncr soulution works for tcp only. Then, you need to realize that for every packet, you need to change (translate) both of sour

Re: need help using ng_patch to modify src/dst packets or alternative way

Hi Eugene, I'm looking for a solution for IP traffic. in linux iptables its possible but I couldn't find freebsd way yet. bkuncr soulution works for tcp only. Thanks for the hint though, Sami בתאריך 17 בדצמ׳ 2017 11:29 AM,‏ "Eugene Grosbein" כתב: > 17.12.2017 14:52, Sami Halabi пишет: > > hi,

need help using ng_patch to modify src/dst packets or alternative way

hi, Can you help in my situation? My goal is so Box in my lan 10.1.1.2 to talk to 10.1.1.1 and actually it would be talking to X.X.X.X outside ip using one of my public IPs say 1.1.1.1. I'm trying to modify packets to passthrough to a local IP. I have a box that a specific IP is routed to it.. sa

Need help debugging rc script

Hello, I'm dealing with an odd issue with an rc script working pre-11. The change that is causing the prog to fail seems to be the new limits feature, $name_login_class. After commenting out the limits command in rc.subr, the script starts as expected. Adding limits directly in the rc script with

Re: Need help with New Build -- Skylake

On 12/24/15, Konstantin Belousov wrote: > On Thu, Dec 24, 2015 at 08:29:20AM -0700, Ian Lepore wrote: >> We had exactly this symptom -- long delay with spincursor before >> loading the kernel -- on arm systems when we first enabled forth in >> loader. The problem turned out to be the fact that lo

Re: Need help with New Build -- Skylake

On Thu, Dec 24, 2015 at 08:29:20AM -0700, Ian Lepore wrote: > We had exactly this symptom -- long delay with spincursor before > loading the kernel -- on arm systems when we first enabled forth in > loader. The problem turned out to be the fact that loader was running > with instruction and data c

Re: Need help with New Build -- Skylake

On Thu, 24 Dec 2015 13:28:51 +0530 Vijay Rajah wrote > On 12/24/15 12:22 PM, Ian Smith wrote: > > ~2 minutes delay there. sendmail (mta and msp both) at least > > are unhappy about your hostname, and sleep on it. I don't know whether > > that's significant or related to the longer delay you r

Re: Need help with New Build -- Skylake

On Thu, 2015-12-24 at 12:48 +0100, Oliver Pinter wrote: > On 12/24/15, Vijay Rajah wrote: > > > > > > On 12/24/15 12:22 PM, Ian Smith wrote: > > > ~2 minutes delay there. sendmail (mta and msp both) at least > > > are unhappy about your hostname, and sleep on it. I don't know > > > whether >

Re: Need help with New Build -- Skylake

On 12/24/15 5:18 PM, Oliver Pinter wrote: On 12/24/15, Vijay Rajah wrote: On 12/24/15 12:22 PM, Ian Smith wrote: ~2 minutes delay there. sendmail (mta and msp both) at least are unhappy about your hostname, and sleep on it. I don't know whether that's significant or related to the long

Re: Need help with New Build -- Skylake

On 12/24/15, Vijay Rajah wrote: > > > On 12/24/15 12:22 PM, Ian Smith wrote: >> ~2 minutes delay there. sendmail (mta and msp both) at least >> are unhappy about your hostname, and sleep on it. I don't know whether >> that's significant or related to the longer delay you report. I just >> ski

Re: Need help with New Build -- Skylake

On 12/24/15 12:22 PM, Ian Smith wrote: ~2 minutes delay there. sendmail (mta and msp both) at least are unhappy about your hostname, and sleep on it. I don't know whether that's significant or related to the longer delay you report. I just skimmed through your dmesg, but didn't spot anythi

Re: Need help with New Build -- Skylake

On 12/23/15 2:29 AM, Ed Maste wrote: On 22 December 2015 at 12:39, Vijay Rjah wrote: The only issue i have is that the boot process takes a lot of time.. (similar to https://forums.freebsd.org/threads/new-motherboard-and-processor-kernel-load-very-slow.53511/ ). the system ultimately boots, b

Re: Need help with New Build -- Skylake

22 дек. 2015 г. 23:00 пользователь "Ed Maste" написал: > > On 22 December 2015 at 12:39, Vijay Rjah wrote: > > > > The only issue i have is that the boot process takes a lot of time.. > > (similar to > > https://forums.freebsd.org/threads/new-motherboard-and-processor-kernel-load-very-slow.53511/

Re: Need help with New Build -- Skylake

On 22 December 2015 at 12:39, Vijay Rjah wrote: > > The only issue i have is that the boot process takes a lot of time.. > (similar to > https://forums.freebsd.org/threads/new-motherboard-and-processor-kernel-load-very-slow.53511/ > ). the system ultimately boots, but boot times are around 4 - 5 M

Re: Need help with New Build -- Skylake

On 12/19/15 4:23 PM, Vijay Rjah wrote: Hello, I'm planning to build a file server for my home. I'm planning on using the B150 Intel chipset (specifically this MoBo: http://www.msi.com/product/motherboard/B150M-PRO-VDH.html#hero-overview) This has Realtek RTL8111H Gigabit LAN controller, Do

Re: Need help fixing failing locale tests

Craig Rodrigues wrote: > I don't know much about locales, so don't know what to do. I find LANG=C LC_ALL=C solves most locale induced issues. I suspect the tests in question assume the above anyway. ___ freebsd-current@freebsd.org mailing list https://l

Re: Need help fixing failing locale tests

On 11/15/2015 4:38 PM, Andrey Chernov wrote: > On 15.11.2015 18:17, John Marino wrote: >> >> For the traditional checks, It's ironic, DragonFly uses short locales >> like "fr_FR" which link to the approprioprate ISO8859 or UTF-8 locale. >> Bapt removed them to avoid a bike shed and if he had not do

Re: Need help fixing failing locale tests

On 11/15/2015 3:59 PM, Andrey Chernov wrote: > On 15.11.2015 17:47, John Marino wrote: Please provide an example of such a program (in ports). >>> >>> See gettext-0.19.6/gettext-tools/configure, part started with >>> # Test for the usual locale name. >>> I don't have time to dig more such code

Re: Need help fixing failing locale tests

Documentation on any existing regressions and how they are expected to fail would be a good thing… Change is necessary, but so is modification of a regression to continue to pass (or fail) as expected. Demonstration of the unit testing process can also be very beneficial. : mdm > On Nov 15, 2015,

Re: Need help fixing failing locale tests

John Marino wrote on 11/15/2015 15:47: On 11/15/2015 3:39 PM, Andrey Chernov wrote: As I already say, I don't want to insist on any particular point of view in such area as human behavior. I just say that it is POLA violation (even while it is upgrade) and we can let users decide by themselves,

Re: Need help fixing failing locale tests

FWIW; While I personally don’t use it, Latin is the official language for the Holy See [1]. I think it is still taught in schools in Italy for cultural reasons and because it’s supposed to make easier to learn other “romance” languages. It shouldn't hurt to keep it but I have no strong opinion.

Re: Need help fixing failing locale tests

On 15.11.2015 18:38, Andrey Chernov wrote: >> For the traditional checks, It's ironic, DragonFly uses short locales >> like "fr_FR" which link to the approprioprate ISO8859 or UTF-8 locale. >> Bapt removed them to avoid a bike shed and if he had not done that, this >> gettext configure would not be

Re: Need help fixing failing locale tests

On 15.11.2015 18:17, John Marino wrote: See gettext-0.19.6/gettext-tools/configure, part started with # Test for the usual locale name. I don't have time to dig more such code now, but I remember I saw more for sure. > Of course it's the same topic. > If the configure of a port

Re: Need help fixing failing locale tests

On 11/15/2015 3:39 PM, Andrey Chernov wrote: > As I already say, I don't want to insist on any particular point of view > in such area as human behavior. I just say that it is POLA violation > (even while it is upgrade) and we can let users decide by themselves, > what it best for them (without me

Re: Need help fixing failing locale tests

On 15.11.2015 18:01, Baptiste Daroussin wrote: > I have restored the 8859-1 Thanx! BTW, speaking with John I find at least one configure script from ports which depends on 8859-1 presence. See gettext-0.19.6/gettext-tools/configure, part started with # Test for the usual locale name. -- http://a

Re: Need help fixing failing locale tests

On Sun, Nov 15, 2015 at 04:04:33PM +0300, Andrey Chernov wrote: > On 15.11.2015 16:00, Baptiste Daroussin wrote: > > On Sun, Nov 15, 2015 at 03:56:26PM +0300, Andrey Chernov wrote: > >> On 15.11.2015 15:46, Baptiste Daroussin wrote: > >>> On Sun, Nov 15, 2015 at 03:24:19PM +0300, Andrey Chernov wro

Re: Need help fixing failing locale tests

On 15.11.2015 17:47, John Marino wrote: >>> Please provide an example of such a program (in ports). >> >> See gettext-0.19.6/gettext-tools/configure, part started with >> # Test for the usual locale name. >> I don't have time to dig more such code now, but I remember I saw more >> for sure. > If t

Re: Need help fixing failing locale tests

On 15.11.2015 16:54, John Marino wrote: > We are talking about people that install FreeBSD 11 as a release. If > it's an upgrade, it's documented in UPDATING (it will be) and anybody on > -CURRENT is taking responsibility for knowing what they are doing. *IF* > this is an obstacle, it's either tr

Re: Need help fixing failing locale tests

On 11/15/2015 2:10 PM, Andrey Chernov wrote: >> Well, there is "harm". The -1/-15 confusion happens a lot. > > It is user confusion and his responsibility. It not leads to wrong > program build f.e. Moreover, you can't protect users who set 8859-1 that > way, they do not convert to 8859-15 as you

Re: Need help fixing failing locale tests

On 11/15/2015 2:04 PM, Andrey Chernov wrote: > On 15.11.2015 16:00, Baptiste Daroussin wrote: >> On Sun, Nov 15, 2015 at 03:56:26PM +0300, Andrey Chernov wrote: >>> On 15.11.2015 15:46, Baptiste Daroussin wrote: On Sun, Nov 15, 2015 at 03:24:19PM +0300, Andrey Chernov wrote: > On 15.11.201

Re: Need help fixing failing locale tests

On 15.11.2015 16:14, John Marino wrote: >> It is user confusion and his responsibility. It not leads to wrong >> program build f.e. Moreover, you can't protect users who set 8859-1 that >> way, they do not convert to 8859-15 as you assume but start to complain >> everywhere that FreeBSD is not work

Re: Need help fixing failing locale tests

On 11/15/2015 2:36 PM, Andrey Chernov wrote: > On 15.11.2015 16:14, John Marino wrote: >>> It is user confusion and his responsibility. It not leads to wrong >>> program build f.e. Moreover, you can't protect users who set 8859-1 that >>> way, they do not convert to 8859-15 as you assume but start

Re: Need help fixing failing locale tests

> > There is soft-fail, configure just marks that locales are not supported > > and use "C". Sorry I don't remember port names where I saw it right now > > and don't have a time to search for them right now too. Soft-fails (like > > in tcl with nl_langinfo) are almost impossible to detect excepting

Re: Need help fixing failing locale tests

On 11/15/2015 1:56 PM, Andrey Chernov wrote: > On 15.11.2015 15:46, Baptiste Daroussin wrote: >> On Sun, Nov 15, 2015 at 03:24:19PM +0300, Andrey Chernov wrote: >>> On 15.11.2015 10:09, John Marino wrote: >>> ISO8859-1 locales are legacy even if obsoleted in modern world (I agree >>> with that). Lo

Re: Need help fixing failing locale tests

> Well, there is "harm". The -1/-15 confusion happens a lot. It is user confusion and his responsibility. It not leads to wrong program build f.e. Moreover, you can't protect users who set 8859-1 that way, they do not convert to 8859-15 as you assume but start to complain everywhere that FreeBSD

Re: Need help fixing failing locale tests

On 15.11.2015 16:00, Baptiste Daroussin wrote: > On Sun, Nov 15, 2015 at 03:56:26PM +0300, Andrey Chernov wrote: >> On 15.11.2015 15:46, Baptiste Daroussin wrote: >>> On Sun, Nov 15, 2015 at 03:24:19PM +0300, Andrey Chernov wrote: On 15.11.2015 10:09, John Marino wrote: ISO8859-1 locales

Re: Need help fixing failing locale tests

On Sun, Nov 15, 2015 at 03:56:26PM +0300, Andrey Chernov wrote: > On 15.11.2015 15:46, Baptiste Daroussin wrote: > > On Sun, Nov 15, 2015 at 03:24:19PM +0300, Andrey Chernov wrote: > >> On 15.11.2015 10:09, John Marino wrote: > >> ISO8859-1 locales are legacy even if obsoleted in modern world (I ag

Re: Need help fixing failing locale tests

On 15.11.2015 15:46, Baptiste Daroussin wrote: > On Sun, Nov 15, 2015 at 03:24:19PM +0300, Andrey Chernov wrote: >> On 15.11.2015 10:09, John Marino wrote: >> ISO8859-1 locales are legacy even if obsoleted in modern world (I agree >> with that). Lots of ports (even at configure stage!) have checks

Re: Need help fixing failing locale tests

> >> There's also a common > >> problem that users view -15 documents with -1 accidently. So there was > >> a conscience decision to have either ISO8859-1 or ISO8859-15 but not > >> both. For western Europe this means the ISO8859-1 versions were dropped. > > It is pure user problem choosing its

Re: Need help fixing failing locale tests

On Sun, Nov 15, 2015 at 03:24:19PM +0300, Andrey Chernov wrote: > On 15.11.2015 10:09, John Marino wrote: > > We (DragonFly) didn't just update locales. We took the opportunity to > > do spring cleaning. We didn't want to be as drastic as OpenBSD which > > removed all encodings except for C/POSIX

Re: Need help fixing failing locale tests

On 15.11.2015 15:24, Andrey Chernov wrote: > On 15.11.2015 10:09, John Marino wrote: >> We (DragonFly) didn't just update locales. We took the opportunity to >> do spring cleaning. We didn't want to be as drastic as OpenBSD which >> removed all encodings except for C/POSIX and UTF, but we did rem

Re: Need help fixing failing locale tests

On 15.11.2015 10:09, John Marino wrote: > We (DragonFly) didn't just update locales. We took the opportunity to > do spring cleaning. We didn't want to be as drastic as OpenBSD which > removed all encodings except for C/POSIX and UTF, but we did remove > several locales intentionally. > > In the

Re: Need help fixing failing locale tests

On 11/15/2015 12:23 PM, Craig Rodrigues wrote: > > > On Sat, Nov 14, 2015 at 11:47 PM, John Marino > wrote: > > > With 4.) they have been removed from FreeBSD when "Make upgrade" is run > after rebuilding. Does FreeBSD have a cleanup like that, and di

Re: Need help fixing failing locale tests

On 11/15/2015 8:24 AM, NGie Cooper wrote: >> On Nov 14, 2015, at 23:09, John Marino wrote: >> Bapt liked DF approach well enough that he adopted it. Even Edwin was >> first in desiring to clean up locales. The major update was a perfect time. >> >> Bottom line: >> The testsuite needs to be updat

Re: Need help fixing failing locale tests

On 11/15/2015 4:46 AM, NGie Cooper wrote: > >> On Nov 14, 2015, at 19:28, NGie Cooper wrote: > > … > >> Why were these locales removed? >> >> 58 OLD_FILES+=usr/share/locale/la_LN.ISO8859-1/LC_COLLATE >> 59 OLD_FILES+=usr/share/locale/la_LN.ISO8859-1/LC_CTYPE >> 60 OLD_FILES+=usr/share/locale

Re: Need help fixing failing locale tests

> On Nov 15, 2015, at 03:30, John Marino wrote: … > by they way, this was meant to be "removed from DragonFly". I don't > know if "make upgrade" is set right for FreeBSD. (it appears not) make upgrade doesn’t exist on FreeBSD: $ (cd /usr/src/svn/; make upgrade) make: don't know how to make

Re: Need help fixing failing locale tests

On Sat, Nov 14, 2015 at 11:47 PM, John Marino wrote: > > With 4.) they have been removed from FreeBSD when "Make upgrade" is run > after rebuilding. Does FreeBSD have a cleanup like that, and did you > run it? If not, then maybe that needs to be updated. > > I did not run "make upgrade". I did

Re: Need help fixing failing locale tests

> On Nov 14, 2015, at 23:09, John Marino wrote: > > On 11/15/2015 4:46 AM, NGie Cooper wrote: >> >>> On Nov 14, 2015, at 19:28, NGie Cooper wrote: >> >> … >> >>> Why were these locales removed? >>> >>> 58 OLD_FILES+=usr/share/locale/la_LN.ISO8859-1/LC_COLLATE >>> 59 OLD_FILES+=usr/share/loc

Re: Need help fixing failing locale tests

> On Nov 14, 2015, at 19:46, NGie Cooper wrote: > > >> On Nov 14, 2015, at 19:28, NGie Cooper wrote: > > … > >> Why were these locales removed? >> >> 58 OLD_FILES+=usr/share/locale/la_LN.ISO8859-1/LC_COLLATE >> 59 OLD_FILES+=usr/share/locale/la_LN.ISO8859-1/LC_CTYPE >> 60 OLD_FILES+=usr/sha

Re: Need help fixing failing locale tests

> On Nov 14, 2015, at 19:28, NGie Cooper wrote: … > Why were these locales removed? > > 58 OLD_FILES+=usr/share/locale/la_LN.ISO8859-1/LC_COLLATE > 59 OLD_FILES+=usr/share/locale/la_LN.ISO8859-1/LC_CTYPE > 60 OLD_FILES+=usr/share/locale/la_LN.ISO8859-1/LC_TIME > 61 OLD_DIRS+=usr/share/loca

Re: Need help fixing failing locale tests

> On Nov 14, 2015, at 19:18, Craig Rodrigues wrote: > > On Sat, Nov 14, 2015 at 7:05 PM, Craig Rodrigues > wrote: > >> Hi, >> >> After the recent locale commits, some of the tests are failing: >> >> https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1675/testReport/ >> >> I can reproduce tw

Re: Need help fixing failing locale tests

On Sat, Nov 14, 2015 at 7:05 PM, Craig Rodrigues wrote: > Hi, > > After the recent locale commits, some of the tests are failing: > > https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1675/testReport/ > > I can reproduce two failures quite easily by doing with a newly built > world: > > /bin/sh

Re: Need help fixing failing locale tests

> On Nov 14, 2015, at 19:05, Craig Rodrigues wrote: > > Hi, > > After the recent locale commits, some of the tests are failing: > > https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1675/testReport/ > > I can reproduce two failures quite easily by doing with a newly built world: > > /bin/sh

Need help fixing failing locale tests

Hi, After the recent locale commits, some of the tests are failing: https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1675/testReport/ I can reproduce two failures quite easily by doing with a newly built world: /bin/sh /usr/tests/bin/sh/builtins/case7.0 /bin/sh /usr/tests/bin/sh/builtins/loca

Re: Need help reducing compilation warnings in CURRENT

On May 30, 2015, at 19:15, Craig Rodrigues wrote: > On Thu, May 28, 2015 at 9:49 AM, Konstantin Belousov > wrote: > >> On Wed, May 27, 2015 at 11:30:45PM -0700, Craig Rodrigues wrote: >> >> I take some time to do a pass over mine code or code I am somewhat >> knowledgable, to correct some 'ass

Re: Need help reducing compilation warnings in CURRENT

On Thu, May 28, 2015 at 9:49 AM, Konstantin Belousov wrote: > On Wed, May 27, 2015 at 11:30:45PM -0700, Craig Rodrigues wrote: > > I take some time to do a pass over mine code or code I am somewhat > knowledgable, to correct some 'assigned but not used variable' warnings. > There might be even on

Re: Need help reducing compilation warnings in CURRENT

On Thu, May 28, 2015 at 5:45 AM, Muhammad Moinur Rahman wrote: > Hi, > > Can anyone give me any ideas about how can I contribute some of my idle > times? Do I need commit bit to submit patches in Jenkins? Or should I > submit through CODE Review? > Please read this: https://wiki.freebsd.org/Cod

Re: Need help reducing compilation warnings in CURRENT

On 28 May 2015, at 21:09, Craig Rodrigues wrote: > > On Thu, May 28, 2015 at 5:38 AM, Johannes Jost Meixner ... >> The warnings are almost all in contrib/ areas. Hence, any fix might >> want to probably be submitted to upstream first. >> > Sure, if we can push fixes upstream that would be great

Re: Need help reducing compilation warnings in CURRENT

On Thu, May 28, 2015 at 12:18 PM, Baptiste Daroussin wrote: ... > If not upstreamed, there is a good chance it get lost during the next update. > So > in the special case of warning fixes, I would strongly advice to upstream > first!! +200 Plus upstream sources generally get slammed by multiple

Re: Need help reducing compilation warnings in CURRENT

On Thu, May 28, 2015 at 12:09:35PM -0700, Craig Rodrigues wrote: > On Thu, May 28, 2015 at 5:38 AM, Johannes Jost Meixner > wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Hi Craig, > > > > I'll gladly help (good excuse to learn C), but looking at those errors > > in gene

Re: Need help reducing compilation warnings in CURRENT

On Thu, May 28, 2015 at 5:38 AM, Johannes Jost Meixner wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi Craig, > > I'll gladly help (good excuse to learn C), but looking at those errors > in general, one thing pops out: > > The warnings are almost all in contrib/ areas. Hence, an

Re: Need help reducing compilation warnings in CURRENT

On Wed, May 27, 2015 at 11:30:45PM -0700, Craig Rodrigues wrote: > Hi, > > I've configured Jenkins to highlight compiler warnings and > generate a table. Jenkins also keeps track of new compiler warnings > over time. See: > > https://jenkins.freebsd.org/job/FreeBSD_HEAD/warnings7 > > Can anyon

Re: Need help reducing compilation warnings in CURRENT

Hi, You don't need src bit to submit any patch and you can do it via review without any problem. Just try to drive the patch to the right person. Best, 2015-05-28 20:45 GMT+08:00 Muhammad Moinur Rahman : > Hi, > > Can anyone give me any ideas about how can I contribute some of my idle > times?

Re: Need help reducing compilation warnings in CURRENT

Hi, Can anyone give me any ideas about how can I contribute some of my idle times? Do I need commit bit to submit patches in Jenkins? Or should I submit through CODE Review? BR, @bofh On Thu, May 28, 2015 at 6:38 PM, Johannes Jost Meixner wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA

Re: Need help reducing compilation warnings in CURRENT

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Craig, I'll gladly help (good excuse to learn C), but looking at those errors in general, one thing pops out: The warnings are almost all in contrib/ areas. Hence, any fix might want to probably be submitted to upstream first. Correct me if I'm

Re: Need help reducing compilation warnings in CURRENT

Hi Craig, I can give a hand with it. Best, 2015-05-28 14:30 GMT+08:00 Craig Rodrigues : > Hi, > > I've configured Jenkins to highlight compiler warnings and > generate a table. Jenkins also keeps track of new compiler warnings > over time. See: > > https://jenkins.freebsd.org/job/FreeBSD_HEA

Need help reducing compilation warnings in CURRENT

Hi, I've configured Jenkins to highlight compiler warnings and generate a table. Jenkins also keeps track of new compiler warnings over time. See: https://jenkins.freebsd.org/job/FreeBSD_HEAD/warnings7 Can anyone help improve the code by periodically looking at this table and submitting patche

Re: Need help fixing tests in CURRENT

On Tue, Oct 7, 2014 at 4:38 PM, Craig Rodrigues wrote: > > On Tue, Oct 7, 2014 at 4:30 PM, NGie Cooper wrote: >> >> On Tue, Oct 7, 2014 at 2:04 PM, Craig Rodrigues >> wrote: >> > Hi, >> > >> > After committing this fix to yacc in HEAD ( >> > https://lists.freebsd.org/pipermail/svn-src-all/2014-O

Re: Need help fixing tests in CURRENT

On Tue, Oct 7, 2014 at 4:30 PM, NGie Cooper wrote: > On Tue, Oct 7, 2014 at 2:04 PM, Craig Rodrigues > wrote: > > Hi, > > > > After committing this fix to yacc in HEAD ( > > https://lists.freebsd.org/pipermail/svn-src-all/2014-October/092553.html > ) > > I've been able to do: "cd /usr/tests; ky

Re: Need help fixing tests in CURRENT

On Tue, Oct 7, 2014 at 2:04 PM, Craig Rodrigues wrote: > Hi, > > After committing this fix to yacc in HEAD ( > https://lists.freebsd.org/pipermail/svn-src-all/2014-October/092553.html ) > I've been able to do: "cd /usr/tests; kyua test" > > and get 0 test failures: > > https://jenkins.freebsd.org

Re: Need help fixing tests in CURRENT

Hi, After committing this fix to yacc in HEAD ( https://lists.freebsd.org/pipermail/svn-src-all/2014-October/092553.html ) I've been able to do: "cd /usr/tests; kyua test" and get 0 test failures: https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/16/testReport/ -- Craig _

Re: Need help debugging yacc test failure in CURRENT

On Thu, Oct 2, 2014 at 2:23 AM, Craig Rodrigues wrote: > Hi, > > I have managed to eliminate all the test failures from /usr/tests in > CURRENT > except for one failure. See: > > https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/ > > I can reproduce the failure by doing th

Re: Need help debugging yacc test failure in CURRENT

On Thu, Oct 2, 2014 at 11:14 AM, Garrett Cooper wrote: ... > Let me rephrase that. Using an older atf/kyua didn't repro the bug, so it's > probably atf/kyua Here's the bug I was referring to: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193499 (was replying on my phone earlier). Thank

Re: Need help debugging yacc test failure in CURRENT

> On Oct 2, 2014, at 11:10, Garrett Cooper wrote: > > >>> On Oct 2, 2014, at 10:56, Julio Merino wrote: >>> >>> On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues wrote: >>> Hi, >>> >>> I have managed to eliminate all the test failures from /usr/tests in CURRENT >>> except for one failure. Se

Re: Need help debugging yacc test failure in CURRENT

> On Oct 2, 2014, at 10:56, Julio Merino wrote: > >> On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues wrote: >> Hi, >> >> I have managed to eliminate all the test failures from /usr/tests in CURRENT >> except for one failure. See: >> >> https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tes

Re: Need help debugging yacc test failure in CURRENT

On Thu, Oct 2, 2014 at 5:23 AM, Craig Rodrigues wrote: > Hi, > > I have managed to eliminate all the test failures from /usr/tests in CURRENT > except for one failure. See: > > https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/ > > I can reproduce the failure by doing the f

Need help debugging yacc test failure in CURRENT

Hi, I have managed to eliminate all the test failures from /usr/tests in CURRENT except for one failure. See: https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/8/testReport/ I can reproduce the failure by doing the following: mkdir /tmp/x cd /tmp/x /usr/tests/usr.bin/yacc/yacc_tests

Need help fixing tests in CURRENT

Hi, Based on feedback from Garrett, it looks like there were some problems in kyua, causing test failures. I patched my local copy of the kyua port: https://github.com/rodrigc/kyua-port/ and re-ran the tests: cd /usr/tests kyua test kyua report kyua report-html kyua report-junit https://jenk

Re: Need help fixing tests in CURRENT

On Tue, Sep 9, 2014 at 10:11 AM, Allan Jude wrote: > > > > > https://jenkins.freebsd.org/jenkins/job/FreeBSD_HEAD-tests2/lastCompletedBuild/testReport/ > > > Most of the errors (jot, m4, sed, etc) seems to be: > > kyua-tap-tester: Configuration variables not supported; ignoring > 'has.cleanup=fal

Re: Need help fixing tests in CURRENT

On Sep 9, 2014, at 10:17, Alan Somers wrote: > On Tue, Sep 9, 2014 at 11:13 AM, wrote: >> On Sep 9, 2014, at 10:11, Allan Jude wrote: >> >>> On 2014-09-09 13:05, Craig Rodrigues wrote: Hi, I did a buildworld/installworld of current in a bhyve VM, and then did the followin

Re: Need help fixing tests in CURRENT

On Tue, Sep 9, 2014 at 11:13 AM, wrote: > On Sep 9, 2014, at 10:11, Allan Jude wrote: > >> On 2014-09-09 13:05, Craig Rodrigues wrote: >>> Hi, >>> >>> I did a buildworld/installworld of current in a bhyve VM, and then did the >>> following. >>> >>> pkg install devel/kyua >>> cd /usr/tests >>> ky

Re: Need help fixing tests in CURRENT

On Sep 9, 2014, at 10:11, Allan Jude wrote: > On 2014-09-09 13:05, Craig Rodrigues wrote: >> Hi, >> >> I did a buildworld/installworld of current in a bhyve VM, and then did the >> following. >> >> pkg install devel/kyua >> cd /usr/tests >> kyua test >> kyua report >> kyua report-html >> kyua r

Re: Need help fixing tests in CURRENT

On 2014-09-09 13:05, Craig Rodrigues wrote: > Hi, > > I did a buildworld/installworld of current in a bhyve VM, and then did the > following. > > pkg install devel/kyua > cd /usr/tests > kyua test > kyua report > kyua report-html > kyua report-junit > > I then published the results in Jenkins: >

Need help fixing tests in CURRENT

Hi, I did a buildworld/installworld of current in a bhyve VM, and then did the following. pkg install devel/kyua cd /usr/tests kyua test kyua report kyua report-html kyua report-junit I then published the results in Jenkins: The results are here: https://jenkins.freebsd.org/jenkins/job/FreeBSD

Re: [Need Help]isboot (iSCSI boot driver) version 0.2.1

Thank you for your advice! 128KB is a default MAXPHYS value. You may rise it in your kernel if you want. I am successfully using 1MB MAXPHYS now. I misunderstood. I thought maxio was able to overwrite in GENERIC kernel. OK, I built custom kernel. There is a result. It's great! The log shows: c

Re: [Need Help]isboot (iSCSI boot driver) version 0.2.1

> iscsi initiator paniced over 4 dev, and the code has limitations of > devices, it is hardcoded to 4 > > 9f2ae5be (scottl 2007-07-24 15:35:02 + 39) #define ISCSIDEV > "iscsi" > 9f2ae5be (scottl 2007-07-24 15:35:02 + 40) > 9f2ae5be (scottl 2007-07-24 15:35:02 + 41) #define >

Re: [Need Help]isboot (iSCSI boot driver) version 0.2.1

iscsi initiator paniced over 4 dev, and the code has limitations of devices, it is hardcoded to 4 9f2ae5be (scottl 2007-07-24 15:35:02 + 39) #define ISCSIDEV"iscsi" 9f2ae5be (scottl 2007-07-24 15:35:02 + 40) 9f2ae5be (scottl 2007-07-24 15:35:02 + 41) #define ISCSI_MAX_TARGET

Re: [Need Help]isboot (iSCSI boot driver) version 0.2.1

Daisuke Aoyama wrote: >>> Notes/Known Issues/Limitations: >>> FreeBSD can't use transfer length > 64KB. >> >> Since 8.0 FreeBSD can use any transfer lengths. 64K is a safety limit >> for CAM SIMs that do not report maximum transfer size. If your driver >> supports bigger transactions (and even if n

Re: [Need Help]isboot (iSCSI boot driver) version 0.2.1

Updated to 0.2.2 I noticed a bug after writing previous mail. sosend was called from XPT_SCSI_IO with locked mutex. It caused "sleeping thread owns a non-sleepable lock". What's new?: add auto sense. add maxio=1m. modify max tags by iSCSI command window. fix locked sleep problem. Download links

Re: [Need Help]isboot (iSCSI boot driver) version 0.2.1

Hi, Notes/Known Issues/Limitations: FreeBSD can't use transfer length > 64KB. Since 8.0 FreeBSD can use any transfer lengths. 64K is a safety limit for CAM SIMs that do not report maximum transfer size. If your driver supports bigger transactions (and even if not), you should fill maxio field

Re: [Need Help]isboot (iSCSI boot driver) version 0.2.1

Hi. Daisuke Aoyama wrote: > I uploaded isboot 0.2.1. > Now isboot supports R2T command and non-immediate mode. > I believe that the compatibility of iSCSI target is improved. > Please check it with your iSCSI target and NIC. > Also this version supports task queue, which improves performance. > My

[Need Help]isboot (iSCSI boot driver) version 0.2.1

Hi all, I uploaded isboot 0.2.1. Now isboot supports R2T command and non-immediate mode. I believe that the compatibility of iSCSI target is improved. Please check it with your iSCSI target and NIC. Also this version supports task queue, which improves performance. My test machine got read 74MB/s

Re: wi0 - need help

On Sat, Mar 01, 2003 at 12:23:22PM -0700, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Marcel Moolenaar <[EMAIL PROTECTED]> writes: > : BTW: Shouldn't we obsolete wicontrol then or strip functionality? > : It appears we have 2 ways in which we can do things now... > > I'm

Re: wi0 - need help

In message: <[EMAIL PROTECTED]> Marcel Moolenaar <[EMAIL PROTECTED]> writes: : BTW: Shouldn't we obsolete wicontrol then or strip functionality? : It appears we have 2 ways in which we can do things now... I'm planning on doing that soonish. However, I think that hacking wi to make it

Re: wi0 - need help

On Sat, Mar 01, 2003 at 06:08:27AM -0700, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Marcel Moolenaar <[EMAIL PROTECTED]> writes: > : > status: no carrier > : > ssid "" 1:"" > : > : Did you do `wicontrol -i wi0 -p 1'? > > I've found that the new driver really really rea

Re: wi0 - need help

On Sat, Mar 01, 2003 at 08:08:36PM +0100, Christoph P. Kukulies wrote: > On Sat, Mar 01, 2003 at 11:35:37AM -0700, M. Warner Losh wrote: > > > It works! > Packets started flowing right after I typed in the above line. > > > > > and > > > > ifconfig wi0 192.168.254.2 netmask 255.255.255.0 ssid

Re: wi0 - need help

On Sat, Mar 01, 2003 at 11:35:37AM -0700, M. Warner Losh wrote: Not sure whether I group replied, so maybe you will be receiving two similar sounding answers, Warner. > In message: <[EMAIL PROTECTED]> > "Christoph P. Kukulies" <[EMAIL PROTECTED]> writes: > : Warner, I applied the patc

Re: wi0 - need help

In message: <[EMAIL PROTECTED]> "Christoph P. Kukulies" <[EMAIL PROTECTED]> writes: : Warner, I applied the patch and no change. marcel's patch, or my patch? : How does one specify the commands in the ifconfig interface? : This is what I used to invoke from /etc/rc.local: : : /usr/sb

Re: wi0 - need help

On Sat, Mar 01, 2003 at 06:08:27AM -0700, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Marcel Moolenaar <[EMAIL PROTECTED]> writes: > : > status: no carrier > : > ssid "" 1:"" > : > : Did you do `wicontrol -i wi0 -p 1'? As already said, I did that and the wicontrol output

  1   2   >