Re: CLang and WERROR
Please don't try to start a new thread by replying to a message and changing the subject line. Those of us who use threaded mail readers see the new message under the old thread, which can cause the new message to be missed. It's better to start a whole new message. hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kern/157863: [geli] kbdmux prevents geli passwords from being entered properly on boot
Hello, Just to let everyone know that this is still an issue. I am trying to install FreeBSD 9.0 amd64 on a Lenovo X121e and I can't get it to accept the geli passphrase during boot. I've confirmed using kern.geom.eli.visible_passphrase=1 that the passphrase is correct, and the same passphrase is accepted when the system is booted up. I've tried disabling kbdmux in /boot/device.hints like the PR said, but that didn't help. I also tried disabling atkbd and atkbdc without any luck, infact I couldn't type anything at all when disabling those. Any hints or suggestions to what I might try ? I have another 9-stable laptop that mounts a geli volume at boot, no idea why that one works and this new one doesn't. Thanks in advance, /Thomas Steen Rasmussen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kern/157863: [geli] kbdmux prevents geli passwords from being entered properly on boot
Thomas Steen Rasmussen tho...@gibfest.dk wrote: Just to let everyone know that this is still an issue. I am trying to install FreeBSD 9.0 amd64 on a Lenovo X121e and I can't get it to accept the geli passphrase during boot. I've confirmed using kern.geom.eli.visible_passphrase=1 that the passphrase is correct, and the same passphrase is accepted when the system is booted up. I've tried disabling kbdmux in /boot/device.hints like the PR said, but that didn't help. I also tried disabling atkbd and atkbdc without any luck, infact I couldn't type anything at all when disabling those. If disabling kbdmux doesn't help, it sounds like a different issue to me. Any hints or suggestions to what I might try ? I have another 9-stable laptop that mounts a geli volume at boot, no idea why that one works and this new one doesn't. Are you using the password together with a keyfile? I've misconfigured the keyfile in loader.conf in the past, which results in the valid password not being accepted. Obviously the setup then magically works later on when the keyfile is specified correctly on the command line. If you aren't using keyfiles, you could try setting up an USB stick with geli, to confirm that the same media works on one laptop, but doesn't on the other. Fabian signature.asc Description: PGP signature
Re: kern/157863: [geli] kbdmux prevents geli passwords from being entered properly on boot
On 13-06-2012 15:01, Fabian Keil wrote: Thomas Steen Rasmussen tho...@gibfest.dk wrote: Just to let everyone know that this is still an issue. I am trying to install FreeBSD 9.0 amd64 on a Lenovo X121e and I can't get it to accept the geli passphrase during boot. I've confirmed using kern.geom.eli.visible_passphrase=1 that the passphrase is correct, and the same passphrase is accepted when the system is booted up. I've tried disabling kbdmux in /boot/device.hints like the PR said, but that didn't help. I also tried disabling atkbd and atkbdc without any luck, infact I couldn't type anything at all when disabling those. If disabling kbdmux doesn't help, it sounds like a different issue to me. You are right, shame on me for polluting an innocent PR with unrelated stuff. More info below. Any hints or suggestions to what I might try ? I have another 9-stable laptop that mounts a geli volume at boot, no idea why that one works and this new one doesn't. Are you using the password together with a keyfile? Yes I am. I've misconfigured the keyfile in loader.conf in the past, which results in the valid password not being accepted. Obviously the setup then magically works later on when the keyfile is specified correctly on the command line. This (a small typo in keyfile in loader.conf) was the problem, and I need to get my eyes examined :-) geli could be better at explaining the problem though. Thank you Fabian! Just what I needed. Apologies for the noise, Thomas Steen Rasmussen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ULE Scheduler
On 12.06.12 16:08, Momchil Ivanov wrote: So the L2 cache is shared between both cores and hence it's size does not matter at all? If the cache is shared between both cores then it does not matter on which core the process runs, as long as data is in teh case. The cache size is irrelevant. Some CPUs have shared cache between cores, some don't. The ULE scheduler takes this into account, the 4BSD does not. Even if the ULE scheduler takes the CPU topology into consideration, if you only have two cores, it is almost guaranteed that processes will be switched between both, because the OS is running way more than two processes at the same time. Even with more cores... it is not guaranteed an computational process won't be 'bouncing'. Here is an example. Suppose you have an 8 core (or threads) CPU. If you happen to have an modern Ethernet controller, like the Intel 82576 (the igb driver in FreeBSD), then it will use up to 8 interrupt lines, by default routing them each to a different core. Then, if you have heavier network traffic, chances are that at any given moment all 8 interrupts might be fired and all 8 cores switched to service network traffic -- removing your computational process from the running queue. The next time it runs, it might run on any other core, especially if the cache is not shared. Of course, if you have sufficiently large number of CPUs, you can configure your system so that such things do not happen, like by limiting the number of cores the igb driver attaches to, and have some of the cores dedicated to 'only' running an computational task. There is however, very little sense doing so. Daniel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel trap with stable/8 on DL360p G8 w/ BCM5719
Rick Miller wrote: Hi all, I am attempting to build stable/8 (as of 21 May 2012) on a DL360p G8 with a BCM5719. I receive a kernel panic very similar to the one at this URL: http://freebsd.1045724.n5.nabble.com/Fatal-trap-19-Stopped-at-bge-init-locked-and-bge-booting-problems-td5504461.html When booting 9.0-RELEASE on the exact same machine everything is fine, until I set an interface to UP which has an active link. Greetings, Philipp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel trap with stable/8 on DL360p G8 w/ BCM5719
On Wed, Jun 13, 2012 at 12:07 PM, Philipp Wuensche cryx-free...@h3q.com wrote: Rick Miller wrote: Hi all, I am attempting to build stable/8 (as of 21 May 2012) on a DL360p G8 with a BCM5719. I receive a kernel panic very similar to the one at this URL: http://freebsd.1045724.n5.nabble.com/Fatal-trap-19-Stopped-at-bge-init-locked-and-bge-booting-problems-td5504461.html When booting 9.0-RELEASE on the exact same machine everything is fine, until I set an interface to UP which has an active link. I can install stable/8 from physical media, but like you, I get the panic under the same circumstances. -- Take care Rick Miller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
problem with chpass after recent libutil change
Hi, I have some 8-STABLE and 9-STABLE systems which have been upgraded from sources csuped on June 3, and I found that I could no more change the shell for toor: #chpass -s /bin/csh toor chpass: entry inconsistent chpass: pw_copy: Invalid argument and seemingly ONLY for toor. reverting lib/lib/libutil/pw_util.c from r236451 (on 9.X) or r236452 (on 8.X) to the previous version seems to be workaround. Claude Buisson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Thanks John. I'm building HEAD now... What about 9.0? If I just apply r237008 it would be work? -- Andrey Zonov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Wednesday, June 13, 2012 3:29:45 pm Andrey Zonov wrote: On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Thanks John. I'm building HEAD now... What about 9.0? If I just apply r237008 it would be work? Yes, I believe so. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
nxstack in 9-STABLE
Hi Konstantin! Do you have any plan, to MFC to 9-STABLE this commit: r230767 in HEAD commit f3be56eac8844592f627e88d16ec8ef761473512 Author: kib kib@ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Date: Mon Jan 30 07:56:00 2012 + Finally, try to enable the nxstacks on amd64 and powerpc64 for both 64bit and 32bit ABIs. Also try to enable nxstacks for PAE/i386 when supported, and some variants of powerpc32. MFC after: 2 months (if ever) git-svn-id: svn://svn.freebsd.org/base/head@230767 ccf9f872-aa2e-dd11-9fc8-0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with chpass after recent libutil change
On Wed, Jun 13, 2012 at 06:57:38PM +0200, Claude Buisson wrote: Hi, I have some 8-STABLE and 9-STABLE systems which have been upgraded from sources csuped on June 3, and I found that I could no more change the shell for toor: #chpass -s /bin/csh toor chpass: entry inconsistent chpass: pw_copy: Invalid argument and seemingly ONLY for toor. reverting lib/lib/libutil/pw_util.c from r236451 (on 9.X) or r236452 (on 8.X) to the previous version seems to be workaround. Claude Buisson Crap I'll work on a fix asap. regards, Bapt pgp7TKGicWM0u.pgp Description: PGP signature
Re: problem with chpass after recent libutil change
On Wed, Jun 13, 2012 at 06:57:38PM +0200, Claude Buisson wrote: Hi, I have some 8-STABLE and 9-STABLE systems which have been upgraded from sources csuped on June 3, and I found that I could no more change the shell for toor: #chpass -s /bin/csh toor chpass: entry inconsistent chpass: pw_copy: Invalid argument and seemingly ONLY for toor. reverting lib/lib/libutil/pw_util.c from r236451 (on 9.X) or r236452 (on 8.X) to the previous version seems to be workaround. Claude Buisson Can you try with the following patch? http://people.freebsd.org/~bapt/add-special-case-for-toor.diff Regards, Bapt pgpzug7i7qFFB.pgp Description: PGP signature
Re: problem with chpass after recent libutil change
On 06/13/2012 23:44, Baptiste Daroussin wrote: On Wed, Jun 13, 2012 at 06:57:38PM +0200, Claude Buisson wrote: Hi, I have some 8-STABLE and 9-STABLE systems which have been upgraded from sources csuped on June 3, and I found that I could no more change the shell for toor: #chpass -s /bin/csh toor chpass: entry inconsistent chpass: pw_copy: Invalid argument and seemingly ONLY for toor. reverting lib/lib/libutil/pw_util.c from r236451 (on 9.X) or r236452 (on 8.X) to the previous version seems to be workaround. Claude Buisson Can you try with the following patch? http://people.freebsd.org/~bapt/add-special-case-for-toor.diff Regards, Bapt Thanks, Will try tomorrow Claude Buisson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with chpass after recent libutil change
On 06/13/2012 23:44, Baptiste Daroussin wrote: On Wed, Jun 13, 2012 at 06:57:38PM +0200, Claude Buisson wrote: Hi, I have some 8-STABLE and 9-STABLE systems which have been upgraded from sources csuped on June 3, and I found that I could no more change the shell for toor: #chpass -s /bin/csh toor chpass: entry inconsistent chpass: pw_copy: Invalid argument and seemingly ONLY for toor. reverting lib/lib/libutil/pw_util.c from r236451 (on 9.X) or r236452 (on 8.X) to the previous version seems to be workaround.Fisr Claude Buisson Can you try with the following patch? http://people.freebsd.org/~bapt/add-special-case-for-toor.diff Regards, Bapt I managed to do a first test sooner. On 9-STABLE i386, I confirm that the patch solves the problem !! Tomorrow , I will patch 9-STABLE amd64 and 8-STABLE i386. Claude Buisson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
devd problem with 9-stable
Since updating my systems to 9-Stable, I am not getting my smartcard
reader attached when hot-plugged.
From devd.conf
attach 50 {
device-name ugen[0-9]+;
match vendor 0x0529;
match product 0x0600;
action /usr/local/sbin/openct-control attach usb:529/600 usb /dev/$dev$
};
detach 50 {
device-name ugen[0-9]+;
match vendor 0x0529;
match product 0x0600;
action /usr/bin/pkill -fx '/usr/local/sbin/ifdhandler -H -p [a-z0-9]+ $
};
If I manually enter the action command, it works fine, but it fails
when I insert the device. It worked fine under version 8. I have
confirmed devd is seeing the device inserted just fine. the action
just does not seem to be carried out.
Any idea where I should look? I saw a couple of threads on current
from others seeing something similar, but could find no resolution.
I have seen a
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: GCC-4.6-20120608 has a corrupt archive or a bad checksum
On 06/12/12 12:04, Gerald Pfeifer wrote: John Merryweather Cooper wrote: Bad distfile or checksum for lang/gcc46 The mirror you are using per your e-mail -- ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/sources.redhat.com/ -- provides a broken image. I have done several downloads myself, from the original source and other mirrors, and always get the correct checksum (and a matching tarball), that is, the one matching gcc46/distinfo in FreeBSD Ports CVS. If you download directly from ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20120608/gcc-4.6-20120608.tar.bz2 and put that into ports/distfiles, that should work? Alternatively, download repeatedly until it hits a different mirror? Gerald ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org Well, that's exactly the point. It never got me to any other mirrors. Repeated runs always ended the same way even with me manually deleted the distfile before each run. -- John M. Cooper -- -- John M. Cooper ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: GCC-4.6-20120608 has a corrupt archive or a bad checksum
On 06/13/12 20:37, John Merryweather Cooper wrote: On 06/12/12 12:04, Gerald Pfeifer wrote: John Merryweather Cooper wrote: Bad distfile or checksum for lang/gcc46 The mirror you are using per your e-mail -- ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/sources.redhat.com/ -- provides a broken image. I have done several downloads myself, from the original source and other mirrors, and always get the correct checksum (and a matching tarball), that is, the one matching gcc46/distinfo in FreeBSD Ports CVS. If you download directly from ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20120608/gcc-4.6-20120608.tar.bz2 and put that into ports/distfiles, that should work? Alternatively, download repeatedly until it hits a different mirror? Gerald ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org Well, that's exactly the point. It never got me to any other mirrors. Repeated runs always ended the same way even with me manually deleted the distfile before each run. -- John M. Cooper Finally got it from: = gcc-4.6-20120608.tar.bz2 doesn't seem to exist in /usr/ports/distfiles//. = Attempting to fetch http://mirrors.kernel.org/sources.redhat.com/gcc/snapshots/4.6-20120608/gcc-4.6-20120608.tar.bz2 gcc-4.6-20120608.tar.bz264 MB 597 kBps Clearly a bad mirror. -- John M. Cooper -- -- John M. Cooper ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problem with chpass after recent libutil change
14.06.2012 8:44, Baptiste Daroussin написал: On Wed, Jun 13, 2012 at 06:57:38PM +0200, Claude Buisson wrote: Hi, I have some 8-STABLE and 9-STABLE systems which have been upgraded from sources csuped on June 3, and I found that I could no more change the shell for toor: #chpass -s /bin/csh toor chpass: entry inconsistent chpass: pw_copy: Invalid argument and seemingly ONLY for toor. reverting lib/lib/libutil/pw_util.c from r236451 (on 9.X) or r236452 (on 8.X) to the previous version seems to be workaround. Claude Buisson Can you try with the following patch? http://people.freebsd.org/~bapt/add-special-case-for-toor.diff Works here. FreeBSD 10.0-113-CURRENT clang #0 r236355M: -- Dima Panov (flu...@freebsd.org) (KDE, Office)@FreeBSD team Facebook: http://www.facebook.com/fluffy.khv IRC: fluffy@EFNet, fluffykhv@FreeNode twitter: fluffy_khv | skype: dima.panov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
