On 14.07.2019 14:46, Chris Wilson wrote:
> Quoting Heiner Kallweit (2019-07-14 13:39:15)
>> On 14.07.2019 14:34, Chris Wilson wrote:
>>> Quoting Heiner Kallweit (2019-07-13 12:12:56)
I debugged a little bit and remount_fs isn't set in sb->s_op.
The following at least avoids the NPE, not s
On 14.07.2019 14:34, Chris Wilson wrote:
> Quoting Heiner Kallweit (2019-07-13 12:12:56)
>> On 13.07.2019 12:38, Heiner Kallweit wrote:
>>> Since few days I'm getting the following on a N3450-based headless system
>>> with linux-next.
>>> linux-next from Jul 4th was still ok.
>>> Is this a known i
Quoting Heiner Kallweit (2019-07-14 13:51:45)
> On 14.07.2019 14:46, Chris Wilson wrote:
> > Quoting Heiner Kallweit (2019-07-14 13:39:15)
> >> On 14.07.2019 14:34, Chris Wilson wrote:
> >>> Quoting Heiner Kallweit (2019-07-13 12:12:56)
> I debugged a little bit and remount_fs isn't set in sb-
Quoting Heiner Kallweit (2019-07-14 13:39:15)
> On 14.07.2019 14:34, Chris Wilson wrote:
> > Quoting Heiner Kallweit (2019-07-13 12:12:56)
> >> I debugged a little bit and remount_fs isn't set in sb->s_op.
> >> The following at least avoids the NPE, not sure whether it's the correct
> >> fix.
> >
Quoting Heiner Kallweit (2019-07-13 12:12:56)
> On 13.07.2019 12:38, Heiner Kallweit wrote:
> > Since few days I'm getting the following on a N3450-based headless system
> > with linux-next.
> > linux-next from Jul 4th was still ok.
> > Is this a known issue?
> >
> > [4.818139] BUG: kernel NU
Since few days I'm getting the following on a N3450-based headless system with
linux-next.
linux-next from Jul 4th was still ok.
Is this a known issue?
[4.818139] BUG: kernel NULL pointer dereference, address:
[4.818165] #PF: supervisor instruction fetch in kernel mode
[
On 13.07.2019 12:38, Heiner Kallweit wrote:
> Since few days I'm getting the following on a N3450-based headless system
> with linux-next.
> linux-next from Jul 4th was still ok.
> Is this a known issue?
>
> [4.818139] BUG: kernel NULL pointer dereference, address:
> [4.8
