January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c8 --- Comment #8 from Daniel Wagner <daniel.wagner(a)suse.com> --- With 6.0 the printk_ratelimited() was replaced with dev_warn_ratelimited() and that seems also to make it appear. I didn't see this message in older logs neither. So this explains why suddenly we are seeing this message. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c7 --- Comment #7 from Chris Puttick <chris(a)twoten.is> --- I ran zypper ref && zypper dup for the first time since last year. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c6 --- Comment #6 from Daniel Wagner <daniel.wagner(a)suse.com> --- I just realize on my own system I also see these warnings, also running kernel 6.0.12-1-default. Could still be a red herring... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c5 --- Comment #5 from Daniel Wagner <daniel.wagner(a)suse.com> --- If you didn't see it before, it means user space was not trying to read the uuid. Hmm, I think we need to figure out why first. Did you update just the kernel or also parts of the user space? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207259] after Kernel update from 6.0 to 6.1
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1207259 https://bugzilla.suse.com/show_bug.cgi?id=1207259#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com, | |peter_haak_otd(a)web.de Flags| |needinfo?(peter_haak_otd@we | |b.de) --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- You write that the kernel update broke HDMI output, but you show that the system booted into neither kernel 6.0 nor 6.1? Please explain. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207259] New: after Kernel update from 6.0 to 6.1
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207259 Bug ID: 1207259 Summary: after Kernel update from 6.0 to 6.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: peter_haak_otd(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- after update no boot and since update no hdmi output with Linux bananapi r2 5.16.14-1-default #1 SMP Fri Mar 11 12:33:34 UTC 2022 (80acc65) armv7l armv7l armv7l GNU/Linux the machine started but no hdmi output only the kernel is not updatet -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c4 --- Comment #4 from Chris Puttick <chris(a)twoten.is> --- NB parsing the logs shows the nvme entry only occurred during the failed boots (but may still be a red herring) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c3 --- Comment #3 from Chris Puttick <chris(a)twoten.is> --- Installed nvme-cli, nvme id-ctrl /dev/nvme0 output: NVME Identify Controller: vid : 0x1c5c ssvid : 0x1c5c sn : AD9BN4767109YBG55 mn : PC601 NVMe SK hynix 512GB fr : 80002111 rab : 4 ieee : ace42e cmic : 0 mdts : 6 cntlid : 0x1 ver : 0x10300 rtd3r : 0x7a120 rtd3e : 0x1e8480 oaes : 0x200 ctratt : 0 rrls : 0 cntrltype : 0 fguid : 00000000-0000-0000-0000-000000000000 crdt1 : 0 crdt2 : 0 crdt3 : 0 nvmsr : 0 vwci : 0 mec : 0 oacs : 0x17 acl : 3 aerl : 7 frmw : 0x16 lpa : 0x2 elpe : 255 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 359 cctemp : 360 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 0 unvmcap : 0 rpmbs : 0 edstt : 30 dsto : 1 fwug : 0 kas : 0 hctma : 0x1 mntmt : 273 mxtmt : 358 sanicap : 0x2 hmminds : 0 hmmaxd : 0 nsetidmax : 0 endgidmax : 0 anatt : 0 anacap : 0 anagrpmax : 0 nanagrpid : 0 pels : 0 domainid : 0 megcap : 0 sqes : 0x66 cqes : 0x44 maxcmd : 0 nn : 1 oncs : 0x5f fuses : 0 fna : 0 vwc : 0x1 awun : 0 awupf : 0 icsvscc : 1 nwpc : 0 acwu : 0 ocfs : 0 sgls : 0 mnan : 0 maxdna : 0 maxcna : 0 subnqn : ioccsz : 0 iorcsz : 0 icdoff : 0 fcatt : 0 msdbd : 0 ofcs : 0 ps 0 : mp:6.3000W operational enlat:5 exlat:5 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- active_power_workload:- ps 1 : mp:2.4000W operational enlat:30 exlat:30 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- active_power_workload:- ps 2 : mp:1.9000W operational enlat:100 exlat:100 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- active_power_workload:- ps 3 : mp:0.0500W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- active_power_workload:- ps 4 : mp:0.0040W non-operational enlat:1000 exlat:9000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- active_power_workload:- -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c2 --- Comment #2 from Daniel Wagner <daniel.wagner(a)suse.com> --- FWIW, the nvme log is likely to be a red herring. The warning was there for a long time (since v4.12) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 18 Jan '23

18 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c1 Daniel Wagner <daniel.wagner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.wagner(a)suse.com --- Comment #1 from Daniel Wagner <daniel.wagner(a)suse.com> --- This message is triggered when user space tries to read /sys/class/nvme/nvme0/nvme0n1/uuid Given that the normal boot process doesn't work indicates that systemd waits for a device to appear with a given uuid. Can you provide information on the nvme device? nvme id-ctrl /dev/nvme0 -- You are receiving this mail because: You are the assignee for the bug.

1 0