Re: panics in network stack in 12-current

On Thu, Apr 27, 2017 at 10:02 AM, Tom Uffner wrote: > Andrey V. Elsukov wrote: >> >> On 27.04.2017 08:42, Tom Uffner wrote: >>> >>> r315956 panicked about 22 min after boot. failed to dump a core. >> >> >> Why not update to the latest revision? > > > I did several times a while ago, but didn't get

Re: FYI: example "panic: ARM64TODO: reclaim_pv_chunk" on a Pine64+ 2GB with head -r317015 [mdconfig -d not effectively releasing memory?]

[As the text does not really follow from the earlier text I'd sent directly I'm top posting a hypothesis about where so much active memory came from to be so low in available memory to get an reclaim_pv_chunk attempt.] My hypothesis is that the "mdconfig -d"s from vm_copy_base (from /usr/src/relea

Re: FYI: example "panic: ARM64TODO: reclaim_pv_chunk" on a Pine64+ 2GB with head -r317015 [another example]

[Another example panic. Again no dump. But I have what a top -PCwaopid froze at this time.] On 2017-Apr-27, at 4:22 PM, Mark Millard wrote: > Unfortunately for this FYI the attempt to produce a dump > failed and so all the information that I have is what I > first captured from the console outpu

FYI: example "panic: ARM64TODO: reclaim_pv_chunk" on a Pine64+ 2GB with head -r317015

Unfortunately for this FYI the attempt to produce a dump failed and so all the information that I have is what I first captured from the console output: a backtrace. The context was head -r317015 on a Pine64+ 2GB. At the time I was experimenting with trying to build a vm.raw from my own build of F

Re: Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631

On 27/04/2017 18:52, Michael Jung wrote: > Hi: > > Recently upgraded from r315905 to r317435 and during a poudriere run got this > panic which I have not seen before. > > https://charon.gopai.com/core.txt.1 > https://charon.gopai.com/info.1 > > Let me know what additional information I might sup

Re: panics in network stack in 12-current

Andrey V. Elsukov wrote: On 27.04.2017 08:42, Tom Uffner wrote: Tom Uffner wrote: Andrey V. Elsukov wrote: I think the most of these panics should be fixed in r315956. thanks. I'll give it a try and report back as soon as I have a result. r315956 panicked about 22 min after boot. failed to

Re: panics in network stack in 12-current

Andrey V. Elsukov wrote: On 27.04.2017 08:42, Tom Uffner wrote: r315956 panicked about 22 min after boot. failed to dump a core. Why not update to the latest revision? I did several times a while ago, but didn't get a panic free system. I was hoping to bisect the point the point where the pr

Panic String: solaris assert: (lsize != psize) implies ((flags & ZIO_FLAG_RAW) != 0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: 631

Hi: Recently upgraded from r315905 to r317435 and during a poudriere run got this panic which I have not seen before. https://charon.gopai.com/core.txt.1 https://charon.gopai.com/info.1 Let me know what additional information I might supply. --mikej panic: solaris assert: (lsize != psize) i

Re: panics in network stack in 12-current

On 27.04.2017 08:42, Tom Uffner wrote: > Tom Uffner wrote: >> Andrey V. Elsukov wrote: >>> I think the most of these panics should be fixed in r315956. >> >> thanks. I'll give it a try and report back as soon as I have a result. > > r315956 panicked about 22 min after boot. failed to dump a core.

Re: Opteron 6100-series "Magny-Cours"

If you still have not found it, I have two Supermicro blades with these, one to be upgraded with 6127 these days… Daniel > On 27.03.2017 г., at 16:11, Andriy Gapon wrote: > > On 27/03/2017 15:06, Piotr Kubaj wrote: >> Does it have to be specifically 61xx series? I have a server running 2 >>