Re: Help debugging stable/10
On 24/03/2015 01:55, Shane Ambler wrote: On 25/12/2014 23:03, Andriy Gapon wrote: On 25/12/2014 11:29, Hans Petter Selasky wrote: The cam_sim_free() is stuck, blocking the rest of that controller from enumerating. It might look like a non-USB stack issue. MAV: Do you have some ideas where to start looking, now we have a dump? Any refcounts to check in particular? Apparently sim->refcount > 0. Not sure how to check who has the reference(s). Can anyone think of something I can try? To recap to save you going back through history - After running 9.0 - 9.2 for 3 years I upgraded to 10.1RC3 and started getting a locking issue, most new processes fail to start, top and ps failing being indicators, the most info I have got is a back trace using kgdb, there are 4 instances I got output from procstat -kk -a On several occasions I have found that after inserting a usb memstick the device failed to be created, leaving me unable to mount the filesystem without a restart. I then switched to stable/10 in hopes of a fix finding it's way in. The back traces I have been able to collect (and a dmesg) are listed at http://shaneware.biz/freebsddebugdata/ This is my everyday desktop machine. I am now running FreeBSD leader.local 10.1-STABLE FreeBSD 10.1-STABLE #11 r283839: Thu Jun 4 17:41:28 ACST 2015 root@leader.local:/usr/obj/usr/src/sys /GENERIC amd64 I can only say it appears to be getting worse, though I may just be getting sick of having to restart nearly every day. Lately it seems that the less I do the quicker it locks up. I have restarted twice this week and then let it sit while I have gone out, after returning I get maybe 10-15 mins then have to restart, one of them was less than an hour uptime. While running poudriere I have got past 1 day uptime but it locks up harder and I don't usually get a chance to record any data. -- FreeBSD - the place to B...Software Developing Shane Ambler ___ 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: Help debugging stable/10
On 06/17/15 09:24, Shane Ambler wrote: On 24/03/2015 01:55, Shane Ambler wrote: On 25/12/2014 23:03, Andriy Gapon wrote: On 25/12/2014 11:29, Hans Petter Selasky wrote: The cam_sim_free() is stuck, blocking the rest of that controller from enumerating. It might look like a non-USB stack issue. MAV: Do you have some ideas where to start looking, now we have a dump? Any refcounts to check in particular? Apparently sim->refcount > 0. Not sure how to check who has the reference(s). Can anyone think of something I can try? To recap to save you going back through history - After running 9.0 - 9.2 for 3 years I upgraded to 10.1RC3 and started getting a locking issue, most new processes fail to start, top and ps failing being indicators, the most info I have got is a back trace using kgdb, there are 4 instances I got output from procstat -kk -a On several occasions I have found that after inserting a usb memstick the device failed to be created, leaving me unable to mount the filesystem without a restart. I then switched to stable/10 in hopes of a fix finding it's way in. The back traces I have been able to collect (and a dmesg) are listed at http://shaneware.biz/freebsddebugdata/ This is my everyday desktop machine. I am now running FreeBSD leader.local 10.1-STABLE FreeBSD 10.1-STABLE #11 r283839: Thu Jun 4 17:41:28 ACST 2015 root@leader.local:/usr/obj/usr/src/sys /GENERIC amd64 I can only say it appears to be getting worse, though I may just be getting sick of having to restart nearly every day. Lately it seems that the less I do the quicker it locks up. I have restarted twice this week and then let it sit while I have gone out, after returning I get maybe 10-15 mins then have to restart, one of them was less than an hour uptime. While running poudriere I have got past 1 day uptime but it locks up harder and I don't usually get a chance to record any data. Hi, One solution is to use fuse instead of the native fs, until the CAM/SCSI refcount issues are resolved. --HPS ___ 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: Getting going with a new Dell 7810
On Tue, 16 Jun 2015 22:29:48 +0200, Richard Kuhns wrote: On 06/16/15 15:58, John Nielsen wrote: On Jun 16, 2015, at 12:39 PM, Ronald Klop wrote: What does 'sysctl kern.vty' say? If it is not 'vt', you need the following stuff. /boot/loader.conf should contain kern.vty="vt" And /etc/rc.conf kld_list="radeonkms" Or something similar. FreeBSD is in the transition of old-style syscons- and vt-terminal. The last one has support for modern KMS graphics, but is not the default on 10 yet. With UEFI boot it will be using vt but with the efifb driver by default. Hopefully loading the radeon KMS driver (as Ronald suggests above) will let it take over. Try it with just a “kldload radeonkms” before adding it to rc.conf, just in case something gets wedged.. As you said, it is using vt. Unfortunately loading radeonkms didn't help. It actually seems to be a regression; the only RADEON line /var/log/Xorg.0.log now is the one that lists all the supported chipsets. Immediately after that line it ends with [ 4005.835] (II) VESA: driver for VESA chipsets: vesa [ 4005.835] (++) Using config file: "/home/rjk/xorg.conf.new" [ 4005.836] (==) ServerLayout "X.org Configured" [ 4005.836] (**) |-->Screen "Screen0" (0) [ 4005.836] (**) | |-->Monitor "Monitor0" [ 4005.836] (**) | |-->Device "Card0" [ 4005.836] (**) |-->Screen "Screen1" (1) [ 4005.836] (**) | |-->Monitor "Monitor1" [ 4005.836] (**) | |-->Device "Card1" [ 4005.836] (**) |-->Input Device "Mouse0" [ 4005.836] (**) |-->Input Device "Keyboard0" [ 4005.836] (==) Automatically adding devices [ 4005.836] (==) Automatically enabling devices [ 4005.836] (==) Not automatically adding GPU devices [ 4005.836] (**) FontPath set to: /usr/local/share/fonts/misc/, /usr/local/share/fonts/TTF/, /usr/local/share/fonts/OTF/, /usr/local/share/fonts/Type1/, /usr/local/share/fonts/100dpi/, /usr/local/share/fonts/75dpi/, /usr/local/share/fonts/misc/, /usr/local/share/fonts/TTF/, /usr/local/share/fonts/OTF/, /usr/local/share/fonts/Type1/, /usr/local/share/fonts/100dpi/, /usr/local/share/fonts/75dpi/ [ 4005.836] (**) ModulePath set to "/usr/local/lib/xorg/modules" [ 4005.836] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 4005.836] (WW) Disabling Mouse0 [ 4005.836] (WW) Disabling Keyboard0 [ 4005.836] (II) [KMS] Kernel modesetting enabled. [ 4005.836] (WW) Falling back to old probe method for vesa [ 4005.836] Number of created screens does not match number of detected devices. Configuration failed. [ 4005.836] (EE) Server terminated with error (2). Closing log file. I noticed in the previous log that it said [ 1292.463] (--) Using syscons driver with X support (version 2.0) which made me think I had something set up incorrectly, since it's using vt, not syscons. Hi, I don't know about the other issues, but can confirm that my Xorg.0.log also says syscons here while I'm using vt. That is normal. Regards, Ronald. On Tue, 16 Jun 2015 18:55:10 +0200, Richard Kuhns wrote: Greetings all, I've just received a new Dell Precision 7810. I've installed FreeBSD 10.1 (UEFI boot), checked out sources, built world & kernel and am now running r284449. So far, so good. The problem is Xorg. I'm running the latest Xorg in ports; I just did a 'make install clean' in /usr/ports/x11/xorg with no errors. The display card is a FirePro W4100. lspci shows: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] It has 4 DisplayPorts, and I have 2 monitors plugged in. If I run 'Xorg -configure' it says Number of created screens does not match number of detected devices. Configuration failed. Looking through /var/log/Xorg.0.log it appears that the X server is trying to use the RADEON driver, but ends with: = [ 1292.463] (--) Using syscons driver with X support (version 2.0) [ 1292.463] (--) using VT number 9 [ 1292.485] (II) [KMS] Kernel modesetting enabled. [ 1292.485] (WW) Falling back to old probe method for vesa [ 1292.485] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 1292.485] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 1292.485] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 1292.485] (==) RADEON(0): Default visual is TrueColor [ 1292.485] (==) RADEON(0): RGB weight 888 [ 1292.485] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 1292.485] (--) RADEON(0): Chipset: "VERDE" (ChipID = 0x682c) [ 1292.579] (EE) RADEON(0): [drm] Failed to open DRM device for pci::03:00.0: No such file or directory [ 1292.579] (EE) RADEON(0): Kernel modesetting setup failed [ 1292.579] (II) UnloadModule: "radeon" [ 1292.579] (EE) Screen(s) found, but none have a usable configuration. [ 1292.579] (EE) Fatal server error: [ 1292.579] (EE) no screens
Re: Getting going with a new Dell 7810
On 06/16/2015 12:55, Richard Kuhns wrote: > Greetings all, > > I've just received a new Dell Precision 7810. I've installed FreeBSD > 10.1 (UEFI boot), checked out sources, built world & kernel and am now > running r284449. So far, so good. > > The problem is Xorg. I'm running the latest Xorg in ports; I just did a > 'make install clean' in /usr/ports/x11/xorg with no errors. > > The display card is a FirePro W4100. lspci shows: > > 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Cape Verde GL [FirePro W4100] > If it is brand new, it is probably not supported and probably won't be for a while. Please see https://wiki.freebsd.org/Graphics for a list of devices which does include your Radeon HD 4670. ___ 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: Getting going with a new Dell 7810
You would be more likely to get good feedback on Xorg issues by sending them to x11@. X is not a part of stable or any base system. It i a group of ports and the issues with it are often very esoteric. This is just not the best place to find expertise on them. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com On Wed, Jun 17, 2015 at 8:43 AM, Adam McDougall wrote: > On 06/16/2015 12:55, Richard Kuhns wrote: > > Greetings all, > > > > I've just received a new Dell Precision 7810. I've installed FreeBSD > > 10.1 (UEFI boot), checked out sources, built world & kernel and am now > > running r284449. So far, so good. > > > > The problem is Xorg. I'm running the latest Xorg in ports; I just did a > > 'make install clean' in /usr/ports/x11/xorg with no errors. > > > > The display card is a FirePro W4100. lspci shows: > > > > 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > > [AMD/ATI] Cape Verde GL [FirePro W4100] > > > > If it is brand new, it is probably not supported and probably won't be > for a while. Please see https://wiki.freebsd.org/Graphics for a list of > devices which does include your Radeon HD 4670. > ___ > 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" > ___ 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"
building -stable after FreeBSD-SA-15:10.openssl
Hello All, Trying to upgrade from r283863 to 284520 after I applied this patch: https://www.freebsd.org/security/advisories/FreeBSD-SA-15:10.openssl.asc In the manner described: # fetch https://security.FreeBSD.org/patches/SA-15:10/openssl-10.1.patch # cd /usr/src # patch < /path/to/patch I begin the build by doing: cd /usr/src svn update make -j `sysctl -n hw.ncpu` buildworld -DNO_CLEAN But then this happened: Removing stale symlinks. rm -f /usr/obj/usr/src/tmp/usr/include/des.h rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.a rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.so rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.so.3 rm -f /usr/obj/usr/src/tmp/usr/lib/libdes_p.a ===> lib/libldns (obj,depend,all,install) sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libldns.a /usr/obj/usr/src/tmp/usr/lib/private sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libldns.so.5 /usr/obj/usr/src/tmp/usr/lib/private sh /usr/src/tools/install.sh -l s libldns.so.5 /usr/obj/usr/src/tmp/usr/lib/private/libldns.so ===> secure/lib/libssl (obj,depend,all,install) cc -fpic -DPIC -O2 -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libssl/../../../crypto/openssl -I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/libssl -DOPENSSL_THREADS -DDSO_DLFCN -DH$ /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:3371:9: error: redefinition of 'al' int al = SSL_AD_HANDSHAKE_FAILURE; ^ /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:3276:9: note: previous definition is here int al = SSL_AD_HANDSHAKE_FAILURE; ^ 1 error generated. *** [s3_clnt.So] Error code 1 make[4]: stopped in /usr/src/secure/lib/libssl 1 error make[4]: stopped in /usr/src/secure/lib/libssl A failure has been detected in another branch of the parallel make make[3]: stopped in /usr/src *** [libraries] Error code 2 make[2]: stopped in /usr/src 1 error make[2]: stopped in /usr/src *** [_libraries] Error code 2 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [buildworld] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src My patch happened to be in /usr/src when I applied it. Is this what caused the issue? Is there a way to revert the patch? Thanks & Best, jungle -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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: building -stable after FreeBSD-SA-15:10.openssl
On Wed, Jun 17, 2015 at 9:14 PM, jungle Boogie wrote: > Hello All, > > Trying to upgrade from r283863 to 284520 after I applied this patch: > https://www.freebsd.org/security/advisories/FreeBSD-SA-15:10.openssl.asc > > In the manner described: > > # fetch https://security.FreeBSD.org/patches/SA-15:10/openssl-10.1.patch > # cd /usr/src > # patch < /path/to/patch > > > I begin the build by doing: > cd /usr/src > svn update > make -j `sysctl -n hw.ncpu` buildworld -DNO_CLEAN > > But then this happened: > > Removing stale symlinks. > rm -f /usr/obj/usr/src/tmp/usr/include/des.h > rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.a > rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.so > rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.so.3 > rm -f /usr/obj/usr/src/tmp/usr/lib/libdes_p.a > ===> lib/libldns (obj,depend,all,install) > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libldns.a > /usr/obj/usr/src/tmp/usr/lib/private > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 > libldns.so.5 /usr/obj/usr/src/tmp/usr/lib/private > sh /usr/src/tools/install.sh -l s libldns.so.5 > /usr/obj/usr/src/tmp/usr/lib/private/libldns.so > ===> secure/lib/libssl (obj,depend,all,install) > cc -fpic -DPIC -O2 -pipe -DTERMIOS -DANSI_SOURCE > -I/usr/src/secure/lib/libssl/../../../crypto/openssl > -I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto > -I/usr/obj/usr/src/secure/lib/libssl -DOPENSSL_THREADS -DDSO_DLFCN > -DH$ > /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:3371:9: > error: redefinition of 'al' > int al = SSL_AD_HANDSHAKE_FAILURE; > ^ > /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:3276:9: > note: previous definition is here > int al = SSL_AD_HANDSHAKE_FAILURE; > ^ > 1 error generated. > *** [s3_clnt.So] Error code 1 > > make[4]: stopped in /usr/src/secure/lib/libssl > 1 error > > make[4]: stopped in /usr/src/secure/lib/libssl > A failure has been detected in another branch of the parallel make > > make[3]: stopped in /usr/src > *** [libraries] Error code 2 > > make[2]: stopped in /usr/src > 1 error > > make[2]: stopped in /usr/src > *** [_libraries] Error code 2 > > make[1]: stopped in /usr/src > 1 error > > make[1]: stopped in /usr/src > *** [buildworld] Error code 2 > > make: stopped in /usr/src > 1 error > > make: stopped in /usr/src > > > > My patch happened to be in /usr/src when I applied it. Is this what > caused the issue? > > Is there a way to revert the patch? > > > Thanks & Best, > jungle > > -- > --- > inum: 883510009027723 > sip: jungleboo...@sip2sip.info > xmpp: jungle-boo...@jit.si Don't use the patch at all if you're following stable/10, the necessary security fixes are already included in updates you pull in from SVN. You can revert all local changes with 'svnlite revert -R .' in /usr/src, might take a while for it to finish though. -Kimmo ___ 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: building -stable after FreeBSD-SA-15:10.openssl
On 17 June 2015 at 11:23, Kimmo Paasiala wrote: > Don't use the patch at all if you're following stable/10, the > necessary security fixes are already included in updates you pull in > from SVN. Oh, so in the future, just svn up and rebuild? Thanks for the tip on reverting, I'll try that out. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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: building -stable after FreeBSD-SA-15:10.openssl
On Wed, Jun 17, 2015 at 9:36 PM, jungle Boogie wrote: > On 17 June 2015 at 11:23, Kimmo Paasiala wrote: >> Don't use the patch at all if you're following stable/10, the >> necessary security fixes are already included in updates you pull in >> from SVN. > > > Oh, so in the future, just svn up and rebuild? > Exactly. -Kimmo ___ 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: Getting going with a new Dell 7810
On 06/17/15 11:43, Adam McDougall wrote: > On 06/16/2015 12:55, Richard Kuhns wrote: >> Greetings all, >> >> I've just received a new Dell Precision 7810. I've installed FreeBSD >> 10.1 (UEFI boot), checked out sources, built world & kernel and am now >> running r284449. So far, so good. >> >> The problem is Xorg. I'm running the latest Xorg in ports; I just did a >> 'make install clean' in /usr/ports/x11/xorg with no errors. >> >> The display card is a FirePro W4100. lspci shows: >> >> 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. >> [AMD/ATI] Cape Verde GL [FirePro W4100] >> > > If it is brand new, it is probably not supported and probably won't be > for a while. Please see https://wiki.freebsd.org/Graphics for a list of > devices which does include your Radeon HD 4670. That's what I was afraid of. I was hoping that the message that it was using syscons when my machine was using vt had something to do with it, but based on a couple of other messages that isn't the case. Thanks! -- Richard Kuhns Main Number: 765-742-8428 Wintek Corporation Direct: 765-269-8541 427 N 6th Street Internet Support: 765-269-8503 Lafayette, IN 47901-2211 Consulting: 765-269-8504 ___ 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: Help debugging stable/10
On 17/06/2015 17:22, Hans Petter Selasky wrote: On 06/17/15 09:24, Shane Ambler wrote: On 24/03/2015 01:55, Shane Ambler wrote: On 25/12/2014 23:03, Andriy Gapon wrote: On 25/12/2014 11:29, Hans Petter Selasky wrote: The cam_sim_free() is stuck, blocking the rest of that controller from enumerating. It might look like a non-USB stack issue. MAV: Do you have some ideas where to start looking, now we have a dump? Any refcounts to check in particular? Apparently sim->refcount > 0. Not sure how to check who has the reference(s). Can anyone think of something I can try? To recap to save you going back through history - After running 9.0 - 9.2 for 3 years I upgraded to 10.1RC3 and started getting a locking issue, most new processes fail to start, top and ps failing being indicators, the most info I have got is a back trace using kgdb, there are 4 instances I got output from procstat -kk -a On several occasions I have found that after inserting a usb memstick the device failed to be created, leaving me unable to mount the filesystem without a restart. I then switched to stable/10 in hopes of a fix finding it's way in. The back traces I have been able to collect (and a dmesg) are listed at http://shaneware.biz/freebsddebugdata/ This is my everyday desktop machine. I am now running FreeBSD leader.local 10.1-STABLE FreeBSD 10.1-STABLE #11 r283839: Thu Jun 4 17:41:28 ACST 2015 root@leader.local:/usr/obj/usr/src/sys /GENERIC amd64 I can only say it appears to be getting worse, though I may just be getting sick of having to restart nearly every day. Lately it seems that the less I do the quicker it locks up. I have restarted twice this week and then let it sit while I have gone out, after returning I get maybe 10-15 mins then have to restart, one of them was less than an hour uptime. While running poudriere I have got past 1 day uptime but it locks up harder and I don't usually get a chance to record any data. Hi, One solution is to use fuse instead of the native fs, until the CAM/SCSI refcount issues are resolved. --HPS If you refer to the usb stick, it locks up without inserting one. I'll try with the extra fs kmods unloaded and see how it goes. -- FreeBSD - the place to B...Software Developing Shane Ambler ___ 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"
