On Tue, Aug 29, 2023 at 07:15:14PM +0200, Claudio Jeker wrote:
> On Tue, Aug 29, 2023 at 01:01:10AM +, Eric Wong wrote:
> > >Synopsis: RLIMIT_CPU doesn't work reliably on mostly idle systems
> > >Category: system
> > >Environment:
> > System : OpenBSD 7.3
> > Details : OpenBSD
> On Aug 28, 2023, at 20:04, Eric Wong wrote:
>
>
>>
>> Synopsis: RLIMIT_CPU doesn't work reliably on mostly idle systems
>> Category: system
>> Environment:
>System : OpenBSD 7.3
>Details : OpenBSD 7.3 (GENERIC.MP) #1242: Sat Mar 25 18:04:31 MDT 2023
>
> dera...@
> On Mar 14, 2023, at 11:32 AM, p...@delphinusdns.org wrote:
>
>> Synopsis: can we resist agains bit flipping?
>> Category: system
>> Environment:
> System : OpenBSD 7.2
> Details : OpenBSD 7.2 (GENERIC.MP) #2: Thu Nov 24 23:53:03 MST 2022
> r...@syspatch-72-arm64.openbsd.org:/usr/src/sys
Pedro,
On Wed, Dec 14, 2022 at 12:24:42PM -0600, Scott Cheloha wrote:
> On Wed, Dec 14, 2022 at 11:37:14AM +, Pedro Caetano wrote:
> > Hi bugs@
> >
> > In the process of upgrading a pair of servers to release 7.2, the following
> > panic was triggered after sysupgr
On Wed, Dec 14, 2022 at 11:37:14AM +, Pedro Caetano wrote:
> Hi bugs@
>
> In the process of upgrading a pair of servers to release 7.2, the following
> panic was triggered after sysupgrade reboot. (dell poweredge R740)
>
> One of the reboots happened before syspatch, the other happened after
On Mon, Oct 31, 2022 at 12:43:50PM +0100, Paul de Weerd wrote:
> Hi folks,
>
> I just upgraded a VM on my AMD EPYC host. I get the following
> protection fault during boot:
>
> ddb> bo re
> rebooting...
> Using drive 0, partition 3.
> Loading..
> probing: pc0 com0 mem[638K 3838M 256M a20=on]
On Wed, Oct 26, 2022 at 03:23:51PM +0200, Kalabic S. wrote:
> On 26/10/2022 11:33, Scott Cheloha wrote:
> > There might be a second workaround. Kalabic mentions here in the
> > other thread about this problem:
> >
> > https://marc.info/?l=openbsd-bugs&m=14
On Wed, Oct 26, 2022 at 07:36:28AM -0700, James J. Lippard wrote:
> On Wed, Oct 26, 2022 at 04:33:23AM -0500, Scott Cheloha wrote:
> > Thank you for testing, let's take a look.
> > [...]
> > I don't know how to explain this. Maybe another developer will read
On Tue, Oct 25, 2022 at 09:00:33PM -0700, James J. Lippard wrote:
> On Tue, Oct 25, 2022 at 09:20:05PM -0500, Scott Cheloha wrote:
> > On Tue, Oct 25, 2022 at 02:24:24PM -0700, James J. Lippard wrote:
> > > I'm one of several people experiencing this issue with OpenBSD 7.2 o
On Tue, Oct 25, 2022 at 02:24:24PM -0700, James J. Lippard wrote:
> I'm one of several people experiencing this issue with OpenBSD 7.2 on
> VMware ESXi 7.5. Scott C. has given me help in trying to track the issue
> down; a patched -current kernel to remove the acpi_delay code added in
> 7.2 makes t
On Mon, Oct 24, 2022 at 08:26:30AM -0500, Scott Cheloha wrote:
> On Sun, Oct 23, 2022 at 02:07:12PM +0200, Kalabic S. wrote:
> > [...]
>
> > machdep.cpuvendor=GenuineIntel
> > machdep.cpuid=0x306a9
> > machdep.cpufeature=0x1fbbfbff
> > machdep.tscfreq=745206414
On Sun, Oct 23, 2022 at 02:07:12PM +0200, Kalabic S. wrote:
> On 23/10/2022 12:28, Scott Cheloha wrote:
> > On Fri, Oct 21, 2022 at 12:28:26AM +0200, Kalabic S. wrote:
> > > Hello,
> > >
> > > I noticed a system clock issue after upgrade from 7.1 to 7.2, cloc
On Fri, Oct 21, 2022 at 12:28:26AM +0200, Kalabic S. wrote:
> Hello,
>
> I noticed a system clock issue after upgrade from 7.1 to 7.2, clock started
> to run really fast, almost at 10x speed or so. It is a virtual machine guest
> on ESXi 6.0 host, VM is used as a main Internet router for my home n
On Thu, Sep 01, 2022 at 04:26:18PM -0500, Scott Cheloha wrote:
> Hi,
>
> mlarkin@ said someone needed to verify my i386/lapic.c changes on real
> hardware:
>
> https://marc.info/?l=openbsd-tech&m=166186787532304&w=2
>
> So, like a chucklehead, I thought &
Hi,
mlarkin@ said someone needed to verify my i386/lapic.c changes on real
hardware:
https://marc.info/?l=openbsd-tech&m=166186787532304&w=2
So, like a chucklehead, I thought "how hard could it be?" and tried
installing OpenBSD/i386 to an external drive and booting my amd64
laptop (Lenovo X1 Car
On Sun, Jan 30, 2022 at 10:41:34AM -0500, Ryan Kavanagh wrote:
> On Sun, Jan 30, 2022 at 12:39:02AM -0600, Scott Cheloha wrote:
> > > btrace -e 'profile:hz:100 { @[kstack] = count(); }' > /tmp/btrace.out
> > >
> > > for ten seconds and ran the out
On Mon, Jan 10, 2022 at 10:36:41AM -0500, Ryan Kavanagh wrote:
> >Synopsis:high interrupt processing time on Dell Latitude E7450
> >Category:kernel amd64
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC.MP) #242: Sat Jan 8
> 12:33:38 MST
On Sun, Dec 05, 2021 at 06:21:50PM +0100, Stefan Sperling wrote:
> On Sun, Dec 05, 2021 at 11:05:32AM -0600, Scott Cheloha wrote:
> > > diff 0b61c8235787960f0010ef627ea5b2c6309a81f0
> > > de98c050ea709bdb8e26be40ab0cc82ef9afed80
> > > blob - 7bb68194dd78417b06c59
On Sat, Dec 04, 2021 at 08:40:42PM +0100, Stefan Sperling wrote:
> On Sat, Dec 04, 2021 at 09:32:40PM +0300, Vitaliy Makkoveev wrote:
> > I think rtm_80211info() could follow the if_link_state_change()
> > way and use task for that.
>
> Indeed. I did not realize that if_link_state_change() schedul
Hit a witness panic during boot yesterday. Can't repro, have never
seen it before. The photo is a mess (ask if you want it) but the
backtrace is:
panic
witness_checkorder
rw_enter_write
solock
route input
ieee80211_set_link_state
ieee80211_recv_4way_msg3
ieee80211_eapol_key_input
ieee80211_decap
On Thu, May 06, 2021 at 02:36:21PM +0200, Mark Kettenis wrote:
> > Date: Thu, 6 May 2021 21:59:12 +1000
> > From: Jonathan Gray
> >
> > On Wed, May 05, 2021 at 04:47:50PM -0500, Scott Cheloha wrote:
> > >
> > > [...]
> > >
> > > On a
Hi,
On a hunch I added additional parameter checks to task_add(9) and
task_del(9) and caught intel(4) doing something strange.
The patch is straightforward: check that the taskq pointer tq is not
NULL. In the current code we return early if a flag is set or cleared
in the task w, in which case w
Yesterday I enabled witness(4) to debug something unrelated and
started seeing traces during boot.
My kernel is up-to-date as of yesterday night. My inteldrm firmware
is also up-to-date.
The traces appear during every cold boot. Here is the most recent set
from my last reboot, plucked from the
> On Aug 7, 2020, at 11:28 AM, Otto Moerbeek wrote:
>
> On Fri, Aug 07, 2020 at 11:17:18AM -0500, Scott Cheloha wrote:
>
>> On Mon, Aug 05, 2069 at 09:33:05AM +, Toby Betts wrote:
>>>> Synopsis: ntpd(8) adds time since epoch to system clock
>>&
On Mon, Aug 05, 2069 at 09:33:05AM +, Toby Betts wrote:
> >Synopsis:ntpd(8) adds time since epoch to system clock
> >Category:system
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
> 2019
>
On Fri, Mar 29, 2019 at 08:19:12PM +0100, Martijn van Duren wrote:
> Running getdelim on a nonblocking socket results in data loss of the
> first part of the message if the said message is sent in chunks.
> Code below shows how to repeat.
>
> POSIX states the following:
> For the conditions under
On Thu, Sep 27, 2018 at 05:09:22PM -0500, Scott Cheloha wrote:
> > On Sep 27, 2018, at 10:26, Todd C. Miller wrote:
> >
> >> On Thu, 27 Sep 2018 16:19:46 +0100, Dave Hines wrote:
> >>
> >> Oops - my patch contained a bug (though it worked on my machine).
> On Sep 27, 2018, at 10:26, Todd C. Miller wrote:
>
>> On Thu, 27 Sep 2018 16:19:46 +0100, Dave Hines wrote:
>>
>> Oops - my patch contained a bug (though it worked on my machine).
>> Here is a corrected patch for /usr/src/usr.bin/wc/wc.c
>
> That fix looks correct to me.
Ditto, works here. I
ange log to figure out why the behavior is what it
is now. Someone more familiar with the code will need to corroborate
what I've said and the attached diff.
That said, feel free to try this diff in the meantime. Does this work
for you?
Anyone more familiar with apmd(8) wanna chime in he
ns" to the pledge(2) promise corrects this.
It looks like this has been broken since ~2015 but I have no
release machines handy to confirm.
--
Scott Cheloha
Index: usr.bin/openssl/s_time.c
===
RCS file: /cvs/src/usr.bin/openssl/s_time
> On Sep 17, 2017, at 4:53 AM, Marc Espie wrote:
>
> On Sat, Sep 16, 2017 at 10:25:19PM -0500, Scott Cheloha wrote:
>> Hi,
>>
>> [...]
>>
>> --
>> Scott Cheloha
>>
>> Index: lib/libc/sys/write.2
>> ==
t the correct code should be but attached is
my best guess.
Also, if "nr" is for "Number Read", because this is the write(2)
page, would "nw" be better?
--
Scott Cheloha
Index: lib/libc/sys/write.2
==
> On Aug 18, 2017, at 1:18 AM, Jason McIntyre wrote:
>
> [...]
>
>> --
>> Scott Cheloha
>>
>> Index: bin/ksh/ksh.1
>> ===
>> RCS file: /cvs/src/bin/ksh/ksh.1,v
>> retrieving
> On Aug 17, 2017, at 7:52 PM, Scott Cheloha wrote:
>
>> On Aug 17, 2017, at 7:47 PM, Theo Buehler wrote:
>>
>> On Fri, Aug 18, 2017 at 02:37:51AM +0200, Theo Buehler wrote:
>>> On Thu, Aug 17, 2017 at 07:25:14PM -0500, Scott Cheloha wrote:
>>>
Spotted these when customizing my prompt.
I think "may differ from" is better than "could be different from,"
and you're free to (heh) differ, but in either case we get the
to -> from
--
Scott C
Due to something like the Echo Effect this particular typo has been
picked up from our collection by various online fortune/quote collections
and spread from there.
--
Scott Cheloha
Index: games/fortune/datfiles/fortunes
===
RCS
Hi,
The pledge(2) "request" parameter is now called "promises".
--
Scott Cheloha
Index: lib/libc/sys/pledge.2
===
RCS file: /cvs/src/lib/libc/sys/pledge.2,v
retrieving revision 1.43
diff -u -p -r1.43 pledg
The struggle is very real when you're getting kernel panics, but the
struggle needn't have typos.
--
Scott Cheloha
Index: sys/arch/macppc/macppc/machdep.c
===
RCS file: /cvs/src/sys/arch/macppc/macppc/machdep.c,v
retrievin
:
https://web-beta.archive.org/web/2004104718/http://developer.apple.com/technotes/tn/tn1167.html
All archives after that date snagged the aforementioned redirect
instead.
--
Scott Cheloha
ot;ksh" instead of "sh" (trivial patch below), so that the
documentation in the system itself is consistent... but elsewhere
in the manpages XSI extensions are marked and such, so I don't
know what else, if anything, should be changed.
Something just seems off, hence bugs@.
Tho
better choice in most
cases.
But lib/libc/string/strcpy.3 has no EXAMPLES section.
Seen on OpenBSD 6.0 AMD64 (installed from the CD media), still present in CVS.
Cheers,
Scott Cheloha
41 matches
Mail list logo
