[Bug 206227] [patch] Teach mx25l SPI flash driver to interact with fdt_slicer and geom_flashmap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206227 Bug ID: 206227 Summary: [patch] Teach mx25l SPI flash driver to interact with fdt_slicer and geom_flashmap Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: sgala...@gmail.com Keywords: patch Created attachment 165546 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165546&action=edit Teach mx25l SPI flash driver to interact with fdt_slicer and geom_flashmap The attached patch teaches the mx25l driver (sys/dev/flash/mx25l.c) to interact with sys/dev/fdt/fdt_slicer.c and sys/geom/geom_flashmap.c. This allows systems with SPI flash to benefit from the possibility to define flash 'slices' via FDT, just the same way that it's currently possible for CFI and NAND flashes. -- 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 206228] [patch] Add fdt_reset based on the fdt_clock implementation
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206228 Bug ID: 206228 Summary: [patch] Add fdt_reset based on the fdt_clock implementation Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: sgala...@gmail.com Keywords: patch Created attachment 165547 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165547&action=edit Add fdt_reset based on fdt_clock The attached patch adds fdt_reset functionality in much the same way as the sys/dev/fdt/fdt_clock* functionality by ian@. Basically, a driver that provides reset controller functionality (provider) to other drivers (consumers), can (un)register itself by calling fdt_reset_(un)register_provider. Once registered, consumers can simply call fdt_reset_(de)assert_all(consumer), where consumer is the consumer's device_t in order to get their associated resets (de)asserted. -- 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 202290] /usr/bin/vi conversion error on valid character
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202290 Kubilay Kocak changed: What|Removed |Added Keywords|needs-patch |easy -- 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 206230] dc(1) bugs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206230 Bug ID: 206230 Summary: dc(1) bugs Product: Base System Version: 9.3-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: nibb...@gmx.us CC: freebsd-i...@freebsd.org CC: freebsd-i...@freebsd.org FreeBSD-9.3 dc(1) # FIRST # $ dc -xe '50k16o16i.1vp' 0 $ dc -xe '50k10o16i.1vp' 0 $ dc -xe '50k10o10i.1vp' [0].31622776601683793319988935444327185337195551393252 This should be telling dc(1): a) scale is 50 (in decimal) digits. b) output in base16, base10, and base10 respectively. c) input will be in base16, base16, and base10 respectively. d) take the square root, and print it to the display. Of course, the 3rd example above is correct, but the first 2? Why 0? ## SECOND ## $ dc -xe '50k16o16i.4 2^p' [0].0A $ dc -xe '50k16o16i.0Avp' [0].2C572B0D5A1443EC508B9E24D8DF392750959EE138 This should be telling dc(1): a) scale is 50 (in decimal) digits. b) output in base16, input is now base16. c) square "0.4", and print it to the display (result=0.0A). d) take the square-root of "0.0A", and print it to the display. Of course, the square-root of a squared number should result in the orginal number. But, this is not happening. # THIRD # $ dc -xe '50k16o16i.4 2^p' [0].0A $ dc -xe '50k16o16i.40 2^p' [0].1000 $ dc -xe '50k16o16i.400 2^p' [0].1 $ dc -xe '50k16o16i.4000 2^p' [0].100 dc(1) is supposed to be precise in the digits it calculates, but here? Something is not right about these results, or so it appears to me. ## FOURTH ## $ dc -xe '50k16o16i.1vp' 0 $ dc -xe '50k16o16i.10vp' [0].3EB4F9D9B6D094C33D38373D38777A7D9233A1B0FB $ dc -xe '50k16o16i.100vp' [0].3FBE55183CA5ADC8B39B27C6258E4C7E64338B909F $ dc -xe '50k16o16i.1000vp' [0].40 Checking the result of the THIRD example, dc(1) is not outputting to the scale specified, and despite having all a scale of 50, they are all giving different results with inputs having a scale of only 1/2/3/4; Something seems broken to me. -- GNU's dc(1) is broken too (reported to GNU bc maintainer also): Thanks! I really needed a calculator to do squares and square-roots of hexadecimal fractions, and I use FreeBSD, but their dc(1) is broken too ... http://lists.freebsd.org/pipermail/freebsd-questions/2016-January/26.html http://lists.freebsd.org/pipermail/freebsd-bugs/2016-January/065825.html I would assert scale is the number of fractional digits displayed regardless of any base. Why should anyone care about base10 or whatever other base the dc(1) author decided to assign as an across-the-board base for the scale value? That makes no sense at all for a user of dc(1). Scale is the number of fractional digits the dc(1) user wants, not what the author of dc(1) decided secretly for everybody. I don't think it was ever intended to be the "base10" fractional digits only, or whatever other scale was used "behind the scenes". Scale is a "user demand" for the result, IMHO. A modern computer should have a working calculator - at least, I think so. Thank you so much for your reply, I have some encryption-related software that depends on it. > On Tuesday 12 January 2016 23:05:41: > > > dc (GNU bc 1.06.95) 1.3.95 > > > > $ dc -e '50k16o16i.4vp' > > [0].727C9716FFB764D594A519C0252BE9AE6D00DC9192 > > > > This is not a 50-digit scale. > > It is a 50 digit scale base 10 which is of course shorter base 16. > > > $ dc -e '50k16o16i.727C9716FFB764D594A519C0252BE9AE6D00DC9192 2^p' > > [0].3325CC2DCA > > > > This is not even close to being the original number: 0.4. > > This appears to be true. I'll investigate why the algorithm is wrong. -- 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 206231] [net] [patch] ipv6 address on stf(4) interface "tentative" indefinitely
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206231 Bug ID: 206231 Summary: [net] [patch] ipv6 address on stf(4) interface "tentative" indefinitely Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: d...@neosystem.org Keywords: patch Created attachment 165549 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165549&action=edit Fix DAD for stf(4) Modifications to DAD code - r287734 (MFC of r287094) and r290348 (MFC of r288600) - rendered 6to4 connectivity non-working. Address assigned to an stf(4) interface stays "tentative" indefinitely. Attached patch fixes that. -- 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 206231] [net] [patch] ipv6 address on stf(4) interface "tentative" indefinitely
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206231 Kurt Jaeger changed: What|Removed |Added CC||p...@freebsd.org --- Comment #1 from Kurt Jaeger --- see https://lists.freebsd.org/pipermail/freebsd-stable/2015-December/083856.html and https://lists.freebsd.org/pipermail/freebsd-stable/2016-January/083951.html -- 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 206238] FUSE can't enter to DIRECT_IO mode during file create.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206238 Bug ID: 206238 Summary: FUSE can't enter to DIRECT_IO mode during file create. Product: Base System Version: 10.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: free...@moosefs.com CC: freebsd-am...@freebsd.org CC: freebsd-am...@freebsd.org When we want to use direct IO flag it's mostly working ok. But in very specific situation still uses cache omitting DIRECT FLAG. This situation appears only when we are creating file. We suspect that this problem is connected with function: fuse_vnode_open(vp, 0, td) in /usr/src/sys/fs/fuse/fuse_fnops.c file. The second parameter of this function is always set to 0 value and in some cases removing DIRECT flag set by other functions. -- 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 206192] ls -R warns about EACCES on directories it's not going to list anyway
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206192 --- Comment #1 from nibb...@gmx.us --- On 9.3, notice that something similar affects rm(1): $ mkdir aaa; cd aaa; mkdir .bbb; chmod 0077 .bbb $ cd ..; rm -r aaa override ---rwxrwx user/wheel for aaa/.bbb? y rm: aaa/.bbb: Permission denied rm: aaa: Directory not empty I don't know all the rules, but this seems wrong also. The user was a member of group wheel, and all have rwx permissions, and it would seem that they ought to be able to remove the directory; alternatively, perhaps the permissions are hierarchial in nature, and a lower class user can't do what a higher class user can't do. Just thought it may be a worthy comment. -- 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 205932] [panic] Kernel panic when copying from ext2fs partition to UFS partition
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205932 --- Comment #18 from Torfinn Ingolfsen --- (In reply to Damjan Jovanovic from comment #17) You are correct. I implemented the patch from Bug 205938, and when I copy files from a read-only mounted ext4 now, it works - no crashes. 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 206274] Segfault with the new 64bit linux_compatibility
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206274 Bug ID: 206274 Summary: Segfault with the new 64bit linux_compatibility Product: Base System Version: 10.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: steru...@gmail.com CC: freebsd-am...@freebsd.org CC: freebsd-am...@freebsd.org Created attachment 165603 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165603&action=edit Output of ktrace / kdump When trying to run the 64bit X-Plane installer it ends with a segfault. System is a 10.2-STABLE with the linux64.ko module loaded and the nvidia driver installed. 64bit libraries for the driver are in place. Now i have run ktrace / kdump. For the results see the attachment -- 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 206274] Segfault with the new 64bit linux_compatibility
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206274 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|emulat...@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"
[Bug 206238] FUSE can't enter to DIRECT_IO mode during file create.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206238 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd...@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"
[Bug 206231] [net] [patch] ipv6 address on stf(4) interface "tentative" indefinitely
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206231 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@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"
[Bug 206219] Kernel panic from lagg_ioctl and lagg_port_ioctl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206219 Mark Linimon changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org Keywords||patch -- 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 206224] bv_cnt is sometimes examined without holding the bufobj lock
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206224 Mark Linimon changed: What|Removed |Added Keywords||patch -- 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 204916] Add Quirks for Dell ChromeBook: Allows boot/run
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204916 Kubilay Kocak changed: What|Removed |Added Summary|quirks for dell chromebook |Add Quirks for Dell |[patch] |ChromeBook: Allows boot/run Keywords||easy, needs-qa Severity|Affects Only Me |Affects Some People Priority|--- |Normal -- 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 183618] [panic] Dell PowerEdge R620 -- PERC H710 Mini (mfi) freezes and panics (softdep_deallocate_dependencies)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183618 Kubilay Kocak changed: What|Removed |Added Keywords||crash, needs-qa Flags||mfc-stable9?, mfc-stable10? Summary|[panic][mfi] System on Dell |[panic] Dell PowerEdge R620 |PERC H710 Mini freezes and |-- PERC H710 Mini (mfi) |panics |freezes and panics ||(softdep_deallocate_depende ||ncies) -- 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 203746] Panic in NVME driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203746 Jim Harris changed: What|Removed |Added Status|New |In Progress Assignee|freebsd-bugs@FreeBSD.org|jimhar...@freebsd.org --- Comment #8 from Jim Harris --- Issue should be fixed with SVN r290198 - waiting for confirmation from submitter. -- 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"
