Re: kernel panic with _autoload_ nvidia driver
Hello ! This problems appears about 4-6 months ago after updating of -CURRENT host. Unable to boot host with nvidia_load="YES" in loader.conf because panic. But when nvidia driver loads manually via kldload, everything OK. Nvidia driver version is 310.44 at this moment, but problem was and on earlier version too. As far as I can tell this is OK again with nvidia version 319.17. I've got panic with nvidia-driver 319.17 too. ___ 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: kernel panic with _autoload_ nvidia driver
On 05.05.2013 09:24 (UTC+2), de...@stasyan.com wrote: > Hello ! >>> This problems appears about 4-6 months ago after updating of -CURRENT >>> host. >>> Unable to boot host with nvidia_load="YES" in loader.conf because panic. >>> But when nvidia driver loads manually via kldload, everything OK. >>> Nvidia driver version is 310.44 at this moment, but problem was and on >>> earlier version too. >> As far as I can tell this is OK again with nvidia version 319.17. > I've got panic with nvidia-driver 319.17 too. > Do you know the workaround to build the port with 'env USE_GCC=any make' ? With this it should not panic anymore, but start normal again ... Perhaps danfe@ as the maintainer has more ideas? ___ 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: kernel panic with _autoload_ nvidia driver
Hello ! This problems appears about 4-6 months ago after updating of -CURRENT host. Unable to boot host with nvidia_load="YES" in loader.conf because panic. But when nvidia driver loads manually via kldload, everything OK. Nvidia driver version is 310.44 at this moment, but problem was and on earlier version too. As far as I can tell this is OK again with nvidia version 319.17. I've got panic with nvidia-driver 319.17 too. Do you know the workaround to build the port with 'env USE_GCC=any make' ? With this it should not panic anymore, but start normal again ... Yes, it works normal with GCC. Thank you ! Perhaps danfe@ as the maintainer has more ideas? ___ 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 build error (header pollution ?) after 249958
Since svn 249959 (when NO_IDEA was removed) I cannot build HEAD on a somewhat recent stable/9 (see below; kernel and userland in sync) > uname -a FreeBSD bsd9 9.1-STABLE FreeBSD 9.1-STABLE #0 r248472: Tue Mar 19 08:36:09 CET 2013 luigi@bsd9:.../RELENG_9/sys/LUIGI amd64 (note that head was unbuildable in general since 249972 because there were leftovers of the IDEA option around) The error occurs during the 'toolchain' target (actually, probably in the 'libraries' one) and it is the following: ---> [ remember the cflags below ] cc -O2 -pipe -DTERMIOS -DANSI_SOURCE -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/home/luigi/FreeBSD/obj_head/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_SSE2 -DAES_ASM -DBSAES_ASM -DVPAES_ASM -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_ASM -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1 -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes -std=gnu89 -fstack-protector -Wno-pointer-sign -c /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c -o a_sign.o /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c: In function 'ASN1_item_sign_ctx': /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:243: error: 'EVP_MD_CTX' has no member named 'pctx' /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:243: warning: assignment makes pointer from integer without a cast /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:251: error: 'EVP_PKEY' has no member named 'ameth' /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:253: error: 'EVP_PKEY' has no member named 'ameth' /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:273: error: 'EVP_MD_FLAG_PKEY_METHOD_SIGNATURE' undeclared (first use in this function) /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:273: error: (Each undeclared identifier is reported only once /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:273: error: for each function it appears in.) /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:275: error: 'EVP_PKEY' has no member named 'ameth' /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:278: error: 'EVP_PKEY' has no member named 'ameth' /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:288: error: 'EVP_PKEY' has no member named 'ameth' /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c:288: error: 'ASN1_PKEY_SIGPARAM_NULL' undeclared (first use in this function) *** [a_sign.o] Error code 1 Stop in /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto. *** [secure/lib/libcrypto__L] Error code 1 Stop in /usr/home/luigi/FreeBSD/head. *** [libraries] Error code 1 Stop in /usr/home/luigi/FreeBSD/head. *** [_libraries] Error code 1 Stop in /usr/home/luigi/FreeBSD/head. *** [toolchain] Error code 1 Stop in /usr/home/luigi/FreeBSD/head. -- and happens whether or not CLANG is used as a compiler, and on all version up to the current one (250266 as i write). Interestingly, the build works on a stable/9 host with only a slightly more recent world/kernel > uname -a FreeBSD bsd9b 9.1-STABLE FreeBSD 9.1-STABLE #0 r249364M: Thu Apr 11 18:29:30 CEST 2013 luigi@bsd9b:.../RELENG_9/sys/LUIGI amd64 This makes me think that the libraries are built using the headers installed on the host instead of those belonging to the source tree. Looking at the arguments to 'cc' above seems to confirm this. Any idea on how to fix this problem (which probably may affect cross builds in general) ? cheers luigi ___ 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"
clang static analyzer page: scripts
Hi, Im looking at the clang static analyzer page over at http://scan.freebsd.your.org/. Im thinking about setting up something similar to that for another project. Would it be possible to get a copy of the (buildbot ?) scripts that performs the scan-build's and generates the pages ? Thanks. Regards, John Smith. ___ 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 build error (header pollution ?) after 249958
On May 5, 2013, at 12:04, Luigi Rizzo wrote:
> Since svn 249959 (when NO_IDEA was removed) I cannot build HEAD on
> a somewhat recent stable/9 (see below; kernel and userland in sync)
>
> > uname -a
> FreeBSD bsd9 9.1-STABLE FreeBSD 9.1-STABLE #0 r248472:
> Tue Mar 19 08:36:09 CET 2013 luigi@bsd9:.../RELENG_9/sys/LUIGI
> amd64
>
> (note that head was unbuildable in general since 249972 because
> there were leftovers of the IDEA option around)
> The error occurs during the 'toolchain' target (actually, probably
> in the 'libraries' one) and it is the following:
>
> ---> [ remember the cflags below ]
> cc -O2 -pipe -DTERMIOS -DANSI_SOURCE
> -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl
> -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto
>
> -I/usr/home/luigi/FreeBSD/obj_head/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto
> -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_SSE2
> -DAES_ASM -DBSAES_ASM -DVPAES_ASM -DOPENSSL_BN_ASM_MONT
> -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM -DSHA1_ASM
> -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_ASM
> -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1
>
> -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp
>
> -I/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes
> -std=gnu89 -fstack-protector -Wno-pointer-sign -c
> /usr/home/luigi/FreeBSD/head/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c
> -o a_sign.o
...
> This makes me think that the libraries are built using the headers
> installed on the host instead of those belonging to the source tree.
> Looking at the arguments to 'cc' above seems to confirm this.
How come? If you are building stage 4.2 (libraries), you have already built
cross-tools, so the "cc" invoked above only uses headers from ${WORLDTMP}.
The -I options you show only point to either your source directory, or your
object directory:
-I/usr/home/luigi/FreeBSD/head/crypto/openssl
-I/usr/home/luigi/FreeBSD/head/crypto/openssl/crypto
-I/usr/home/luigi/FreeBSD/obj_head/usr/home/luigi/FreeBSD/head/secure/lib/libcrypto
-I/usr/home/luigi/FreeBSD/head/crypto/openssl/crypto/asn1
-I/usr/home/luigi/FreeBSD/head/crypto/openssl/crypto/evp
-I/usr/home/luigi/FreeBSD/head/crypto/openssl/crypto/modes
> Any idea on how to fix this problem (which probably may affect
> cross builds in general) ?
No idea, sorry. I have never seen this problem. I have even built very recent
head on 8.1-RELEASE and 7.3-RELEASE, with a few minor patches...
-Dimitry
___
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: files disappearing from ls on NFS
Looks like the problem is in the new NFS code - the old code does the right thing. I've still to try your patch... harti From: Rick Macklem [rmack...@uoguelph.ca] Sent: Sunday, May 05, 2013 12:49 AM To: Brandt, Hartmut Cc: curr...@freebsd.org Subject: Re: files disappearing from ls on NFS Hartmut Brandt wrote: > On Fri, 3 May 2013, Rick Macklem wrote: > > RM>Ok, if you succeed in isolating the commit, that would be great. > > Hmm. I'm somewhat stuck. clang from yesterday can't compile clang from > a > month ago... > > harti > Oh, and one other thing you can try is switching to the old client "mount -t oldnfs ...". rick > RM> > RM>rick > RM> > RM>> harti > RM>> > RM>> On Fri, 3 May 2013, Rick Macklem wrote: > RM>> > RM>> RM>Hartmut Brandt wrote: > RM>> RM>> Hi, > RM>> RM>> > RM>> RM>> I've updated one of my -current machines this week (previous > RM>> update > RM>> RM>> was in > RM>> RM>> february). Now I see a strange effect (it seems only on NFS > RM>> mounts): > RM>> RM>> ls or > RM>> RM>> even echo * will list only some files (strange enough the > first > RM>> files > RM>> RM>> from > RM>> RM>> the normal, alphabetically ordered list). If I change > something > RM>> in the > RM>> RM>> directory (delete a file or create a new one) for some time > the > RM>> RM>> complete > RM>> RM>> listing will appear but after sime time (seconds to a minute > or > RM>> so) > RM>> RM>> again > RM>> RM>> only part of the files is listed. > RM>> RM>> > RM>> RM>> A ktrace on ls /usr/src/lib/libc/gen shows that > getdirentries is > RM>> RM>> called > RM>> RM>> only once (returning 4096). For a full listing getdirentries > is > RM>> called > RM>> RM>> 5 > RM>> RM>> times with the last returning 0. > RM>> RM>> > RM>> RM>> I can still open files that are not listed if I know their > name, > RM>> RM>> though. > RM>> RM>> > RM>> RM>> The NFS server is a Windows 2008 server with an OpenText NFS > RM>> Server > RM>> RM>> which > RM>> RM>> works without problems to all the other FreeBSD machines. > RM>> RM>> > RM>> RM>> So what could that be? > RM>> RM>> > RM>> RM>Someone else reported missing files returned via "ls" > recently, > RM>> when > RM>> RM>they used a small readdirsize (below 8K). I haven't yet had a > RM>> change to try > RM>> RM>and reproduce it or do any snooping around. > RM>> RM> > RM>> RM>There haven't been any recent changes to readdir in the NFS > client, > RM>> RM>except a trivial one that adds a check for vnode type being > VDIR, > RM>> RM>so I don't see that it can be a recent NFS change. > RM>> RM> > RM>> RM>If you can increase the readdirsize, try that to see if it > avoids > RM>> RM>the problem. "nfsstat -m" shows you what the mount options end > up > RM>> RM>being after doing the mount. The server might be limiting the > RM>> readdirsize > RM>> RM>to 4K, so you should check, even if you specify a large value > for > RM>> RM>the mount. > RM>> RM> > RM>> RM>rick > RM>> RM> > RM>> RM>> Regards, > RM>> RM>> harti > RM>> RM>> ___ > RM>> RM>> freebsd-current@freebsd.org mailing list > RM>> RM>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > RM>> RM>> To unsubscribe, send any mail to > RM>> RM>> "freebsd-current-unsubscr...@freebsd.org" > RM>> RM> > RM>> ___ > RM>> freebsd-current@freebsd.org mailing list > RM>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > RM>> To unsubscribe, send any mail to > RM>> "freebsd-current-unsubscr...@freebsd.org" > RM> > ___ > 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-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: clang static analyzer page: scripts
On Sun, 2013-05-05 at 12:29:55 +0200, John Smith wrote: > Hi, > > > Im looking at the clang static analyzer page over at > http://scan.freebsd.your.org/. Im thinking about setting up something > similar to that for another project. Would it be possible to get a > copy of the (buildbot ?) scripts that performs the scan-build's and > generates the pages ? Committed to svn://svn.freebsd.org/base/user/uqs/scan-world as of r250268. I'm not sure they are a good basis for said project, however, seeing that they work hard to get individual sub-dirs builds, etc. If you can lump everything into one run, then it's as simple as 'scan-build make' and you get your HTML output. hth Uli ___ 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: clang static analyzer page: scripts
On Sun, May 5, 2013 at 2:26 PM, Ulrich Spörlein wrote: > > Committed to svn://svn.freebsd.org/base/user/uqs/scan-world as of > r250268. > Thanks. > > I'm not sure they are a good basis for said project, however, > Ill take a look at it. - John Smith. ___ 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: clang static analyzer page: scripts
On 5 May 2013, at 13:26, Ulrich Spörlein wrote: > If you can > lump everything into one run, then it's as simple as 'scan-build make' > and you get your HTML output. The most important thing is to remember to do a make clean. As scan-build just interposes itself in front of the compiler, it won't be run for anything that isn't compiled. David ___ 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: Installing new world failed (install -l)
Hack
INSTALL=/usr/obj/${TARGET}.${TARGET_ARCH}${SRC_PATH}/tmp/legacy/usr/bin/install
is working, but this conversation will become PR.
-- Eir Nym
On 30 April 2013 23:13, Brooks Davis wrote:
> On Tue, Apr 30, 2013 at 10:17:09PM +0400, Eir Nym wrote:
>> -- Eir Nym
>>
>>
>> On 29 April 2013 19:25, Brooks Davis wrote:
>> > On Sun, Apr 28, 2013 at 11:36:20PM +0400, Eir Nym wrote:
>> >> Since -l switch introduced into install(8), I can't build new FreeBSD
>> >> box at all.
>> >>
>> >> I do following command set to build new box: (http://eroese.org/mkw.sh)
>> >> 1) cd /usr/head/src && svn up
>> >> 2) make buildworld
>> >> 3) make DESTDIR=/path/to/directory hierarchy distrib-dirs distribution
>> >> installworld
>> >
>> > heriarchy and distrib-dirs are both pointless here AFACT.
>> >
>> >>
>> >> This worked for long time but after some point it had been broken. I
>> >> found only 20130425 in UPDATING about this, but installing mergemaster
>> >> gives nothing, obviously.
>> >> I can't compile new install(8) since I have old system like
>> >> FreeBSD-9-RELEASE (FreeBSD-CURRENT, r226748) and it doesn't have
>> >> needed functions.
>> >>
>> >> The tail of install log is below.
>> >>
>> >> .. (lines removed)
>> >> mtree -deU -f /usr/head/src/etc/mtree/BSD.sendmail.dist -p
>> >> /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/
>> >> ./var/spool/clientmqueue missing (created)
>> >> install -l s usr/src/sys
>> >> /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/sys
>> >> install: illegal option -- l
>> >> usage: install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
>> >>[-o owner] file1 file2
>> >>install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
>> >>[-o owner] file1 ... fileN directory
>> >>install -d [-v] [-g group] [-m mode] [-o owner] directory ...
>> >> *** [distrib-dirs] Error code 64
>> >
>> > Are you setting INSTALL= in make.conf, src.conf, etc?
>> >
>> > -- Brooks
>>
>> I don't set this option at all.
>> As far as I know I should not set it setting and I've tested with
>> clean environment (like __MAKE_CONF=/dev/null & SRCCONF=/dev/null).
>> The PATH should be different for cross-platform build as I do.
>> the correct install path is
>> ${MAKEOBJDIRPREFIX}/i386.i386/usr/head/src/tmp/legacy/usr/bin/install
>
> That's not the problem. I belive that the problem is that the hierarchy
> target is broken when called directly. As I mention above, it's also
> pointless. Just use installworld before distribution so installworld
> creates all the required directories rather than pre-creating them with
> hierarchy and distrib-dirs.
>
> -- Brooks
___
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: Audio Hints, T520?
On 04.05.2013 07:14, Sean Bruno wrote: Speaker/headphones working great on Current. Was trying to get the microphone working, but it seems to not quite be working. By "not" working, there is no audio detected when recording. Is there something in here that looks like a thing that I should adjust? http://people.freebsd.org/~sbruno/t520_sysctl_hdaa.txt Verbose dmesg would be easier to read, since the provided sysctl output is mostly the raw input data. I see there that your system has two microphones. Have you tried to select both (mic and monitor) in mixer? -- Alexander Motin ___ 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"
Problem with firewire disks with recent -CURRENT.
Tried upgrading one of my machines to -CURRENT yesterday and got the following panic when the sbp code did its probing of all the firewire devices: sbp0: on firewire0 sbp0: sbp_show_sdev_info: sbp0:0:0: ordered:1 type:14 EUI:00048304ee01f418 node: 1 speed:2 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:0 'DAT Optic Inc ' 'Master ' '40' sbp0: sbp_show_sdev_info: sbp0:0:1: ordered:1 type:14 EUI:00048304ee01f418 node: 1 speed:2 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:0:1 'DAT Optic Inc ' 'Master ' '40' sbp0: sbp_show_sdev_info: sbp0:1:0: ordered:1 type:1 EUI:00d080043f208713 node:0 speed:2 maxrec:8 sbp0: sbp_show_sdev_info: sbp0:1:0 'EXABYTE ' 'VXA-3a ' '000201' sbp1: on firewire1 panic: mutex sbp not owned at /usr/src/sys/cam/cam_xpt.c:4549 cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xff81fe6837f0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xff81fe6838a0 vpanic() at vpanic+0x126/frame 0xff81fe6838e0 panic() at panic+0x43/frame 0xff81fe683940 __mtx_assert() at __mtx_assert+0xc2/frame 0xff81fe683950 xpt_compile_path() at xpt_compile_path+0xa1/frame 0xff81fe6839a0 xpt_create_path() at xpt_create_path+0x5b/frame 0xff81fe6839f0 sbp_do_attach() at sbp_do_attach+0xe8/frame 0xff81fe683a30 fwohci_txd() at fwohci_txd+0x378/frame 0xff81fe683a90 fwohci_task_dma() at fwohci_task_dma+0x5d4/frame 0xff81fe683b30 taskqueue_run_locked() at taskqueue_run_locked+0xf0/frame 0xff81fe683b80 taskqueue_thread_loop() at taskqueue_thread_loop+0x9b/frame 0xff81fe683bb0 fork_exit() at fork_exit+0x84/frame 0xff81fe683bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xff81fe683bf0 --- trap 0, rip = 0, rsp = 0xff81fe683cb0, rbp = 0 --- (alas, it happened too early to get an actual core file, but dcons let me get the console data logged to another machine.) I'm guessing the recent changes to cam_xpt and friends in mid-April might be to blame... ___ 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 build error (header pollution ?) after 249958
On Sun, May 05, 2013 at 01:52:37PM +0200, Dimitry Andric wrote: > On May 5, 2013, at 12:04, Luigi Rizzo wrote: > > Since svn 249959 (when NO_IDEA was removed) I cannot build HEAD on > > a somewhat recent stable/9 (see below; kernel and userland in sync) >... > > Any idea on how to fix this problem (which probably may affect > > cross builds in general) ? > > No idea, sorry. I have never seen this problem. I have even built very > recent head on 8.1-RELEASE and 7.3-RELEASE, with a few minor patches... my bad, after further investigation it turns out that the checkout directory was spammed with some extra directories, which probably caused old copies of the headers to be installed. sorry for the noise luigi ___ 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: Audio Hints, T520?
On Sun, 2013-05-05 at 21:32 +0300, Alexander Motin wrote: > On 04.05.2013 07:14, Sean Bruno wrote: > > Speaker/headphones working great on Current. > > > > Was trying to get the microphone working, but it seems to not quite be > > working. > > > > By "not" working, there is no audio detected when recording. Is there > > something in here that looks like a thing that I should adjust? > > > > http://people.freebsd.org/~sbruno/t520_sysctl_hdaa.txt > > Verbose dmesg would be easier to read, since the provided sysctl output > is mostly the raw input data. I see there that your system has two > microphones. Have you tried to select both (mic and monitor) in mixer? > Yes. I've toggled both, but I see no difference. Zero input from on board microphone. http://people.freebsd.org/~sbruno/verbose_hdaac.txt Sean p.s. physically, there is no microphone jack on this machine. There is just the headphone jack. signature.asc Description: This is a digitally signed message part
Re: Audio Hints, T520?
On 5/5/2013 5:33 PM, Sean Bruno wrote: Yes. I've toggled both, but I see no difference. Zero input from on board microphone. http://people.freebsd.org/~sbruno/verbose_hdaac.txt Sean p.s. physically, there is no microphone jack on this machine. There is just the headphone jack. So, what were you using to test the microphone? ___ 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: Audio Hints, T520?
On Sun, 2013-05-05 at 17:54 -0500, Joshua Isom wrote: > On 5/5/2013 5:33 PM, Sean Bruno wrote: > > > > Yes. I've toggled both, but I see no difference. Zero input from on > > board microphone. > > > > http://people.freebsd.org/~sbruno/verbose_hdaac.txt > > > > Sean > > > > p.s. physically, there is no microphone jack on this machine. There is > > just the headphone jack. > > > > So, what were you using to test the microphone? > ___ I was using audacity. Should I try something else? Sean signature.asc Description: This is a digitally signed message part
Re: Audio Hints, T520?
On 5/5/2013 6:11 PM, Sean Bruno wrote: On Sun, 2013-05-05 at 17:54 -0500, Joshua Isom wrote: On 5/5/2013 5:33 PM, Sean Bruno wrote: Yes. I've toggled both, but I see no difference. Zero input from on board microphone. http://people.freebsd.org/~sbruno/verbose_hdaac.txt Sean p.s. physically, there is no microphone jack on this machine. There is just the headphone jack. So, what were you using to test the microphone? ___ I was using audacity. Should I try something else? Sean I meant what hardware? How's it connected? So far I think you've only focused on the software side. ___ 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: Audio Hints, T520?
On Sun, 2013-05-05 at 18:57 -0500, Joshua Isom wrote: > On 5/5/2013 6:11 PM, Sean Bruno wrote: > > On Sun, 2013-05-05 at 17:54 -0500, Joshua Isom wrote: > >> On 5/5/2013 5:33 PM, Sean Bruno wrote: > >>> > >>> Yes. I've toggled both, but I see no difference. Zero input from on > >>> board microphone. > >>> > >>> http://people.freebsd.org/~sbruno/verbose_hdaac.txt > >>> > >>> Sean > >>> > >>> p.s. physically, there is no microphone jack on this machine. There is > >>> just the headphone jack. > >>> > >> > >> So, what were you using to test the microphone? > >> ___ > > > > I was using audacity. Should I try something else? > > > > Sean > > > > I meant what hardware? How's it connected? So far I think you've only > focused on the software side. It's a laptop. On board microphone thingy. No wires required. :-) Sean signature.asc Description: This is a digitally signed message part
Re: Audio Hints, T520?
On 5/5/2013 7:03 PM, Sean Bruno wrote: On Sun, 2013-05-05 at 18:57 -0500, Joshua Isom wrote: On 5/5/2013 6:11 PM, Sean Bruno wrote: On Sun, 2013-05-05 at 17:54 -0500, Joshua Isom wrote: On 5/5/2013 5:33 PM, Sean Bruno wrote: Yes. I've toggled both, but I see no difference. Zero input from on board microphone. http://people.freebsd.org/~sbruno/verbose_hdaac.txt Sean p.s. physically, there is no microphone jack on this machine. There is just the headphone jack. So, what were you using to test the microphone? ___ I was using audacity. Should I try something else? Sean I meant what hardware? How's it connected? So far I think you've only focused on the software side. It's a laptop. On board microphone thingy. No wires required. :-) Sean Are you sure it's not a USB microphone? What do you get when you run `usbconfig list`? It's probably doubtful, since your keyboard could be PS/2 and manufacturers don't like change. Also, what's the output of `pciconf -lv` just for clarity? ___ 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: Audio Hints, T520?
On 04.05.2013 06:14, Sean Bruno wrote: Speaker/headphones working great on Current. Was trying to get the microphone working, but it seems to not quite be working. I got the same problem with my X220. Before the last Lenovo HDA quirk commits everything worked fine, but I had to set the default sound unit to 1. Now I do not need to set the sound unit, audio output works out of the box but recording does not work anymore. I fiddled with nid config but got bored after the fifth reboot. The behaviour changed at my last world build a month ago. I can supply dmesg or sysctl output if you want. Thanks Michael ___ 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: Audio Hints, T520?
On Mon, 2013-05-06 at 03:25 +0200, Michael Schmiedgen wrote: > On 04.05.2013 06:14, Sean Bruno wrote: > > Speaker/headphones working great on Current. > > > > Was trying to get the microphone working, but it seems to not quite be > > working. > > I got the same problem with my X220. Before the last Lenovo > HDA quirk commits everything worked fine, but I had to set > the default sound unit to 1. > Now I do not need to set the sound unit, audio output works > out of the box but recording does not work anymore. I fiddled > with nid config but got bored after the fifth reboot. > > The behaviour changed at my last world build a month ago. > > I can supply dmesg or sysctl output if you want. > > Thanks >Michael > Ok, this smells like a recent regression. Sean signature.asc Description: This is a digitally signed message part
Re: Audio Hints, T520?
On Sun, May 5, 2013 at 6:25 PM, Michael Schmiedgen wrote: > On 04.05.2013 06:14, Sean Bruno wrote: > >> Speaker/headphones working great on Current. >> >> Was trying to get the microphone working, but it seems to not quite be >> working. >> > > I got the same problem with my X220. Before the last Lenovo > HDA quirk commits everything worked fine, but I had to set > the default sound unit to 1. > Now I do not need to set the sound unit, audio output works > out of the box but recording does not work anymore. I fiddled > with nid config but got bored after the fifth reboot. > > The behaviour changed at my last world build a month ago. > > I can supply dmesg or sysctl output if you want. > > Thanks > Michael > > I have a T520. It has an internal mic. Not USB. It also has a standard headphone/mic jack. It works with a headset with a mic. It's a four contact jack: Left, right, mic, and common. A cell-phone headset will work fine. Have you tried the hints I supplied? They worked for me. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.com ___ 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: Audio Hints, T520?
On Sun, May 5, 2013 at 7:43 PM, Sean Bruno wrote: > On Mon, 2013-05-06 at 03:25 +0200, Michael Schmiedgen wrote: > > On 04.05.2013 06:14, Sean Bruno wrote: > > > Speaker/headphones working great on Current. > > > > > > Was trying to get the microphone working, but it seems to not quite be > > > working. > > > > I got the same problem with my X220. Before the last Lenovo > > HDA quirk commits everything worked fine, but I had to set > > the default sound unit to 1. > > Now I do not need to set the sound unit, audio output works > > out of the box but recording does not work anymore. I fiddled > > with nid config but got bored after the fifth reboot. > > > > The behaviour changed at my last world build a month ago. > > > > I can supply dmesg or sysctl output if you want. > > > > Thanks > >Michael > > > > Ok, this smells like a recent regression. > > Sean > Could be. I'm running 9-STABLE, not current, on my T520. I can only say that the hints I provided work fine on my T520 on 9-stable. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.com ___ 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: kernel panic with _autoload_ nvidia driver
On Sun, 2013-05-05 at 10:01 +0400, de...@stasyan.com wrote: > Hello ! > >This problems appears about 4-6 months ago after updating of -CURRENT host. > Unable to boot host with nvidia_load="YES" in loader.conf because panic. > But when nvidia driver loads manually via kldload, everything OK. > Nvidia driver version is 310.44 at this moment, but problem was and on > earlier version too. > [...] This problem is present much longer than 4 - 5 months and it is bugging me now for a while more frequently since FreeBSD uses CLANG, but it isn't only related to CLANG since I have had those problems even before with the legacy gcc (4.2). The crash occurs only when loading the nvidia.ko at a very early stage, as it is done with the loader.conf. i do not know exactly at which stage is crashed in my case, but it is always a gambling. You can easily circumvent this by loading the nvidia.ko kernel module at a very late stage via /etc/rc.conf.local with the entry: kld_list="nvidia" In my case, it is the only way to have the nvidia module loaded save and sound and it works for me since a couple of time for now. Regards, Oliver signature.asc Description: This is a digitally signed message part
RE: files disappearing from ls on NFS
Hi Rick,
the patch doesn't help. So how can I help to fix that? Of course, I can use the
work-around with oldnfs, but ...
harti
-Original Message-
From: Rick Macklem [mailto:rmack...@uoguelph.ca]
Sent: Saturday, May 04, 2013 11:33 PM
To: Brandt, Hartmut
Cc: curr...@freebsd.org; Andrzej Tobola
Subject: Re: files disappearing from ls on NFS
Hartmut Brandt wrote:
> On Fri, 3 May 2013, Rick Macklem wrote:
>
> RM>Ok, if you succeed in isolating the commit, that would be great.
>
> Hmm. I'm somewhat stuck. clang from yesterday can't compile clang from
> a month ago...
>
> harti
>
Oh well. You could try this patch (which is the one to fix readdir for union
mounts), since I can see that VOP_VPTOCNP() will also be broken without it. (I
can't see how that would break "ls", but it breaks __getcwd() and friends, so
maybe it can affect "ls" somehow?)
It's a cut/paste under windows, so I'm afraid the whitespace will be messed up,
but it's pretty simple to apply by hand.
Index: nfs_clvnops.c
===
--- nfs_clvnops.c(revision 249568)
+++ nfs_clvnops.c(working copy)
@@ -2221,6 +2221,7 @@
!NFS_TIMESPEC_COMPARE(&np->n_mtime,
&vattr.va_mtime)) {
mtx_unlock(&np->n_mtx);
NFSINCRGLOBAL(newnfsstats.direofcache_hits);
+*ap->a_eofflag = 1;
return (0);
} else
mtx_unlock(&np->n_mtx); @@ -2233,8 +2234,10 @@
tresid = uio->uio_resid;
error = ncl_bioread(vp, uio, 0, ap->a_cred);
-if (!error && uio->uio_resid == tresid)
+if (!error && uio->uio_resid == tresid) {
NFSINCRGLOBAL(newnfsstats.direofcache_misses);
+*ap->a_eofflag = 1;
+}
return (error);
}
I haven't yet succeeded in reproducing the problem, but will be poking at it
some more, rick
> RM>
> RM>rick
> RM>
> RM>> harti
> RM>>
> RM>> On Fri, 3 May 2013, Rick Macklem wrote:
> RM>>
> RM>> RM>Hartmut Brandt wrote:
> RM>> RM>> Hi,
> RM>> RM>>
> RM>> RM>> I've updated one of my -current machines this week (previous
> RM>> update
> RM>> RM>> was in
> RM>> RM>> february). Now I see a strange effect (it seems only on NFS
> RM>> mounts):
> RM>> RM>> ls or
> RM>> RM>> even echo * will list only some files (strange enough the
> first
> RM>> files
> RM>> RM>> from
> RM>> RM>> the normal, alphabetically ordered list). If I change
> something
> RM>> in the
> RM>> RM>> directory (delete a file or create a new one) for some time
> the
> RM>> RM>> complete
> RM>> RM>> listing will appear but after sime time (seconds to a minute
> or
> RM>> so)
> RM>> RM>> again
> RM>> RM>> only part of the files is listed.
> RM>> RM>>
> RM>> RM>> A ktrace on ls /usr/src/lib/libc/gen shows that
> getdirentries is
> RM>> RM>> called
> RM>> RM>> only once (returning 4096). For a full listing getdirentries
> is
> RM>> called
> RM>> RM>> 5
> RM>> RM>> times with the last returning 0.
> RM>> RM>>
> RM>> RM>> I can still open files that are not listed if I know their
> name,
> RM>> RM>> though.
> RM>> RM>>
> RM>> RM>> The NFS server is a Windows 2008 server with an OpenText NFS
> RM>> Server
> RM>> RM>> which
> RM>> RM>> works without problems to all the other FreeBSD machines.
> RM>> RM>>
> RM>> RM>> So what could that be?
> RM>> RM>>
> RM>> RM>Someone else reported missing files returned via "ls"
> recently,
> RM>> when
> RM>> RM>they used a small readdirsize (below 8K). I haven't yet had a
> RM>> change to try
> RM>> RM>and reproduce it or do any snooping around.
> RM>> RM>
> RM>> RM>There haven't been any recent changes to readdir in the NFS
> client,
> RM>> RM>except a trivial one that adds a check for vnode type being
> VDIR,
> RM>> RM>so I don't see that it can be a recent NFS change.
> RM>> RM>
> RM>> RM>If you can increase the readdirsize, try that to see if it
> avoids
> RM>> RM>the problem. "nfsstat -m" shows you what the mount options end
> up
> RM>> RM>being after doing the mount. The server might be limiting the
> RM>> readdirsize
> RM>> RM>to 4K, so you should check, even if you specify a large value
> for
> RM>> RM>the mount.
> RM>> RM>
> RM>> RM>rick
> RM>> RM>
> RM>> RM>> Regards,
> RM>> RM>> harti
> RM>> RM>> ___
> RM>> RM>> freebsd-current@freebsd.org mailing list
> RM>> RM>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> RM>> RM>> To unsubscribe, send any mail to
> RM>> RM>> "freebsd-current-unsubscr...@freebsd.org"
> RM>> RM>
> RM>> ___
> RM>> freebsd-current@freebsd.org mailing list
> RM>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> RM>> To unsubscribe, send any mail to
> RM>> "freebsd-current-unsubscr...@freebsd.org"
> RM>
> ___
x11/nvidia-driver-173 build failed on CURRENT
Any help is appreciated. base r250200 ports r317168 ===> Returning to build of nvidia-driver-173.14.35_2 ===> nvidia-driver-173.14.35_2 depends on shared library: GL.1 - found == ===> Cleaning for nvidia-driver-173.14.35_2 = == = ===> License NVIDIA accepted by the user ===> nvidia-driver-173.14.35_2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by nvidia-driver-173.14.35_2 for building == = ===> License NVIDIA accepted by the user ===> nvidia-driver-173.14.35_2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by nvidia-driver-173.14.35_2 for building => SHA256 Checksum OK for NVIDIA-FreeBSD-x86-173.14.35.tar.gz. == = ===> License NVIDIA accepted by the user ===> nvidia-driver-173.14.35_2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by nvidia-driver-173.14.35_2 for building ===> Extracting for nvidia-driver-173.14.35_2 => SHA256 Checksum OK for NVIDIA-FreeBSD-x86-173.14.35.tar.gz. == = ===> Patching for nvidia-driver-173.14.35_2 ===> Applying extra patch /usr/ports/x11/nvidia-driver-173/../nvidia-driver/files/legacy-patch-nvidia.lib.mk ===> Applying extra patch /usr/ports/x11/nvidia-driver-173/../nvidia-driver/files/security-patch-CVE-2012-4225 == = ===> nvidia-driver-173.14.35_2 depends on file: /usr/local/libdata/pkgconfig/xorg-server.pc - found ===> nvidia-driver-173.14.35_2 depends on shared library: m.3 - found ===> nvidia-driver-173.14.35_2 depends on shared library: GL.1 - found ===> Configuring for nvidia-driver-173.14.35_2 == = ===> Building for nvidia-driver-173.14.35_2 ===> src (all) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include x86 -> /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"173.14.35\" -D__KERNEL__ -DNVRM -UDEBUG -U_DEBUG -DNDEBUG -O -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/wrkdirs/usr/ports/x11/nvidia-driver-173/work/NVIDIA-FreeBSD-x86-173.14.35/src -I. -I@ -I@/contrib/altq -fno-common -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -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 -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -c nvidia_ctl.c cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"173.14.35\" -D__KERNEL__ -DNVRM -UDEBUG -U_DEBUG -DNDEBUG -O -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/wrkdirs/usr/ports/x11/nvidia-driver-173/work/NVIDIA-FreeBSD-x86-173.14.35/src -I. -I@ -I@/contrib/altq -fno-common -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -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 -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -c nvidia_dev.c cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"173.14.35\" -D__KERNEL__ -DNVRM -UDEBUG -U_DEBUG -DNDEBUG -O -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/wrkdirs/usr/ports/x11/nvidia-driver-173/work/NVIDIA-FreeBSD-x86-173.14.35/src -I. -I@ -I@/contrib/altq -fno-common -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -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
Re: Audio Hints, T520?
On 06.05.2013 05:43, Sean Bruno wrote: On Mon, 2013-05-06 at 03:25 +0200, Michael Schmiedgen wrote: On 04.05.2013 06:14, Sean Bruno wrote: Speaker/headphones working great on Current. Was trying to get the microphone working, but it seems to not quite be working. I got the same problem with my X220. Before the last Lenovo HDA quirk commits everything worked fine, but I had to set the default sound unit to 1. Now I do not need to set the sound unit, audio output works out of the box but recording does not work anymore. I fiddled with nid config but got bored after the fifth reboot. The behaviour changed at my last world build a month ago. I can supply dmesg or sysctl output if you want. Ok, this smells like a recent regression. From information provided by Sean I can't see why added quirk for playback may affect recording in any way. More likely I would guess that change from two playback pcm/dsp devices to one, while still having two record ones, made hw.snd.default_unit less usable (because there is no choice of output devices for it any more). Respective two input pcm/dsp device may require to be chosen manually in recording application. Or you can try additional hints to join both mics in one dsp/pcm device, provided by Kevin Oberman: hint.hdac.0.cad0.nid35.config="as=2" hint.hdac.0.cad0.nid27.config="as=2 seq=15" PS: When checking mixer, remember that there is separate mixer for every pcm/dsp device. Sean. you've provided output only for one. I guess that other (internal) microphone is on another pcm device/mixer. -- Alexander Motin ___ 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"
