[Bug 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #2 from Bernhard Berger --- "reboot" does the same thing in name as "shutdown -p -now"! No, it doesn't, it doesn't call "/etc/rc.shutdown" and that's a big mistake in my eyes because the programmers of rc.d/scripts assume that their services which start with "# KEYWORD shutdown" are executed on shutdown (reboot is also a kind of shutdown). Please make sure that "reboot" executes the script "/etc/rc.shutdown". Many people will "not" read the manual for reboot because the name already says what it does. For me, the inexperienced use of "reboot" has led to some serious errors and I was very surprised about that. I will not use reboot any more until I am informed that it is running /etc/rc.shutdown because rebooting two different programs on the same system is unnecessary. Therefore I prefer to add the missing options in "shutdown". With kind regards translated from German to English with deepL -- 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 243106] [patch] jail(3): memory leak when resizing jail parameter list.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243106 Hans Christian Woithe changed: What|Removed |Added Summary|jail(3): memory leak when |[patch] jail(3): memory |resizing jail parameter |leak when resizing jail |list. |parameter list. -- 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 243116] Apple hardware with Realtek ALC889A no sound
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243116 Bug ID: 243116 Summary: Apple hardware with Realtek ALC889A no sound Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: j...@freebsd.org There appear to be several Mac models with this issue. I found a workaround using device hints here: https://forums.freebsd.org/threads/macbook-pro-5-1-realtek-alc889a-sound-setup.56061/ hint.hdaa.0.config="ovref" hint.hdaa.0.gpio_config="0=set" For headphone jack autoswitch: hint.hdaa.0.nid20.config="as=4 seq=15" Might it be possible to tweak the base to make these models work out of the box? I'm familiar with buildkern/buildworld in case either is necessary to test a fix. -- 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 243117] panic: keg dma coherent 32 initialization after use. (MIPS MALTA64)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243117 Bug ID: 243117 Summary: panic: keg dma coherent 32 initialization after use. (MIPS MALTA64) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: arichard...@freebsd.org With today's HEAD I get the following panic when booting a MALTA64 kernel on QEMU: Breakpoint 1, panic (fmt=0x80766a14 "keg %s initialization after use.") at /exports/users/alr48/sources/freebsd/sys/kern/kern_shutdown.c:835 835 vpanic(fmt, ap); (gdb) bt #0 panic (fmt=0x80766a14 "keg %s initialization after use.") at /exports/users/alr48/sources/freebsd/sys/kern/kern_shutdown.c:835 #1 0x8068a1f4 in uma_zone_set_allocf (zone=, allocf=0x8070a180 ) at /exports/users/alr48/sources/freebsd/sys/vm/uma_core.c:4265 #2 0x80709f68 in busdma_bufalloc_create (name=, minimum_alignment=, alloc_func=0x8070a180 , free_func=0x8070a1e0 , zcreate_flags=) at /exports/users/alr48/sources/freebsd/sys/kern/subr_busdma_bufalloc.c:110 #3 0x806e0678 in busdma_init (dummy=) at /exports/users/alr48/sources/freebsd/sys/mips/mips/busdma_machdep.c:246 #4 0x803a3f40 in mi_startup () at /exports/users/alr48/sources/freebsd/sys/kern/init_main.c:314 #5 0x80100388 in _locore () at /exports/users/alr48/sources/freebsd/sys/mips/mips/locore.S:201 -- 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 243117] panic: keg dma coherent 32 initialization after use. (MIPS MALTA64)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243117 Alex Richardson changed: What|Removed |Added CC||j...@freebsd.org --- Comment #1 from Alex Richardson --- Probably caused by https://reviews.freebsd.org/rS356348 ? -- 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 156920] isspecial(3) is not helpful
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156920 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #5 from Ed Maste --- (In reply to Yuri Pankov from comment #4) I wonder if we should request an exp-run with it removed, and just take it out if nothing in ports uses it either? -- 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 241531] autofs: stale entries remain in /media, "automount -c" does not remove them
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241531 Jason W. Bacon changed: What|Removed |Added CC||j...@freebsd.org --- Comment #5 from Jason W. Bacon --- I'm not sure if this is the same issue, but when inserting a media with the same device name as but a different filesystem than a previously mounted FS, it will not be detected. E.g. I have two USB sticks, one with FAT32 and volume ID "SONY8" and another with exFAT, both identified as /dev/da1s1. After accessing the FAT32 FS, the /media/SONY8 directory remains indefinitely and inserting the exFAT stick does not trigger creation of /media/da0s1. It seems a reboot is necessary to clear this condition. -- 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 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #3 from Mark Johnston --- (In reply to Bernhard Berger from comment #2) The point is that "reboot" has worked this way for a long time, and changing it will likely break existing workflows. So while it is unfortunate that "reboot" and "shutdown -r now" do not do the same thing, I don't think we can realistically change it. -- 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 236527] kbdmap won't set Swedish keymap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236527 --- Comment #3 from Ed Maste --- (In reply to Per Gunnarsson from comment #2) In other words, the issue is that shells/bash is not accepting accented characters? -- 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 243117] panic: keg dma coherent 32 initialization after use. (MIPS MALTA64)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243117 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #2 from Mark Johnston --- I think the issue is that the assertion checks the value of uz_allocs while it still points to EARLY_COUNTER, and so we get bogus values. -- 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 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #4 from Bernhard Berger --- (In reply to Mark Johnston from comment #3) Yes, there are four alternatives: 1. replace reboot with a script that executes "shutdown -r now 2. reboot to make sure that it restarts the system in accordance with the system 3. abandon reboot! What I'm going to do now! 4. switch to linux in the furture bye bye FreeBDS -- 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 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #5 from Conrad Meyer --- So AFAICT, this command isn't specified by POSIX; we're not constrained by a standard, just history. What Linux has done is make reboot more like 'shutdown', unless you specify "--force" (and maybe there is some weird semantics for --force --force, I didn't read the manual closely), it does a clean shutdown. I don't know if people would object strongly to 'reboot' => 'shutdown -r' like behavior, with 'reboot -f' or 'reboot --force' providing the old behavior. Probably. It's the kind of thing old FreeBSDers love to bikeshed about. :-( -- 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 156920] isspecial(3) is not helpful
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156920 --- Comment #6 from Conrad Meyer --- #define isspecial(c)__sbistype((c), _CTYPE_T) Whatever that means. @Ed, there are a host of other BSD-specific ctype.h extensions that could maybe be better defined, or removed: 127-#if __BSD_VISIBLE 128-#define digittoint(c) __sbmaskrune((c), 0xFF) 129-#define ishexnumber(c) __sbistype((c), _CTYPE_X) 130-#define isideogram(c) __sbistype((c), _CTYPE_I) 131-#define isnumber(c) __sbistype((c), _CTYPE_D|_CTYPE_N) 132-#define isphonogram(c) __sbistype((c), _CTYPE_Q) 133-#define isrune(c) __sbistype((c), 0xFF00L) (And keep in mind the corresponding wchar versions, 116-#if __BSD_VISIBLE 117-#define iswascii(wc)(((wc) & ~0x7F) == 0) 118-#define iswhexnumber(wc)__istype((wc), _CTYPE_X) /* alias of iswxdigit */ 119-#define iswideogram(wc) __istype((wc), _CTYPE_I) 120-#define iswnumber(wc) __istype((wc), _CTYPE_D|_CTYPE_N) 121-#define iswphonogram(wc)__istype((wc), _CTYPE_Q) 122-#define iswrune(wc) __istype((wc), 0xFF00L) 123:#define iswspecial(wc) __istype((wc), _CTYPE_T) ) There is a hardcoded ASCII table in lib/libc/locale/table.c that includes several characters marked as whitespace (_CTYPE_S) but zero references to _CTYPE_T. -- 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 156920] isspecial(3) is not helpful
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156920 --- Comment #7 from Conrad Meyer --- Similarly, share/ctypedef/C.UTF-8.src declares several classes (alpha, upper, lower, cntrl, digit, "graph", punct) but no "special." -- 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 156920] isspecial(3) is not helpful
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156920 --- Comment #8 from Conrad Meyer --- (This may be an artifact of tools/tools/locale/tools/utf8-rollup.pl, but it's unclear what was intended by isspecial(). Someone could do some CSRG archaeology to discover the original intent, but it seems defunct now.) -- 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 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #6 from Bernhard Berger --- (In reply to Conrad Meyer from comment #5) I am a user and use FreeBSD as a server system for a home server. What I really liked about FreeBSD was the ports system. Of course, between ports that are not part of the FreeBSD system, you have to evaluate differently than programs that are part of the system. A program that says what it does by name must also do exactly what it says by name. reboot System reboot shutdown -r now >>> System reboot reboot <<< do the same >>> shutdown -r now at least by all appearances. I found out by accident that reboot does not execute the script /etc/rc.shutdown(logs). And therefore not the service vm! VM's take a long time to shut down and are then simply shot down and I have always wondered about VM's being shot AFTER using reboot. Then I always manually stopped all VM#s before a reboot. Often the system got stuck and had to be rebooted by me via power off/on with anxious in my heart if everything will start well again. And as it looks it is reboot that caused all the trouble. I never expected such an error. But this is a big mistake, because basically "MUST" reboot does the same as shutdown -r now and this is because that's what the name "reboot" says. You should not ignore this problem. I am very disappointed ps: i am now thinking about switching to linux or windows. -- 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 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 Conrad Meyer changed: What|Removed |Added Severity|Affects Many People |Affects Some People Version|12.1-RELEASE|CURRENT --- Comment #7 from Conrad Meyer --- (In reply to Bernhard Berger from comment #4) > 4. switch to linux in the furture > bye bye FreeBDS (In reply to Bernhard Berger from comment #6) > ps: i am now thinking about switching to linux or windows. These are not useful ultimatums and in case you are under the mistaken impression otherwise, they are not magic incantations to give more credence to your proposal. If anything, it hurts the credibility of your otherwise good suggestion. If Linux or Windows would meet your needs better, solely because there is hesitation to change 40 years of historical behavior of the 'reboot(8)' command, that's totally fine. Use the right tool for the job; if it isn't FreeBSD for you, that's ok! The world is better with a diversity of operating systems and FreeBSD isn't and shouldn't always be the best option for all cases. Your theory on how naming programs governs their behavior and how similar programs MUST behave identically is certainly novel, but ultimately incorrect. Your best case for this change was already made in the bug description. -- 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"
Problem reports for b...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- In Progress |221973 | cam iosched: BIO_ZONE commands probably shouldn't In Progress |221974 | cam iosched: The iops limiter should enforce limi New |197876 | [devfs] an error in devfs leads to data loss and New |198797 | [PATCH] Added an option to install BSDstats to bs New |202362 | ntp: restore refclocks selection (10.2-RELEASE re New |202740 | vi/ex string substitution problem when there is m New |204097 | witness_initialize() does not perform bound check New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi New |209213 | UEFI Loader shows only black screen with Nvidia G New |210804 | installerconfig - using ZFS create in custom scri New |223470 | freebsd-update: Cannot identify running kernel (/ New |224436 | vt: CONS_CLRHIST (vidcontrol -C) not implemented New |230620 | "install -d" issue New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( Open| 71667 | [patch] cleanup of the usr.sbin/bootparamd code Open|182466 | [headers] [patch] make self-contained Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf Open|187015 | agpgart: Panic make_dev_credv: bad si_name (error Open|194925 | [pf] [ifconfig] interface group keywords do not w Open|197921 | scheduler: Allow non-migratable threads to bind t Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4) Open|207248 | [patch] daemon(8): Add option to redirect stdout Open|207940 | stand/efi/boot1: Add boot partition selection Open|212608 | sockstat(1) and lsof(8) can not identity the owne Open|220246 | syslogd does not send RFC3164-conformant messages Open|221305 | Mouse cursor loss when moving cursor while loadin Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL Open|221854 | makefs: Reject UFS labels that are too long to fi Open|222632 | connect(2) not available in capability mode Open|226893 | freebsd-update: Support patchlevel argument for f Open|231810 | [build] release always fails with "mkimg: partiti Open|233578 | Unprivileged local user can prevent other users l Open|233988 | freebsd-update: Improve progress output on termin Open|236718 | system panics with message: vm_fault_hold: fault Open|237271 | Radeon video card no longer works on 12-STABLE (a Open|237287 | moused(8) ignores button release events in virtua Open|237924 | Possible infinite loop in function empty_aux_buff Open|237981 | cxgb(4): Driver doesn't work with latest (7.12) C Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana Open|238486 | Possible buffer overflow bug in sc_allocate_keybo Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea Open|239976 | Integer Overflow: ping(8) option "-s", bypass the Open|239977 | Integer Overflow: ping(8) option "-G" and "-g", b Open|239978 | Integer Overflow: ping(8) option "-h", bypass the Open|240572 | libefi: FreeBSD cannot boot with U-Boot patch efi Open|241697 | i915kms: Kernel panic loading module on custom ke Open|241746 | sys/conf: Unbreak kernel tags New |230955 | [patch] Some speedup mergemaster 50 problems total for which you should take action. ___ 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 243116] Apple hardware with Realtek ALC889A no sound
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243116 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|multime...@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 243106] jail(3): memory leak when resizing jail parameter list.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243106 Mark Linimon changed: What|Removed |Added Summary|[patch] jail(3): memory |jail(3): memory leak when |leak when resizing jail |resizing jail parameter |parameter list. |list. Assignee|b...@freebsd.org|j...@freebsd.org Keywords||patch --- Comment #1 from Mark Linimon --- Assign appropriately. fwiw, the [patch] convention has been replaced by the use of the 'patch' Keyword. -- 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 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #8 from Bernhard Berger --- (In reply to Conrad Meyer from comment #7) I'll give you an example: If it says "bread" on the package, then any reasonable person would assume that there is bread inside. This is also the case with the "reboot" program, so even if called without parameters, the "reboot" function should be executed in a system-compliant manner, and that includes executing /etc/rc.shutdown. But it's not the error that upsets me, it's that you don't even try to fix it. I am very outraged by this. Maybe it wasn't so serious "before" and therefore not noticeable. But with the arrival of bhyve, it takes on a whole new meaning. Therefore, the program reboot should definitely be revised and adapted to the new requirements (this has obviously been missed). Since it is not part of the Posix standard, you can also move it into the ports and remove it from the ports with notice. There are solutions, you just have to want it. -- 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 243094] reboot problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #9 from Bernhard Berger --- like this, and that's it. No more discussion. I'm very upset. Overwork reboot or don't. No more bug reports from me, that upsets me too much. -- 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 240992] linprocfs: /proc/[pid]/maps returns rounded file (?) size in the offset column
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240992 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #2 from Mark Johnston --- Created attachment 210472 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=210472&action=edit proposed patch Indeed, this column is supposed to be the mapping offset and linprocfs is just returning the object size. The attached patch should fix it. It also fixes a secondary bug which causes us to potentially print the previous entry's "offset" for an entry with no backing object. -- 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 240992] linprocfs: /proc/[pid]/maps returns rounded file (?) size in the offset column
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240992 Mark Johnston changed: What|Removed |Added Status|New |In Progress Assignee|b...@freebsd.org|ma...@freebsd.org --- Comment #3 from Mark Johnston --- I guess this is not quite right when the mapping is COW, the entry's offset will give the offset into the top-level anonymous shadow object. We need to sum the offsets along the object chain, assuming that Linux provides the same info. -- 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 243117] panic: keg dma coherent 32 initialization after use. (MIPS MALTA64)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243117 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: jeff Date: Sun Jan 5 22:54:26 UTC 2020 New revision: 356389 URL: https://svnweb.freebsd.org/changeset/base/356389 Log: The fix in r356353 was insufficient. Not every architecture returns 0 for EARLY_COUNTER. Only amd64 seems to. Suggested by: markj Reported by: lwhsu Reviewed by: markj PR: 243117 Changes: head/sys/vm/uma_core.c -- 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 243117] panic: keg dma coherent 32 initialization after use. (MIPS MALTA64)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243117 Mark Johnston changed: What|Removed |Added Assignee|b...@freebsd.org|j...@freebsd.org Status|New |Closed Resolution|--- |FIXED --- Comment #4 from Mark Johnston --- Before r356348 we were reading EARLY_COUNTER, giving a bogus allocation counter. It happens to work on amd64 because counter_u64_fetch() uses CPU_FOREACH, which is a no-op before SI_SUB_CPU. -- 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"
Re: [Bug 243094] reboot problem
Call me crazy, but it seems like the real question is why you would want a command called, "reboot," to NOT execute /etc/rc.shutdown, no? Sure, maybe with some extra param. it would just force a shutdown without executing /etc/rc.shutdown, but certainly not as the default. Of course, if it's specified in the man page for the command that it doesn't then there's really nothing to complain about. If it isn't in the man page then it ought to be, right? I have to agree, however, that, "threatening," to use some other OS is really no threat at all. (Particularly when the, "threat," is to start using Windoze... "If you don't make this work the way I want you to I'm going to whack my thumb with this hammer! And I'll continue whacking my own thumb until you capitulate!" "Well... I guess... You can do that. It's your thumb, after all. Do what you like with it.") (Yes, for those who don't understand, I don't really think there is no place is the world for Windoze. There just isn't any place for it on my LAN. Do what you want with your own thumbs.) On 1/5/20 4:31 PM, bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094 --- Comment #8 from Bernhard Berger --- (In reply to Conrad Meyer from comment #7) I'll give you an example: If it says "bread" on the package, then any reasonable person would assume that there is bread inside. This is also the case with the "reboot" program, so even if called without parameters, the "reboot" function should be executed in a system-compliant manner, and that includes executing /etc/rc.shutdown. But it's not the error that upsets me, it's that you don't even try to fix it. I am very outraged by this. Maybe it wasn't so serious "before" and therefore not noticeable. But with the arrival of bhyve, it takes on a whole new meaning. Therefore, the program reboot should definitely be revised and adapted to the new requirements (this has obviously been missed). Since it is not part of the Posix standard, you can also move it into the ports and remove it from the ports with notice. There are solutions, you just have to want it. ___ 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"
