You are not logged in.

#1 2021-10-10 13:23:08

itarill
Member
Registered: 2020-06-03
Posts: 14

[solved] boot stuck: i915 drm error

So I set up btrfs in my new arch install on my old laptop. I made an error with some packages and decided to try booting my snapshot before that error in GRUB. My issue is that GRUB is stuck at this step (on LTS kernel):

Bluetooth: hci0: unexpected event for opcode 0xfc2f

On linux kernel it goes one step further:

i915 0000:00:02.0: [drm] *ERROR* Failed to write source OUI.

Now I have absolutely no clue based on my google searches to find how to solve this.

Last edited by itarill (2021-10-13 18:36:13)

Offline

#2 2021-10-10 18:50:44

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

https://bbs.archlinux.org/viewtopic.php … 2#p1997062

Can you boot w/ the "nomodeset" parameter or the multi-user.target (2nd link below)?

Offline

#3 2021-10-10 20:50:43

itarill
Member
Registered: 2020-06-03
Posts: 14

Re: [solved] boot stuck: i915 drm error

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 2#p1997062

Can you boot w/ the "nomodeset" parameter or the multi-user.target (2nd link below)?

Thanks for responding smile
With the nomodeset the boot hands at the Bluetooth message above. With regards to multi-user.target, I cannot edit the snapshots so I don't really know how I would get about adjusting that...?

Offline

#4 2021-10-10 20:51:53

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

the wiki wrote:


Alternatively, append one of the following kernel parameters to your bootloader:
systemd.unit=multi-user.target (which roughly corresponds to the old runlevel 3),…

Offline

#5 2021-10-10 21:15:55

itarill
Member
Registered: 2020-06-03
Posts: 14

Re: [solved] boot stuck: i915 drm error

seth wrote:
the wiki wrote:


Alternatively, append one of the following kernel parameters to your bootloader:
systemd.unit=multi-user.target (which roughly corresponds to the old runlevel 3),…

Thanks - I am kinda new with this.
So with multi-user.target I reach tty and I can login.

sudo dmesg | grep err

gives a single error on top a bunch of interrupts:

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 

Not sure how to continue. But I guess the problem that hinders booting comes after multi-user.target so there was no point checking this anyway.

Last edited by itarill (2021-10-10 21:23:57)

Offline

#6 2021-10-11 07:16:17

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

is irrelevant.
The system boots, but you GUI target doesn't start (properly)

=> what is your graphical target? (some DM, startx/xinit, some wayland session …)
Do you have xf86-video-intel installed? Try to remove it.

Offline

#7 2021-10-11 08:12:22

itarill
Member
Registered: 2020-06-03
Posts: 14

Re: [solved] boot stuck: i915 drm error

seth wrote:

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

is irrelevant.
The system boots, but you GUI target doesn't start (properly)

=> what is your graphical target? (some DM, startx/xinit, some wayland session …)
Do you have xf86-video-intel installed? Try to remove it.

Right. So my boot messages in order:

Reached target Multi-User System
Started SDDM
Reached target Graphical Interface
i915 drm error
Started Hostname Service
Bluetooth hci unexpected event
915 drm error

I do have xf86-video-intel, I tried removing it as well. In my bios I have the option to disable the nVidia GPU or go with intel, I have tried both settings. I also installed nvidia and nvidia-utils. These yielded no change.

Last edited by itarill (2021-10-11 08:12:43)

Offline

#8 2021-10-11 08:19:40

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

Please post a complete system journal covering a failed SDDM start ("sudo journalctl -b" for the current one) and your xorg log, https://wiki.archlinux.org/title/Xorg#General

Offline

#9 2021-10-11 21:08:34

itarill
Member
Registered: 2020-06-03
Posts: 14

Re: [solved] boot stuck: i915 drm error

seth wrote:

Please post a complete system journal covering a failed SDDM start ("sudo journalctl -b" for the current one) and your xorg log, https://wiki.archlinux.org/title/Xorg#General

Journalctl
Xorg
Xorg.old

Thanks. As an afterthought, you probably need the Xorg.old for troubleshooting.

Last edited by itarill (2021-10-11 21:11:56)

Offline

#10 2021-10-11 21:18:38

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

This is a running X11 server and the journal shows SDDM starting and you logging into a plasma session ~10 seconds later?
Also there's no i915 error and the nvidia chip isn't utilized at all.

Is this supposed to cover a failing boot/sddm start?

Edit: the old xorg log runs successfully for 2 seconds, whatever starts there (SDDM?) must have insta-crashed.

Last edited by seth (2021-10-11 21:20:44)

Offline

#11 2021-10-11 21:38:03

itarill
Member
Registered: 2020-06-03
Posts: 14

Re: [solved] boot stuck: i915 drm error

Should I try switching to another DM?

Sorry, I may have misunderstood previously. This is the journal for the crashed boot attempt:
journal-1

Last edited by itarill (2021-10-11 21:46:10)

Offline

#12 2021-10-12 06:42:52

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 14,007

Re: [solved] boot stuck: i915 drm error

No failure there either. Which exact journal command are you invoking? FWIW if you know the date of when the failure happened you can also pass a date and time range to journalctl: https://wiki.archlinux.org/title/System … ing_output

There's also a chance that the fact you are booting a snapshot confuses journalctl

Offline

#13 2021-10-12 06:57:07

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

Oct 11 22:57:44 balu-lenovo systemd-logind[308]: New session c1 of user sddm.
…
Oct 11 22:57:53 balu-lenovo systemd-logind[308]: New session 2 of user balu.

