On 2022/06/01 08:26, Florian Obser wrote:
> On 2022-06-01 06:57 +02, Florian Obser wrote:
> > On 2022-05-31 23:27 +01, Stuart Henderson wrote:
> >> I accidentally updated a router to -current instead of 7.1 and hit this.
> >> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
> >
On 2022/06/01 06:57, Florian Obser wrote:
> On 2022-05-31 23:27 +01, Stuart Henderson wrote:
> > I accidentally updated a router to -current instead of 7.1 and hit this.
> > (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
>
> Hmm? Are you saying running just running
On 2022-06-01 06:57 +02, Florian Obser wrote:
> On 2022-05-31 23:27 +01, Stuart Henderson wrote:
>> I accidentally updated a router to -current instead of 7.1 and hit this.
>> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
>
> Hmm? Are you saying running just running
On 2022-05-31 23:27 +01, Stuart Henderson wrote:
> I accidentally updated a router to -current instead of 7.1 and hit this.
> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
Hmm? Are you saying running just running 'sysupgrade', without any flags, moves
you from 7.0-stable to
On 1.6.2022. 0:27, Stuart Henderson wrote:
> I accidentally updated a router to -current instead of 7.1 and hit this.
> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
>
> Unfortunately it runs with ddb.panic=0 and this time it hanged, I won't
> have time to figure anything out
