Memory is exhausted error when trying to run kernel from upstream sources
Hello, I am unsure if this is the right place to ask. I am trying to build the upstream mainline kernel (6.7-rc6) as instructed at https://wiki.debian.org/BuildingKernelFromUpstreamSources for troubleshooting purposes. The build and installation were successful, but when I try to boot the kernel, I get an error stating that my memory (RAM) is exhausted. My system has 64 GB of RAM, so that seems unlikely. Here are a picture of the error message (in German) and my kernel .config: https://data.moto9000.moe/m/IMG_20231219_145904_1.jpg https://bin.linux.pizza/?2d9f547017a8c36a#45SspcmKnFHjS2h9qxMT4QHXN7tEc7GV9A9qPsqhFT3h Greetings Julian Groß OpenPGP_signature.asc Description: OpenPGP digital signature
Memory is exhausted error when trying to run kernel from upstream sources
Hello, I am unsure if this is the right place to ask. I am trying to build the upstream mainline kernel (6.7-rc6) as instructed at https://wiki.debian.org/BuildingKernelFromUpstreamSources for troubleshooting purposes. The build and installation were successful, but when I try to boot the kernel, I get an error stating that my memory (RAM) is exhausted. My system has 64 GB of RAM, so that seems unlikely. Here are a picture of the error message (in German) and my kernel .config: https://data.moto9000.moe/m/IMG_20231219_145904_1.jpg https://bin.linux.pizza/?2d9f547017a8c36a#45SspcmKnFHjS2h9qxMT4QHXN7tEc7GV9A9qPsqhFT3h Greetings Julian Groß OpenPGP_0xAF605C87F9E5AE94.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1028309: linux-image-6.0.0-6-amd64: Regression in Kernel 6.0: System partially freezes with "nvme controller is down"
My computer just froze on Kernel version 5.19.11-1. Though nothing got logged. Now I don't know if this is the same issue and newer kernels just behave better in terms of logging, or if this is a different issue.. I guess I will add a second screen to my computer, open journalctl on there, and point a camera at it to capture the issue. I am pretty sure that I have had it not log on a 6.0 Kernel as well, but since I have been troubleshooting this for weeks now I am not completely sure. OpenPGP_0xAF605C87F9E5AE94.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1028309: linux-image-6.0.0-6-amd64: Regression in Kernel 6.0: System partially freezes with "nvme controller is down"
On Mon, 09 Jan 2023 14:09:30 +0100 Diederik de Haas wrote: > https://wiki.debian.org/DebianKernel/GitBisect describes a procedure to find > the exact commit which introduced the issue you reported, but it's often > faster to first narrow down the range using snapshot.d.o. The way I understand the `git bisect`, and with the issue taking sometimes days to happen, I will be sitting on this for months by the way. What happens if I give `git bisect` a false “good”? Because it is perfectly possible that my computer will run fine for 48 hours; I will tell git bisect that the revision is good; But the issue actually didn't trigger just by chance, instead of it not being in the revision. OpenPGP_0xAF605C87F9E5AE94.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1028309: linux-image-6.0.0-6-amd64: Regression in Kernel 6.0: System partially freezes with "nvme controller is down"
Thanks for your help. > Unstable currently has version 6.1.4-1, could you try that to see whether the > issue is already resolved? Version 6.1.4-1 shows the same issue. > If not, then we need to figure out when the issue first occurred. > Via https://snapshot.debian.org/binary/linux-image-amd64/ you can find several > other kernel versions from the 6.0.x series, could you try those? > It's probably quickest to try 6.0~rc7-1~exp1 first. I will try 6.0~rc7-1~exp1 next. OpenPGP_0xAF605C87F9E5AE94.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1023631: firmware-misc-nonfree: Possibly missing firmware for Creative Labs Sound Blaster Z PCIe sound card
Package: firmware-misc-nonfree Version: 20221012-1 Severity: normal Dear Maintainer, I have been running into weird behaviour on my Creative Labs Sound Blaster Z (Serial number either SB1500 or SB1502). Just now I noticed that a seemingly related firmware file doesn't get loaded. Here is a section out of dmesg: [9.591329] snd_hda_intel :02:00.0: firmware: failed to load ctefx-desktop.bin (-2) [9.591355] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [9.591387] snd_hda_intel :02:00.0: firmware: failed to load ctefx-desktop.bin (-2) [9.591409] snd_hda_intel :02:00.0: Direct firmware load for ctefx-desktop.bin failed with error -2 [9.592599] snd_hda_intel :02:00.0: firmware: direct-loading firmware ctefx.bin ctefx-desktop.bin shows up in the list of firmware that is supposed to be included in Debian. https://wiki.debian.org/Firmware/List While the driver seems to load a different firmware file, and the sound card works most of the time, the identification in lspci seems wrong, and there is random issues like no audio output until reboot, "electric" audio output until reboot, no audio input until reboot, settings needing to be applied multiple times, and alsactl store failing. lspci reports a "Subsystem: Creative Labs SB1570 SB Audigy Fx", while this card is from a different series and looks completely different from it. Not knowing much about this sort of thing, I am assuming the driver is falling back to the firmware for a different sound card, which might be causing a bunch of my issues. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-misc-nonfree depends on no packages. firmware-misc-nonfree recommends no packages. Versions of packages firmware-misc-nonfree suggests: ii initramfs-tools 0.142 -- no debconf information
