On Thu, Nov 07, 2024 at 05:19:19PM +0100, Johan Hovold wrote:
> On Tue, Nov 05, 2024 at 10:26:40AM -0800, Chris Lew wrote:
> > On 11/4/2024 9:08 PM, Johan Hovold wrote:
> > > I naively tried adding a sleep after registering the endpoint, but that
> > > is at least not sufficient to trigger the NUL
On Tue, Nov 05, 2024 at 10:26:40AM -0800, Chris Lew wrote:
> On 11/4/2024 9:08 PM, Johan Hovold wrote:
> > On Mon, Nov 04, 2024 at 04:26:15PM -0800, Chris Lew wrote:
> >> This looks like the null pointer would happen if qrtr tried to send
> >> before mhi_channel_prepare() is called.
> >> I think
On 11/4/2024 9:08 PM, Johan Hovold wrote:
On Mon, Nov 04, 2024 at 04:26:15PM -0800, Chris Lew wrote:
On 11/1/2024 8:01 AM, Johan Hovold wrote:
[8.825593] Unable to handle kernel NULL pointer dereference at virtual
address 0034
.
[9.002030] CPU: 10 UID: 0 PID: 11 Comm
On Mon, Nov 04, 2024 at 04:26:15PM -0800, Chris Lew wrote:
> On 11/1/2024 8:01 AM, Johan Hovold wrote:
> > [8.825593] Unable to handle kernel NULL pointer dereference at virtual
> > address 0034
> > .
> > [9.002030] CPU: 10 UID: 0 PID: 11 Comm: kworker/u48:0 Not tainted
> > 6
On 11/1/2024 8:01 AM, Johan Hovold wrote:
Hi,
I just ran into a NULL-deref in a qrts/mhi path during boot of the
x1e80100 CRD for the second time.
First time was with a 6.11 kernel (but I never got around to reporting
it) and today it happened again with 6.12-rc5.
Both times I was using the
5 matches
Mail list logo