Hi Alexander,
No problem, this happens and it doesn?t impact me. I try to stay up to date and
when there is a regression I rollback and narrow it down as an early warning.
Your commit fixed the problem in 364020.
Next time I have a crash and have narrowed it down to a specific commit I?ll add
the committer again.
Peter
> On 8 Aug 2020, at 21:36, Alexander Motin <mav at FreeBSD.org> wrote:
>
> Peter,
>
> I am sorry, there appeared to be a merge mistake in commit 364003. It was
fixed in 364020. Have you tried it? Do you still have a problem after it? If
so, please add any more details. 'acpidump -t' would be a good start,
same as last output before reboot.
>
> PS: I don't know about "different committer", but I read mail
all the time and appreciate related problem reports.
>
>
> On Sat, Aug 8, 2020, 1:49 AM <peter.blok at bsd4all.org
<mailto:peter.blok at bsd4all.org>> wrote:
> Last time I ( a week ago or so ) I did for another crash and wasn?t getting
any response from (a different) committer.
>
>
> > On 7 Aug 2020, at 21:48, Konstantin Belousov <kostikbel at
gmail.com <mailto:kostikbel at gmail.com>> wrote:
> >
> > On Fri, Aug 07, 2020 at 03:09:00PM +0200, peter.blok at bsd4all.org
<mailto:peter.blok at bsd4all.org> wrote:
> >> Hi,
> >>
> >> After commit 364003 STABLE-12 reboots almost immediately. No error
message, not dump. Just a reboot.
> >>
> >> Last working commit 364002.
> >>
> >> Please let me know what is needed - acpidump or something like
that.
> > Why did not you added the committer to Cc: ?
> > _______________________________________________
> > freebsd-stable at freebsd.org <mailto:freebsd-stable at
freebsd.org> mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
<https://lists.freebsd.org/mailman/listinfo/freebsd-stable>
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org <mailto:freebsd-stable-unsubscribe at freebsd.org>"
>