Re: Deprecating ISA sound cards
On Fri, Mar 18, 2022 at 12:08:02PM -0400, Ed Maste wrote: > ISA sound cards have been obsolete for more than a decade, and it is > (past) time to retire their drivers. This includes the following > drivers/devices: > > snd_ad1816 Analog Devices AD1816 SoundPort > snd_ess Ensoniq ESS > snd_guscGravis UltraSound > snd_mss Microsoft Sound System > snd_sbc Creative Sound Blaster You can remove snd_aureal, snd_ds1 and snd_maestro as well while you're at it. They've been broken for 10+ years: https://lists.freebsd.org/pipermail/freebsd-multimedia/2012-January/012751.html -- Joel
Re: FCP-101: obsolete driver removal planned for 2019-05-18
On Fri, May 10, 2019 at 06:27:12PM +, Brooks Davis wrote: > I've posted a review to remove obsolete 10 and 10/100 Ethernet drivers > as previous approved in FCP-101. The following drivers are slated for > removal from FreeBSD-HEAD (to be FreeBSD-13): > > ae, bm, cs, de, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe I've said it before and I'll try one last time. Can we save ae? I have one machine with ae, running 12. There are three dmesgs from NYC*BUG dmesgd containing ae cards, all running recent versions of FreeBSD. I also have ed, pcn and vx in a few machines, but I guess I'll have to live without those... -- Joel ___ 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 futur of the roff toolchain
On Sun, May 21, 2017 at 02:57:33PM +0200, Baptiste Daroussin wrote: > > I would like to change this approach and get back to the initial approach > taken > by others before I jumped in and I would like just entirely remove the roff > toolchain from base and let people rely on GNU roff from ports. > > What I want to propose now, it to render them as PDF (html?) once and push > them > somewhere (to be defined) as static document on our documentation website. > Please doceng@ provide me a location where to push them. > > And then remove bsd.doc.mk from FreeBSD 12.0 along with the removal of groff. Yes. I definitely support these ideas. :-) -- Joel ___ 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: UTF-8 by default?
On Wed, Jul 20, 2016 at 09:08:41PM +0200, Baptiste Daroussin wrote: > On Wed, Jul 20, 2016 at 08:38:14PM +0200, Joel Dahl wrote: > > On Wed, Jul 20, 2016 at 04:07:41PM +0200, Baptiste Daroussin wrote: > > > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: > > > > On 20 Jul 2016, at 9:13, Tim Čas wrote: > > > > > > > > > So, without further ado: > > > > > 1) What are the reasons that UTF-8 isn't the default yet? > > > > > 2) Would it be possible to make this the default in 11.0? What about > > > > > 12.0? > > > > > 3) Assuming an effort is started towards making UTF-8 the default, > > > > > what changes would be required? > > > > > > > > At least according to one of my students (who makes more extensive use > > > > of > > > > i18n than I do), enabling UTF-8 by default is pretty straightforward: > > > > > > > > https://github.com/musec/freebsd/wiki/Common-setup#utf-8-support > > > > > > the LC_COLLATE=C is not needed anymore with freebsd 11+ > > > > > > > > If there's anything missing there, I'd love to hear about it. > > > > > > > - unicode support in our old groff is pretty bad, I plan to replace it > > > with > > > heirloom-doctools which does handle unicode propertly (as far I have > > > tested > > > at least) > > > > I haven't really been paying attention lately so things might have changed, > > but why can't we just remove groff now? We have mdocml, and for people that > > really need the groff functionality can just install it or heirloom-doctools > > from ports. The initial plan was to remove groff after we imported mdocml, > > but > > it was never removed and I lost interest, so again, things might have > > changed > > since then. > > We have roff documentation in based, plus a lot of people argues that not > havin > a roff toolchain in base is an issue for them. What is the issue? I tried to find some clues in the mailing list archive, but my google skills are obviously weak. When we discussed this (mainly uqs@ and me) 4 years ago the goal was to move the old roff'ed papers to the doc/ repo. I didn't see any objections when it was suggested on the doc/www mailing lists back in 2013. There is even an old pr about it, 178730. -- Joel ___ 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: UTF-8 by default?
On Wed, Jul 20, 2016 at 04:07:41PM +0200, Baptiste Daroussin wrote: > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: > > On 20 Jul 2016, at 9:13, Tim Čas wrote: > > > > > So, without further ado: > > > 1) What are the reasons that UTF-8 isn't the default yet? > > > 2) Would it be possible to make this the default in 11.0? What about > > > 12.0? > > > 3) Assuming an effort is started towards making UTF-8 the default, > > > what changes would be required? > > > > At least according to one of my students (who makes more extensive use of > > i18n than I do), enabling UTF-8 by default is pretty straightforward: > > > > https://github.com/musec/freebsd/wiki/Common-setup#utf-8-support > > the LC_COLLATE=C is not needed anymore with freebsd 11+ > > > > If there's anything missing there, I'd love to hear about it. > > > - unicode support in our old groff is pretty bad, I plan to replace it with > heirloom-doctools which does handle unicode propertly (as far I have > tested > at least) I haven't really been paying attention lately so things might have changed, but why can't we just remove groff now? We have mdocml, and for people that really need the groff functionality can just install it or heirloom-doctools from ports. The initial plan was to remove groff after we imported mdocml, but it was never removed and I lost interest, so again, things might have changed since then. -- Joel ___ 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: "_secure_path: cannot stat /etc/login.conf: Not permitted in capability mode"
On Mon, Jun 20, 2016 at 04:42:39AM -0700, David Wolfskill wrote: > After updating my (amd64) build machine from r302018 to r302026, things > work OK, but (now that I've re-connected the serial cable so I can > actually interact with the serial console -- i.e., this may have > occurred a while back, but I wouldn't have noticed), I see: > > ... > Starting devd. > add host 127.0.0.1: gateway lo0 fib 0: route already in table > add net default: gateway 172.16.8.1 > add > FreeBSD/amd64 (freebeast.catwhisker.org) (ttyu0) > > login: Jun 20 11:34:16 freebeast sshd[736]: _secure_path: cannot stat > /etc/login.conf: Not permitted in capability mode > Jun 20 11:34:16 freebeast last message repeated 2 times > Jun 20 11:34:21 freebeast sshd[810]: _secure_path: cannot stat > /etc/login.conf: Not permitted in capability mode > Jun 20 11:34:21 freebeast last message repeated 2 times > Jun 20 11:34:25 freebeast sshd[882]: _secure_path: cannot stat > /etc/login.conf: Not permitted in capability mode Yes, me too. I reported this a few days ago here on current@. -- Joel ___ 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: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode
On Mon, Jun 13, 2016 at 07:00:46AM -0400, Ngie Cooper (yaneurabeya) wrote: > > > On Jun 13, 2016, at 06:57, Joel Dahl wrote: > > > > Hi, > > > > I've just rebuilt and installed latest current on a machine here. I noticed > > the following message in dmesg after a reboot: > > > > _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode > > > > I don't remember seeing this before. > > Hi Joe, > Try reverting r301867. Let Robert know if that fixes your issue. Hi, This is with r301857. Forgot to mention that in my previous mail. Sorry. -- Joel ___ 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"
_secure_path: cannot stat /etc/login.conf: Not permitted in capability mode
Hi, I've just rebuilt and installed latest current on a machine here. I noticed the following message in dmesg after a reboot: _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode I don't remember seeing this before. -- Joel ___ 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: em(4) broken in HEAD?
On Fri, May 20, 2016 at 07:32:30PM -0700, K. Macy wrote: > I'm seeing watchdog resets on em(4) in my VMWare as of the last day or two. > > > > > > > I don't use ipfw, aliases or anything other than stock networking. I > > was unable to copy a large image off the VM without getting an > > unending stream of watchdog resets which could only be fixed by a > > reboot. Fortunately a subsequent IFC fixed it as of ~15 hours ago. > > > > I take that back. It's still happening. OK - good to know. I'm going to be travelling for a few days so I won't have time to do a binary search to find the commit that broke it. -- Joel ___ 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: em(4) broken in HEAD?
On Fri, May 20, 2016 at 01:59:46PM +0200, O. Hartmann wrote: > On Fri, 20 May 2016 13:55:50 +0200 > Joel Dahl wrote: > > > Hi, > > > > I've just rebuilt CURRENT on a VMware virtual machine and it's now > > running r300276. After reboot, I ssh'ed to the machine but my ssh > > session hanged after ~10 seconds or so. The console started spitting > > out "em0: Watchdog timeout - resetting" messages at the same time. > > Basically no networking works. > > > > It's the same thing after every reboot. Networking works for a few > > seconds, just long enough for you to run a couple of commands over > > ssh. Then it breaks. > > > > My previous build on this machine was from about one week ago. It > > works like it should. > > > > Do you use by any means IPFW ? Nope. -- Joel ___ 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"
em(4) broken in HEAD?
Hi, I've just rebuilt CURRENT on a VMware virtual machine and it's now running r300276. After reboot, I ssh'ed to the machine but my ssh session hanged after ~10 seconds or so. The console started spitting out "em0: Watchdog timeout - resetting" messages at the same time. Basically no networking works. It's the same thing after every reboot. Networking works for a few seconds, just long enough for you to run a couple of commands over ssh. Then it breaks. My previous build on this machine was from about one week ago. It works like it should. -- Joel ___ 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: boot with floppy enabled doesn't.....
On Wed, May 04, 2016 at 06:54:34AM -0700, John Baldwin wrote: > On Wednesday, May 04, 2016 09:51:45 AM Joel Dahl wrote: > > On Tue, May 03, 2016 at 03:52:43PM -0700, John Baldwin wrote: > > > On Tuesday, May 03, 2016 10:20:21 PM Joel Dahl wrote: > > > > On Tue, May 03, 2016 at 12:58:15PM -0700, John Baldwin wrote: > > > > > On Tuesday, May 03, 2016 03:37:27 PM Michael Butler wrote: > > > > > > On 05/03/16 11:21, Larry Rosenman wrote: > > > > > > > On 2016-05-03 05:49, Joel Dahl wrote: > > > > > > >> On Sat, Apr 30, 2016 at 10:36:53PM -0500, Larry Rosenman wrote: > > > > > > >>> On a current -CURRENT if my Floppy disk controller and device > > > > > > >>> are > > > > > > >>> ENABLED, we do NOT pass mount root, and the floppy disk > > > > > > >>> light is ON. > > > > > > >> > > > > > > >> Just a "me too". But this is with VMware Fusion. If I disable the > > > > > > >> floppy from > > > > > > >> BIOS, the virtual machine boots. If I leave it enabled, it hangs. > > > > > > > Thanks for posting that I'm not the only one, and it's not flakey > > > > > > > hardware. > > > > > > > > > > > > > > > > > > > I have an, otherwise extremely reliable but ancient, Intel TR440BXA > > > > > > motherboard doing this :-( > > > > > > > > > > > > What drove me mad for a while is that I have an identical machine, > > > > > > with > > > > > > exception of 10k RPM SCSI disks, which doesn't hang. I simply > > > > > > optioned > > > > > > out "device fdc" and it's behaved ever since, > > > > > > > > > > Larry wasn't able to get into DDB when his box hung, are either of > > > > > you able > > > > > to get into DDB when it hangs? > > > > > > > > Um, ctrl-alt-backspace doesn't work for me, but ctrl-alt-esc does. > > > > > > > > I uploaded a few screenshots here: https://www.vnode.se/files/freebsd/ > > > > > > Thanks. It seems like the fdc worker thread isn't there and GEOM is stuck > > > waiting for that thread to do something (well waiting for the commands > > > that thread handles to be executed). > > > > > > First step would be just add a 'panic' to fdc_start_worker() in fdc.c at > > > the end to make sure it is getting called. (And when it drops you into > > > ddb > > > you should be able to see the fdc0 kproc in 'ps' output). > > > > I did this, but no change. It hangs at the same place, so I guess the added > > panic() is never called. > > The logic in fdc_acpi.c is a bit odd to follow, it sometimes goes to 'out' in > the success case which is unusual. As a result, if your fdc device doesn't > have an _FDE entry in the ACPI namespace we wouldn't start the worker thread. > Try this change: I applied the patch and rebuilt my kernel. It boots fine now with the floppy enabled. Thanks. -- Joel ___ 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: boot with floppy enabled doesn't.....
On Tue, May 03, 2016 at 03:52:43PM -0700, John Baldwin wrote: > On Tuesday, May 03, 2016 10:20:21 PM Joel Dahl wrote: > > On Tue, May 03, 2016 at 12:58:15PM -0700, John Baldwin wrote: > > > On Tuesday, May 03, 2016 03:37:27 PM Michael Butler wrote: > > > > On 05/03/16 11:21, Larry Rosenman wrote: > > > > > On 2016-05-03 05:49, Joel Dahl wrote: > > > > >> On Sat, Apr 30, 2016 at 10:36:53PM -0500, Larry Rosenman wrote: > > > > >>> On a current -CURRENT if my Floppy disk controller and device are > > > > >>> ENABLED, we do NOT pass mount root, and the floppy disk > > > > >>> light is ON. > > > > >> > > > > >> Just a "me too". But this is with VMware Fusion. If I disable the > > > > >> floppy from > > > > >> BIOS, the virtual machine boots. If I leave it enabled, it hangs. > > > > > Thanks for posting that I'm not the only one, and it's not flakey > > > > > hardware. > > > > > > > > > > > > > I have an, otherwise extremely reliable but ancient, Intel TR440BXA > > > > motherboard doing this :-( > > > > > > > > What drove me mad for a while is that I have an identical machine, with > > > > exception of 10k RPM SCSI disks, which doesn't hang. I simply optioned > > > > out "device fdc" and it's behaved ever since, > > > > > > Larry wasn't able to get into DDB when his box hung, are either of you > > > able > > > to get into DDB when it hangs? > > > > Um, ctrl-alt-backspace doesn't work for me, but ctrl-alt-esc does. > > > > I uploaded a few screenshots here: https://www.vnode.se/files/freebsd/ > > Thanks. It seems like the fdc worker thread isn't there and GEOM is stuck > waiting for that thread to do something (well waiting for the commands > that thread handles to be executed). > > First step would be just add a 'panic' to fdc_start_worker() in fdc.c at > the end to make sure it is getting called. (And when it drops you into ddb > you should be able to see the fdc0 kproc in 'ps' output). I did this, but no change. It hangs at the same place, so I guess the added panic() is never called. -- Joel ___ 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: boot with floppy enabled doesn't.....
On Tue, May 03, 2016 at 12:58:15PM -0700, John Baldwin wrote: > On Tuesday, May 03, 2016 03:37:27 PM Michael Butler wrote: > > On 05/03/16 11:21, Larry Rosenman wrote: > > > On 2016-05-03 05:49, Joel Dahl wrote: > > >> On Sat, Apr 30, 2016 at 10:36:53PM -0500, Larry Rosenman wrote: > > >>> On a current -CURRENT if my Floppy disk controller and device are > > >>> ENABLED, we do NOT pass mount root, and the floppy disk > > >>> light is ON. > > >> > > >> Just a "me too". But this is with VMware Fusion. If I disable the > > >> floppy from > > >> BIOS, the virtual machine boots. If I leave it enabled, it hangs. > > > Thanks for posting that I'm not the only one, and it's not flakey > > > hardware. > > > > > > > I have an, otherwise extremely reliable but ancient, Intel TR440BXA > > motherboard doing this :-( > > > > What drove me mad for a while is that I have an identical machine, with > > exception of 10k RPM SCSI disks, which doesn't hang. I simply optioned > > out "device fdc" and it's behaved ever since, > > Larry wasn't able to get into DDB when his box hung, are either of you able > to get into DDB when it hangs? Um, ctrl-alt-backspace doesn't work for me, but ctrl-alt-esc does. I uploaded a few screenshots here: https://www.vnode.se/files/freebsd/ -- Joel ___ 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: boot with floppy enabled doesn't.....
On Tue, May 03, 2016 at 10:21:25AM -0500, Larry Rosenman wrote: > On 2016-05-03 05:49, Joel Dahl wrote: > > On Sat, Apr 30, 2016 at 10:36:53PM -0500, Larry Rosenman wrote: > >> On a current -CURRENT if my Floppy disk controller and device are > >> ENABLED, we do NOT pass mount root, and the floppy disk > >> light is ON. > > > > Just a "me too". But this is with VMware Fusion. If I disable the > > floppy from > > BIOS, the virtual machine boots. If I leave it enabled, it hangs. > Thanks for posting that I'm not the only one, and it's not flakey > hardware. I forgot to mention that -CURRENT from three weeks ago works. I rebuilt -CURRENT today and now it hangs. -- Joel ___ 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: boot with floppy enabled doesn't.....
On Sat, Apr 30, 2016 at 10:36:53PM -0500, Larry Rosenman wrote: > On a current -CURRENT if my Floppy disk controller and device are > ENABLED, we do NOT pass mount root, and the floppy disk > light is ON. Just a "me too". But this is with VMware Fusion. If I disable the floppy from BIOS, the virtual machine boots. If I leave it enabled, it hangs. -- Joel ___ 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: Kernel panic with fresh current, probably nfs related
On Tue, Aug 25, 2015 at 12:55:02PM -0700, Sean Bruno wrote: > > > On 08/25/15 12:10, Joel Dahl wrote: > >> > Seems to work. However, I cannot reproduce the user panic in the first > >> > place. What's the scenario that seems to work here? NFS seems happy > >> > with/without the patch so I'm not confident in anything we are doing her > >> > e. > > I see several patches here. Which one should I be using? > > This: > > Index: sys/dev/e1000/if_em.c > === > --- sys/dev/e1000/if_em.c (revision 287087) > +++ sys/dev/e1000/if_em.c (working copy) > @@ -3044,7 +3044,7 @@ em_setup_interface(device_t dev, struct adapter *a > if_setioctlfn(ifp, em_ioctl); > if_setgetcounterfn(ifp, em_get_counter); > /* TSO parameters */ > - ifp->if_hw_tsomax = EM_TSO_SIZE; > + ifp->if_hw_tsomax = IP_MAXPACKET; > ifp->if_hw_tsomaxsegcount = EM_MAX_SCATTER; > ifp->if_hw_tsomaxsegsize = EM_TSO_SEG_SIZE; Using this patch, my nfs server has survived several installkernel/installworld cycles. -- Joel ___ 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: Kernel panic with fresh current, probably nfs related
On Mon, Aug 24, 2015 at 11:18:00AM -0700, Sean Bruno wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > > > On 08/23/15 18:36, Yonghyeon PYUN wrote: > > Index: sys/dev/e1000/if_em.c > > === > > > > > - --- sys/dev/e1000/if_em.c (revision 287087) > > +++ sys/dev/e1000/if_em.c (working copy) @@ -3044,7 +3044,7 @@ > > em_setup_interface(device_t dev, struct adapter *a > > if_setioctlfn(ifp, em_ioctl); if_setgetcounterfn(ifp, > > em_get_counter); /* TSO parameters */ - ifp->if_hw_tsomax = > > EM_TSO_SIZE; + ifp->if_hw_tsomax = IP_MAXPACKET; > > ifp->if_hw_tsomaxsegcount = EM_MAX_SCATTER; > > ifp->if_hw_tsomaxsegsize = EM_TSO_SEG_SIZE; > > > Seems to work. However, I cannot reproduce the user panic in the first > place. What's the scenario that seems to work here? NFS seems happy > with/without the patch so I'm not confident in anything we are doing her > e. I see several patches here. Which one should I be using? -- Joel ___ 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: Kernel panic with fresh current, probably nfs related
On Sat, Aug 22, 2015 at 08:57:40AM -0400, Rick Macklem wrote: > Joel Dahl wrote: > > Hi, > > > > I hit a kernel panic running a fresh -CURRENT today. This machine is my home > > NFS > > server and it exports src and obj to a bunch of other machines. During an > > installkernel on one of the other machines (using the src and obj exports > > from > > the NFS server) the NFS server kernel paniced. > > > > I took a quick photo of the stack backtrace, since I didn't have time to > > investigate further (but I haven't rebooted the machine yet, it's still > > sitting at the db> prompt: > > > > http://mirror.vnode.se/upload/panic001-20150822.JPG > > > > Any ideas? > > > I'm going to guess that you're using an "em" net driver, since that is the > only one that sets if_hw_tsomax > IP_MAXPACKET (65535) from what I can see. Correct, this machine is using em. I'll wait for sbruno to reply before rebooting the machine, in case anyone wants me to try anything in the debugger. -- Joel ___ 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"
Kernel panic with fresh current, probably nfs related
Hi, I hit a kernel panic running a fresh -CURRENT today. This machine is my home NFS server and it exports src and obj to a bunch of other machines. During an installkernel on one of the other machines (using the src and obj exports from the NFS server) the NFS server kernel paniced. I took a quick photo of the stack backtrace, since I didn't have time to investigate further (but I haven't rebooted the machine yet, it's still sitting at the db> prompt: http://mirror.vnode.se/upload/panic001-20150822.JPG Any ideas? -- Joel ___ 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: ping not working after upgrading to -CURRENT
On Thu, Apr 30, 2015 at 05:28:09PM +0200, Edvard Fagerholm wrote: > Hi, > > I just started looking into FreeBSD after a hiatus of some years. I > did an upgrade to -CURRENT this morning following the instructions > here: FWIW, I'm seeing the same thing with a fresh CURRENT (r282296). -- Joel ___ 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: ntpd errors after upgrade on current amd64
FWIW, I’m seeing the same thing. — Joel > 1 apr 2015 kl. 17:32 skrev Manfred Antar : > > After build install world on current ntpd doesn't work. > Here is error: > > FreeBSD/amd64 (pozo.com) (ttyu0) > > login: Apr 1 08:29:19 pozo ntpd[49825]: line 22 column 1 syntax error > Apr 1 08:29:19 pozo ntpd[49825]: setsockopt IPV6_MULTICAST_IF 0 for > fe80::1%2 fails: Can't assign requested address > > I'm using the stock ntp.conf from /usr/src/etc. > It worked fine before the upgrade > Thanks ___ 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] man(1) now uses mandoc
Thank you. — Joel > 23 nov 2014 kl. 01:18 skrev Baptiste Daroussin : > > Hi, > > The default renderer on HEAD has been switched to mandoc(1) by default > The man(1) command has been instrumented to first test the manpage and > fallback > on groff if the man page cannot be rendered with mandoc(1). > > If base is built without groff then man(1) recommands to install groff from > packages. > > makewhatis(1), apropos(1) have not yet been switched to mandoc(1) equivalent. > > Best regards, > Bapt ___ 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: Boot loader too large with Aug-11 FreeBSD/i386 11-CURRENT snapshot
23 aug 2014 kl. 20:45 skrev Adrian Chadd : > I thought there was a recent discussion about this. > > Would you mind filing a bug so this gets looked at? Done. See Bug 192962. Joel ___ 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: Boot loader too large with Aug-11 FreeBSD/i386 11-CURRENT snapshot
23 aug 2014 kl. 09:17 skrev Matthew D. Fuller : > On Sat, Aug 23, 2014 at 09:02:10AM +0200 I heard the voice of > Joel Dahl, and lo! it spake thus: >> >> Today I installed 11-CURRENT from the 20140811 FreeBSD/i386 snapshot >> on my IBM T43 laptop but encountered some problems. The memstick >> installation went fine and I pretty much used default values >> everywhere, but upon reboot I got ”Boot loader too large”. Nothing >> more. Any ideas? > > The freebsd-boot partition is bigger than five hundred twenty-mumble > k. It'll be OK if you squeeze it down to 512. Somthing like 'gpart > resize -i 1 -s 512k ada23' (untested, sub your disk). Yes, gpart fixed it. Thanks. But it’s annoying. Why is manual tinkering required here? Why isn’t it set to 512k by default? I checked the handbook (2.6.3), and it says ”the freebsd-boot partition should be no larger than 512K due to current boot code limitations” ... Joel ___ 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"
Boot loader too large with Aug-11 FreeBSD/i386 11-CURRENT snapshot
Hi, Today I installed 11-CURRENT from the 20140811 FreeBSD/i386 snapshot on my IBM T43 laptop but encountered some problems. The memstick installation went fine and I pretty much used default values everywhere, but upon reboot I got ”Boot loader too large”. Nothing more. Any ideas? Joel ___ 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: libelf.so.1 missing after -CURRENT update
1 feb 2014 kl. 21:52 skrev Thomas Hoffmann : > Did my weekly update of -CURRENT today to r261350 from r261236. After the > upgrade when I tried to run 'pkg' I got the error: > > libelf.so.1 required by libpkg.so.1 > > So, I reinstalled 'pkg', which fixed the problem. Then I ran pkg_libchk to > see if any other libs were missing and got: > > glib -2.36.3_1: /usr/local/bin/gresource misses libelf.so.1 > > So i re-installed glib and re-ran pkg_libchk against it. No more missing > libelf.so.1. > > Anyway, I'm wondering if I inadvertently deleted libelf.so.1 during the > 'make delete-old' or 'make delete-old-libs' steps of the rebuild. > Unfortunately, these are the only two steps of the build process > (mergemaster excepted) that I do not 'script' the output, so I cannot go > back to see if that is the case. Obviously I need to begin "script'ing > these two steps on future builds. > > Anyone else seen this or that can confirm an inadvertent delete of > libelf.so.1 on my part? I’m seeing the same thing. — Joel ___ 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: installworld broken - osreldate.h: permission denied
On Mon, Sep 30, 2013 at 07:02:43PM +0200, Jilles Tjoelker wrote: > On Sun, Sep 29, 2013 at 10:13:29AM +0200, Joel Dahl wrote: > > On Sat, Sep 28, 2013 at 11:19:51AM -0600, Ian Lepore wrote: > > > On Sat, 2013-09-28 at 15:09 +0200, Joel Dahl wrote: > > > > Fresh HEAD. installworld from read-only /usr/obj and /usr/src: > > > > > /usr/src/include/iconv.h osreldate.h /usr/include > > > > install: osreldate.h: Permission denied > > > > *** Error code 71 > > > > > Stop. > > > > make[4]: stopped in /usr/src/include > > > > *** Error code 1 > > > > > Everything was working fine 2 weeks ago, so it's a recent breakage. > > > > Okay, I just accidentally created conditions for this error on my > > > system... I checked in a change to newvers.sh while a buildworld was > > > running, which led to a situation where newvers.sh was newer than > > > osreldate.h at the end of the buildworld. Then an installworld tried to > > > regenerate osreldate.h due to its dependency on newvers.sh, which would > > > fail if the obj was readonly at that point. > > > > I think we could see if something similar applies for you if you use > > > this command: > > > > make -dm installworld SUBDIR_OVERRIDE=include > > > I tried this with a fresh HEAD but the error message is still the same. > > > /usr/src and /usr/obj are NFS mounted, FYI. > > I had the same problem as Joel. It has nothing to do with timestamps, > but with the default -maproot -2:-2. The include/mk-osreldate.sh script > creates osreldate.h from mktemp(1), so with mode 600. The squashed root > (nobody) is then not allowed to read it. > > The below patch should fix it. > > Index: include/mk-osreldate.sh > === > --- include/mk-osreldate.sh (revision 255946) > +++ include/mk-osreldate.sh (working copy) > @@ -48,4 +48,5 @@ > #define __FreeBSD_version $RELDATE > #endif > EOF > +chmod 644 $tmpfile > mv $tmpfile osreldate.h This patch fixes the problem for me. Thanks. -- Joel ___ 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: installworld broken - osreldate.h: permission denied
On Mon, Sep 30, 2013 at 12:03:47PM +0400, Boris Samorodov wrote: > 30.09.2013 09:12, Joel Dahl пишет: > > On Sun, Sep 29, 2013 at 07:53:44PM -0700, John-Mark Gurney wrote: > >> Joel Dahl wrote this message on Sun, Sep 29, 2013 at 10:13 +0200: > >>> On Sat, Sep 28, 2013 at 11:19:51AM -0600, Ian Lepore wrote: > >>>> On Sat, 2013-09-28 at 15:09 +0200, Joel Dahl wrote: > >>>>> Hi, > >>>>> > >>>>> Fresh HEAD. installworld from read-only /usr/obj and /usr/src: > >>>>> > >>>>> /usr/src/include/iconv.h osreldate.h /usr/include > >>>>> install: osreldate.h: Permission denied > >>>>> *** Error code 71 > >>>>> > >>>>> Stop. > >>>>> make[4]: stopped in /usr/src/include > >>>>> *** Error code 1 > >>>>> > >>>>> Everything was working fine 2 weeks ago, so it's a recent breakage. > >>>>> > >>>> > >>>> Okay, I just accidentally created conditions for this error on my > >>>> system... I checked in a change to newvers.sh while a buildworld was > >>>> running, which led to a situation where newvers.sh was newer than > >>>> osreldate.h at the end of the buildworld. Then an installworld tried to > >>>> regenerate osreldate.h due to its dependency on newvers.sh, which would > >>>> fail if the obj was readonly at that point. > >>>> > >>>> I think we could see if something similar applies for you if you use > >>>> this command: > >>>> > >>>> make -dm installworld SUBDIR_OVERRIDE=include > >>> > >>> I tried this with a fresh HEAD but the error message is still the same. > >>> > >>> /usr/src and /usr/obj are NFS mounted, FYI. > >> > >> Are you building on one machine and running install on another? Are > >> the dates the same between the two machines? > > > > Yes, both machines are running ntp. I've double-checked the dates and they > > are > > in sync. > > Do those machines have accurate timezones set? Yes, they do. -- Joel ___ 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: installworld broken - osreldate.h: permission denied
On Sun, Sep 29, 2013 at 07:53:44PM -0700, John-Mark Gurney wrote: > Joel Dahl wrote this message on Sun, Sep 29, 2013 at 10:13 +0200: > > On Sat, Sep 28, 2013 at 11:19:51AM -0600, Ian Lepore wrote: > > > On Sat, 2013-09-28 at 15:09 +0200, Joel Dahl wrote: > > > > Hi, > > > > > > > > Fresh HEAD. installworld from read-only /usr/obj and /usr/src: > > > > > > > > /usr/src/include/iconv.h osreldate.h /usr/include > > > > install: osreldate.h: Permission denied > > > > *** Error code 71 > > > > > > > > Stop. > > > > make[4]: stopped in /usr/src/include > > > > *** Error code 1 > > > > > > > > Everything was working fine 2 weeks ago, so it's a recent breakage. > > > > > > > > > > Okay, I just accidentally created conditions for this error on my > > > system... I checked in a change to newvers.sh while a buildworld was > > > running, which led to a situation where newvers.sh was newer than > > > osreldate.h at the end of the buildworld. Then an installworld tried to > > > regenerate osreldate.h due to its dependency on newvers.sh, which would > > > fail if the obj was readonly at that point. > > > > > > I think we could see if something similar applies for you if you use > > > this command: > > > > > > make -dm installworld SUBDIR_OVERRIDE=include > > > > I tried this with a fresh HEAD but the error message is still the same. > > > > /usr/src and /usr/obj are NFS mounted, FYI. > > Are you building on one machine and running install on another? Are > the dates the same between the two machines? Yes, both machines are running ntp. I've double-checked the dates and they are in sync. -- Joel ___ 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: installworld broken - osreldate.h: permission denied
On Sat, Sep 28, 2013 at 11:19:51AM -0600, Ian Lepore wrote: > On Sat, 2013-09-28 at 15:09 +0200, Joel Dahl wrote: > > Hi, > > > > Fresh HEAD. installworld from read-only /usr/obj and /usr/src: > > > > /usr/src/include/iconv.h osreldate.h /usr/include > > install: osreldate.h: Permission denied > > *** Error code 71 > > > > Stop. > > make[4]: stopped in /usr/src/include > > *** Error code 1 > > > > Everything was working fine 2 weeks ago, so it's a recent breakage. > > > > Okay, I just accidentally created conditions for this error on my > system... I checked in a change to newvers.sh while a buildworld was > running, which led to a situation where newvers.sh was newer than > osreldate.h at the end of the buildworld. Then an installworld tried to > regenerate osreldate.h due to its dependency on newvers.sh, which would > fail if the obj was readonly at that point. > > I think we could see if something similar applies for you if you use > this command: > > make -dm installworld SUBDIR_OVERRIDE=include I tried this with a fresh HEAD but the error message is still the same. /usr/src and /usr/obj are NFS mounted, FYI. -- Joel ___ 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"
installworld broken - osreldate.h: permission denied
Hi, Fresh HEAD. installworld from read-only /usr/obj and /usr/src: /usr/src/include/iconv.h osreldate.h /usr/include install: osreldate.h: Permission denied *** Error code 71 Stop. make[4]: stopped in /usr/src/include *** Error code 1 Everything was working fine 2 weeks ago, so it's a recent breakage. -- Joel ___ 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"
sysctl: unknown oid 'kern.random.sys.harvest.interrupt
Hi, I noticed the following during boot on a machine running HEAD from today: Entropy harvesting:sysctl: unknown oid 'kern.random.sys.harvest.interrupt': No such file or directory interruptssysctl: unknown oid 'kern.random.sys.harvest.ethernet': No such file or directory ethernetsysctl: unknown oid 'kern.random.sys.harvest.point_to_point': No such file or directory point_to_point kickstart. Known problem? -- Joel ___ 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: mountroot> while booting r255342 memstick
On Thu, Sep 12, 2013 at 12:32:12AM +, Uzumaki Naruto wrote: > Hi, > I downloaded FreeBSD-10.0-CURRENT-amd64-20130907-r255342-memstick.img and dd > into KINGSTON DT 101 G2 1.00 USB pendrive Looks similar to what I reported back in February: http://lists.freebsd.org/pipermail/freebsd-current/2013-February/039542.html mav@ committed a fix for this here: http://lists.freebsd.org/pipermail/svn-src-head/2013-February/045143.html Perhaps a quirk is needed for your USB pendrive as well. -- Joel ___ 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: [installworld via r/o NFS] cannot create mapper.dir: Permission denied
On Tue, Aug 27, 2013 at 10:32:51PM +0400, Boris Samorodov wrote: > Hi All, > > > While installing fresh CURRENT (make -C installworld) > via NFS (exported -ro)...: > - > 192.168.119.49:/usr/src on /usr/src (nfs) > 192.168.119.49:/usr/obj on /usr/obj (nfs) > - > > ... I get the following error: > - > ===> share/examples/pf (install) > install -o root -g wheel -m 444 faq-example1 faq-example2 faq-example3 > ackpri queue1 queue2 queue3 queue4 pf.conf spamd /usr/share/examples/pf > ===> share/i18n (install) > ===> share/i18n/csmapper (install) > > mapper.dir > cannot create mapper.dir: Permission denied > *** Error code 2 > - I've reported this several times. r254273 broke it. -- Joel ___ 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"
panic on boot with fresh current
Hi, I just rebuilt a fresh current on my laptop. It panics on boot with: panic: witness_init: pending locks list is too small, increase WITNESS_PENDLIST I'm in a hurry right now so I can't gather much more info at the moment, but I thought I'd mention it. -- Joel ___ 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: [CFT] VMware vmxnet3 ethernet driver
6 aug 2013 kl. 08:05 skrev Bryan Venteicher : > > > - Original Message - >> Perhaps not, but they do support FreeBSD. I've started several support cases >> with FreeBSD-specific problems and they've fixed all so far. >> > > Yes, it is not a blackhole of support. At $JOB, we got caught by the FreeBSD > specific issue of the busted timer that was fixed. But they've less helpful > in other regards, and have more or less said FreeBSD isn't high in their > priority because it isn't Linux. > >> Are you aiming at completely replacing VMware tools, or just the device >> drivers? >> > > I'd like as much as possible to work out of the box. vmxnet3 is as far as > my current interests go. OpenBSD has a vmt device that apparently does (at > least the important bits of) what vmtoolsd does; I'll look at that closer > at some point. Cool. I didn't know about vmt. I read the CVS log in the OpenBSD tree and it actually seems to do most of what I need. Having all this working out of the box (without VMware Tools installed) would be most welcome. …but I guess VMware would consider this an unsupported configuration or something like that, which sucks if/when I need to contact their support. -- Joel ___ 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: [CFT] VMware vmxnet3 ethernet driver
On Mon, Aug 05, 2013 at 05:52:01PM -0500, Bryan Venteicher wrote: > > > - Original Message - > > I have ~100 FreeBSD 8/9 VMs in my vSphere 5.1 environment, all using the > > VMware tools package from VMware. Everything has been running great for > > years. > > (we skipped vSphere 5.0). Why should I use this vmxnet driver instead of the > > VMware tools driver or the emulated e1000? > > > > They are out of tree and subject to rotting. I had to use the patches > at [1] to even get them to compile on 9.1 and -current. I don't think > VMware puts much engineering resources behind it; Perhaps not, but they do support FreeBSD. I've started several support cases with FreeBSD-specific problems and they've fixed all so far. Are you aiming at completely replacing VMware tools, or just the device drivers? -- Joel ___ 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: [CFT] VMware vmxnet3 ethernet driver
On Sun, Aug 04, 2013 at 07:12:17PM -0500, Bryan Venteicher wrote: > Hi, > > I've ported the OpenBSD vmxnet3 ethernet driver to FreeBSD. I did a > lot of cleanup, bug fixes, new features, etc (+2000 new lines) along > the way so there is not much of a resemblance left. > > The driver is in good enough shape I'd like additional testers. A patch > against -CURRENT is at [1]. Alternatively, the driver and a Makefile is > at [2]; this should compile at least as far back as 9.1. I can look at > 8-STABLE if there is interest. > > Obviously, besides reports of 'it works', I'm interested performance vs > the emulated e1000, and (for those using it) the VMware tools vmxnet3 > driver. Hopefully it is no worse :) I have ~100 FreeBSD 8/9 VMs in my vSphere 5.1 environment, all using the VMware tools package from VMware. Everything has been running great for years. (we skipped vSphere 5.0). Why should I use this vmxnet driver instead of the VMware tools driver or the emulated e1000? -- Joel ___ 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: Lenovo x220 - hangs on shutdown
On Mon, Jul 22, 2013 at 02:32:06PM -0700, Neel Natu wrote: > Hi Joel, > > On Mon, Jul 22, 2013 at 1:36 PM, Konstantin Belousov > wrote: > > On Mon, Jul 22, 2013 at 10:52:55AM -0700, Adrian Chadd wrote: > >> Hi kib, > >> > >> Is there a wiki page or some other kind of documentation descibing how > >> AMT works? > > It is Intel documentation for vPro. Setting up AMT on the motherboard > > is specific to the motherboard BIOS, you should look at the hardware > > vendor documentation. > > > > Random googling for you revealed e.g. http://wiki.debian.org/AMT > > which is actually good introduction (i.e. there is not much to say > > about AMT usage in fact). > > > >> > >> I'd like to set this up at home on some newer machines (read: buy > >> machines that have this) but I don't know what/where to start. > > For the controlling side of things, I use amttools, available in > > ports collection as comms/amtterm. The manual pages are brief > > but useful. > > > > Amttools provide amttool(1) for power control, and amtterm/gamt for console. > > Could you apply the following patch to amd64/amd64/pmap.c and see if it helps? > http://people.freebsd.org/~neel/patches/pmap_remove_pages.patch Yes, it helps. I can shutdown the machine from X again. -- Joel ___ 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: Lenovo x220 - hangs on shutdown
On Sun, Jul 21, 2013 at 07:12:33PM +0300, Konstantin Belousov wrote: > On Sun, Jul 21, 2013 at 09:20:45AM +0200, Joel Dahl wrote: > > On Tue, Jul 16, 2013 at 10:48:35PM +0200, Joel Dahl wrote: > > > Hi, > > > > > > Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now > > > it hangs when I do a shutdown from an xterm. The screen just goes black > > > and the fan never spins down. It doesn't respond to ping. > > > > > > It didn't do this while I was running a current from mid-June. > > > > > > Any specific revision I should try to back out before I start a time > > > consuming binary search? > > > > I found it. r252652 works. r252653 does not. > > What is the chipset on your machine ? Intel Core i7-2640M / Mobile Intel QM67 Express Chipset > Do you have AMT ? If yes, please configure serial over LAN using AMT > and use it for the console, to obtain the usual debugging information > from the kernel. At least, 'ps' output from ddb is needed. I found "Intel (R) AMT Control" in the BIOS. It's enabled. I haven't figured out how it works yet though. -- Joel ___ 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: Lenovo x220 - hangs on shutdown
On Tue, Jul 16, 2013 at 10:48:35PM +0200, Joel Dahl wrote: > Hi, > > Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it > hangs when I do a shutdown from an xterm. The screen just goes black and the > fan never spins down. It doesn't respond to ping. > > It didn't do this while I was running a current from mid-June. > > Any specific revision I should try to back out before I start a time > consuming binary search? I found it. r252652 works. r252653 does not. -- Joel ___ 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: Lenovo x220 - hangs on shutdown
On Wed, Jul 17, 2013 at 07:39:30PM +0200, Michael Schmiedgen wrote: > On 07/16/13 22:48, Joel Dahl wrote: > > Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it > > hangs when I do a shutdown from an xterm. The screen just goes black and > > the fan never spins down. It doesn't respond to ping. > > X220, 10.0-CURRENT #0 r253368 amd, powerd running. In xterm I type > 'shutdown -p now' and everything works fine. But the kernel is > compiled without INVARIANTS and without WITNESS and malloc runs > in production mode. I tried enabling powerd - no change. The machine won't power off. -- Joel ___ 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"
Lenovo x220 - hangs on shutdown
Hi, Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it hangs when I do a shutdown from an xterm. The screen just goes black and the fan never spins down. It doesn't respond to ping. It didn't do this while I was running a current from mid-June. Any specific revision I should try to back out before I start a time consuming binary search? // Joel ___ 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: Panic during boot with fresh CURRENT (r248090)
On Sat, Mar 09, 2013 at 10:39:20AM +0100, Joel Dahl wrote: > Hi, > > Just updated to the latest CURRENT. Got this during boot: > (sorry for the large image) > > http://mirror.vnode.se/upload/r248090_panic.jpg This is fixed with r248093. -- Joel ___ 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"
Panic during boot with fresh CURRENT (r248090)
Hi, Just updated to the latest CURRENT. Got this during boot: (sorry for the large image) http://mirror.vnode.se/upload/r248090_panic.jpg -- Joel ___ 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: HEAD memsticks broken? [USB/CAM Problems?]
On 14-02-2013 20:37, Joel Dahl wrote: > On 12-02-2013 8:51, Hans Petter Selasky wrote: > > On Monday 11 February 2013 23:21:05 Joel Dahl wrote: > > > On 10-02-2013 0:09, Joel Dahl wrote: > > > > On 09-02-2013 20:28, Alexander Motin wrote: > > > > > How long ago that HEAD was built? Could you get full dmesg? I don't > > > > > think that "PREVENT ALLOW MEDIUM REMOVAL" should cause device drop. > > > > > "No > > > > > sense data present" also doesn't look right. > > > > > > > > As I mentioned earlier, I've tried several HEAD snapshots. > > > > > > Just a quick update on this: I've built quite a few releases now and > > > managed to track down the problem to somewhere between r235789 and > > > r237855. It'll probably take me another day or two before I know which > > > commit actually broke it. > > > > Hi, > > > > I don't see any relevant USB+UMASS patches for your issue in this interval, > > but many patches in the SCSI/CAM area. > > I finally found it. A r237477 memstick boots fine. A r237478 memstick does > not. > > 237478 is the following commit by mav@: > > > r237478 | mav | 2012-06-23 14:32:53 +0200 (Sat, 23 Jun 2012) | 3 lines > > Add scsi_extract_sense_ccb() -- wrapper around scsi_extract_sense_len(). > It allows to remove number of duplicate checks from several places. > > So, mav@ haven't replied yet so I did some more investigation. I collected all the USB sticks I had in the office (5 in total, all Kingston but different size and models) and tried a memstick installation with each stick. Turns out r237478 only breaks memstick installation in combination with certain USB sticks: # Works: da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 7664MB (15695872 512 byte sectors: 255H 63S/T 977C) da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1906MB (3903488 512 byte sectors: 255H 63S/T 242C) # Does not work: da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 15295MB (31324160 512 byte sectors: 255H 63S/T 1949C) da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 3690MB (7557704 512 byte sectors: 255H 63S/T 470C) da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 1905MB (3903264 512 byte sectors: 255H 63S/T 242C) It seems that only USB sticks labeled as "Kingston DataTraveler G3" are affected by r237478 (in my limited testing, at least). This particular model is what you get if you buy the cheapest Kingston model on the market right now. -- Joel ___ 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: HEAD memsticks broken? [USB/CAM Problems?]
On 12-02-2013 8:51, Hans Petter Selasky wrote: > On Monday 11 February 2013 23:21:05 Joel Dahl wrote: > > On 10-02-2013 0:09, Joel Dahl wrote: > > > On 09-02-2013 20:28, Alexander Motin wrote: > > > > How long ago that HEAD was built? Could you get full dmesg? I don't > > > > think that "PREVENT ALLOW MEDIUM REMOVAL" should cause device drop. "No > > > > sense data present" also doesn't look right. > > > > > > As I mentioned earlier, I've tried several HEAD snapshots. > > > > Just a quick update on this: I've built quite a few releases now and > > managed to track down the problem to somewhere between r235789 and > > r237855. It'll probably take me another day or two before I know which > > commit actually broke it. > > Hi, > > I don't see any relevant USB+UMASS patches for your issue in this interval, > but many patches in the SCSI/CAM area. I finally found it. A r237477 memstick boots fine. A r237478 memstick does not. 237478 is the following commit by mav@: r237478 | mav | 2012-06-23 14:32:53 +0200 (Sat, 23 Jun 2012) | 3 lines Add scsi_extract_sense_ccb() -- wrapper around scsi_extract_sense_len(). It allows to remove number of duplicate checks from several places. -- Joel ___ 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: HEAD memsticks broken? [USB/CAM Problems?]
On 10-02-2013 0:09, Joel Dahl wrote: > On 09-02-2013 20:28, Alexander Motin wrote: > > How long ago that HEAD was built? Could you get full dmesg? I don't > > think that "PREVENT ALLOW MEDIUM REMOVAL" should cause device drop. "No > > sense data present" also doesn't look right. > > As I mentioned earlier, I've tried several HEAD snapshots. Just a quick update on this: I've built quite a few releases now and managed to track down the problem to somewhere between r235789 and r237855. It'll probably take me another day or two before I know which commit actually broke it. -- Joel ___ 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: HEAD memsticks broken? [USB/CAM Problems?]
On 09-02-2013 20:28, Alexander Motin wrote: > How long ago that HEAD was built? Could you get full dmesg? I don't > think that "PREVENT ALLOW MEDIUM REMOVAL" should cause device drop. "No > sense data present" also doesn't look right. As I mentioned earlier, I've tried several HEAD snapshots. This is booting a r246472 memstick. I currently have no way to get a full dmesg, but I have hand-typed the last parts below: usbus0: 480Mbps High Speed USB v2.0 usbus1: 5.0Gbps Super Speed USB v3.0 usbus2: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: <0x1033> at usbus1 uhub1: <0x1033 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ses0 at ahciem0 bus 0 scbus3 target 0 lun 0 ses0: SEMB S-E-S 2.00 device ses0: SEMB SES Device ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 152627MB (312581808 512 byte sectors: 1H 63S/T 16383C) ada0: Previously was known as ad4 SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! Timecounter "TSC-low" frequency 1395499430 Hz quality 1000 WARNING: WITNESS option enabled, expect reduced performance. uhub1: 4 ports with 4 removable, self powered Root mount waiting for: usbus2 usbus0 uhub0: 3 ports with 3 removable, self powered uhub2: 3 ports with 3 removable, self powered ugen0.2: at usbus0 uhub3: on usbus0 ugen2.2: at usbus2 uhub4: on usbus2 Root mount wating for: usbus2 usbus0 ugen0.4: at usbus0 ugen0.5: at usbus0 ugen2.3: at usbus2 umass0: on usbus2 umass0: SCSI over BUlk-Only; quirks = 0x0100 umass0:5:0:-1: Attached to scbus5 da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 3690MB (7557704 512 byte sectors: 255H 63S/T 470C) (da0:umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 00 00 00 01 00 (da0:umass-sim0:0:0:0): CAM status: Auto-Sense Retrieval Failed (da0:umass-sim0:0:0:0): Error 5, Unretryable error (da0:umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 00 00 00 01 00 (da0:umass-sim0:0:0:0): CAM status: Auto-Sense Retrieval Failed (da0:umass-sim0:0:0:0): Error 5, Unretryable error (da0:umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 00 00 00 01 00 (da0:umass-sim0:0:0:0): CAM status: Auto-Sense Retrieval Failed (da0:umass-sim0:0:0:0): Error 5, Unretryable error (da0:umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 00 00 00 01 00 (da0:umass-sim0:0:0:0): CAM status: Auto-Sense Retrieval Failed (da0:umass-sim0:0:0:0): Error 5, Unretryable error (da0:umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 00 00 00 01 00 (da0:umass-sim0:0:0:0): CAM status: Auto-Sense Retrieval Failed (da0:umass-sim0:0:0:0): Error 5, Unretryable error (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 (da0:umass-sim0:0:0:0): CAM status: Auto-Sense Retrieval Failed (da0:umass-sim0:0:0:0): Error 5, Unretryable error (da0:umass-sim0:0:0:0): got CAM status 0x50 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 4 refs (da0:umass-sim0:0:0:0): removing device entry Root mount waiting for: usbus2 ugen2.4: at usbus2 Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro, noatime]... mountroot: waiting for device /dev/ufs/FreeBSD_Install ... Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19. mountroot> I can probably take a couple of pictures of the entire dmesg, if that would be of any interest. -- Joel ___ 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: HEAD memsticks broken? [USB/CAM Problems?]
On 09-02-2013 8:32, Joel Dahl wrote: > Hi, > > I suspect something is broken with memsticks built from HEAD. I noticed that I > couldn't boot the latest HEAD (amd64) memstick snapshot on two machines > (Lenovo X220 and HP ProLiant ML350 G5). Trying snapshots from the FreeBSD.org > FTP or allbsd.org makes no difference. I compared output from booting RELENG_9 and HEAD: RELENG_9: ugen2.3: at usbus2 umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:4:0:-1: Attached to scbus4 da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 da0: Removable Direct Access SCSI-2 device ??? da0: 40.000MB/s transfers da0: 1905MB (3903264 512 byte sectors: 255H 63S/T 24SC) (da0-umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (da0-umass-sim0:0:0:0): CAM status: SCSI Status Error (da0-umass-sim0:0:0:0): SCSI status: Check Condition (da0-umass-sim0:0:0:0): SCSI sense: No sense data present (da0-umass-sim0:0:0:0): Retrying command (per sense data) Root mount waiting for: usbus2 ugen2.4: at usbus2 Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]... Starting file system checks: /dev/ufs/FreeBSD_Install: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ufs/FreeBSD_Install: clean, 43155 free (507 frags, 5331 blocks, 0.1% fragmentation) Mounting local file systems:. and it works. HEAD: ugen2.3: at usbus2 umass0: on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:5:0:-1: Attached to scbus5 da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 da0: Removable Direct Access SCSI-0 device ?? da0: 40.000MB/s transfers da0: 3690MB (7557704 512 byte sectors: 255H 63S/T 470SC) (da0-umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (da0-umass-sim0:0:0:0): CAM status: SCSI Status Error (da0-umass-sim0:0:0:0): SCSI status: Check Condition (da0-umass-sim0:0:0:0): SCSI sense: No sense data present (da0-umass-sim0:0:0:0): Retrying command (per sense data) (da0-umass-sim0:0:0:0): Error 5, Retries exhausted (da0-umass-sim0:0:0:0): got CAM status 0x8c (da0-umass-sim0:0:0:0): fatal error, failed to attach to device (da0-umass-sim0:0:0:0): lost device - 0 outstanding, 4 refs (da0-umass-sim0:0:0:0): removing device entry ugen2.4: at usbus2 Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]... mountroot: waiting for device /dev/ufs/FreeBSD_Install ... Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19. BOOM -- Joel ___ 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"
HEAD memsticks broken?
Hi, I suspect something is broken with memsticks built from HEAD. I noticed that I couldn't boot the latest HEAD (amd64) memstick snapshot on two machines (Lenovo X220 and HP ProLiant ML350 G5). Trying snapshots from the FreeBSD.org FTP or allbsd.org makes no difference. It boots fine until mountroot, where I get (help messages removed): Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]... mountroot: waiting for device /dev/ufs/FreeBSD_Install ... Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ufs/FreeBSD_Install vfs.root.mountfrom.option=ro,noatime mountroot> I then tried a few older HEAD snapshots, but the problem persists. I've tried the following HEAD snapshots available at allbsd.org: FreeBSD-10.0-HEAD-r246472-JPSNAP-amd64-amd64-memstick.img FreeBSD-10.0-HEAD-r243701-JPSNAP-amd64-amd64-memstick.img FreeBSD-10.0-HEAD-r242396-JPSNAP-amd64-amd64-memstick.img FreeBSD-10.0-HEAD-r241545-JPSNAP-amd64-amd64-memstick.img FreeBSD-10.0-HEAD-r241070-JPSNAP-amd64-amd64-memstick.img I've also tried the following two snapshots from FreeBSD.org: FreeBSD-10.0-CURRENT-amd64-20130202-r246254-memstick FreeBSD-10.0-CURRENT-amd64-20130108-r245175-memstick None of the above works on these machines. Problem is exactly the same. Next up, I tried a 9.1-RELEASE amd64 memstick from FreeBSD.org. Boots without any problems whatsoever. After that, tried the latest (r246455) RELENG_9 amd64 snapshot from allbsd.org - also boots fine on both machines. Any ideas? -- Joel ___ 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: Reboot during startup with recent head
On 08-11-2012 19:32, Konstantin Belousov wrote: > On Thu, Nov 08, 2012 at 05:33:53PM +0100, Joel Dahl wrote: > > On 08-11-2012 16:33, Konstantin Belousov wrote: > > > On Thu, Nov 08, 2012 at 01:23:13PM +0100, Joel Dahl wrote: > > > > On 08-11-2012 12:55, Andriy Gapon wrote: > > > > > on 08/11/2012 10:45 Joel Dahl said the following: > > > > > > Hi, > > > > > > > > > > > > I rebuilt head (r242605) in a VMware virtual machine a couple of > > > > > > days ago, and > > > > > > now it won't boot anymore. The loader menu appears, the countdown > > > > > > starts, and boom, > > > > > > reboot. I tried a fresh head (r242700) but the problem remains. > > > > > > > > > > > > Going back to r242205 solves the problem, so this was introduced > > > > > > somewhere > > > > > > between r242205 and r242605. > > > > > > > > > > > > I managed to record the entire thing with my phone before I had to > > > > > > leave for > > > > > > work today. You can see it here: > > > > > > > > > > > > http://mirror.vnode.se/upload/head-reboots.mov > > > > > > > > > > > > Any ideas? Any specific revision I should try to back out? > > > > > > > > > > > > > > > > Rather wild guess - try to back out the recent SMEP commit. > > > > > > > > Well, it was a good guess. :-) I backed out revision 242433, rebuilt > > > > the kernel, > > > > and now it boots again. > > > > > > The following patch should allow you to boot. Please show me the verbose > > > dmesg > > > of the boot with the patch applied. > > > > With this patch the machine is back to a non-booting state again. :-( > > > > Anything else I should try? > Yes, please try the patch below. If it boots, I need a verbose dmesg. I removed the old patch, applied this one instead and rebuilt - but no difference. It's still an instant reboot. -- Joel ___ 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: Reboot during startup with recent head
On 08-11-2012 16:33, Konstantin Belousov wrote: > On Thu, Nov 08, 2012 at 01:23:13PM +0100, Joel Dahl wrote: > > On 08-11-2012 12:55, Andriy Gapon wrote: > > > on 08/11/2012 10:45 Joel Dahl said the following: > > > > Hi, > > > > > > > > I rebuilt head (r242605) in a VMware virtual machine a couple of days > > > > ago, and > > > > now it won't boot anymore. The loader menu appears, the countdown > > > > starts, and boom, > > > > reboot. I tried a fresh head (r242700) but the problem remains. > > > > > > > > Going back to r242205 solves the problem, so this was introduced > > > > somewhere > > > > between r242205 and r242605. > > > > > > > > I managed to record the entire thing with my phone before I had to > > > > leave for > > > > work today. You can see it here: > > > > > > > > http://mirror.vnode.se/upload/head-reboots.mov > > > > > > > > Any ideas? Any specific revision I should try to back out? > > > > > > > > > > Rather wild guess - try to back out the recent SMEP commit. > > > > Well, it was a good guess. :-) I backed out revision 242433, rebuilt the > > kernel, > > and now it boots again. > > The following patch should allow you to boot. Please show me the verbose dmesg > of the boot with the patch applied. With this patch the machine is back to a non-booting state again. :-( Anything else I should try? -- Joel ___ 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: Reboot during startup with recent head
On 08-11-2012 12:55, Andriy Gapon wrote: > on 08/11/2012 10:45 Joel Dahl said the following: > > Hi, > > > > I rebuilt head (r242605) in a VMware virtual machine a couple of days ago, > > and > > now it won't boot anymore. The loader menu appears, the countdown starts, > > and boom, > > reboot. I tried a fresh head (r242700) but the problem remains. > > > > Going back to r242205 solves the problem, so this was introduced somewhere > > between r242205 and r242605. > > > > I managed to record the entire thing with my phone before I had to leave for > > work today. You can see it here: > > > > http://mirror.vnode.se/upload/head-reboots.mov > > > > Any ideas? Any specific revision I should try to back out? > > > > Rather wild guess - try to back out the recent SMEP commit. Well, it was a good guess. :-) I backed out revision 242433, rebuilt the kernel, and now it boots again. -- Joel ___ 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"
Reboot during startup with recent head
Hi, I rebuilt head (r242605) in a VMware virtual machine a couple of days ago, and now it won't boot anymore. The loader menu appears, the countdown starts, and boom, reboot. I tried a fresh head (r242700) but the problem remains. Going back to r242205 solves the problem, so this was introduced somewhere between r242205 and r242605. I managed to record the entire thing with my phone before I had to leave for work today. You can see it here: http://mirror.vnode.se/upload/head-reboots.mov Any ideas? Any specific revision I should try to back out? -- Joel ___ 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: removal of share/doc/{papers,psd,smm,usd} in 2 months
On 22-10-2012 14:53, C. P. Ghost wrote: > On Sun, Oct 21, 2012 at 11:53 AM, Ulrich Spörlein wrote: > > On Sun, 2012-10-21 at 10:40:45 +0200, Hans Ottevanger wrote: > >> On 10/19/12 16:36, Ulrich Spörlein wrote: > >> > Hi all, > >> > > >> > those roff sources have been very naughty and will be removed from the > >> > tree by the end of the year. Most of those papers are severely out of > >> > date and provide no more use to the system. They can probably also be > >> > found online using a search engine of your choice. > >> > > >> > >> Could you be more specific as to why these sources have been "very > >> naughty"? > >> > >> > Should people feel strongly about them, we might be able to move them > >> > over to the doc repository. > >> > > >> > >> I strongly object this removal. As already pointed out by others, there > >> are papers documenting vi/ex and RPC/XDR. These papers are practically > >> the only docs available on these subjects, apart from the very terse man > >> pages. There are also tutorials on e.g. Yacc and Lex, that probably are > >> not that up-to-date but quite short and (at least for now) readily > >> available. And there is also the IPC Tutorial. > >> > >> This may not all be documents that are immediately needed for > >> operational purposes, but they do offer much needed background > >> information, also of historical character, i.e. how and why things > >> became as they are today. > > > > The handbook provides even more useful documentation and information, > > yet we don't have xsltproc in the base system, force everyone to compile > > it twice and then typeset all the documentation over and over again. > > > > They will therefore be moved to the doc repository were they probably > > should have been all along. > > How about converting them to SGML and integrating them into > the Handbook (with the caveat that they are outdated, but > retained for archival purposes)? We recently removed several outdated articles from the doc repo, so spending time on converting outdated stuff to XML and adding them to the doc repo makes no sense at all. -- Joel ___ 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: removal of share/doc/{papers,psd,smm,usd} in 2 months
On 19-10-2012 16:36, Ulrich Spörlein wrote: > Hi all, > > those roff sources have been very naughty and will be removed from the > tree by the end of the year. Most of those papers are severely out of > date and provide no more use to the system. They can probably also be > found online using a search engine of your choice. I definitely support this. -- Joel ___ 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: underexposed snapshots
On 15-09-2012 15:43, Randy Bush wrote: > ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch is a bit empty. i > guess things are moving around. any idea where i can get the latest > tag=. https://pub.allbsd.org/FreeBSD-snapshots/ -- Joel ___ 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: FreeBSD and LDAP users, bug or feature?
On 17-05-2012 8:24, Mark Felder wrote: > Check man adduser.conf(5) > > There is an option for "uidstart" which should do what you want. If you > set it to 1000 every time you run "adduser" it will show: Thanks, setting uidstart to 1000 indeed works around the problem. :) However, I would still like to know if this is intended behaviour. -- Joel ___ 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"
FreeBSD and LDAP users, bug or feature?
Hi, I have a machine running FreeBSD and openldap24-server, and several client machines running FreeBSD and openldap24-client and I'm experiencing a weird behaviour with adduser/pw. I create my LDAP users on the LDAP server, with UIDs starting at 5001. Local users on the server and clients should start at UID 1001, but this does not really work. If I use adduser to create a new local user on one of the client machines, it'll automatically be assigned with UID 5002 - which I find very confusing. This also breaks my LDAP setup, because when I add an LDAP user on the server, it'll also get UID 5002. Running pw usernext on one of the client machines confirms this behaviour: root@crashbox [~] pw usernext 5002:5002 But looking inside my /etc/passwd on the same machine reveals that the next free UID should be 1002. So pw is obviously getting information from LDAP and tries to be friendly and automatically gives me the next free UID from LDAP - which would make sense if pw could create LDAP users in addition to local users, but it can't. So right now I'm forced to check /etc/passwd on my machines each time I add a new local user and manually use that UID whenever I run adduser or pw. It works, but it's easy to shoot myself in the foot. Is this intended behaviour, or a bug? Or perhaps a misconfiguration on my part? I can provide configuration examples from my environment, but there really isn't much to see - I haven't made many changes besides installing the required applications from ports (openldap,nss_ldap,pam_ldap), changed my nsswitch.conf and a couple of files in /etc/pam.d/. -- Joel ___ 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: buildkernel fails
On 16-05-2012 23:41, Dimitry Andric wrote: > On 2012-05-16 23:18, Joel Dahl wrote:> Hi, > > I did a buildworld+buildkernel on my workstation today and buildkernel > > fails with: > > > > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign > > -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option > > -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL > > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > > -finline-limit=8000 --param inline-unit-growth=100 --param > > large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel > > -mno-red-zone -mno-mmx -mno-sse -msoft-float > > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror > > /usr/src/sys/dev/et/if_et.c > > Bus error (core dumped) > > *** [isci.ko.debug] Error code 138 > > 1 error > > *** [all] Error code 2 > > 1 error > > *** [modules-all] Error code 2 > > ctfconvert -L VERSION -g if_et.o > > 1 error > > *** [buildkernel] Error code 2 > > 1 error > > *** [buildkernel] Error code 2 > > 1 error > > > > My src tree is at the latest rev. No /usr/obj. I'm currently running > > CURRENT from May, 5th. > > I think you may be hitting the libthr issue that was introduced in > r234947 (Thu May 3 09:17:31 2012 UTC) and fixed in r235068 (Sat May 5 > 23:51:24 2012 UTC). This caused some programs to randomly bomb out with > bus errors or other weirdness. > > Please try building and installing lib/libthr (from your updated source > tree) before running the rest of the world/kernel build. That fixed it. Thanks! -- Joel ___ 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"
buildkernel fails
Hi, I did a buildworld+buildkernel on my workstation today and buildkernel fails with: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/dev/et/if_et.c Bus error (core dumped) *** [isci.ko.debug] Error code 138 1 error *** [all] Error code 2 1 error *** [modules-all] Error code 2 ctfconvert -L VERSION -g if_et.o 1 error *** [buildkernel] Error code 2 1 error *** [buildkernel] Error code 2 1 error My src tree is at the latest rev. No /usr/obj. I'm currently running CURRENT from May, 5th. Any ideas? -- Joel ___ 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: Intel GPU driver import
On 13-05-2012 0:39, Konstantin Belousov wrote: > The positive points to the second approach is that we still have older > kernel drivers around. Also, I have more freedom in changing the DRM > core, without fearing breakage in the DRI1 land. Since I do not really > want to deal with Gen2-3 hardware What is Gen2-3 hardware in this context? Can you give examples? -- Joel ___ 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: No working IDE in FreeBSD!
On 23-02-2012 12:22, O. Hartmann wrote: > Before I waste more time on searching for a suitable IDE apart ANJUTA, > I'd like to ask people here what alternative they would suggest if the > focus is devel/anjuta. Eclipse is no way, KDevelop is broken, CodeBlocks > is incapable of being easily adapted to CLANG. Haven't used it myself, but maybe devel/geany ? http://www.geany.org/ -- Joel ___ 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: Enhancing the user experience with tcsh
On 12-02-2012 4:05, Gonzalo Nemmi wrote: > On Sat, Feb 11, 2012 at 5:07 AM, Joel Dahl wrote: > > On 10-02-2012 9:03, Eitan Adler wrote: > >> Picking a random person to reply to. > >> > >> There are a lot of good suggestions in this thread, but can we please > >> remember a few things: > >> > >> - Users can always add their own ~/.cshrc > >> - Many users will get annoyed by what is someone else's amazing setup > > > > With the above in mind, I suggest we change as little as possible from what > > we have today (for now) and that we do improvements in small steps. > > > > I believe 99.99% of all users would find the change below to be a definite > > improvement over the current default values in .cshrc: > > > > Index: dot.cshrc > > === > > --- dot.cshrc (revision 231507) > > +++ dot.cshrc (working copy) > > @@ -24,8 +24,10 @@ > > # An interactive shell -- set some stuff up > > set prompt = "`/bin/hostname -s`# " > > set filec > > - set history = 100 > > - set savehist = 100 > > + set history = 1000 > > + set savehist = (1000 merge) > > + set autolist > > + set autoexpand > > set mail = (/var/mail/$USER) > > if ( $?tcsh ) then > > bindkey "^W" backward-delete-word > > > > Also, a comment pointing to /usr/share/examples/tcsh/complete.tcsh would > > be a nice addition to the default .cshrc. > > > > -- > > Joel > > Joel, with all due respect, do you really think that 99.9% of all > users will not find the _non_intrusive_ additions below useful? You're missing the point. We need to start with something small that we all can agree on. We'll never reach consensus if we're trying to change too much at once (just check the amount of messages this topic has created already). -- Joel ___ 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: Enhancing the user experience with tcsh
On 10-02-2012 9:03, Eitan Adler wrote: > Picking a random person to reply to. > > There are a lot of good suggestions in this thread, but can we please > remember a few things: > > - Users can always add their own ~/.cshrc > - Many users will get annoyed by what is someone else's amazing setup With the above in mind, I suggest we change as little as possible from what we have today (for now) and that we do improvements in small steps. I believe 99.99% of all users would find the change below to be a definite improvement over the current default values in .cshrc: Index: dot.cshrc === --- dot.cshrc (revision 231507) +++ dot.cshrc (working copy) @@ -24,8 +24,10 @@ # An interactive shell -- set some stuff up set prompt = "`/bin/hostname -s`# " set filec - set history = 100 - set savehist = 100 + set history = 1000 + set savehist = (1000 merge) + set autolist + set autoexpand set mail = (/var/mail/$USER) if ( $?tcsh ) then bindkey "^W" backward-delete-word Also, a comment pointing to /usr/share/examples/tcsh/complete.tcsh would be a nice addition to the default .cshrc. -- Joel ___ 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: Enhancing the user experience with tcsh
On 09-02-2012 23:50, Warren Block wrote: > On Fri, 10 Feb 2012, Gonzalo Nemmi wrote: > > > On Thu, Feb 9, 2012 at 9:52 PM, Eitan Adler wrote: > >> In conf/160689 (http://www.freebsd.org/cgi/query-pr.cgi?pr=160689) > > >> there has been some discussion about changing the default cshrc file. > > In the same line that Wojciech on the PR ".cshrc should be updated for > > modern hardware" I always set this ones on /usr/share/skel/dot.cshrc > > > > bindkey "\e[1~" beginning-of-line #make Home key work; > > bindkey "\e[2~" overwrite-mode #make Ins key work; > > bindkey "\e[3~" delete-char #make Delete key work; > > bindkey "\e[4~" end-of-line #make End key work; > > > > Besides that I add an "if [ -d $HOME/bin ]" and add it to $PATH if it > > exists, but that has nothing to do with ".cshrc should be updated for > > modern hardware" ... it jsut comes in really handy. > > The question becomes "how much is too much?" For example, ever since a > thread in the forums showed examples of csh/tcsh autocompletion, I've > thought the default .cshrc should be stuffed with them. Not for typing > reduction so much as self-documenting commands like > > complete chown'p/1/u/' > complete man 'C/*/c/' > complete service 'n/*/`service -l`/' > > 'service' autocompletes with a list of services--it helps the user by > showing valid choices. Same with 'chown', it gives a list of users. > > Then there's this, which probably isn't quite right but has been useful > to me (thanks to forum members for help with it): > > complete make 'n@*@`make -pn | sed -n -E "/^[#_.\/[:blank:]]+/d; > /=/d; s/[[:blank:]]*:.*//gp;"`@' > > That completes with all lower-case make targets for the current > directory. > > Package operations are easier when the package names autocomplete: > > complete pkg_delete 'c/-/(i v D n p d f G x X r)/' \ > 'n@*@`ls /var/db/pkg`@' > complete pkg_info 'c/-/(a b v p q Q c d D f g i I j k K r R m L s o G O x > X e E l t V P)/' \ > 'n@*@`\ls -1 /var/db/pkg | sed s%/var/db/pkg/%%`@' How about adding stuff like this to /usr/share/examples/tcsh/complete.tcsh ? -- Joel ___ 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: Enhancing the user experience with tcsh
On 09-02-2012 19:52, Eitan Adler wrote: > In conf/160689 (http://www.freebsd.org/cgi/query-pr.cgi?pr=160689) > there has been some discussion about changing the default cshrc file. > > I'd like to commit something like the following based on Chris's patch > at the end of the thread. This post is an attempt to open the change > to wider discussion. > + set autolist > + # Use history to aid expansion > + set autoexpand +1 for autolist and autoexpand. -- Joel ___ 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: Improving the FreeBSD-9 boot menu
On 20-01-2012 7:57, Warren Block wrote: > On Tue, 20 Sep 2011, Warren Block wrote: > > > The patch in PR 160818 makes some clarifications and improvements to the > > new > > boot menu. Obviously this is not for 9.0-RELEASE, just wanting to get it > > out > > there so people can look at it. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=160818 > > > > Among other things, the patch removes the word "boot" from options that > > don't > > actually boot. The options are lined up, and enabled options are drawn in > > reverse video when loader_color=1 is set in /boot/loader.conf. > > Just reminding people about this now that 9.0 is out. It makes what I > feel are genuine usability and readability improvements to the boot > menu. I agree. Definitely an improvement. -- Joel ___ 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: sysinstall as a post-install tool
On 03-01-2012 18:33, Eitan Adler wrote: > Hi, > > In the the recent sysinstall thread there seems to be general agreement that > having a post-install configuration tool is a good thing. Until such a > tool is written I think it would be a good idea to use sysinstall for > this purpose. I am willing to do the work to restore sysinstall and > maintain it as a post-install tool until a new one is written. > > My plan would be to: > > - Restore sysinstall and libodialog You should read the following post by Freddie Cash to current@, in case you haven't seen it: http://lists.freebsd.org/pipermail/freebsd-current/2012-January/030954.html I agree with all his points. -- Joel ___ 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: BETA2 panic
On 02-10-2011 0:54, Adrian Chadd wrote: > On 1 October 2011 20:46, Joel Dahl wrote: > > > My laptop has been running with your patch for almost 8 hours now. No > > panics. > > > > Do you have all of the -current debugging enabled (witness, invariants, etc) ? I'm running GENERIC, so yes. -- Joel ___ 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: BETA2 panic
On 30-09-2011 17:52, Adrian Chadd wrote: > Hi, > > Would you please try this patch? Make sure that witness and the rest > of the lock debugging is enabled. > > I've been working on this problem with someone else on the list (but I > can't trigger it myself; I think I need to get some dual-CPU wireless > test hardware.) My laptop has been running with your patch for almost 8 hours now. No panics. -- Joel ___ 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: BETA2 panic
On 07-09-2011 10:59, Bernhard Schmidt wrote: > On Tue, Sep 6, 2011 at 22:42, Joel Dahl wrote: > > On 05-09-2011 9:02, Bernhard Schmidt wrote: > >> On Mon, Sep 5, 2011 at 08:24, Joel Dahl wrote: > >> > On 05-09-2011 5:09, Adrian Chadd wrote: > >> >> On 5 September 2011 01:04, Joel Dahl wrote: > >> >> > Hi, > >> >> > > >> >> > I upgraded my laptop from BETA1 to rev. 225367 today, and now my > >> >> > laptop panics just a few minutes after booting. This is 100% > >> >> > reproducible, it panics every time. > >> >> > > >> >> > I've got a pic with the backtrace here: > >> >> > http://www.vnode.se/sc/panic_20110904.jpg > >> >> > >> >> Hi, > >> >> > >> >> There weren't many commits between BETA1 and -HEAD in the wireless > >> >> area; would you please do a binary search of the kernel revisions (no > >> >> need to do full buildworlds) to find which commit broke it? > >> > > >> > Yes, I'll do that tonight. > >> > >> While doing so, can you enable at least some debugging? > >> wlandebug +state > >> or even better > >> wlandebug 0x > >> > >> It smells like that something is poking the SW bmiss handler while not > >> in RUN state and therefore you're hitting a KASSERT(). Question is if > >> the bmiss timer isn't stopped/drained somewhere or if there is too > >> excessive call. > > > > Exactly what in the wlandebug output are you looking for? I've posted a pic > > at http://www.vnode.se/sc/panic_20110906.jpg showing what it looks like > > right > > before the panic. This is with "wlandebug 0x". > > Thanks, so, looks like it is scanning while the panic happens. At that > point it should actually never ever care about beacon misses.. this is > strange, really. > > Can you try to comment out the call to ieee80211_beacon_miss() on line > 2936 in if_iwn.c? If the panic no longer happens the issue is > somewhere in the conditions before that call. Hm, this is with bwn(4), not iwn(4). :) -- Joel ___ 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: BETA2 panic
On 05-09-2011 9:02, Bernhard Schmidt wrote: > On Mon, Sep 5, 2011 at 08:24, Joel Dahl wrote: > > On 05-09-2011 5:09, Adrian Chadd wrote: > >> On 5 September 2011 01:04, Joel Dahl wrote: > >> > Hi, > >> > > >> > I upgraded my laptop from BETA1 to rev. 225367 today, and now my laptop > >> > panics just a few minutes after booting. This is 100% reproducible, it > >> > panics every time. > >> > > >> > I've got a pic with the backtrace here: > >> > http://www.vnode.se/sc/panic_20110904.jpg > >> > >> Hi, > >> > >> There weren't many commits between BETA1 and -HEAD in the wireless > >> area; would you please do a binary search of the kernel revisions (no > >> need to do full buildworlds) to find which commit broke it? > > > > Yes, I'll do that tonight. > > While doing so, can you enable at least some debugging? > wlandebug +state > or even better > wlandebug 0x > > It smells like that something is poking the SW bmiss handler while not > in RUN state and therefore you're hitting a KASSERT(). Question is if > the bmiss timer isn't stopped/drained somewhere or if there is too > excessive call. Exactly what in the wlandebug output are you looking for? I've posted a pic at http://www.vnode.se/sc/panic_20110906.jpg showing what it looks like right before the panic. This is with "wlandebug 0x". I've also installed kernels all the way back to revision 222980, but they all panic, which I think is somewhat odd. -- Joel ___ 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: BETA2 panic
On 05-09-2011 5:09, Adrian Chadd wrote: > On 5 September 2011 01:04, Joel Dahl wrote: > > Hi, > > > > I upgraded my laptop from BETA1 to rev. 225367 today, and now my laptop > > panics just a few minutes after booting. This is 100% reproducible, it > > panics every time. > > > > I've got a pic with the backtrace here: > > http://www.vnode.se/sc/panic_20110904.jpg > > Hi, > > There weren't many commits between BETA1 and -HEAD in the wireless > area; would you please do a binary search of the kernel revisions (no > need to do full buildworlds) to find which commit broke it? Yes, I'll do that tonight. -- Joel ___ 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: BETA2 panic
On 04-09-2011 14:45, Garrett Cooper wrote: > On Sun, Sep 4, 2011 at 1:22 PM, Joel Dahl wrote: > > On 04-09-2011 10:56, Garrett Cooper wrote: > >> On Sun, Sep 4, 2011 at 10:04 AM, Joel Dahl wrote: > >> > Hi, > >> > > >> > I upgraded my laptop from BETA1 to rev. 225367 today, and now my > >> > laptop panics just a few minutes after booting. This is 100% > >> > reproducible, it panics every time. > >> > > >> > I've got a pic with the backtrace here: > >> > http://www.vnode.se/sc/panic_20110904.jpg > >> > >> Is your wireless turned off? If so, it looks like the state > >> transition code isn't being handled properly between bwn(4) and > >> net80211(4), in particular because your wireless card was still in > >> 'scan' mode. > > > > No, it's always on. I can ping over the wireless for a few minutes, until > > it panics. > >Hmm.. and the wireless card always appears on? Assuming the > firmware isn't buggy (did you update it recently? have you booted > other OSes, i.e. Windows or Linux that could be updating the firmware > automatically on load?), it should keep the light for the wireless NIC > properly lit. Sure, it always appears on. This laptop has been running freebsd exclusively for at least a year. FWIW, the same "RF switch is changed on/off" message from bwn has always been there on this machine. I also noticed them on my old laptop, an HP 6715b. -- Joel ___ 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: BETA2 panic
On 04-09-2011 10:56, Garrett Cooper wrote: > On Sun, Sep 4, 2011 at 10:04 AM, Joel Dahl wrote: > > Hi, > > > > I upgraded my laptop from BETA1 to rev. 225367 today, and now my laptop > > panics just a few minutes after booting. This is 100% reproducible, it > > panics every time. > > > > I've got a pic with the backtrace here: > > http://www.vnode.se/sc/panic_20110904.jpg > > Is your wireless turned off? If so, it looks like the state > transition code isn't being handled properly between bwn(4) and > net80211(4), in particular because your wireless card was still in > 'scan' mode. No, it's always on. I can ping over the wireless for a few minutes, until it panics. Any particular commit you think I should try to back out? -- Joel ___ 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"
BETA2 panic
Hi, I upgraded my laptop from BETA1 to rev. 225367 today, and now my laptop panics just a few minutes after booting. This is 100% reproducible, it panics every time. I've got a pic with the backtrace here: http://www.vnode.se/sc/panic_20110904.jpg -- Joel ___ 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: Multiple hpet messages during boot
On 16-09-2010 8:28, John Baldwin wrote: > On Wednesday, September 15, 2010 2:32:33 am Joel Dahl wrote: > > I noticed this during boot (HEAD from yesterday): > > > > hpet0: [FILTER] > > hpet0: [FILTER] > > hpet0: [FILTER] > > hpet0: [FILTER] > > hpet0: [FILTER] > > hpet0: [FILTER] > > hpet0: [FILTER] > > hpet0: [FILTER] > > > > Is it really necessary to print this 8 times? > > I'd actually like to remove the interrupt messages that say '[FILTER]' or > '[GIANT]', etc. I think in general they only add clutter. Definitely agreed. Go for it. -- Joel ___ 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"
Multiple hpet messages during boot
I noticed this during boot (HEAD from yesterday): hpet0: [FILTER] hpet0: [FILTER] hpet0: [FILTER] hpet0: [FILTER] hpet0: [FILTER] hpet0: [FILTER] hpet0: [FILTER] hpet0: [FILTER] Is it really necessary to print this 8 times? -- Joel ___ 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: Official request: Please make GNU grep the default
On 14-08-2010 4:35, Sam Fourman Jr. wrote: > >> BSD grep > >> Elapsed time: 47 seconds > > > > what about optimizing BSD grep instead? > > I think this is reasonable, leave BSD grep default for a few more weeks, and > work on performance enhancements. I agree that changing the default back > for a RELEASE is probably a good idea, but the exposure to wider testing > while focusing on performance, can't hurt much can it? I agree, keep bsdgrep as default for a while and focus on the performance problems. This is CURRENT after all, and 9.0 isn't anywhere near release yet (afaik). -- Joel ___ 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: etcupdate tool in base?
On 10-06-2010 13:46, John Baldwin wrote: > I've had several folks ask me recently about importing etcupdate > (http://www.FreeBSD.org/~jhb/etcupdate) into the base system as an alternate > tool for updating /etc during upgrades. Do folks have any strong objections > to doing so? More details about how it works and an HTML version of the > manpage can be found at the URL above. +1 for importing it into base. -- Joel ___ 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: Switchover to CAM ATA?
On 22-04-2010 18:31, Alexander Motin wrote: > Hi. > > With time passed, CAM-based ATA infrastructure IMHO looks enough mature > now to enable it in HEAD. Now we have two new stable drivers ahci(4) and > siis(4), covering major part of modern SATA HBAs, `options ATA_CAM` > wrapper for ata(4) to supports legacy hardware, and one more improved > driver for Marvell HBAs (mvs) is now in development and soon will be > present for testing. Together with many other people I have tested above > at least on i386, amd64, arm and spart64 architectures. If we want this in 9.0 we should probably switch to CAM ATA in HEAD now in order to allow enough testing before the release. -- Joel ___ 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"
