Date: Sat, 4 Apr 2015 11:30:24 +0200
From: Evgeniy Sudyr eject.in...@gmail.com
Sorry for delayed answer, I did both before:
show uvmexp
https://www.dropbox.com/sh/dwmjt7wwunhk5gb/AABTdTS98GLF2vRN56mn6knpa/Screen%20Shot%202015-04-02%20at%2011.37.20.png?dl=0
Sorry for delayed answer, I did both before:
show uvmexp
https://www.dropbox.com/sh/dwmjt7wwunhk5gb/AABTdTS98GLF2vRN56mn6knpa/Screen%20Shot%202015-04-02%20at%2011.37.20.png?dl=0
Hi Adam. Are you able to build a kernel with the last re(4)
commits reverted to make sure that didn't introduce a bug?
If not then I could build one for you to test (let me know which arch).
-
PatchSet 4925
Date: 2015/03/20 12:04:09
Author: dlg
Branch: HEAD
Tag: (none)
Log:
On Sat, Apr 4, 2015, at 11:07 AM, Adam Wolk wrote:
On Fri, Apr 3, 2015, at 10:01 PM, Adam Wolk wrote:
On Fri, Apr 3, 2015, at 09:12 PM, Adam Wolk wrote:
On Fri, Apr 3, 2015, at 07:49 PM, Adam Wolk wrote:
Hi bugs@
I'm trying to install OpenBSD -current snapshot from 01-Apr-2015.
On Sat, Apr 4, 2015, at 01:17 PM, Stuart Henderson wrote:
Hi Adam. Are you able to build a kernel with the last re(4)
commits reverted to make sure that didn't introduce a bug?
If not then I could build one for you to test (let me know which arch).
Hi Stuart,
I didn't build anything on this
On Sat, Apr 4, 2015, at 01:53 PM, Stuart Henderson wrote:
Hi Adam, you can find kernels that are quite likely to be identical to
before that commit
if
you'd like to give that a try.
I did a test with the kernels you provided. Here are the results.
bsd.sp
OpenBSD 5.7 (GENERIC) #825: Sun
On Sat, Apr 4, 2015, at 03:19 PM, Adam Wolk wrote:
You mentioned earlier some watchdog timeout. Do you know if you always
see one when the pool corruption triggers? You can type dmesg at the
ddb prompt to check if there's any weird message before the panic.
No. I only see the
On Sat, Apr 4, 2015, at 03:09 PM, Martin Pieuchot wrote:
On 04/04/15(Sat) 14:40, Adam Wolk wrote:
On Sat, Apr 4, 2015, at 01:53 PM, Stuart Henderson wrote:
Hi Adam, you can find kernels that are quite likely to be identical to
before that commit
if
you'd like to give that a try.
On Sat, Apr 4, 2015, at 02:57 PM, Stuart Henderson wrote:
On 2015/04/04 14:40, Adam Wolk wrote:
On Sat, Apr 4, 2015, at 01:53 PM, Stuart Henderson wrote:
Hi Adam, you can find kernels that are quite likely to be identical to
before that commit
if
you'd like to give that a try.
On 04/04/15(Sat) 14:40, Adam Wolk wrote:
On Sat, Apr 4, 2015, at 01:53 PM, Stuart Henderson wrote:
Hi Adam, you can find kernels that are quite likely to be identical to
before that commit
if
you'd like to give that a try.
I did a test with the kernels you provided. Here are the
You mentioned earlier some watchdog timeout. Do you know if you always
see one when the pool corruption triggers? You can type dmesg at the
ddb prompt to check if there's any weird message before the panic.
No. I only see the watchdog timeout if I don't try to start netstart by
On 2015/04/04 14:40, Adam Wolk wrote:
On Sat, Apr 4, 2015, at 01:53 PM, Stuart Henderson wrote:
Hi Adam, you can find kernels that are quite likely to be identical to
before that commit
if
you'd like to give that a try.
I did a test with the kernels you provided. Here are the
On Sat, Apr 4, 2015, at 06:02 PM, Adam Wolk wrote:
On Sat, Apr 4, 2015, at 03:36 PM, Adam Wolk wrote:
On Sat, Apr 4, 2015, at 03:19 PM, Adam Wolk wrote:
You mentioned earlier some watchdog timeout. Do you know if you
always
see one when the pool corruption triggers? You can
show malloc was there
https://www.dropbox.com/sh/dwmjt7wwunhk5gb/AADreVye4gK770lEL3gxO6Tca/Screen%20Shot%202015-04-02%20at%2011.38.04.png?dl=0
https://www.dropbox.com/sh/dwmjt7wwunhk5gb/AAB9Rm1bYABpSWh6Wt6YQLF5a/Screen%20Shot%202015-04-02%20at%2011.38.10.png?dl=0
Evgeniy Sudyr wrote:
ACPI175742 18750K 18796K 78644K 5721140 0
This looks rather high. I suspect a leak in the acpi code.
How can I help identify this bug, so developers can fix it :)
On Sat, Apr 4, 2015 at 6:49 PM, Ted Unangst t...@tedunangst.com wrote:
Evgeniy Sudyr wrote:
ACPI175742 18750K 18796K 78644K 5721140 0
This looks rather high. I suspect a leak in the acpi code.
--
--
With
Evgeniy Sudyr wrote:
How can I help identify this bug, so developers can fix it :)
Run sudo pstat -d ld acpi_nalloc; then wait some time and run it again. Though
this looks like it could be a bug not in the OpenBSD ACPI code, but in the
interpreted AML code.
Debugging this over email is
17 matches
Mail list logo