The journal again shows you logging in as "balu" ~10 seconds after SDDM starts.
What happens then is that the sesion runs for ~25 minutes until

Oct 11 23:24:13 balu-lenovo systemd-logind[308]: System is rebooting.

Then plasma does its crash-on-shutdown thing and the journal stops at

Oct 11 23:25:44 balu-lenovo systemd[1]: Reached target System Reboot.
Oct 11 23:25:44 balu-lenovo systemd[1]: Shutting down.
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=16 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=15 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=14 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=13 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=12 op=UNLOAD
Oct 11 23:25:44 balu-lenovo audit: BPF prog-id=11 op=UNLOAD
Oct 11 23:25:44 balu-lenovo systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog
Oct 11 23:25:44 balu-lenovo systemd[1]: Set hardware watchdog to 10min.
Oct 11 23:25:44 balu-lenovo kernel: watchdog: watchdog0: watchdog did not stop!
Oct 11 23:25:44 balu-lenovo systemd-shutdown[1]: Syncing filesystems and block devices.
Oct 11 23:25:44 balu-lenovo systemd-journald[212]: Journal stopped

There was an interactive konsole window and you used it to

Oct 11 22:58:05 balu-lenovo sudo[833]:     balu : TTY=pts/1 ; PWD=/home/balu ; USER=root ; COMMAND=/usr/bin/journalctl -b

There're again no i915 errors and no indicators of the system failing to boot whatsoever?
Are you somehow switching snapshots between "System doesn't boot" and "I get the journal"? (the journal shows the current LTS kernel booting…)

Offline

#14 2021-10-12 08:06:24

itarill
Member
Registered: 2020-06-03
Posts: 14

Re: [solved] boot stuck: i915 drm error

I'm starting to feel really dumb. This is the snapshot journal, 3rd time's the charm: https://pastebin.com/z25tR2Ys

Previously, not realizing I have access to tty on a stuck boot I tried snapshot boot -> regular boot -> journal -1 , but I guess it does not work like that.

Offline

#15 2021-10-12 09:10:36

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

Oct 12 09:56:26 balu-lenovo sddm[368]: Display server starting...
Oct 12 09:56:26 balu-lenovo sddm[368]: Adding cookie to "/var/run/sddm/{855e0bf9-c9db-4dca-b600-57205bfc6183}"
Oct 12 09:56:26 balu-lenovo sddm[368]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{855e0bf9-c9db-4dca-b600-57205bfc6183} -noreset -displayfd 17
Oct 12 09:56:26 balu-lenovo sddm[368]: Failed to read display number from pipe
Oct 12 09:56:26 balu-lenovo sddm[368]: Display server stopping...
Oct 12 09:56:26 balu-lenovo sddm[368]: Attempt 3 starting the Display server on vt 1 failed
Oct 12 09:56:26 balu-lenovo sddm[368]: Could not start Display server on vt 1

Better ;-)
Now we'll need an xorg log from that run.

One thnig right off the bat is that your crng is late, check https://wiki.archlinux.org/title/Haveged

Offline

#16 2021-10-12 21:22:10

itarill
Member
Registered: 2020-06-03
Posts: 14

Re: [solved] boot stuck: i915 drm error

seth wrote:
Oct 12 09:56:26 balu-lenovo sddm[368]: Display server starting...
Oct 12 09:56:26 balu-lenovo sddm[368]: Adding cookie to "/var/run/sddm/{855e0bf9-c9db-4dca-b600-57205bfc6183}"
Oct 12 09:56:26 balu-lenovo sddm[368]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{855e0bf9-c9db-4dca-b600-57205bfc6183} -noreset -displayfd 17
Oct 12 09:56:26 balu-lenovo sddm[368]: Failed to read display number from pipe
Oct 12 09:56:26 balu-lenovo sddm[368]: Display server stopping...
Oct 12 09:56:26 balu-lenovo sddm[368]: Attempt 3 starting the Display server on vt 1 failed
Oct 12 09:56:26 balu-lenovo sddm[368]: Could not start Display server on vt 1

Better ;-)
Now we'll need an xorg log from that run.

One thnig right off the bat is that your crng is late, check https://wiki.archlinux.org/title/Haveged

I need to dive deeper in the Haveged topic. In the meanwhile, I checked the /var/log/Xorg.0.log file while booting the snapshot, and the last mod date as well as the log file time is from this morning from the successful boot before the snapshot was taken (I guess), meaning that it does not get overwritten on booting the snapshot. Can I get around this somehow?

Offline

#17 2021-10-12 21:25:36

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

Boot the multi-user.target and try to run "Xorg" instead of SDDM.
If the X11 server doesn't even make it to writing a log, there's probably some unresolvable library or something - trying to start the display server process directly will hopefully reveal that.

Offline

#18 2021-10-12 22:28:11

itarill
Member
Registered: 2020-06-03
Posts: 14

Re: [solved] boot stuck: i915 drm error

I feel ashamed having other people running around in circles for me smile
Having no experience with snapshots I did not realize that it is the read only property that prevented my boot to X. Changing that, I can now boot a snapshot. I cannot say for certain if this is an intended feature (ro images unbootable to X), or it is still a bug in my system.

Offline

#19 2021-10-13 06:03:09

seth
Member
Registered: 2012-09-03
Posts: 23,866

Re: [solved] boot stuck: i915 drm error

Snapshots should™ only be readoly if you created them passing "-r"

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB