Re: regression suspend/resume on Lenovo T420

On 0515T2140, Konstantin Belousov wrote: > On Mon, May 15, 2017 at 06:37:58PM +0100, Edward Tomasz Napiera??a wrote: > > Thanks! The patch fixes resume for me, for both vt(4) and X11. > > Thanks everybody for testing, patch below should be committable, modulo > bugs. I did not tested it and ask

Re: Time to increase MAXPHYS?

On 0605T1849, Edward Tomasz Napierała wrote: > On 0604T0952, Hans Petter Selasky wrote: > > On 06/04/17 09:39, Tomoaki AOKI wrote: > > > Hi > > > > > > One possibility would be to make it MD build-time OTIONS, > > > defaulting 1M o

Re: Time to increase MAXPHYS?

reverted it back ASAP > > On 5 Jun 2017, at 19:49, Edward Tomasz Napierała <tr...@freebsd.org> wrote: > > > > On 0604T0952, Hans Petter Selasky wrote: > >> On 06/04/17 09:39, Tomoaki AOKI wrote: > >>> Hi > >>> > >>> One possib

Re: Time to increase MAXPHYS?

On 0604T0952, Hans Petter Selasky wrote: > On 06/04/17 09:39, Tomoaki AOKI wrote: > > Hi > > > > One possibility would be to make it MD build-time OTIONS, > > defaulting 1M on regular systems and 128k on smaller systems. > > > > Of course I guess making it a tunable (or sysctl) would be best, >

Re: suspend/resume regression

On 0513T1244, Pete Wright wrote: > > > On 05/13/2018 10:27, Pete Wright wrote: > > > > > > On 05/13/2018 08:58, Theron wrote: > >>> Hi! > >>> I'm also seeing issues, not as severe as Pete, but after I resume > >>> (which works, with drm-next and DMC firmware), the system becomes > >>>

Re: suspend/resume regression

On 0514T1158, Andriy Gapon wrote: > On 14/05/2018 11:44, Mikaël Urankar wrote: > > Could it be the same problem described here? > > https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052778.html > > That problem is _not_ a regression. FWIW, this machine (the one affected by the

Re: getfsstat / nullsfs / automount bug?

> On 20 Nov 2017, at 17:39, Jamie Landeg-Jones wrote: > > There appears to be a bug in the system call related to getmntinfo(3) / > getfsstat(2) > , when if the "automount" flag is set on "nullfs" mounts, it is not returned > on > a getfsstat "WAIT" call. The

Re: devdmatch: Can't read linker file.

FWIW, it seems to be a common problem, see https://reviews.freebsd.org/D14534. On 0312T1027, Warner Losh wrote: > Well, is there a /boot/kernel/linker.hints? > > Warner > > On Mon, Mar 12, 2018 at 9:56 AM, Daniel Braniss wrote: > > > Hi, > > the above i get on

FreeBSD Quarterly Status Report - Third Quarter 2018

FreeBSD Project Quarterly Status Report - 3rd Quarter 2018 With FreeBSD having gone all the way to 12, it is perhaps useful to take a look back at all the things that have been accomplished, in terms of many visible changes, as well as all the things that happen behind the scenes to

FreeBSD Quarterly Status Report - Fourth Quarter 2018

FreeBSD Project Quarterly Status Report - 4th Quarter 2018 Since we are still on this island among many in this vast ocean of the Internet, we write this message in a bottle to inform you of the work we have finished and what lies ahead of us. These deeds that we have wrought with our

Call for 2019Q1 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 30, 2019, for work done since the last round of Quarterly Reports: January, 2019 – March, 2019. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD

FreeBSD Quarterly Status Report - First Quarter 2019

FreeBSD Project Quarterly Status Report - 1st Quarter 2019 As spring leads into summer, we reflect back on what the FreeBSD project has accomplished in the first quarter of 2019. Events included FOSDEM and AsiaBSDCon, the FreeBSD Journal is now free to everyone, ASLR is available in

Call for 2019Q2 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July 31, 2019, for work done since the last round of Quarterly Reports: April, 2019 – June, 2019. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD

FreeBSD Quarterly Status Report - Second Quarter 2019

FreeBSD Project Quarterly Status Report - 2nd Quarter 2019 This quarter our report includes some interesting topics easily accessible to anyone, even if you are not a programmer: we report the link to a presentation of the 2019 FreeBSD survey results at BSDCan 2019 and describe an

Re: rc.d/linux runs unconditionally

On 1003T0947, Michael Butler wrote: > In rc.d/sysvipc we see .. > > name="sysvipc" > desc="Load SysV IPC modules" > rcvar="sysvipc_enable" > start_cmd="${name}_start" > > .. so it won't try to run without explicitly setting sysvipc_enable in > /etc/rc.conf. > > However in rc.d/linux, we have

Re: rc.d/zpool runs before ada(4) attaches

On 1201T0834, Ian Lepore wrote: > On Tue, 2020-12-01 at 16:22 +0100, Ronald Klop wrote: [..] > > You can define these in /boot/loader.conf: > > #kern.cam.boot_delay="1" # Delay (in ms) of root mount for CAM > > bus > > #kern.cam.scsi_delay="2000" # Delay (in ms) before probing SCSI > > > >

Re: kernel panic while copying files

On 0610T1150, Gary Jennejohn wrote: > On Tue, 8 Jun 2021 17:54:05 +0200 > Gary Jennejohn wrote: > > [big snip] [..] > So, I did ``git reset --hard 8dc96b74edb844bb621afeba38fe4af104b13120'', > which was the penultimate commit made by trasz to clear CCBs on the stack > after he committed

Re: panic: Unaligned free (was: kernel panic while copying files)

On 0701T1330, Gary Jennejohn wrote: > Gary Jennejohn wrote: > > I noticed that the value of vm.debug.divisor affects what value is > > returned in uma_core.c:uma_dbg_kskip(), so I decided to try a few > > different values. > > > > The returned value is used to set skipdbg in

<    1   2