Subject: no initrd: panic on boot
Package: kernel-image-2.6.6-i386
Version: 2.6.6-2
Severity: grave
Tags: sid
On two of my PIII systems (one server, one desktop) I've installed the
2.6.6-2-686 package which fails to boot. Just when accessing the initrd the
error messages run over the screen too
the initrd repairs the system.
Please let me know what I can do to help find this bug. I attached some
useful information P.S. Thank you in advance for looking at this!
Best regards
Kevin Price
In the unbootable state, The serial console says this:
[...]---snip
Begin: Running /scripts/local-top
maximilian attems schrieb:
is it reproducible?
Yes. I updated a bunch of packages, making the slug unbootable. Then I
flashed the backup. After a normal boot, I installed initramfs-tools
0.91e, flashed again, which made it boot OK. Then I updated only
initrd-tools to 0.92, making it unbootable
Hi!
Martin Michlmayr schrieb:
I just tried (on arm) and it works for me. CCing debian-arm. Anyone
else seeing problems with 2.6.25?
Yes, I can confirm this bug on armel. Thanks Martin fo CCing debian-arm.
In order to reproduce this, I installed 2.6.25-1-ixp4xx_2.6.25-1_armel
onto my
Martin Michlmayr schrieb:
Cool, that'd be great!
Here we go:
Ethernet eth0: MAC address 00:14:bf:65:db:3d
IP: 192.168.0.1/255.255.255.0, Gateway: 192.168.0.1
Default server: 0.0.0.0, DNS server IP: 0.0.0.0
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Martin Michlmayr schrieb:
Can you show me the output of
ls -l /boot
Are you suspecting the initrd size?
My /etc/initramfs-tools/initramfs.conf says MODULES=most, btw.
ls -l /boot
-rw-r--r-- 1 root root 748537 Apr 21 22:05 System.map-2.6.24-1-ixp4xx
-rw-r--r-- 1 root root 762523 Apr 30
Hi again! Problem spotted.
Kevin Price schrieb:
Are you suspecting the initrd size?
My /etc/initramfs-tools/initramfs.conf says MODULES=most, btw.
That was the cause. Chaning modules to dep created an initrd.img with
a size of 2176130, which is less than half the size of
-rw-r--r-- 1 root
Martin Michlmayr schrieb:
Kevin, since you have a serial console, are you interested in testing
the patches in #451882 and #421359?
Yes. My slug is now compiling apex-1.4.15 with the patch from #451882
(CONFIG_RAMDISK_SIZE=0x0050) I am curious if this solves this bug
and I will let you
Martin Michlmayr schrieb:
You'll also need the patch from #421359, otherwise the new APEX is not
written to flash.
Yeah. I was thinking from a more low-level point of view and flashed the
apex binary myself with the script. The result is good: The large initrd
(modules=all) boots fine with
Martin Michlmayr schrieb:
The 2.6.26-rc2 test image is available from
http://people.debian.org/~tbm/armel/kernel/r11383/
The fixed 2.6.25 package will be uploaded in the near future.
At least the 2.6.26-rc2 makes my slug unbootable. Again, I need some
time to hook the serial console up to
Kevin Price schrieb:
Martin Michlmayr schrieb:
The 2.6.26-rc2 test image is available from
http://people.debian.org/~tbm/armel/kernel/r11383/
The fixed 2.6.25 package will be uploaded in the near future.
At least the 2.6.26-rc2 makes my slug unbootable. Again, I need some
time to hook
in initramfs.conf. before installing
2.6.25-3. The initrd became 3840262 bytes small, which is fine. All the
necessary modules are there too.
Thanks a lot for that good piece of work!
--
Kevin Price
http://www.kevin-price.de/
signature.asc
Description: OpenPGP digital signature
.
That answers my question. Thanks Joachim for pinpointing this. I added
my kernel version for completeness.
--
Kevin Price
http://www.kevin-price.de/
signature.asc
Description: OpenPGP digital signature
I just saw that the upstream maintainer had noted the version numbering
in the very commit that broke my WiFi.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/ath10k/QCA9377/hw1.0?id=56e5de3261877e5ca9df285e0751368c72b0861a
What I've not tried is upstream's
linux-image-4.9.0-8-amd64_4.9.130-2 from stretch.
Best regards
Kevin Price
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=
Dear maintainer,
This didn't fix this bug.
Am 06.05.19 um 23:36 schrieb Debian Bug Tracking System:
> #919632: "New" firmware instantly crashes on QCA9377
>
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings
elp you.
Please also specify whether you'd like me to do that testing under
6.1.0-15, in which I cannot even invoke sudo, or under 6.1.0-13, which
will do anything fine.
Thanks a lot in advance, and HTH!
--
Kevin PriceContent-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Conte
I confirm that 6.1.66-1 (6.1.0-15) severely breaks my
amd64/bookworm/gnome physical machine, which runs fine with 6.1.52-1 and
6.1.55-1.
Am 10.12.23 um 20:24 schrieb Andrew M.A. Cater:
> On Sun, Dec 10, 2023 at 08:02:03PM +0100, Kevin Price wrote:
>> Am 09.12.23 um 19:09 schrieb D
let me know what kernel version you want me to test, if they're
provides as debian binaries. I'd be glad to help, probably not only for
my own sake. Bear with me I'm unwilling to build kernel packages myself,
due to lack of computing resources. HTH
--
Kevin Price Mon Dec 11 00:54:03
Control: affects -1 + src:broadcom-sta linux-image-6.1.0-15-amd64
@other affected users: What wifi drivers are you using, and do they
taint your kernel?
Am 11.12.23 um 13:27 schrieb Kevin Price:
> Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:
> Need any more logfiles or t
es/dkms/wl.ko
license:MIXED/Proprietary
alias: pci:v*d*sv*sd*bc02sc80i*
depends:cfg80211
…"
)
Thank you Salvatore. Let's get this into stable soon.
--
Kevin Price
21 matches
Mail list logo
