Opened 2 years ago

Closed 2 years ago

#17766 closed bug (fixed)

kernel crash on latest nightly

Reported by: jason123santa Owned by: nobody
Priority: normal Milestone: R1/beta4
Component: Drivers/Network/nforce Version: R1/Development
Keywords: Cc:
Blocked By: #17763 Blocking:
Platform: All

Description (last modified by jason123santa)

I am getting kernel crashes on latest nightly. It works in a vm but on real hardware it goes to a kernel crash. Images provided

Attachments (4)

mKwhIfAOQ4OM6Coyn7BY3A.jpg​ (374.9 KB ) - added by jason123santa 2 years ago.
kJzXEw1-TPGTrMP3YHJ-yg.jpg​ (486.1 KB ) - added by jason123santa 2 years ago.
syslog.ticket-17766​ (6.1 KB ) - added by jason123santa 2 years ago.
PXL_20220609_232944288.jpg​ (2.6 MB ) - added by jason123santa 2 years ago.
kernel error on 164

Change History (24)

comment:1 by jason123santa, 2 years ago

Description: modified (diff)

by jason123santa, 2 years ago

Attachment: mKwhIfAOQ4OM6Coyn7BY3A.jpg​ added

by jason123santa, 2 years ago

Attachment: kJzXEw1-TPGTrMP3YHJ-yg.jpg​ added

comment:2 by waddlesplash, 2 years ago

Blocked By: 17763 added
Component: - General → Drivers/Network/nforce

Very probably related to #17763.

comment:3 by waddlesplash, 2 years ago

(I am presuming this is memory corruption related to the jumbo-frames changes.)

comment:4 by jason123santa, 2 years ago

It could be related to the jumbo frames changes. Its an issue with only some network devices because 141 boots just fine on my laptop with a broadcom Ethernet boots just fine.

comment:5 by waddlesplash, 2 years ago

Yeah, it probably is. I think I might have an idea about that.

How much RAM does this system have?

comment:6 by jason123santa, 2 years ago

this system has 1gb of ram and the laptop that works fine has 2gb of ram

Last edited 2 years ago by jason123santa (previous) (diff)

comment:7 by waddlesplash, 2 years ago

Can you post a syslog of a successful boot on the device that fails with ..141?

comment:8 by jason123santa, 2 years ago

Where would I get a syslog of the boot?

in reply to:  8 comment:9 by bipolar, 2 years ago

Replying to jason123santa:

Where would I get a syslog of the boot?

You can find the syslog file under the following directory: /boot/system/var/log.

The syslog.old one contains previous kernel messages (gets created when syslog reaches certain size, 512 KB, IIRC).

Version 0, edited 2 years ago by bipolar (next)

by jason123santa, 2 years ago

Attachment: syslog.ticket-17766​ added

comment:10 by jason123santa, 2 years ago

I added the syslog of the computer on 102

comment:11 by waddlesplash, 2 years ago

Please retest after hrev56149.

comment:12 by jason123santa, 2 years ago

Still brings me to the kernel debugging land

comment:13 by jason123santa, 2 years ago

still the same kernel error on the latest haiku

comment:14 by waddlesplash, 2 years ago

OK. I disabled jumbo MTUs for this driver in hrev56160. See if the problem goes away after that.

comment:15 by jason123santa, 2 years ago

on the latest nightly 160 it still has the kernel error

comment:16 by waddlesplash, 2 years ago

Actually this may be really related to the NVIDIA driver. Please retest after hrev56163.

comment:17 by jason123santa, 2 years ago

still kernel error on the latest nightly

comment:18 by waddlesplash, 2 years ago

Which hrev, please? Is it indeed >= hrev56163?

Please post a new screenshot on this version.

by jason123santa, 2 years ago

Attachment: PXL_20220609_232944288.jpg​ added

kernel error on 164

comment:19 by jason123santa, 2 years ago

i get to desktop and go to settings and it shows the revision 56177 so it boots just fine

comment:20 by waddlesplash, 2 years ago

Milestone: Unscheduled → R1/beta4
Resolution: → fixed
Status: new → closed

Very good, thanks for your patience in testing!

Note: See TracTickets for help on using tickets.