[Bug 202650] got CAM status 0x50; fatal error, failed to attach to device
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202650 Bug ID: 202650 Summary: got CAM status 0x50; fatal error, failed to attach to device Product: Base System Version: 10.2-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: p5b2e9...@t-online.de When booting from a FreeBSD-RELEASE-10.2 i386 disc1 CDROM installation medium, these error messages show up: (cd0:ata0:0:0:0): READ(10), CDB: 28 00 00 04 cf 41 00 00 01 00 (cd0:ata0:0:0:0): CAM status: Auto-Sense Retrieval Failed (cd0:ata0:0:0:0): Error 5, Unretryable error (cd0:ata0:0:0:0): cddone: got error 0x5 back Trying to mount root from cd9660:/dev/iso9660/10_2_RELEASE_I386_CD (ro)... When booting from the harddisk no /dev/cd0 can be found. # dmesg | grep cd0 (cd0:ata0:0:0:0): got CAM status 0x50 (cd0:ata0:0:0:0): fatal error, failed to attach to device # camcontrol devlist at scbus0 target 0 lun 0 (ada0,pass0) at scbus2 target 0 lun 0 (pass1) >From a 10.2-RELEASE i386 disc1 verified and burned on a CDROM medium I can boot and run a fixit shell on the related box, but it shows no /dev/cd0 when booted from the harddisk. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 145183] watchdogd(8): it should be possible to not deactivate watchdog timer on shutdown
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=145183 Dmitry Marakasov changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress |Closed Assignee|freebsd-bugs@FreeBSD.org|i...@freebsd.org --- Comment #1 from Dmitry Marakasov --- Fixed by ian@ in r286947. Thanks! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202651] cpufreq no longer works in 10.2 on Intel D525MWV
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202651 Bug ID: 202651 Summary: cpufreq no longer works in 10.2 on Intel D525MWV Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: viktor.stuj...@gmail.com After updating from 10.1-RELENG (2014-12-07) to 10.2-RELEASE, I can no longer manage the CPU's frequency. kernel: Starting powerd. kernel: powerd: no cpufreq(4) support -- aborting: No such file or directory This is the consequence of sysctls 'dev.cpu.X.freq' and 'dev.cpu.X.freq_levels' not being registered, indicating a problem with the 'cpufreq' module. I built/installed a clean GENERIC kernel and all available modules, but the problem still persists. I tried setting sysctl debug.cpufreq.verbose=1, which according to sys/kern/kern_cpu.c activates CF_DEBUG() calls. But the message in cpufreq_attach(), that should say "cpufreq: initializing %s", does not show up. I don't know if this means that the module doesn't even try to load. Help would be appreciated. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202656] make(1) prerequisite not assigned to target if target has ./ prefix
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202656 Bug ID: 202656 Summary: make(1) prerequisite not assigned to target if target has ./ prefix Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: sdao...@yandex.com Makefile contains $(AMALGAM_TARGET) mime_types.o: mime_types.h make(1) produces == CC ./mime_types.c ./mime_types.c:95:10: fatal error: 'mime_types.h' file not found #include "mime_types.h" ^ 1 error generated. *** Error code 1 Stop. make[1]: stopped in /usr/home/sdaoden/usr/src/nail.git *** Error code 1 Stop. make: stopped in /usr/home/sdaoden/usr/src/nail.git == It works if i add a ./mime_types.o target. I guess a basename(3) should be added somewhere. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202182] /home missing for auto-UFS install (under UEFI) -- unable add non-root user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202182 Marcel Moolenaar changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|b...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
For you
for you Hello, My name is Sergey, I propose you cooperation. We are a creative company in the development and creation of unique products for decoration - to design buildings IDENTIKA.PRO. We''re specialized on decoration of shops, petrol station, cafe, fast food restaurants, and retail franchises.We are interested at long-term cooperation with you. We propose a good environment to work with partners.Examples of our work http :http://identika.pro/counter_link/counter.php?click=presentation_enI propose You to become our partner in your area.Let us know about your decision Examples of our work http :http://identika.pro/counter_link/counter.php?click=presentation_en Sergey TyshchenkoCEO | IDENTIKA.PROViber: +380505566965 | WhatsApp: +380505566965Skype: t.sergey.ms.tyshche...@identika.pro | www.identika.pro03040 | Golosiivskyi Ave. 70 | office 502 | Kiev ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 155163] [patch] Add Recursive Functionality to setfacl(1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155163 --- Comment #5 from cl...@clintarmstrong.net --- Is testing and work on this patch still in progress? The inability to recursively set ACLs on FreeBSD is quite an annoyance and I was going to open my own bug report on it when I found this one already open. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 155163] [patch] Add Recursive Functionality to setfacl(1)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155163 --- Comment #6 from Shawn Webb --- The patch I submitted in December of last year works well in HardenedBSD. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 181497] [kernel] [patch] Add ASLR feature to kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181497 chrysa...@chrysalisnet.org changed: What|Removed |Added CC||chrysa...@chrysalisnet.org --- Comment #12 from chrysa...@chrysalisnet.org --- any chance this can be backported to 9.x? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202659] rpcsec_gss has a 16-group limit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202659 Bug ID: 202659 Summary: rpcsec_gss has a 16-group limit Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: matthew.l.dai...@dartmouth.edu Created attachment 160354 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160354&action=edit Patch for svc_rpcsec_gss to switch from RPCAUTH_UNIXGIDS to NGROUPS System: FreeBSD freebsd-test 10.2-RELEASE FreeBSD 10.2-RELEASE #1: Fri Aug 21 11:12:07 EDT 2015 r...@freebsd-test.thayer.dartmouth.edu:/usr/obj/usr/src/sys/GENERIC_GSS amd64 I have observed this issue as far back as 9.1-RELEASE. Overview: The kernel code for svc_rpcsec_gss and the userspace code for gssd implement a 16-group limit for users. Steps to reproduce: The first step is to have a working FreeBSD nfs4 server tied into a kerberos infrastructure and exporting directories with one of the krb5 security flavors The FreeBSD nfs4 server requires a kernel built with: options KGSSAPI device crypto Here is the simple /etc/exports on the server: V4: /exports -sec=krb5:krb5i /exports -sec=krb5 Add a user to more than 16 groups on the nfs4 server: # groups testuser staff group1 group2 group3 group4 group5 group6 group7 group8 group9 group10 group11 group12 group13 group14 group15 group16 Set permissions on an exported directory for the 17th or higher group # ls -ld /exports/group16 drwxrwxr-x 2 root group16 3 Aug 21 13:08 /exports/group16 Try to access this directory as this user from a remote client # mount -t nfs4 -osec=krb5,nosuid freebsd-test:/ /mnt/exports $ touch /mnt/exports/group16/testfile touch: cannot touch `/mnt/exports/group16/testfile`: Permission denied Directories with permissions for the 16th and under groups work: server# ls -ld /exports/group15 drwxrwxr-x 2 root group15 3 Aug 21 10:29 /exports/group15 client$ touch /mnt/exports/group15/testfile client$ ls -al /mnt/exports/group15/testfile -rw-r--r-- 1 testuser group15 0 Aug 21 10:29 /mnt/exports/group15/testfile Problem description: This problem appears to come from defines in both sys/rpc/rpcsec_gss/svc_rpcsec_gss.c and usr.sbin/gssd/gssd.c In sys/rpc/rpcsec_gss/svc_rpcsec_gss.c, the group limit is defined using RPCAUTH_UNIXGIDS. It looks like this may have originally come from sys/fs/nfs/rpc2.h, but I don't think this is included by the code, so RPCAUTH_UNIXGIDS is defined locally. In usr.sbin/gssd/gssd.c, the group limit is defined using NGRPS. This comes ultimately from sys/rpc/auth_unix.h, which is included in gssd.c from sys/rpc/rpc.h. Proposed solution: In both cases, I would propose that this be fixed by using the NGROUPS definition from sys/sys/param.h instead of the existing definitions. This will not only lift the current 16-group limit, but allow the code to track future increases in this value. There was previously a buffer issue in gssd that prevented this increase, but this was fixed in May 2013 in base r250176. We have been running a production system (originally 9.1-RELEASE, upgraded to 9.3-RELEASE in March 2015) where I raised the limit in both svc_rpcsec_gss.c and gssd.c to 256 groups. This has been running since May 2013 without any problems. I have also tested these exact patches on a 10.2-RELEASE system, and experienced no problems in limited testing. Attached are my proposed patches. Please let me know if you have any questions or need any other information about these patches. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202659] rpcsec_gss has a 16-group limit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202659 --- Comment #1 from Matthew L. Dailey --- Created attachment 160355 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160355&action=edit Patch for gssd to switch from NGRPS to NGROUPS -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202147] default listen queue in casperd is too small for some applications
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202147 --- Comment #2 from l...@pix.net --- Works for my application(s) where I ran into this. We have already run into one case where bumping it to merely 16 was inadequate. SOMAXCONN is currently 64. I will revise the patch to do this - it might still be useful to have the command line option to override the queue length setting. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202147] default listen queue in casperd is too small for some applications
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202147 l...@pix.net changed: What|Removed |Added Attachment #159630|0 |1 is obsolete|| --- Comment #3 from l...@pix.net --- Created attachment 160359 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160359&action=edit updated patch, set queue length to SOMAXCONN -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202664] mergemaster as unprivileged user dumps master.passwd into /var/tmp/temproot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202664 Bug ID: 202664 Summary: mergemaster as unprivileged user dumps master.passwd into /var/tmp/temproot Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: jnbek1...@gmail.com I accidentally ran mergemaster -pv as a normal user instead of root and this is the output: ([J:0]jnbek@rtr10[~]% mergemaster -pv [08/25/15][19:39:56]) *** You have /usr/bin/less defined as your pager so we will use that *** The directory specified for the temporary root environment, /var/tmp/temproot, exists. This can be a security risk if untrusted users have access to the system. Use 'd' to delete the old /var/tmp/temproot and continue Use 't' to select a new temporary root directory Use 'e' to exit mergemaster Default is to use /var/tmp/temproot as is How should I deal with this? [Use the existing /var/tmp/temproot] d *** Deleting the old /var/tmp/temproot *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot *** Press the [Enter] or [Return] key to continue install: /var/tmp/temproot/etc/group: chown/chgrp: Operation not permitted *** FATAL ERROR: Cannot copy files to the temproot environment ([J:0]jnbek@rtr10[~]% ls -R /var/tmp/temproot [08/25/15][19:41:40]) etc/ /var/tmp/temproot/etc: master.passwd This seems to be a bad thing. It's a stock master.passwd file but I would think that mergemaster should fail before ever messing with this file in the first place unless the user is root. If a unprivileged user gets compromised on a system, this could be used for evil, although I'm not sure exactly how. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202664] mergemaster as unprivileged user dumps master.passwd into /var/tmp/temproot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202664 Chris Petrik changed: What|Removed |Added CC||ch...@bsdjunk.com --- Comment #1 from Chris Petrik --- I think it uses /usr/src/etc/* as base and then it diffs all that to the system etc, not the actual one installed in /etc/ so I don't think there's any threat. if you have a look at /usr/src/etc/ you will see a generic master.passwd which should be the same one youre looking at. a normal user has no access to /etc/master.passwd -rw--- 1 root wheel 2612 Aug 24 03:06 /etc/master.passwd -rw-r--r-- 1 root wheel 1640 Aug 18 12:26 /usr/src/etc/master.passwd -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202665] clang++ core dump during compile with invalid syntax
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202665 Bug ID: 202665 Summary: clang++ core dump during compile with invalid syntax Product: Base System Version: 10.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: ajcbowh...@gmail.com Created attachment 160365 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160365&action=edit attachments requested by error message clang++ dumps core on attached code, which is likely not legitimate C++, as I was experimenting with syntax. compiled with: clang++ -o M.exe Multidim.cpp -L/usr/local/lib -std=c++0x In the source, removal of parenthesis around (&group), in AddGroup parameter list, and (&s), in array declaration in main makes problem go away. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
