>> 21.01.2020, 20:10, "Nick Hibma" :
>>> That (with the return added, thanks Cy) worked like a charm.
>> Got committed in r357038.
>> Thank you for the report!
>
> Hi.
>
> My machine was panicked on r357061 with in_epoch in netisr.c.
> I can not capture screen.
Screenshot was uploaded
On 2020-01-24 08:01, Cy Schubert wrote:
Let's try this again, this time with a subject line. It's late, almost bed
time and I'm forgetting subject lines.
Hi,
Has anyone seen this before? It started happening on two of my machines
this evening. Both machines are AMD (not intel). In both cases
On 2020-01-24 09:41, Masachika ISHIZUKA wrote:
21.01.2020, 20:10, "Nick Hibma" :
That (with the return added, thanks Cy) worked like a charm.
Got committed in r357038.
Thank you for the report!
Hi.
My machine was panicked on r357061 with in_epoch in netisr.c.
I can not capture
Hi,
I think this patch will fix your issue. Can you check?
https://svnweb.freebsd.org/changeset/base/357050
Look like td->td_oncpu is invalid.
pc = cpuid_to_pcpu[td->td_oncpu]; /* pcpu_find(td->td_oncpu); */
rm_tracker_add(pc, tracker);
And thanks for running -current
On 2020-01-24 14:38, Cy Schubert wrote:
In message <629a6d48-cf47-e76b-81a0-db29d2400...@selasky.org>, Hans Petter
Sela
sky writes:
Hi,
I think this patch will fix your issue. Can you check?
https://svnweb.freebsd.org/changeset/base/357050
Look like td->td_oncpu is invalid.
pc =
On 2020-01-24 09:59, Hans Petter Selasky wrote:
On 2020-01-24 09:41, Masachika ISHIZUKA wrote:
21.01.2020, 20:10, "Nick Hibma" :
That (with the return added, thanks Cy) worked like a charm.
Got committed in r357038.
Thank you for the report!
Hi.
My machine was panicked on r357061
In message <77cdb188-a47e-4a0d-a09f-c04377cda...@selasky.org>, Hans Petter
Sela
sky writes:
> On 2020-01-24 14:38, Cy Schubert wrote:
> > In message <629a6d48-cf47-e76b-81a0-db29d2400...@selasky.org>, Hans Petter
> > Sela
> > sky writes:
> >> Hi,
> >>
> >> I think this patch will fix your issue.
On Fri, Jan 24, 2020 at 02:42:50PM +0100, Hans Petter Selasky wrote:
> On 2020-01-24 14:38, Cy Schubert wrote:
> > In message <629a6d48-cf47-e76b-81a0-db29d2400...@selasky.org>, Hans Petter
> > Sela
> > sky writes:
> > > Hi,
> > >
> > > I think this patch will fix your issue. Can you check?
> > >
In message <036a5750-1af7-b83d-e141-f43585a1b...@selasky.org>, Hans Petter
Sela
sky writes:
> On 2020-01-24 08:01, Cy Schubert wrote:
> > Let's try this again, this time with a subject line. It's late, almost bed
> > time and I'm forgetting subject lines.
> >
> > Hi,
> >
> > Has anyone seen
Op vr 24 jan. 2020 om 13:19 schreef Hans Petter Selasky :
> Can you try these two patches:
> https://reviews.freebsd.org/D23347
> https://reviews.freebsd.org/D23348
These two patches work for me (build- and runtime tested with code
from github.com/freebsd/freebsd)
In message <629a6d48-cf47-e76b-81a0-db29d2400...@selasky.org>, Hans Petter
Sela
sky writes:
> Hi,
>
> I think this patch will fix your issue. Can you check?
> https://svnweb.freebsd.org/changeset/base/357050
>
> Look like td->td_oncpu is invalid.
>
>
> > pc = cpuid_to_pcpu[td->td_oncpu];
In message <20200124150031.GA4765@raichu>, Mark Johnston writes:
> On Fri, Jan 24, 2020 at 02:42:50PM +0100, Hans Petter Selasky wrote:
> > On 2020-01-24 14:38, Cy Schubert wrote:
> > > In message <629a6d48-cf47-e76b-81a0-db29d2400...@selasky.org>, Hans Pette
> r
> > > Sela
> > > sky writes:
> > >
> H> >>> My machine was panicked on r357061 with in_epoch in netisr.c.
> H> >>> I can not capture screen.
> H> >>
> H> >> Screenshot was uploaded to
> H> >> https://www.ish.org/files/panic-r357061.jpeg
> H> >>
> H> >
> H> > Looks like the WLAN subsystem needs some patches for EPOCH().
>
Hello,
I updated my sources from 20200113 to 20200124 and after that my laptop
hangs during boot.
The machine is a Lenovo Thinkpad X1 yoga with a core i7-6500U cpu and 8Gb
ram.
It hangs during kernel boot and the last message printed on console is:
hwpstate_intel0: on cpu0
I reverted commits
On Fri, Jan 24, 2020 at 04:23:44PM +0900, Masachika ISHIZUKA wrote:
M> > 21.01.2020, 20:10, "Nick Hibma" :
M> >> That (with the return added, thanks Cy) worked like a charm.
M> > Got committed in r357038.
M> > Thank you for the report!
M>
M> Hi.
M>
M> My machine was panicked on r357061 with
On January 24, 2020 5:13:25 AM PST, Hans Petter Selasky
wrote:
>Hi,
>
>I think this patch will fix your issue. Can you check?
>https://svnweb.freebsd.org/changeset/base/357050
>
>Look like td->td_oncpu is invalid.
>
>
>> pc = cpuid_to_pcpu[td->td_oncpu]; /* pcpu_find(td->td_oncpu);
>*/
On Fri, Jan 24, 2020 at 01:18:26PM +0100, Hans Petter Selasky wrote:
H> On 2020-01-24 09:59, Hans Petter Selasky wrote:
H> > On 2020-01-24 09:41, Masachika ISHIZUKA wrote:
H> 21.01.2020, 20:10, "Nick Hibma" :
H> > That (with the return added, thanks Cy) worked like a charm.
H> Got
H> >>> My machine was panicked on r357061 with in_epoch in netisr.c.
H> >>> I can not capture screen.
H> >>
H> >> Screenshot was uploaded to
H> >> https://www.ish.org/files/panic-r357061.jpeg
H> >>
H> >
H> > Looks like the WLAN subsystem needs
>>> H> >>> My machine was panicked on r357061 with in_epoch in netisr.c.
>>> H> >>> I can not capture screen.
>>> H> >>
>>> H> >> Screenshot was uploaded to
>>> H> >> https://www.ish.org/files/panic-r357061.jpeg
>>> H> >>
>>> H> >
>>> H> > Looks like the WLAN subsystem needs some
>> H> >>> My machine was panicked on r357061 with in_epoch in netisr.c.
>> H> >>> I can not capture screen.
>> H> >>
>> H> >> Screenshot was uploaded to
>> H> >> https://www.ish.org/files/panic-r357061.jpeg
>> H> >>
>> H> >
>> H> > Looks like the WLAN subsystem needs some patches for
20 matches
Mail list logo
