On Sun, Jun 19, 2022 at 01:26:27PM +0200, Stephan Mending wrote:
> Hi,
> it crashed again.
> Here is the dmesg, this time the kernel had debugging symbols enabled.
>
> [...]
> ic0 at ichiic0
> spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-12800 SO-DIMM
> isa0 at pcib0
> isadma0 at isa0
> vga0 a
Hi,
it crashed again.
Here is the dmesg, this time the kernel had debugging symbols enabled.
[...]
ic0 at ichiic0
spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-12800 SO-DIMM
isa0 at pcib0
isadma0 at isa0
vga0 at isa0 port 0x3b0/48 iomem 0xa/131072
wsdisplay at vga0 not configured
pcppi0 at
>From l...@md5collisions.eu Thu May 26 19:51:47 2022
Date: Thu, 26 May 2022 19:51:47 +0200
From: Stephan Mending
To: misc@openbsd.org
Subject: Re: Cron running at 99% CPU for seemingly no reason
Message-ID:
Mail-Followup-To: Stephan Mending , misc@openbsd.org
References:
MIME-Version:
This is a bug in a diff I put into snapshots.
On 15.5.2022. 16:56, Todd C. Miller wrote:
> On Sun, 15 May 2022 16:02:03 +0200, Hrvoje Popovski wrote:
>
>> I know how to rebuild cron
>>
>> cd /usr/src/usr.sbin/cron/
>> make obj && make depend && make && make install
>>
>> but i don't know how to enabled debug symbols ..
>
> Easiest would be t
On Sun, 15 May 2022 16:02:03 +0200, Hrvoje Popovski wrote:
> I know how to rebuild cron
>
> cd /usr/src/usr.sbin/cron/
> make obj && make depend && make && make install
>
> but i don't know how to enabled debug symbols ..
Easiest would be to do:
cd /usr/src/usr.sbin/cron/
make obj && make depend
On 15.5.2022. 15:38, Todd C. Miller wrote:
> On Sun, 15 May 2022 14:29:28 +0200, Hrvoje Popovski wrote:
>
>> I'm seeing same as Stephan on few servers in lab.
>> I've killed cron and did ktrace -i cron. Is this ok?
>> In attachment you can find kdump -f ktrace.out output.
>
> That's very odd. It
On Sun, 15 May 2022 14:29:28 +0200, Hrvoje Popovski wrote:
> I'm seeing same as Stephan on few servers in lab.
> I've killed cron and did ktrace -i cron. Is this ok?
> In attachment you can find kdump -f ktrace.out output.
That's very odd. It looks like cron parses root's crontab and then
someho
On 15.5.2022. 14:39, Hrvoje Popovski wrote:
> On 15.5.2022. 14:29, Hrvoje Popovski wrote:
>> On 15.5.2022. 12:32, Claudio Jeker wrote:
>>> Also for cron, please attach ktrace to the cron process for a few seconds
>>> and look at the kdump of that. Most probably it is constantly woken up for
>>> som
On 15.5.2022. 12:32, Claudio Jeker wrote:
> Also for cron, please attach ktrace to the cron process for a few seconds
> and look at the kdump of that. Most probably it is constantly woken up for
> some reasons.
Hi,
I'm seeing same as Stephan on few servers in lab.
I've killed cron and did ktrace
On 2022-05-15, Stephan Mending wrote:
> Especially the line stating "the kernel did not panic" surprises me, as I am
> greeted by the kernel debugger. Not sure how to interpret that.
ddb is entered for panics (which are explicit calls from kernel
code) and for other exceptions (which are not) -
On Sun, May 15, 2022 at 12:06:33PM +0200, Stephan Mending wrote:
> Hi *,
> I've got a system running -current that keeps crashing on me every couple of
> days.
> Output of ddb:
>
> Connected to /dev/cuaU0 (speed 115200)
>
> ddb{0}> show panic
> the kernel did not panic
> ddb{0}> show uvm
> Cu
On Sun, May 15, 2022 at 12:06:33PM +0200, Stephan Mending wrote:
> Hi *,
> I've got a system running -current that keeps crashing on me every couple of
> days.
> Output of ddb:
>
> Connected to /dev/cuaU0 (speed 115200)
>
> ddb{0}> show panic
> the kernel did not panic
> ddb{0}> show uvm
> Cu
Hi *,
I've got a system running -current that keeps crashing on me every couple of
days.
Output of ddb:
Connected to /dev/cuaU0 (speed 115200)
ddb{0}> show panic
the kernel did not panic
ddb{0}> show uvm
Current UVM status:
pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12
482451 VM pa
14 matches
Mail list logo
