Re: bl[ao]cklistd, some first impressions...
Hi, > On 21 Nov 2023, at 11:46, Poul-Henning Kamp wrote: > > I have played around with bl[ao]cklistd on 13.2 and I am not terribly > impressed: > [etc] We came up with a similar list of objections and built our own solution. -- Bob Bishop r...@gid.co.uk
Re: Updating motherboard BIOS without MS Windows
Hi, > On 11 Nov 2023, at 10:56, Nuno Teixeira wrote: > > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking for brands > that have bios-cli that work in FreeBSD. Can’t speak to specific brands but it’s becoming pretty common to be able to update firmware from UEFI shell. > > Thanks, > > -- > Nuno Teixeira > FreeBSD Committer (ports) -- Bob Bishop r...@gid.co.uk
Re: zfs autotrim default to off now
Hi, > On 28 Aug 2023, at 20:00, Alexander Motin wrote: > > On 28.08.2023 13:56, Pete Wright wrote: >> So to be clear, if we were using the default autotrim=enabled behavior we in >> fact weren't having our SSDs trimmed? I think that's my concern, as an >> admin I was under the impression that it was enabled by default but >> apparently that wasn't actually happening. > > We wanted autotrim to be enabled by default, but it was not enabled, and it > was reported as not enabled, so there should be no confusion. The only > confusion may have been if you tried to read the code and see it should have > been enabled. > > -- > Alexander Motin Prompted by this thread, I went to check one of my servers that predates the change to OpenZFS. I set autotrim=on at the time of the transition; at some point since, it had become unset (and not by me). The system has been upgraded from time to time and is currently running 13.2R. -- Bob Bishop r...@gid.co.uk
Re: [iwlwifi] ipv6 connection problem
Hi, > On 12 Aug 2022, at 13:00, Nuno Teixeira wrote: > > Hi Merek, > >> If you are connecting to IPv6 only WLAN than you can probably either >> disable DHCP (if the RDNSS is provided for this network): >> ifconfig_wlan0="WPA up" >> or install dhcp client capable of acquiring DHCPv6 lease and use it >> instead of standard dhclient(8) from the base which doesn't support DHCPv6. >> > I've tried ifconfig_wlan0="WPA up" and it crashes os. > > You saying that base dhcp doesn't support ipv6 but it works fine with > ehternet: > --- > ifconfig_re0="DHCP" > ifconfig_re0_ipv6="inet6 accept_rtadv" > rtsold_enable="YES" > --- Above is kind of mixed up. I think the `ifconfig_re0=“DHCP”’ is superfluous, your interface will be getting assigned its address by the router using stateless autoconfiguration not DHCP. Perhaps trying to configure both stateless autoconfiguration and DHCP is upsetting your wireless interface. DHCP is almost never required with IPv6. > > Any clues? > > Thanks -- Bob Bishop r...@gid.co.uk
Re: Dragonfly Mail Agent (dma) in the base system
Hi, > On 27 Jan 2022, at 21:34, Ed Maste wrote: > > The Dragonfly Mail Agent (dma) [etc] We've used it for years on routers and other small boxes to offload mail from periodic and cron. -- Bob Bishop r...@gid.co.uk
Re: The spkr driver
Hi, > On 28 Aug 2020, at 19:47, Kurt Jaeger wrote: > > Hi! > >> I'd like to retire the spkr driver. It was a cute hack before sound cards >> were ubiquitous, but it's not been kept up to date, and it's not clear that >> it still works It is still Giant locked, and though it's not a huge >> effort to do the locking I literally have no way to test it that I trust... > > It works on PC Engines APU devices, and together with morse, it's > very, very cool 8-} > > So, please keep it and un-giant it, if possible. What he said. I’d be happy to test changes. > -- > p...@opsec.eu +49 171 3101372Now what ? -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: OpenZFS support merged
Hi, > On 25 Aug 2020, at 03:38, Matthew Macy wrote: > > r364746 merged OpenZFS support in to HEAD. > > The change should be transparent unless you want to use new features. For clarity, is autotrim enabled by default? If not, some people will be surprised. > I caution against 'zpool upgrade' for the next few weeks. > > https://svnweb.freebsd.org/base?view=revision=364746 > > If you encounter problems please report them to me, Ryan Moeller, and > -current. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How to enable tcp bbr in FreeBSD？
Hi, > On 24 Apr 2020, at 07:29, ykla wrote: > > I search by Google but found no results about how to enable bbr in > FreeBSD. BBR had developed in 2019. So I want to enable it. See: https://svnweb.freebsd.org/base?view=revision=352657 -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: OpenZFS port updated
Hi, > On 17 Apr 2020, at 19:35, Ryan Moeller wrote: > > FreeBSD support has been merged into the master branch of the openzfs/zfs > repository, and the FreeBSD ports have been switched to this branch. > > OpenZFS brings many exciting features to FreeBSD, including: > * native encryption > * improved TRIM implementation [etc] Note that unlike native ZFS, OpenZFS doesn’t (last time I looked) support autotrim by default - you have to enable it explicitly. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HOWTO donate CPU to the fight against the Corona-virus
Hi, Just a note that the client can grow its logfile at the rate of ~1GB a day. You’ll probably want to take avoiding action. > On 19 Mar 2020, at 07:57, Alexander Leidinger via freebsd-stable > wrote: > > Hi, > > if someone wants to donate some FreeBSD based CPU resources to the fight > against the Corona-virus, here is a quick HOWTO in terms of installing the > Folding@Home client on FreeBSD: > > https://www.leidinger.net/blog/2020/03/19/fighting-the-coronavirus-with-freebsd-foldinghome/ > > I tested this on a recent -current. > > If you are interested in how this helps in the fight against the virus, > please refer to the https://foldingathome.org/ website. In short and > over-simplified: they search for vaccines. > > Bye, > Alexander. > > -- > http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF -- Bob Bishop r...@gid.co.uk signature.asc Description: Message signed with OpenPGP
Re: error: yacc.h: No such file or directory
Hi, > On 18 Jun 2019, at 11:56, Kubilay Kocak wrote: > > On 18/06/2019 5:42 pm, Michael Tuexen wrote: >> Dear all, >> I'm trying to run >> sudo make buildworld >> in a directory with r349168. FWIW I have a successful build with r349167 >> The result is: >> cc -O2 -pipe -I/usr/home/tuexen/head/usr.bin/mkesdb_static >> -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../mkesdb >> -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../../lib/libc/iconv -g -MD >> -MF.depend.lex.o -MTlex.o -std=gnu99 >> -I/usr/obj/usr/home/tuexen/head/powerpc.powerpc64/tmp/legacy/usr/include -c >> lex.c -o lex.o >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:46:18: error: yacc.h: No such >> file or directory >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l: In function 'yylex': >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: 'R_LN' undeclared >> (first use in this function) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: (Each undeclared >> identifier is reported only once >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: for each function it >> appears in.) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:72: error: 'yylval' undeclared >> (first use in this function) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:73: error: 'L_IMM' undeclared >> (first use in this function) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:76: error: 'R_NAME' undeclared >> (first use in this function) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:77: error: 'R_ENCODING' >> undeclared (first use in this function) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:78: error: 'R_VARIABLE' >> undeclared (first use in this function) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:79: error: 'R_DEFCSID' undeclared >> (first use in this function) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:80: error: 'R_INVALID' undeclared >> (first use in this function) >> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:88: error: 'L_STRING' undeclared >> (first use in this function) >> *** Error code 1 >> Stop. >> make[3]: stopped in /usr/home/tuexen/head/usr.bin/mkesdb_static >> *** Error code 1 >> Stop. >> make[2]: stopped in /usr/home/tuexen/head >> *** Error code 1 >> Stop. >> make[1]: stopped in /usr/home/tuexen/head >> *** Error code 1 >> Stop. >> make: stopped in /usr/home/tuexen/head >> This is on a 64 bit PPC system. Doing sudo rm -rf /usr/obj does not resolve >> the issue. >> Any idea what is going wrong? >> Best regards >> Michael > > Have seen another report on Twitter yesterday. Didn't see a full build log, > but theirs was had apparently without -j, apparently on June 14 sources: > > Error: > /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not found > > Have not heard back from them whether it continued after trying -j2 but I did > ask them to hit up freebsd-current if it continued to be an issue -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: leaked swap?
Hi, > On 14 May 2019, at 07:50, Andriy Gapon wrote: > > On 18/03/2019 17:32, Konstantin Belousov wrote: >> tmpfs, swap-backed (or even memory backed) md, persistent posix shared >> memory, SysV shared memory. > > In the end, it was POSIX shared memory. > I put the system into the single-user to clean up the memory as much as > possible > and then I panic'ed it and went through dirty pages and their related objects > in > kgdb. As far as I can tell, the memory was leaked via POSIX shared memory > objects that were never shm_unlink-ed. It seems that there was a misbehaving > program that had been creating such objects and then losing track of them. (I > was able to identify it from names it used for the objects) > > It seems that, unfortunately, there is no way to list / discover POSIX shared > memory objects that are not opened by any process. Losing track of shared memory objects has been a problem since SysVr2 ... > I wrote a small gdb script to examine shm_dictionary in kgdb. It would be > nice > to have a utility (and a kernel interface) that could do the same from > userland. ... it is indeed high time it was fixed. > -- > Andriy Gapon > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: The future of ZFS in FreeBSD
ZoL several steps need to be taken: >>>>> - Integrate FreeBSD support into ZoL CI >>>>> - Have most of the ZFS test suite passing >>>>> - Complete additional QA testing at iX >>>>> >>>>> We at iX Systems need to port ZoL's EC2 CI scripts to work with >>>>> FreeBSD and make sure that most of the ZFS Test Suite (ZTS) passes. >>>>> Being integrated in to their CI will mean that, among other things, >>>>> most integration issues will be caught before a PR is merged upstream >>>>> rather than many months later when it is MFVed into FreeBSD. I’m >>>>> hoping to submit the PR to ZoL some time in January. >>>>> >>>>> This port will make it easy for end users on a range of releases to >>>>> run the latest version of ZFS. Nonetheless, transitioning away from an >>>>> Illumos based ZFS is not likely to be entirely seamless. The >>>>> stakeholders I’ve spoken to all agree that this is the best path >>>>> forward but some degree of effort needs to be made to accommodate >>>>> downstream consumers. The current plan is to import ZoF and unhook the >>>>> older Illumos based sources from the build on April 15th or two months >>>>> after iX systems QA deems ZoF stable - which ever comes later. The >>>>> Illumos based sources will be removed some time later - but well >>>>> before 13. This will give users a 3 month period during which both the >>>>> port and legacy Illumos based ZFS will be available to users. Pools >>>>> should interoperate between ZoF and legacy provided the user does not >>>>> enable any features available only in ZoF. We will try to accommodate >>>>> any downstream consumers in the event that they need that date pushed >>>>> back. We ask that any downstream consumers who are particularly >>>>> sensitive to changes start testing the port when it is formally >>>>> announced and report back any issues they have. I will do my best to >>>>> ensure that this message is communicated to all those who it may >>>>> concern. However, I can’t ensure that everyone reads these lists. That >>>>> is the responsibility of -CURRENT users. >>>>> >>>>> -M >>>>> >>>> ___ >>>>> freebsd...@freebsd.org mailing list >>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >>>>> To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org" >>>>> >>>> > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
src committer please
Hi, Please could somebody take a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 It’s been open for over a year with a patch that solves the problem. Failing to install out of the box on commodity HP kit is not a good look. Thanks -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipv6/ppp: FreeBSD obtains linklocal on tun0 only
Hi, > On 30 Nov 2018, at 12:12, O. Hartmann wrote: > > Signed PGP part > My ISP is offering IPv6 only "as an experimental feature", so I had to ask to > enable the > IPv6 stack on my connection. I'm using FreeBSD 12-STABLE as the basis for a > router/firewall/PBX system, FreeBSD's onboard ppp client is performing the > uplink and > authetication and this works well with IPv4 for years for now. > > I'm using IPFW as my filtering system, reading the standard > /etc/rc.ipfirewall and add > some custom rules regarding my setup. > > As far as I know, with the IPv4 stack a IPv4 address is obtained > automatically, so I > would expect the same for IPv6. > > I'm new to IPv6 and I've trouble with my provider for a long time now, so > there is a > slight possibility that my ISP is not truthful on what they say. On the other > hand, there > is still a high probability that I do something wrong. I need need to send > this ahead, > before continueing. > > When booting off, I see the classic tun0 uplink with > > MYADDR -> HISADDR > > For IPv6, I only see my local linklocal address, fe80::... > > Checking the log of ppp (/var/log/ppp.log), there is also a fe80:: linklocal > address > assigned to the variable HISADDR. Somehow, the tun0 never obtains a IPv6 > aprefix so far. > > Can someone give a tip? Guessing because I haven’t used v6 over ppp, but: - You probably need net.inet6.ip6.accept_rtadv set to 1 to accept IPv6 router advertisement from upstream. You should get a prefix from the upstream router. - You may also possibly need to run rtsold(8). > Regards, > > oh > > -- Bob Bishop r...@gid.co.uk signature.asc Description: Message signed with OpenPGP
Re: Denverton CPU on FreeBSD
Hi, > On 7 Nov 2017, at 16:12, Cassiano Peixoto <peixotocassi...@gmail.com> wrote: > > Hi guys, > > I'm backing to this thread because I had no success yet. There is an issue > with console boot on Intel Denverton. I've followed the instruction bellow: > > https://www.freebsd.org/doc/handbook/serialconsole-setup.html > > I tried using an IPMI card and worked fine. > > I don't know who is the maintainer for console code to get in touch. Can > some developer work on this issue? I can help making any test needed. > > Thank you. > > On Wed, Aug 16, 2017 at 5:32 PM, Cassiano Peixoto <peixotocassi...@gmail.com >> wrote: > >> Hi there, >> >> Is someone playing with Denverton CPU On FreeBSD? >> >> I'm trying to use serial console on FreeBSD with Denverton CPU but doesn't >> work. >> >> I can see the boot process but it stops and I do not have the login >> prompt. My keyboard doesn't answer as well. Have you set /etc/ttys entry for the serial port appropriately? https://www.freebsd.org/doc/handbook/term.html#term-config >> I tried it with FreeBSD 10, 11 and 12-CURRENT. Same configuration is >> working with Rangeley CPU. Maybe BIOS initialises the serial port differently? >> Any help is welcome. >> >> Thanks. >> > ___ > freebsd-sta...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Bob Bishop t: +44 (0)118 940 1243 r...@gid.co.uk m: +44 (0)783 626 4518 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Removal of catman from base
Hi, > On 12 Sep 2017, at 22:20, Poul-Henning Kamp <p...@phk.freebsd.dk> wrote: > > > In message <alpine.bsf.2.21.1709121210140.54...@orthanc.ca>, Lyndon Nerenberg > writes: >>> That was actually not why catman was brought into the world: ATT/USL >>> thought text-processing was The Goods so they unbundled it base SVR >>> and invented catman to make up for the missing nroff. >> >> Not quite. They (AT) sold the rights to sell typeset manuals to some >> publishing house (I forget which), at which point they stopped shipping >> the *roff source for the manpages on the source tapes. Instead, you got >> pre-formatted "cat" pages on the source tape. I think this happened >> starting with SVR3. That is correct. We wrote some excruciatingly ugly scripts that mostly reconstructed the *roff source from the formatted pages. > I'm pretty sure that SVR1 had catman and roff was an extra and somewhat > pricey software package. That is also correct: by SVR5 that had become the Documenter’s Workbench (DWB). > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Userland problems in 12-CURRENT
Just copying this reply to the list. > On 9 Aug 2017, at 11:41, Filippo Moretti <filippom...@yahoo.com> wrote: > > I could not find a bios option,the kernel does report PAE as a CPU option > > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Features2=0x441d<SSE3,DTES64,MON,DS_CPL,CNXT-ID,xTPR> > thank you > Filippo > > On Wednesday, August 9, 2017, 12:36:47 PM GMT+2, Bob Bishop <r...@gid.co.uk> > wrote: > > > Hi, > > > On 9 Aug 2017, at 11:19, Filippo Moretti <filippom...@yahoo.com> wrote: > > > > [...] > > Further I did succesfully install a PAE kernel but the OS only finds the > > same 3G ram as standard kernel insted of the 4 G available.Are there other > > procedures in order to enable the 4G ram available?ThanksFilippo > > > Maybe there is a BIOS option to enable PAE? Does the kernel report PAE in the > CPU options at boot? > > -- > Bob Bishop > r...@gid.co.uk > > > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Userland problems in 12-CURRENT
Hi, > On 9 Aug 2017, at 11:19, Filippo Moretti <filippom...@yahoo.com> wrote: > > [...] > Further I did succesfully install a PAE kernel but the OS only finds the same > 3G ram as standard kernel insted of the 4 G available.Are there other > procedures in order to enable the 4G ram available?ThanksFilippo Maybe there is a BIOS option to enable PAE? Does the kernel report PAE in the CPU options at boot? -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 2013 Macbook Pro, sound OK in headphones but no sound in internal speakers
Hi, > On 28 Apr 2017, at 18:10, Johannes Lundberg <johal...@gmail.com> wrote: > > That would be awesome! Yes, my model is also A1398. [etc] FWIW, A1398 is MacBookPro 11,3 -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: How many versions of clang/llvm are currently required to maintain a system
Hi, A big chunk of this is down to lang/pure. The upstream links for pure at bitbucket.org have mysteriously disappeared; those who care may get an uneasy feeling. > On 6 Mar 2017, at 07:16, Mark Linimon <lini...@lonesome.com> wrote: > > Please see https://wiki.freebsd.org/ObsoleteLLVMVersions . > > mcl > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r300951 make buildworld duration 18h
HI, > On 30 May 2016, at 15:37, Matthias Apitz <g...@unixarea.de> wrote: > > > Hello, > > Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld > as > > # make -j2 buildworld > > it ended today at lunchtime after 18 hours. The laptop has 2x Intel Atom > 1.6GHz > and 1 GByte RAM and was otherwise unused. Is this the normal buildworld time > of > today? I think it spent most of the time in building the llvm… With 1GB it probably spent a lot of its time swapping. > Thx > > matthias > -- > Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ ☎ > +49-176-38902045 > "Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer > Gesellschaft bzw. > sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." > (jW 19.05.2016) > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: OpenSSH HPN
Hi, > On 10 Nov 2015, at 09:42, Dag-Erling Smørgrav <d...@des.no> wrote: > > […] > > Therefore, I would like to remove the HPN patches from base and refer > anyone who really needs them to the openssh-portable port, which has > them as a default option. I would also like to remove the NONE cipher > patch, which is also available in the port (off by default, just like in > base). Can’t argue with that. Is removing HPN going to impact the performance of tunnelled X connexions? > DES > -- > Dag-Erling Smørgrav - d...@des.no > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [heads up] axing AppleTalk and IPX/SPX
Hi, On 13 Mar 2014, at 16:43, Gleb Smirnoff gleb...@freebsd.org wrote: Hi! Since initial mail http://lists.freebsd.org/pipermail/freebsd-current/2013-October/045911.html did not raise a lot of objection, I'm going to proceed with this. -- Totus tuus, Glebius. In which case, somebody needs to look at the netatalk ports. netatalk-2.2.5,1 has AppleTalk support so may have problems netatalk3-3.1.0_4,1 long description says it supports AppleTalk; it doesn't, support was dropped at 3.0. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Automated submission of kernel panic reports: sysutils/panicmail
Hi, On 4 Nov 2013, at 10:41, Colin Percival wrote: Hi all, After considerable review on freebsd-hackers (thanks dt71 and jilles!) I have now added sysutils/panicmail to the FreeBSD ports tree. [etc] Nice. Is this applicable to all supported branches? -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [heads up] axing AppleTalk and IPX/SPX
Hi, On 28 Oct 2013, at 12:42, Gleb Smirnoff wrote: Hello! [Cc to stable@, for wider audience] The plan is two axe two old networking protocols from FreeBSD head/, meaning that FreeBSD 11.0-RELEASE, available in couple of years would be shipped without them. 1) AppleTalk Last time claimed to be supported by vendor in 2007[1]. In practice had very little use since 90th. Discontinued by major routing equipment vendors since 2009[2]. More pertinantly, netatalk dropped AppleTalk support with v3.0 in 2012[a]. [a] http://netatalk.sourceforge.net/3.0/ReleaseNotes-3.0-alpha1.html 2) IPX Last time claimed to be supported by vendor in 2007[3]. In practice had very little use since 90th. Discontinued by major routing equipment vendors since 2011[4]. Current status of these protocols in FreeBSD is compilable. For the next couple of years, we plan a lot of changes in networking stack, many of which will require changing the protocols, as well. Keeping them in compilable state would require additional manpower, but it is very probable, that after all the changes they will be utterly broken, albeit compilable. P.S. I account any objector as taker of maintainership :) [1] http://en.wikipedia.org/wiki/Mac_OS_X_v10.5 http://en.wikipedia.org/wiki/Mac_OS_X_v10.6 [2] http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps5460/product_bulletin_c25-520459.html [3] http://en.wikipedia.org/wiki/Open_Enterprise_Server#OES-NetWare [4] http://www.cisco.com/en/US/docs/ios/novipx/configuration/guide/Novell_IPX_Discontinuation.html -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Bob Bishop +44 (0)118 940 1243 r...@gid.co.ukfax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: expanding past 1 TB on amd64
Hi, On 17 Jul 2013, at 15:17, Kurt Lidl wrote: On 7/16/2013 2:12 PM, Alan Cox wrote: ... The Haswell line of CPUs is widely reported to support DIMMs twice as large, and it's due in September. That would make the systems of late 2013 hold up to 1536GB of memory. I'd point you at stuff like the Supermicro X8BQ6 series of mainboards. QP E5-8800 systems with 1 TB of memory have been around since 2011. That might have been true, but I did check SuperMicro's motherboard matrix of available products before posting. The largest listed memory configuration on any of their current products is 768GB. http://www.supermicro.com/products/motherboard/matrix/?cpuclass=allsorton=memory -Kurt http://www.supermicro.com/products/motherboard/Xeon7000 Looks like their matrix is not up-to-date. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS TRIM support committed to HEAD.
On 25 Sep 2012, at 06:40, Pawel Jakub Dawidek wrote: On Tue, Sep 25, 2012 at 12:14:24AM +0100, Bob Bishop wrote: Hi, Still seems to be working OK, but: seagoon# zpool status pool: m1 state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scan: scrub repaired 0 in 0h2m with 0 errors on Mon Sep 24 23:52:08 2012 config: NAME STATE READ WRITE CKSUM m1 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk1 ONLINE109M 0 0 gpt/disk0 ONLINE109M 0 0 errors: No known data errors seagoon# sysctl -a |grep _trim kstat.zfs.misc.zio_trim.zio_trim_bytes: 228731904 kstat.zfs.misc.zio_trim.zio_trim_success: 19406 kstat.zfs.misc.zio_trim.zio_trim_unsupported: 0 kstat.zfs.misc.zio_trim.zio_trim_failed: 0 seagoon# No device errors logged in messages, and scrub comes up clean as you can see. The read error count is increasing, but otherwise everything appears to work OK. Are you sure your world and kernel are in sync? I remember seeing similar problem when my userland was updated. I'm sure they are not. Buildworld time... -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS TRIM support committed to HEAD.
On 25 Sep 2012, at 06:40, Pawel Jakub Dawidek wrote: On Tue, Sep 25, 2012 at 12:14:24AM +0100, Bob Bishop wrote: Hi, Still seems to be working OK, but: seagoon# zpool status pool: m1 state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scan: scrub repaired 0 in 0h2m with 0 errors on Mon Sep 24 23:52:08 2012 config: NAME STATE READ WRITE CKSUM m1 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk1 ONLINE109M 0 0 gpt/disk0 ONLINE109M 0 0 errors: No known data errors seagoon# sysctl -a |grep _trim kstat.zfs.misc.zio_trim.zio_trim_bytes: 228731904 kstat.zfs.misc.zio_trim.zio_trim_success: 19406 kstat.zfs.misc.zio_trim.zio_trim_unsupported: 0 kstat.zfs.misc.zio_trim.zio_trim_failed: 0 seagoon# No device errors logged in messages, and scrub comes up clean as you can see. The read error count is increasing, but otherwise everything appears to work OK. Are you sure your world and kernel are in sync? I remember seeing similar problem when my userland was updated. Building world up to date fixes the problem. Good catch. -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS TRIM support committed to HEAD.
Hi, On 23 Sep 2012, at 23:25, Pawel Jakub Dawidek wrote: I have a patch against stable/8, but not stable/9: http://people.freebsd.org/~pjd/patches/zfstrim8.patch Running with that in an otherwise 8-STABLE GENERIC amd64 kernel, I'm getting: kstat.zfs.misc.zio_trim.zio_trim_bytes: 0 kstat.zfs.misc.zio_trim.zio_trim_success: 0 kstat.zfs.misc.zio_trim.zio_trim_unsupported: 0 kstat.zfs.misc.zio_trim.zio_trim_failed: 2742 which doesn't look like it's working. The SSDs are: ad4: 114473MB ADATA SSD S510 120GB 3.3.2 at ata2-master UDMA100 SATA 3Gb/s ad6: 114473MB ADATA SSD S510 120GB 3.3.2 at ata3-master UDMA100 SATA 3Gb/s Any suggestions? Thanks -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS TRIM support committed to HEAD.
Hi, On 24 Sep 2012, at 16:55, Steven Hartland wrote: - Original Message - From: Bob Bishop r...@gid.co.uk To: Pawel Jakub Dawidek p...@freebsd.org Cc: freebsd-current@freebsd.org; freebsd...@freebsd.org; Steven Hartland kill...@multiplay.co.uk Sent: Monday, September 24, 2012 3:17 PM Subject: Re: ZFS TRIM support committed to HEAD. Hi, On 23 Sep 2012, at 23:25, Pawel Jakub Dawidek wrote: I have a patch against stable/8, but not stable/9: http://people.freebsd.org/~pjd/patches/zfstrim8.patch Running with that in an otherwise 8-STABLE GENERIC amd64 kernel, I'm getting: kstat.zfs.misc.zio_trim.zio_trim_bytes: 0 kstat.zfs.misc.zio_trim.zio_trim_success: 0 kstat.zfs.misc.zio_trim.zio_trim_unsupported: 0 kstat.zfs.misc.zio_trim.zio_trim_failed: 2742 which doesn't look like it's working. The SSDs are: ad4: 114473MB ADATA SSD S510 120GB 3.3.2 at ata2-master UDMA100 SATA 3Gb/s ad6: 114473MB ADATA SSD S510 120GB 3.3.2 at ata3-master UDMA100 SATA 3Gb/s Any suggestions? Thanks Don't think ad supports TRIM, switch to ada (ahci) and you should be good. Although I'm surprised your seeing that many reported failures as it should have disabled it on a pool level after the first few failures. Is it still increasing? Yes I'll try switching to ahci -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS TRIM support committed to HEAD.
Hi, On 24 Sep 2012, at 16:55, Steven Hartland wrote: Don't think ad supports TRIM, switch to ada (ahci) and you should be good. Switched to AHCI and now looks more plausible: kstat.zfs.misc.zio_trim.zio_trim_bytes: 2173466624 kstat.zfs.misc.zio_trim.zio_trim_success: 13244 kstat.zfs.misc.zio_trim.zio_trim_unsupported: 0 kstat.zfs.misc.zio_trim.zio_trim_failed: 0 I'll report back if anything unpleasant happens. Thanks to all for this. dmesg below FTR -- Bob Bishop r...@gid.co.uk Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.3-STABLE #0: Mon Sep 24 14:00:52 BST 2012 r...@seagoon.gid.co.uk:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (1821.67-MHz K8-class CPU) Origin = GenuineIntel Id = 0x106ca Family = 6 Model = 1c Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x40e31dSSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 4080594944 (3891 MB) ACPI APIC Table: INTEL D525MW FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP/HT): APIC ID: 3 ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 acpi0: INTEL D525MW on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0x20c0-0x20c7 mem 0xf020-0xf027,0xe000-0xefff,0xf010-0xf01f irq 16 at device 2.0 on pci0 agp0: Intel Pineview SVGA controller on vgapci0 agp0: aperture size is 256M, detected 8188k stolen memory pci0: multimedia, HDA at device 27.0 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 28.0 on pci0 pci1: ACPI PCI bus on pcib1 re0: RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet port 0x1000-0x10ff mem 0xf0004000-0xf0004fff,0xf000-0xf0003fff irq 16 at device 0.0 on pci1 re0: Using 1 MSI-X message re0: Chip rev. 0x2c00 re0: MAC rev. 0x miibus0: MII bus on re0 rgephy0: RTL8169S/8110S/8211B media interface PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 38:60:77:30:09:63 re0: [ITHREAD] pcib2: ACPI PCI-PCI bridge at device 28.1 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 28.2 on pci0 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 28.3 on pci0 pci4: ACPI PCI bus on pcib4 uhci0: Intel 82801G (ICH7) USB controller USB-A port 0x2080-0x209f irq 23 at device 29.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0 on uhci0 uhci1: Intel 82801G (ICH7) USB controller USB-B port 0x2060-0x207f irq 19 at device 29.1 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x2f00 usbus1 on uhci1 uhci2: Intel 82801G (ICH7) USB controller USB-C port 0x2040-0x205f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x2f00 usbus2 on uhci2 uhci3: Intel 82801G (ICH7) USB controller USB-D port 0x2020-0x203f irq 16 at device 29.3 on pci0 uhci3: [ITHREAD] uhci3: LegSup = 0x2f00 usbus3 on uhci3 ehci0: Intel 82801GB/R (ICH7) USB 2.0 controller mem 0xf0284400-0xf02847ff irq 23 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4 on ehci0 pcib5: ACPI PCI-PCI bridge at device 30.0 on pci0 pci5: ACPI PCI bus on pcib5 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 ahci0: Intel ICH7 AHCI SATA controller port 0x20b8-0x20bf,0x20cc-0x20cf,0x20b0-0x20b7,0x20c8-0x20cb,0x20a0-0x20af mem 0xf0284000-0xf02843ff irq 18 at device 31.2 on pci0 ahci0: [ITHREAD] ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier not supported ahcich0: AHCI channel at channel 0 on ahci0 ahcich0: [ITHREAD] ahcich1: AHCI channel at channel 1 on ahci0 ahcich1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed03fff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 atrtc0: AT realtime clock port 0x70
Re: ZFS TRIM support committed to HEAD.
Hi, Still seems to be working OK, but: seagoon# zpool status pool: m1 state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scan: scrub repaired 0 in 0h2m with 0 errors on Mon Sep 24 23:52:08 2012 config: NAME STATE READ WRITE CKSUM m1 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk1 ONLINE109M 0 0 gpt/disk0 ONLINE109M 0 0 errors: No known data errors seagoon# sysctl -a |grep _trim kstat.zfs.misc.zio_trim.zio_trim_bytes: 228731904 kstat.zfs.misc.zio_trim.zio_trim_success: 19406 kstat.zfs.misc.zio_trim.zio_trim_unsupported: 0 kstat.zfs.misc.zio_trim.zio_trim_failed: 0 seagoon# No device errors logged in messages, and scrub comes up clean as you can see. The read error count is increasing, but otherwise everything appears to work OK. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS TRIM support committed to HEAD.
Hi, On 23 Sep 2012, at 20:53, Pawel Jakub Dawidek wrote: FYI, I just committed TRIM support to ZFS, especially useful for SSD-only pools. [etc] Is any of this applicable to -STABLE or 8.x? -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Use of C99 extra long double math functions after r236148
Hi, On 9 Jul 2012, at 06:02, Steve Kargl wrote: If you're doing accouting, hopefully, you're using BCD. Would be nice, but it's far too slow for financial analysis; the chip designers go out of their way to provide fast floating point. Fortunately 53 bits is usually plenty with 2dp max. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [RFC] Un-staticise the toolchain
Hi, On 28 Apr 2012, at 04:12, David O'Brien wrote: On Thu, Apr 26, 2012 at 12:38:03PM +0100, Bob Bishop wrote: Apparently, current dependencies are much more spread, e.g. /bin/sh is dynamically linked [etc] That seems like a bad mistake, because it would prevent even booting single-user if rtld/libraries are broken. When one enters single user they are prompted for which shell to use. If /bin/sh is broken due to being dynamic, '/rescue/sh' will likely still work. Yes. You to have a statically linked /rescue/sh on board, so what's the point of /bin/sh being dynamic? The memory footprint really isn't an issue, and for my money the default shell ought to be bombproof. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [RFC] Un-staticise the toolchain
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 26 Apr 2012, at 10:35, Konstantin Belousov wrote: I think it is time to stop building the toolchain static. I was told that original reasoning for static linking was the fear of loosing the ability to recompile if some problem appears with rtld and any required dynamic library. Apparently, current dependencies are much more spread, e.g. /bin/sh is dynamically linked [etc] That seems like a bad mistake, because it would prevent even booting single-user if rtld/libraries are broken. - -- Bob Bishop r...@gid.co.uk -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.4 (Darwin) iD8DBQFPmTOivMaT6aS3xb8RAi1NAJ4gyvwPgdqtZjAERJ0grBsZYo5xBQCgikdo P4LXwI1rAbA23+29XWVV8w4= =i8e3 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: GCC debug flags cleanup
Hi, On 22 Dec 2011, at 11:52, Erik Cederstrand wrote: I've created a patch that cleans up FreeBSD Makefiles that unconditionally set the -g flag for GCC. [etc] Just a note of caution that I have had cases in the past where I suspected that GCC was generating broken code without -g and good code with. Makes debugging interesting :-) -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] changes to cam_get_device() and cam_open_device()
Hi, On 8 Oct 2010, at 10:07, Andriy Gapon wrote: As there was no objections, I am going to commit changes to cam_get_device() that remove the following features: - ignoring 'r' and 'n' at the start of device name - ignoring whitespace at end of device name - parsing and ignoring slice and partition names in a device name cam(3) manual page is going to be updated to reflect the changes. This would simplify the code and disambiguate its behavior. Non-rewound and character disk/SCSI devices has not been supported for quite a while now. [etc] Just a clarification, does this mean no /dev/nsa.. ? That would be a showstopper for many tape users. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: grep and Regular expression correctness
Hi, On 23 Aug 2010, at 12:51, chrisk-free...@list.mightyreason.com wrote: [...]The hardest part of POSIX regular expressions is in picking out the correct captured subexpressions. This makes programs like sed vulnerable to the bad regex.h engine that comes with the operating system. Luckily grep does not need the captured subexpressions, and thus does not need the complexity that comes from the ideas behind TRE. [etc] I think grep does potentially need the captured subexpressions, for eg: \([abc]\)99\1 matching eg b99b -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Building world with clang
Hi,
On 17 Aug 2010, at 12:32, Dimitry Andric wrote:
Hi,
Since clang has gone into the tree, there has been an effort to get head
in a state where world can optionally be built with it.
[...]
Now, for building clang as the bootstrap compiler, there are basically
two methods to make it use the correct headers, C startup objects, and
libraries from the object tree (${WORLDTMP}):
1) The isysroot method: build a regular version of clang, and make
sure WMAKEENV contains something like:
CC=${CC} -isysroot ${WORLDTMP} -B${WORLDTMP}/usr/lib/ \
-L${WORLDTMP}/usr/lib/
2) The tools-prefix method: build a special version of clang, that
has its default search paths for headers, startup objects and
libraries modified, to look for everything under ${WORLDTMP}.
Method 1) is used in the clangbsd project branch.
Method 2) is similar to what is used for building the in-tree gcc as
the bootstrap compiler. During the cross-tools stage, TOOLS_PREFIX is
defined to point at ${WORLDTMP}, and the bootstrap gcc's built-in
search paths get prefixed with it.
An advantage of method 1) is that it does not require any modifications
to the compiler, and basically just a few extra command line arguments.
The same method could probably even be made to work for gcc.
However, a disadvantage is that the built-in search paths of the
bootstrap compiler are not entirely disabled by using the -isysroot, -B
and -L flags,
This could be viewed as a bug ...
so there is still a chance that headers, objects or
libraries outside of ${WORLDTMP} will be picked up during the world
stage.
... and the last thing you want in buildworld is this kind of POLA violation ...
An advantage of method 2) is that you can be 100% sure all built-in
search paths of the bootstrap compiler point to directories under
${WORLDTMP}. Of course, a disadvantage is that you have to make some
modifications to the compiler source itself.
... so, which fix to the compiler do you want to make?
[etc]
--
Bob Bishop
r...@gid.co.uk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [patch] big whitespace cleanup in sys/kern/*
Hi, On 3 Aug 2010, at 18:58, Jamie Gritton wrote: I always understood that is was a style error *not* to have at least some whitespace before a label, that only top-level objects should be pushed all the way to the left column. Style(9) appears to be silent on this issue. Labels are special in that their scope is the enclosing function (not the enclosing block). Hanging them to the left emphasises this. -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Question related to FreeBSD Serial Console...
Hi, At 00:36 2/9/03, Nicole wrote: *SIGH* No what I want is NO serial console. DO NOT FOR ANY REASON turn off/not resp ond to the keyboard port Unfortunately, many motherboards (BIOSs?) won't initialise a PS/2 keyboard interface unless a keyboard is connected at boot time, so if you plug in a keyboard subsequently it won't work. Nothing the OS can do in this case (I believe), and yes it's a PITA. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best Known Methods for dual booting WinXP + -current
Hi, You can boot FreeBSD from the XP boot manager: see http://bsdvault.net/sections.php?op=viewarticleartid=88 [This used to be in the FAQ and perhaps should be resurrected there.] At 21:10 7/8/03, John Reynolds wrote: hello all, Having had a positive experience thus far with 5.1-RELEASE and -current beyond that on one of the new boxes I recently built, it is now time to build up the dual-boot system (BSD for me, WinXP for the wife ;). I've read different reports (some from laptop users) about using the WinXP loader to boot FreeBSD and I've also read reports that people used the standard boot-easy to boot both (while even others using GRUB). Are there currently any issues with dual-booting 5.1-RELEASE and/or -current along with Windows XP (probably SP1)? This would be on the same physical disk. What do you other -current users who are faced with dual booting XP do for the most part? Thanks, -Jr -- John Jennifer Reynolds johnjen at reynoldsnet.orgwww.reynoldsnet.org Sr. Physical Design Engineer - WCCG/CCE PDE jreynold at sedona.ch.intel.com Running FreeBSD since 2.1.5-RELEASE. FreeBSD: The Power to Serve! Unix is user friendly, it's just particular about the friends it chooses. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to provide useful debug info
Hi, Generally the minimum required information is /var/run/dmesg.boot and a stack backtrace at the crash. See http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html, particularly 17.4 and 17.5 At 13:13 23/7/03, Harald Schmalzbauer wrote: Hi all, I have currently at least 4 scenarios when my 5.1-release crashes on different hardware. So I built a kernel (GENERIC) with debugging symbols and DDB option. Now I'd like to provide usefull info about the following crashes: 1. booting from degraded RAID1 with HPT372 (machine crashes and I see db) 2. crash when unquirked UMASS is unpluged 3. crash when /stand/sysinstall is called after some uptime 4. machine hangs when LPT is removed in BIOS and ACPI enabled (no crash, I think I have to enter DDB with ctrl-alt-esc?) I read the FAQ (18.13. How can I make the most of the data I see when my kernel panics?) but I think this isn't applicable to my crash when the machine crashes before rc.conf can be read. And I really don't understand what he's talking about :( but perhaps I can help. Please tell me if I should do something like trace and write it down or something like that. Thanks, -Harry -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removal of netns - politically correct version
Hi, Here's a hint: The Apollo Domain and XNS networking protocols will no longer be offered after Cisco IOS Release 12.2. Information about these protocols will not appear in future releases of the Cisco IOS software documentation set. http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a008007fba7.html He's dead, Jim. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removal of netns - politically correct version
Hi At 08:53 5/3/03, Terry Lambert wrote: [...] The code is still useful as a simple implementation, much more easily understood by the student than the current TCP/IP stack, for certain. The same is true for netipx (wc -l *.[ch] is almost identical). -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas why we can't even boot a i386 ?
Hi, At 21:06 28/2/03, M. Warner Losh wrote: [...] We have some a few embedded systems coming back from the field soon and I plan on trying some tests on them (they are amd 386, so might not be good for you). [etc] IIRC AMD had a mask deal with Intel for the 386, so should be OK. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Cardbus-attached USB controller
Hi, I've got a Sitecom cardbus USB controller here, probes as: found- vendor=0x1033, dev=0x0035, revid=0x41 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x01 (250 ns), maxlat=0x2a (10500 ns) intpin=a, irq=255 cardbus0: Resource not specified in CIS: id=10, size=1000 cardbus0: unknown card (vendor=0x1033, dev=0x0035) at 0.0 irq 10 found- vendor=0x1033, dev=0x0035, revid=0x41 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x01 (250 ns), maxlat=0x2a (10500 ns) intpin=b, irq=255 cardbus0: Resource not specified in CIS: id=10, size=1000 cardbus0: unknown card (vendor=0x1033, dev=0x0035) at 0.1 irq 10 found- vendor=0x1033, dev=0x00e0, revid=0x02 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x10 (4000 ns), maxlat=0x22 (8500 ns) intpin=c, irq=255 cardbus0: Resource not specified in CIS: id=10, size=100 cardbus0: unknown card (vendor=0x1033, dev=0x00e0) at 0.2 irq 10 That's 2 ohci and an ehci (which I realise isn't supported (yet)). Would someone like to give me a clue how to plumb this thing in? TIA -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IBM Thinkpad 600E
Hi, Check your BIOS versions: TP600E BIOS had to be updated for ACPI to work with Win2k. The difference may explain the different behaviours. At 12:49 21/1/03, Maxim Sobolev wrote: Hmm, strange, pccard works righ OOB on my 600E running current. -Maxim Michael Lamb wrote: First time poster and susbscriber, someone suggested that I email my findings to the freebsd-current list, so hopefully this is the right place. I have been playing with FreeBSD 5.0 on my Thinkpad 600E and could not get the pccard to work at at all. So I searched thru some of the archives and pieced some information together enough to get it working. I was able to get it working by disabling acpi by adding the following in /boot/device.hints: hint.acpi.0.disabled=1 And it was also recommended in some resent posts to the list to add this to the same file to get pccard cardbus to work: hw.cbb.start_memory=0x2000 From there I just added the following to /etc/rc.conf: apm_enable=YES apmd_enable=YES Hopefully someone might find this information helpful if it has not already been brought up. -- Michael Lamb - [EMAIL PROTECTED] Sr. Network Engineer - O1 Communications To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FAST_IPSEC/racoon vs CISCO PIX anyone?
Hi, Problems interworking this combination, with ESP tunnel. SA gets negotiated OK, but ESP packets get rejected by the PIX: it says host not found a.b.c.d where a.b.c.d is its own endpoint address, and sends invalid SPI back to our end, even thought the SPI on the rejected ESP packet is the one just negitiated. This is RC2, racoon-20021120a. FWIW the same problem occurs on 4.7 with 'ordinary' IPSEC too. Any suggestions? TIA -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FAST_IPSEC/racoon vs CISCO PIX anyone?
At 16:09 13/1/03, Daniel C. Sobral wrote: Bob Bishop wrote: Hi, Problems interworking this combination, with ESP tunnel. SA gets negotiated OK, but ESP packets get rejected by the PIX: it says host not found a.b.c.d where a.b.c.d is its own endpoint address, and sends invalid SPI back to our end, even thought the SPI on the rejected ESP packet is the one just negitiated. This is RC2, racoon-20021120a. FWIW the same problem occurs on 4.7 with 'ordinary' IPSEC too. Any suggestions? TIA Well, this question can be silly, specially if you have already established tunnels before, but... Did you negotiate a SA for each direction? Yes, symmetrically. And we have done this stuff before (but not to a PIX). -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] It was one of those perfect summer days -- the sun was shining, a breeze was blowing, the birds were singing, and the lawn mower was broken ... -- James Dent -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3 floppy system for -current releases
Hi, I think MSDOS installs are pretty rare and NFS ones even rarer (FTP is easier to setup) Survey time! :) I use NFS installs a lot, both with floppies and with pxeboot'd sysinstall. I've never had much luck with FTP installs from a remote server. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd redux
Hi, At 22:55 1/7/02, George V. Neville-Neil wrote: When picobsd goes to build the libraries etc. it chokes on the csu stuff: [etc] First, I'd echo what someone else said about avoiding -current right now. Second, you may have better luck if you buildworld before attempting a picobsd build. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Alcatel Speed Touch PC
Hi, I wonder if there's any planned support for Alcatel Speed Touch PC (a ADSL PCI card) I think there are some linuxdrivers but what could be needed for FreeBSD support? Contact the guys listed on http://www.xsproject.org/speedtouch/ (bottom of the page). -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Please test PAUSE on non-Intel processors
CPU: Cyrix 486DX2 (486-class CPU) Origin = CyrixInstead DIR=0xa01b Stepping=10 Revision=0 # ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffd04 - 0xbfbffcc8 -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Please test PAUSE on non-Intel processors
CPU: Cyrix 6x86MX (166.19-MHz 686-class CPU) Origin = CyrixInstead Id = 0x600 Stepping = 0 DIR=0x0452 Features=0x80a135FPU,DE,TSC,MSR,CX8,PGE,CMOV,MMX spambox2% ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffbbc - 0xbfbffb80 CPU: AMD Duron(tm) Processor (995.77-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x670 Stepping = 0 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc044b18,AMIE,DSP,3DNow! seagoon% ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffb3c - 0xbfbffb00 CPU: AMD-K6(tm) 3D processor (501.14-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! hal%./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffb8c - 0xbfbffb50 CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x562 Stepping = 2 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX atlas% ./pausetest Testing PAUSE instruction: Register esp changed: 0xbfbffbe4 - 0xbfbffba8 -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADSUP!! KSE commit imminent.
Hi, At 15:32 -0400 11/9/01, Garrett Wollman wrote: I'm glad to see that, with a little help, you've managed to get the code into good-enough shape to make this work out. This is an important unit of functionality for FreeBSD 5.0 and I thank you and Matt and Peter for all the work you've done to make this happen without completely destabilizing -current. What he said. Will there be a pre-KSE tag? -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
su broken?
Hi, su appears to be asking for a password when invoked by root, eg: # su bin -c pwd Password: Broken, surely? -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
f77's (and cc's?) profiling
Hi, Can someone give me a hint why f77's profiling doesn't pick up any time data? Is this easy to fix? TIA -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: mutex vm not owned
Hi, I've seem to have the swap-related variety of this one: panic: mutex vm not owned at ../../vm/vm_page.h:328 ...from a kernel cvsup approx 0300 GMT on Sunday. But I'm surprised. This box has 128MB and will rarely swap building world (which is what it was doing). The only other oddity is that it had just had a brief not responding...alive again episode with the NFS server dishing up sources. Anyway, here's the abridged backtrace from DDB: panic() _mtx_assert() swp_pager_async_iodone() bufdone() bufdonebio() ad_interrupt() ata_intr() ithread_loop() fork_exit() fork_trampoline() I'll keep the box in DDB for a bit in case anyone wants more info, so dmesg not available right now but it's a pretty unremarkable configuration running GENERIC. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: workitem_free: still on list
Hi, This happened during a buildworld with a kernel built from: cvsup Fri May 18 04:06:02 BST 2001 On reboot, I got the manual fsck jive with the bad superblock: values disagree ,,with,, first alternate, and had to re-enable softupdates on / Config is basically GENERIC + SMP. dmesg is appended. Abridged backtrace: panic() workitem_free() free_newdirblk() handle_written_inodeblock() softdep_disk_write_complete() bufdone() bufdonebio() dadone() camisr() ithread_loop() fork_exit() fork_trampoline() dmesg: FreeBSD 5.0-CURRENT #20: Wed May 16 00:24:36 BST 2001 [EMAIL PROTECTED]:/source/cleansrc/sys/compile/BLUDNOK_MP Timecounter i8254 frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (349.07-MHz 686-class CPU) Origin = GenuineIntel Id = 0x651 Stepping = 1 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM O V,PAT,PSE36,MMX,FXSR real memory = 134152192 (131008K bytes) config enable ed0 config port ed0 0x300 config irq ed0 10 config iomem ed0 0xd8000 config flags ed0 0 config disable cs0 config disable fe0 config disable ie0 config disable lnc0 config disable sn0 config quit avail memory = 124653568 (121732K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel kernel at 0xc05bb000. Preloaded userconfig_script /boot/kernel.conf at 0xc05bb09c. Pentium Pro MTRR support enabled WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 7 entries at 0xc00fda90 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard IOAPIC #0 intpin 16 - irq 2 IOAPIC #0 intpin 19 - irq 16 pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 11 at de vice 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Timecounter PIIX frequency 3579545 Hz pci0: bridge, PCI-unknown at 7.3 (no driver attached) ahc0: Adaptec 2940 Ultra SCSI adapter port 0xe400-0xe4ff mem 0xea00-0xea00 0fff irq 2 at device 8.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: display, VGA at 11.0 (no driver attached) atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 drq 0 on isa0 ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 pmtimer0 on isa0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0501 can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 ad0: 1222MB QUANTUM FIREBALL_TM1280A [2484/16/63] at ata0-master WDMA2 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s2a cd0 at ahc0 bus 0 target 6 lun 0 cd0: PIONEER DVD-ROM DVD-303 1.09 Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc0 bus 0 target 5 lun 0 da1: IOMEGA ZIP 100 E.08 Removable Direct Access SCSI-2 device da1: 3.300MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DNES-309170W SA30 Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) SMP: AP CPU #1 Launched! -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd
panic: sleeping process owns a mutex
Hi, This while building world, with a kernel cvsup at Fri Apr 27 04:06:40 BST 2001 kern/kern_synch.c:386 sleeping with vr0 locked from pci/if_vr.c:1315 abridged backtrace: panic() propagate_priority() _mtx_lock_sleep() vr_intr() ithread_loop() fork_exit() fork_trampoline() dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-current #0: Sun Apr 29 15:34:55 GMT 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 451029428 Hz CPU: AMD-K6(tm) 3D processor (451.03-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 130011136 (126964K bytes) avail memory = 120705024 (117876K bytes) Preloaded elf kernel kernel at 0xc05a8000. K6-family MTRR support enabled (2 registers) WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 7 entries at 0xc00f0d10 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 atapci0: SiS 5591 ATA33 controller port 0xd000-0xd00f,0xd400-0xd403,0xd800-0xd 807,0xe000-0xe003,0xe400-0xe407 irq 14 at device 0.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 pci0: unknown at 1.1 (no driver attached) pcib1: PCI-PCI bridge at device 2.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at 0.0 (no driver attached) pcm0: ESS Solo-1E port 0x9400-0x9403,0x9800-0x9803,0xa000-0xa00f,0xa400-0xa40f ,0xa800-0xa83f irq 5 at device 6.0 on pci0 vr0: VIA VT6102 Rhine II 10/100BaseTX port 0x9000-0x90ff mem 0xde80-0xde80 00ff irq 12 at device 10.0 on pci0 vr0: Ethernet address: 00:50:ba:25:97:f6 miibus0: MII bus on vr0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto aha0 at port 0x330-0x333 irq 11 drq 5 on isa0 aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 fd1: 1200-KB 5.25 drive on fdc0 drive 1 pmtimer0 on isa0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sn0: ioaddr is 0x300 sn0: test1 failed vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0401 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0303 can't assign resources ad0: 13072MB QUANTUM FIREBALLP KX13.6 [26559/16/63] at ata0-master UDMA33 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s2a cd0 at aha0 bus 0 target 3 lun 0 cd0: IBM CDRM00201 !F 0724 Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ahc_intr - referenced scb not valid... panic for safety
Hi, Just had one of these on yesterday's -current. Anyone interested in the details? -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can't boot recent kernels
Hi, I've been unable to boot any kernel (including GENERIC) built in the past week or so. The machine restarts immediately the kernel is entered, no console output whatsoever after the loader. Older kernels are fine. Have I missed some important change, and/or how do I go about debugging this? -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic on last night's kernel
Hi,
Jake Burkholder wrote:
Could you try this patch and let me know if it changes anything?
Index: i386/isa/intr_machdep.c
===
RCS file: /home/ncvs/src/sys/i386/isa/intr_machdep.c,v
retrieving revision 1.46
diff -u -r1.46 intr_machdep.c
--- i386/isa/intr_machdep.c 2001/01/21 19:25:06 1.46
+++ i386/isa/intr_machdep.c 2001/01/27 18:51:12
@@ -704,6 +704,7 @@
if ((idesc-ih_flags INTR_FAST) == 0) {
mtx_enter(sched_lock, MTX_SPIN);
if (ithd-it_proc-p_stat == SWAIT) {
+ ithd-it_proc-p_intr_nesting_level = 0;
ithd-it_proc-p_stat = SRUN;
setrunqueue(ithd-it_proc);
/*
Yup, that does it. Thanks!
--
Bob Bishop (0118) 977 4017 international code +44 118
[EMAIL PROTECTED]fax (0118) 989 4254
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
panic on last night's kernel
Hi, cvsup at Sat Jan 27 04:04:26 GMT 2001 While booting, just after the message: faith0 XXX: driver didn't initialize queue mtx panic: malloc(M_WAITOK) in interrupt context DDB gives: panic() malloc() exit1() kthread_suspend() ithd_loop() fork_exit() fork_trampoline() -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: -current grinds exceeding slow
Hi, At 11:42 -0700 11/10/00, John Baldwin wrote: On 10-Oct-00 Bob Bishop wrote: Hi, What's happened recently to make -current so slow? [etc] I don't know. Can you try to narrow down the date by cvsupping or cvs updating with date tags to see when it started slowing down? More data: it's networking that's doing it, not NFS per se. I'm doing a build with local sources on one of the affected boxes, on first impression looks like that is up to speed. Both my affected boxes have ed NICs, I'll see if I can scare up a different card to try in case it's the ed driver. Watch this space... -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ed0: warning - receiver ring buffer overrun
Hi, I'm seeing lots of: ed0: warning - receiver ring buffer overrun This box is building the world with sources via NFS. What gives? -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ed0: warning - receiver ring buffer overrun
At 20:08 +0200 10/10/00, Wilko Bulte wrote: On Tue, Oct 10, 2000 at 01:35:57PM +0100, Bob Bishop wrote: Hi, I'm seeing lots of: ed0: warning - receiver ring buffer overrun This box is building the world with sources via NFS. What gives? Something not servicing the ed0 card fast enough? That would be consistent with what I'm seeing. FWIW: my -current build on a PPro 200 took it's normal 3-something hours. NFS seems to be horrendously slow right now, my builds are taking 5 times as long as expected. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ed0: warning - receiver ring buffer overrun
Hi, ed0: warning - receiver ring buffer overrun One more datapoint: I have two boxes doing this, both with ed but one is ISA, the other is PCI. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent kernels won't boot
Hi, At 01:04 -0700 9/10/00, Peter Wemm wrote: Mike Smith wrote: That was it. Is the 4MB kernel size limit documented anywhere? I don't know :-) I luckily noticed this by a lot of trials. I'm not aware of any 4MB limit on kernel size (and I ought to be if there is one 8). Can you run the details past me? (I've regularly booted much larger kernels in the past...) Uhh, are you sure? Ignore the size of the file, what does 'size(1)' say about these large kernels? Does text+data+bss excede 4MB? I have a nagging suspicion that we only set up 4MB of page tables during the early part of the bootstrap process in locore.s. (forgive me for not looking, I have a most evil headache and locore.s is no way to improve it :-). Thinking about it some more, there may be a 3MB limit as we load above 1MB. I recall some heavy magic with the SMP bootstrap where we only use one PTD slot for 0-4MB in early boot Example: % size kernel*/kernel textdata bss dec hex filename 3302182 206816 2265368 5774366 581c1e kernel.old/kernel 2947194 207168 168152 3322514 32b292 kernel/kernel Same kernel config except that top one includes KTR options and won't boot, bottom one has no KTR and boots OK. I've been running with SMP_DEBUG, KTR and the rest for a while, this trouble started a few days ago. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ahc-related panics
Hi, I'm getting repeatable panics with -current, related to ahc. I'm seeing lots of ahc:0:A:0: ahc_intr - referenced scb not valid during seqint 0x71 scb(nn) WARNING no cammand for scb nn (cmdcmplt) plus the WARNING without the other message. Eventually it panics with a kernel-mode page fault, typically either in ahc_set_recoveryscb() in the softinterrupt thread or in ahc_match_scb() in the ahc interrupt thread. This is an SMP box building the world with -j8, so fairly busy. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent kernels won't boot
Hi, At 02:27 +0900 9/10/00, Mitsuru IWASAKI wrote: I think ACPI is not related with this problem, it was simply kernel size ( 4MB) for me. I removed some device drivers and options from my kernel config then the problem was solved. That was it. Is the 4MB kernel size limit documented anywhere? -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Recent kernels won't boot
Hi, Kernels built from recent cvsup (24 hrs) quit immediately on boot, back to the BIOS, no messages no nothin'. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB modems
Hi, Can anyone give a quick synopsis of the current status of support for USB modems? TIA -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -e option to umount?
At 16:02 -0700 18/6/00, Greg Lehey wrote: What do people think about adding a -e option to umount(8) to eject a removable medium where possible? What's special about mounted devices? I'd prefer to see an eject command which attempts to unmount the device if it's mounted. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bug in advansys driver
At 11:52 +0400 23/5/00, Oleg Sharoiko wrote: Hello! It seems that during porting to newbus architecture adv_attach was left unchanged and current version (I mean the current version of -STABLE sources, I didn't check -CURRENT) returns incorrect values (1 on success, 0 in all other cases). FWIW -CURRENT is the same, but it looks like none of the calls check the return value anyway. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bug in advansys driver
At 16:11 23/05/00 +0400, Oleg Sharoiko wrote: On Tue, 23 May 2000, Bob Bishop wrote: BB FWIW -CURRENT is the same, but it looks like none of the calls check the BB return value anyway. Well. There was a message during the boot of kernel which notified that "adv0 device prove/attach returned 1" (or smt. like this). So I think the return code is checked somewhere and (what's more important) before the fix kernel seemed to hang at stage xpt_for_all_busses(xptconfigfunc, NULL); You are on -STABLE, right? On -CURRENT it's been working fine for me, no complaining messages... ed0: address 00:20:18:80:b4:6d, type NE2000 (16 bit) adw0: AdvanSys 38C0800 Ultra2 SCSI Adapter port 0x6600-0x66ff mem 0xe000-0 xe0ff irq 10 at device 12.0 on pci0 adw0: SCSI ID 7, High Low SE Term Enabled, LVD Term Enabled, Queue Depth 253 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ... because the return value apparently isn't checked; which is why I posted (and included -current) in the first place. -- Bob Bishop +44 118 977 4017 [EMAIL PROTECTED]fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
At 18:12 -0600 14/4/00, Nate Williams wrote: [...] You can easily run out of inodes on the roof partition. Sure, my roof leaks from time to time. But _inodes_? :-) :-) -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The world ain't building
Hi, With USA_RESIDENT=NO and -DNOCRYPT: cc -O2 -pipe -I/usr/obj/source/cleansrc/lib/libipsec -DIPSEC_DEBUG -DIPSEC -DINE T6 -I/usr/obj/source/cleansrc/i386/usr/include -c policy_token.c -o policy_token .o /source/cleansrc/lib/libipsec/policy_token.l: In function `__libyylex': /source/cleansrc/lib/libipsec/policy_token.l:88: `__libipsecyylval' undeclared ( first use in this function) /source/cleansrc/lib/libipsec/policy_token.l:88: (Each undeclared identifier is reported only once /source/cleansrc/lib/libipsec/policy_token.l:88: for each function it appears in .) *** Error code 1 Stop in /source/cleansrc/lib/libipsec. -- Bob Bishop +44 118 977 4017 [EMAIL PROTECTED]fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP buildworld times / performance tests
:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote: [...] 6 minutes 20 seconds (about 7%). I'm seeing the same order of improvement still. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: src/sys/i386/isa/ipl.s rev 1.35 should fix boot lockups
Hi, At 01:14 -0800 29/3/00, Matthew Dillon wrote: [...] I am hoping that this will also fix Bob Bishop's reported boot lockup. It does! When I get a minute I'll rerun that timing test... -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMP kernel broken at cvsup Tue Mar 28 11:56:07 BST 2000
Hi, Appears to boot OK, but then won't answer to network or console, not even CtlAltEsc to DDB. Screen saver kicks in OK though. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP kernel broken at cvsup Tue Mar 28 11:56:07 BST 2000
At 09:52 -0800 28/3/00, Matthew Dillon wrote: Make sure you haven't confused it between the patch set and the commit I made last night. Do a cvs update and then a cvs diff to make sure things haven't gotten confused. Just blew /sys away and checked it out afresh. Same result I'm afraid, although I did get into DDB this time. Nothing obviously wrong, but the backtrace didn't go back past the keyboard interrupt. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Buildworld hung up with lots of cron processes
Hi, cvsup at Wed Mar 22 04:03:28 GMT 2000, this built without problems with -j8 on my SMP box, but on a uniprocessor (-j4, eveything else the same) something appears to have deadlocked. The machine is generally OK but the build has hung and there are 57 cron processes hanging around (ps ax follows). Any ideas? I'll keep it hanging around for a bit, let me know if you want more info. atlas# ps ax PID TT STAT TIME COMMAND 0 ?? DLs0:00.12 (swapper) 1 ?? ILs0:00.01 /sbin/init -- 2 ?? DL 0:00.83 (pagedaemon) 3 ?? DL 0:00.00 (vmdaemon) 4 ?? DL 0:01.17 (bufdaemon) 5 ?? DL 0:07.85 (syncer) 107 ?? Ss 0:00.54 syslogd 114 ?? Ss0:06.86 ntpd -p /var/run/ntpd.pid 118 ?? Is 0:00.01 /usr/sbin/portmap 129 ?? Is 0:00.01 mountd -r 132 ?? Is 0:00.01 nfsd: master (nfsd) 134 ?? I 3:48.71 nfsd: server (nfsd) 135 ?? I 0:16.24 nfsd: server (nfsd) 136 ?? I 0:05.48 nfsd: server (nfsd) 137 ?? I 0:01.57 nfsd: server (nfsd) 140 ?? Is 0:00.00 rpc.statd 145 ?? I 0:00.00 nfsiod -n 4 146 ?? I 0:00.00 nfsiod -n 4 148 ?? I 0:00.00 nfsiod -n 4 149 ?? I 0:00.00 nfsiod -n 4 172 ?? Is 0:00.03 inetd 175 ?? Ss 0:00.83 cron 250 ?? RNs 1614:32.53 ./dnetc -quiet 263 ?? Ss 0:00.21 telnetd 2174 ?? D 0:00.00 cron 2175 ?? DVL0:00.00 cron [54 more cron processes here, state D or DVL] 2277 ?? D 0:00.00 cron 2278 ?? DVL0:00.00 cron 264 p0 Is 0:00.06 csh 265 p0 S 0:00.09 _su (csh) 1446 p0 I 0:00.01 sh -c (\nmake -j4 CFLAGS='-O2 -pipe' -DNOCRYPT -DNOPR 1447 p0 I 0:00.00 sh -c (\nmake -j4 CFLAGS='-O2 -pipe' -DNOCRYPT -DNOPR 1448 p0 S 0:03.08 make -j4 CFLAGS=-O2 -pipe -DNOCRYPT -DNOPROFILE world 1455 p0 I 0:00.00 sh -ev 1456 p0 S 0:03.04 make -m /source/cleansrc/share/mk -f Makefile.inc1 bu 1459 p0 I 0:00.03 sh -ev 1479 p0 S 0:02.79 make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML boots 1482 p0 I 0:00.03 sh -ev 1907 p0 S 0:02.79 make all 1908 p0 I 0:00.01 sh -ev 2172 p0 I 0:00.00 sh -ev 2173 p0 DL 0:00.00 sh -ev 2279 p0 R+ 0:00.00 ps ax 247 v0 Is+0:00.01 /usr/libexec/getty Pc ttyv0 248 v1 Is+0:00.01 /usr/libexec/getty Pc ttyv1 249 v2 Is+0:00.01 /usr/libexec/getty Pc ttyv2 atlas# -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
World not building
Hi, Building the world with -DNOCRYPT -DNOPROFILE as is my habit, I'm getting the following in stage 4: /source/cleansrc/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-esp.c:5 4: blowfish.h: No such file or directory /source/cleansrc/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-esp.c:5 6: rc5.h: No such file or directory /source/cleansrc/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-esp.c:5 9: cast.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /source/cleansrc/usr.sbin/tcpdump/tcpdump. *** Error code 1 Stop in /source/cleansrc/usr.sbin/tcpdump. *** Error code 1 Stop in /source/cleansrc/usr.sbin. *** Error code 1 Stop in /source/cleansrc. *** Error code 1 Have I missed something? Any ideas? TIA -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cdrecord problem with current current
At 17:19 -0700 19/2/00, Kenneth D. Merry wrote: On Sat, Feb 19, 2000 at 19:28:23 +, Bob Bishop wrote: Hi, cdrecord, freshly built on last night's -current: Freshly built? That's cdrecord 1.8a21, which is several versions old. I think you should be using cdrecord 1.8 release from the ports tree. red face Uh, yes, it would have helped enormously if I'd actually installed it. Works just fine, sorry for the false alarm. /red face -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cdrecord problem with current current
Hi, cdrecord, freshly built on last night's -current: atlas# cdrecord -v dev=1,6,0 -inq Cdrecord release 1.8a21 Copyright (C) 1995-1999 Jrg Schilling TOC Type: 1 = CD-ROM scsidev: '1,6,0' scsibus: 1 target: 6 lun: 0 atapi: 0 cdrecord: Warning: controller returns zero sized CD capabilities page. cdrecord: Warning: controller returns wrong size for CD capabilities page. cdrecord: Warning: controller returns wrong page 0 for CD capabilities page (2A) . Device type: Removable CD-ROM Version: 2 Response Format: 2 Capabilities : SYNC Vendor_info: 'YAMAHA ' Identifikation : 'CRW4416S' Revision : '1.0f' Device seems to be: Generic CD-ROM. atlas# ...so cdrecord can't tell what the device is. Am I in trouble because the CDR isn't on the first SCSI controller, or has something got broken? Dmesg follows: FreeBSD 4.0-CURRENT #28: Sat Feb 19 15:56:28 GMT 2000 rb@atlas:/source/cleansrc/sys/compile/ATLAS Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x400b10 real memory = 33554432 (32768K bytes) avail memory = 28872704 (28196K bytes) Preloaded elf kernel "kernel" at 0xc03b1000. md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 10 chip1: Intel 82371AB Power management controller port 0x5f00-0x5f0f at device 7.3 on pci0 ed0: NE2000 PCI Ethernet (ProLAN) port 0x6500-0x651f irq 9 at device 10.0 on p ci0 ed0: address 00:20:18:80:b4:6d, type NE2000 (16 bit) adw0: AdvanSys 38C0800 Ultra2 SCSI Adapter port 0x6600-0x66ff mem 0xe000-0 xe0ff irq 10 at device 12.0 on pci0 adw0: SCSI ID 7, High Low SE Term Enabled, LVD Term Enabled, Queue Depth 253 devclass_alloc_unit: ata0 already exists, using next available unit number devclass_alloc_unit: ata1 already exists, using next available unit number devclass_alloc_unit: ed0 already exists, using next available unit number fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 aha0 at port 0x330-0x333 irq 11 drq 5 on isa0 aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: Parallel I/O on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port plip0: PLIP network interface on ppbus0 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0a cd0 at aha0 bus 0 target 6 lun 0 cd0: YAMAHA CRW4416S 1.0f Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [1 x 2048 byte records] da0 at adw0 bus 0 target 0 lun 0 da0: IBM DCAS-34330W S65A Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at adw0 bus 0 target 1 lun 0 da1: IBM DDRS-34560D DC1B Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Odd panic
Hi, cvsup at Sat Nov 27 04:02:41 GMT 1999, looks like it went in the middle of starting up SCSI devices. This box is not SMP and has a 2940UW, my SMP -current box with a plain 2940 doesn't do this. ... da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DCAS-34330W S65A Fied Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2b da1 at ahc0 bus 0 target 1 lun 0 da1: IBM DDRS-34560D DC1B Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) fault code = supervisor read, page not present instruction pointer = 0x8:0xc01658e6 stack pointer = 0x10:0xc03a6f3c frame pointer = 0x10:0xc03a6f3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enable, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = none kernel: type 12 trap, code=0 Stopped at devsw+0x6 cmpl $0, 0x2c(%eax) db -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Odd panic
Hi, can you try to locate the symbols around 0xc01658e6 in your kernel ? I mistranscribed that (really must get serial consoles sorted out), in fact it's: c0165e80 T devsw Also, when you end in the debugger, always type "trace" so we get a stacktrace to look at. Yes, sorry, got called for dinner at an inopportune moment ;-) devsw() at devsw+0x6 vfs_mountroot_try(c0391092,c02c531c) at vfs_mountroot_try+0xe9 vfs_mountroot(0,3a4c00,3ab000,0,c011d5e6) at vfs_mountroot+0x5a mi_startup(c03a6fb4,b0246,ffe,3ab000,c017ada1) at mi_startup+0x70 begin() at begin+0x4b Also, further back in the log there's a "setrootbyname failed". -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Odd panic
Hi, At 7:54 pm +0100 27/11/99, Poul-Henning Kamp wrote: [...] What is in your /etc/fstab for the root fs ? That was it: I was still running on /dev/sd*, looks like that just stopped working. Thanks -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: calcru() warnings...
Hi, At 8:00 pm +0100 24/11/99, Poul-Henning Kamp wrote: I still hear reports of sporadic calcru() warnings. If any of you see these, could you try to see if they correlate to the uptime of the machine in question ? Nov 23 00:03:35 bludnok /kernel: [boot] Nov 24 09:02:06 bludnok /kernel: calcru: negative time of -4660895 usec for pid 76002 (cc) Ie up just under 9 hours. Building world at the time. This box is running SMP, full details on request. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 4.0 SCSI Tape Driver
Hi, At 11:01 am -0800 15/11/99, Matthew Jacob wrote: I repeat what I said in other mail- can you actually show me a tape drive where what I propose really doesn't work? I have access to a few assorted drives and I'll do the experiments but don't hold your breath. BUT I have to say that on principle I'm with Rod on this one: EOF != EOT and mixing them up is a recipe for (inter alia) finding you can't read back dumps when you need them. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot)
Hi, At 12:33 pm +0100 31/10/99, Leif Neland wrote: current, cvsupped around 3:00 GMT 31 oct. When trying to boot a new kernel, the machine simply hangs. I have narrowed it down to ed0[etc] The LinkSys probe code (in particular the checksum at the start of ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine up. I guess you have the same problem. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot)
Hi, At 2:56 pm +0100 31/10/99, Leif Neland wrote: [...]If ed_get_linksys was called later than my card was detected... I guess it's an ordering thing, but I don't have a LinkSys card here for testing. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot)
Hi, At 7:03 am -0800 31/10/99, Jonathan M. Bresler wrote: The LinkSys probe code (in particular the checksum at the start of ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine up. I guess you have the same problem. ouch! not goodwhat is the ethernet address of your ne2000 clone? ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linksys conflicts with NE2000
Hi, At 10:52 am -0800 31/10/99, Jonathan M. Bresler wrote: okay i have changed the order in which we test for NE1000, NE2000, and the Linksys (dl10016c ? ethernet controller). pleazse test and let me know how this patch does.[etc] OK the patch fixes the problem here. [Thanks for the context diff] -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current kernel locks up during boot
Hi, -current kernels from the past 48hrs or so lock up during boot on my SMP box, as in: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #50: Tue Oct 26 13:53:14 BST 1999 rb@bludnok:/source/cleansrc/sys/compile/BLUDNOK_MP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (349.07-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,MMX,FXSR real memory = 134152192 (131008K bytes) avail memory = 126148608 (123192K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel.old" at 0xc03cb000. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ide_pci0: Intel PIIX4 Bus-master IDE controller at device 7.1 on pci0 chip1: UHCI USB controller irq 11 at device 7.2 on pci0 Timecounter "PIIX" frequency 3579545 Hz chip2: Intel 82371AB Power management controller at device 7.3 on pci0 ahc0: Adaptec 2940 Ultra SCSI adapter irq 16 at device 8.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: S3 ViRGE DX/GX graphics accelerator irq 19 at device 11.0 on pci0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): QUANTUM FIREBALL_TM1280A wd0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 ...and there it freezes. Total lockup, reset button or power cycle only. Apparently it's barfing either on one of the PCI netcard probes, or trying to initialise ed0 which on an older kernel probes as: ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) Any ideas? -- Bob Bishop +44 118 977 4017 [EMAIL PROTECTED]fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: free vnode isn't
Hi, At 1:16 pm -0700 3/10/99, Archie Cobbs wrote: I'd suggest turining off soft-updates first.[etc] Here's a thing. I'd forgotten that I'd borrowed the scratch drive (where /usr/obj is) out of this box a while back. It seems when I replaced it I forgot to enable softupdates (which had been on previously). So the failures occurred with softupdates off on /usr/obj but on on root, and /usr/src coming in on NFS. I reenabled softupdates on /usr/obj and I haven't seen the panic since. Go figure. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
