Re: pool related crashes, but "kernel did no panic"

On Tue, May 31, 2016 at 7:16 PM, Theo de Raadt wrote: >> is exactly 80 characters long (such a long printf violates "80 chars" >> rule, isn't it?). > > there is no hard and fast rule for that at all; printing extra newlines > has other downsides such as the screen

Re: pool related crashes, but "kernel did no panic"

> is exactly 80 characters long (such a long printf violates "80 chars" > rule, isn't it?). there is no hard and fast rule for that at all; printing extra newlines has other downsides such as the screen scrolling sooner.

Re: pool related crashes, but "kernel did no panic"

On Mon, May 30, 2016 at 9:02 PM, Ted Unangst wrote: > Alexey Suslikov wrote: >> On Thu, May 12, 2016 at 4:14 PM, Bob Beck wrote: >> > Thank you!now that's a bug report.. >> >> Hi. >> >> Moved to 6.0-beta some time ago to make crash dumps more up >> to

Re: pool related crashes, but "kernel did no panic"

Alexey Suslikov wrote: > On Thu, May 12, 2016 at 4:14 PM, Bob Beck wrote: > > Thank you!now that's a bug report.. > > Hi. > > Moved to 6.0-beta some time ago to make crash dumps more up > to date. Also, removed some services to minimize their impact. > > Fresh build

Re: pool related crashes, but "kernel did no panic"

On Thu, May 12, 2016 at 4:14 PM, Bob Beck wrote: > Thank you!now that's a bug report.. Hi. Moved to 6.0-beta some time ago to make crash dumps more up to date. Also, removed some services to minimize their impact. Fresh build against today's cvs don't survived even half

Re: pool related crashes, but "kernel did no panic"

On Fri, May 13, 2016 at 3:59 AM, David Gwynne wrote: > >> On 12 May 2016, at 20:28, Alexey Suslikov wrote: >> >> On Wed, Apr 27, 2016 at 7:22 PM, Theo de Raadt >> wrote: On 27/04/16(Wed) 15:45, Alexey Suslikov wrote:

Re: pool related crashes, but "kernel did no panic"

Thank you!now that's a bug report.. On Thu, May 12, 2016 at 4:28 AM, Alexey Suslikov wrote: > On Wed, Apr 27, 2016 at 7:22 PM, Theo de Raadt > wrote: >>> On 27/04/16(Wed) 15:45, Alexey Suslikov wrote: >>> > Theo de Raadt

Re: pool related crashes, but "kernel did no panic"

On Wed, Apr 27, 2016 at 7:22 PM, Theo de Raadt wrote: >> On 27/04/16(Wed) 15:45, Alexey Suslikov wrote: >> > Theo de Raadt cvs.openbsd.org> writes: >> > >> > > >> > > Most of these bug reports completely stink. >> > > >> > > ALWAYS include *ALL* information in a report.

Re: pool related crashes, but "kernel did no panic"

On Wed, Apr 27, 2016 at 03:45:45PM +, Alexey Suslikov wrote: > Theo de Raadt cvs.openbsd.org> writes: > > > > > Most of these bug reports completely stink. > > > > ALWAYS include *ALL* information in a report. > > In an idealistic world, yes. > > Above are not parts of the "chain", but

Re: pool related crashes, but "kernel did no panic"

> On 27/04/16(Wed) 15:45, Alexey Suslikov wrote: > > Theo de Raadt cvs.openbsd.org> writes: > > > > > > > > Most of these bug reports completely stink. > > > > > > ALWAYS include *ALL* information in a report. > > > > In an idealistic world, yes. > > In an idealistic world their would be no

Re: pool related crashes, but "kernel did no panic"

On 27/04/16(Wed) 15:45, Alexey Suslikov wrote: > Theo de Raadt cvs.openbsd.org> writes: > > > > > Most of these bug reports completely stink. > > > > ALWAYS include *ALL* information in a report. > > In an idealistic world, yes. In an idealistic world their would be no bug. > Above are not

Re: pool related crashes, but "kernel did no panic"

Theo de Raadt cvs.openbsd.org> writes: > > Most of these bug reports completely stink. > > ALWAYS include *ALL* information in a report. In an idealistic world, yes. Above are not parts of the "chain", but different statements of the same bug. To have both blue screen and ddb, I need to keep

Re: pool related crashes, but "kernel did no panic"

Most of these bug reports completely stink. ALWAYS include *ALL* information in a report. If you are told your report is missing information, write a completely fresh report that includes ALL INFORMATION. Don't reply in a series of emails adding more and more information. People who submit

Re: pool related crashes, but "kernel did no panic"

Stuart Henderson spacehopper.org> writes: > There should be some lines printed before you get dumped into DDB > (probably a uvm_fault), the information in them is important. I either have a screenshot, or ddb. Not both at the same time. Here is one of screenshots from 5.9 transcribed:

Re: pool related crashes, but "kernel did no panic"

Another one from my collection. Apr 16: ddb{0}> show panic the kernel did not panic ddb{0}> trace pool_do_get() at pool_do_get+0x90 pool_get() at pool_get+0xb5 m_get() at m_get+0x28 sbappendaddr() at sbappendaddr+0x9a uipc_usrreq() at uipc_usrreq+0x3b8 sosend() at sosend+0x3d8 dosendsyslog() at

Re: pool related crashes, but "kernel did no panic"

On 2016/04/27 13:54, Alexey Suslikov wrote: > Another one from my collection. > > Apr 16: > > ddb{0}> show panic > the kernel did not panic There should be some lines printed before you get dumped into DDB (probably a uvm_fault), the information in them is important. > ddb{0}> trace >

Re: pool related crashes, but "kernel did no panic"

On Wed, Apr 27, 2016 at 02:57:31PM +0200, Olivier Cherrier wrote: > On Wed, Apr 27, 2016 at 09:13:40AM +, alexey.susli...@gmail.com wrote: > > Hi tech@. > > > > (Maybe related to http://marc.info/?l=openbsd-bugs=146174654219490=2). > > ;-) > > > Crashing server acts as a carp backup

Re: pool related crashes, but "kernel did no panic"

On Wed, Apr 27, 2016 at 09:13:40AM +, alexey.susli...@gmail.com wrote: > Hi tech@. > > (Maybe related to http://marc.info/?l=openbsd-bugs=146174654219490=2). ;-) > Crashing server acts as a carp backup (master has same hardware config but > don't crash, in contrast to backup). Will post

Re: pool related crashes, but "kernel did no panic"

On 27/04/16(Wed) 09:13, Alexey Suslikov wrote: > Hi tech@. > > (Maybe related to http://marc.info/?l=openbsd-bugs=146174654219490=2). Maybe maybe not. Please keep send your bug reports to bugs@ with all the required informations.