Bug#777243: Boot fails due to missing ext4 module
W dniu 07.02.2015 o 02:18, Ben Hutchings pisze: On Fri, 2015-02-06 at 22:57 +0100, Rafal Pietrak wrote: W dniu 06.02.2015 o 20:31, Ben Hutchings pisze: Control: retitle -1 Boot fails due to missing ext4 module On Fri, 2015-02-06 at 18:48 +0100, Rafał Pietrak wrote: [--] Can you clarify how far the system boots? Does it stop at a shell with the prompt '(initramfs)'? Stops at: maintenance mode. Give root password or control-D Oh, so this is not an initramfs problem as I suspected. Frankly, I woulnd't tell. And I think, it does that because /srv/pgdat is ext4 and cannot be mounted because of missing ext4.ko within the kernel. [...] Then I think the package is not properly installed. Naturally someting is wrong. But since the wheezy to jessie upgrade, there was at least one time the kernel was updated too. And the problem remains while the update didn't complain about anything. In any case, first thing I did (after reviving the system to the point I had a usable /usr) I did apt-get install --reinstall both kernels. No errors reported. Something really strange did happen on the moment of transition from wheezy to jessie. But I'm lost guessing which package to blame (apart from ext4, my notebook keyboard stopped working then, it works only when I boot i485 kernel - the one without ext4 - and only when I boot it with sysvinit scripts, otherwise it's dead). My best guess is that the problem has something to do with the kernel. May be the load order of modules?? Boot screen shows two red FAILURE lines (somewhat apart from one another) reporting something along the lines of unable to load module, but dissapears quickly and isn't copied to neither dmesg nor kern.log nos syslog. Do these commands produce any output? debsums -c linux-image-3.2.0-4-486 debsums -c linux-image-3.16.0-4-586 both report OK (echo $? -- 0). If not, does modprobe start working if you run 'depmod' first? no, it didn't. (although I can see /lib/modules/3.2*/modules* files were touched). And a direct insmod /lub/modules/3.2.*/kernel/fs/ext4/ext4.ko doesn't work either. -R -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d5ce8a.5070...@ztk-rp.eu
linux 3.18.6 exp upload
hello, I do plan to upload today sometime after 22h UT. This should be the last 3.18, as afterwards exp will move to 3.19 base. -- maks signature.asc Description: Digital signature
Bug#763155: Bug#764528: Cross-referencing i915 kernel bugs on EEEpc
tag 764528 + patch jessie tag 763155 + patch jessie thanks There appears to be a rather easy patch available: http://patchwork.freedesktop.org/patch/38659/ Quietly reject attempts to create non-pagealigned stolen objects Judging from the discussion, it is not a real bug. It is an unexpected behavior (Bios using non-aligned video buffer, supported by the hardware, but not aligned to the driver requirements). The patch essentially replaces the BUG_ON with a log statement and then returns null, which is supposed to reliably work. (Without reusing the memory the bios used.) This probably won't be the final fix. There is some discussion here: http://permalink.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/52613 which suggests that instead it may be desirable to reuse the bios allocation, and just align it as desired. But since this causes boot issues on some eeePC models (apparently, it depends on the bios and CPU), and the patch is quite simple, it should be considered for jessie, even if the patch isn't the long-term solution yet. Thank you. Regards, Erich On Sun, Nov 30, 2014 at 10:59 PM, Erich Schubert er...@debian.org wrote: https://bugs.freedesktop.org/show_bug.cgi?id=86883 Not sure if kernel bugzilla wouldn't have been the better address, given that the BUG_ON clearly is in kernel code. But I guess it's the same developers anyway. Regards, Erich -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAGKbab9pZZoom2w1cGpDH7zxSf=j86g0mn7uok8rdu5mbkv...@mail.gmail.com
Bug#777243: Boot fails due to missing ext4 module
On Sat, 2015-02-07 at 18:21 +0100, Rafał Pietrak wrote: W dniu 07.02.2015 17:48, Ben Hutchings pisze: On Sat, 2015-02-07 at 09:36 +0100, Rafal Pietrak wrote: [...] [---] And a direct insmod /lub/modules/3.2.*/kernel/fs/ext4/ext4.ko doesn't work either. How does it fail? What error messages do you see (both at the shell and in the kernel log)? The command is silent, returns 0 (meaning: echo $? == 0 ... which is surprising when I think of it now, since strace reports exit=1), and the log contains nothing. I only know that it faile because neither lsmod show it, nor mount starts working. But I've also done a strace of the insmod (attached) - may be this'll give something. write(2, insmod: ERROR: could not insert ..., 113insmod: ERROR: could not insert module /lib/modules/3.2.0-4-486/kernel/fs/ext4/ext4.ko: Unknown symbol in module ) = 113 This implies that the wrong kernel image is being loaded. As you are using GRUB this is surprising. What does 'type insmod' say? And regarding the screen reporting errors during the boot; this is the first one (when booting 3.16*586 kernel): Failed to start Load Kernel Modules. Very strange... Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#777243: Boot fails due to missing ext4 module
W dniu 07.02.2015 o 18:47, Ben Hutchings pisze: On Sat, 2015-02-07 at 18:21 +0100, Rafał Pietrak wrote: W dniu 07.02.2015 17:48, Ben Hutchings pisze: On Sat, 2015-02-07 at 09:36 +0100, Rafal Pietrak wrote: [...] [---] And a direct insmod /lub/modules/3.2.*/kernel/fs/ext4/ext4.ko doesn't work either. How does it fail? What error messages do you see (both at the shell and in the kernel log)? The command is silent, returns 0 (meaning: echo $? == 0 ... which is surprising when I think of it now, since strace reports exit=1), and the log contains nothing. I only know that it faile because neither lsmod show it, nor mount starts working. But I've also done a strace of the insmod (attached) - may be this'll give something. write(2, insmod: ERROR: could not insert ..., 113insmod: ERROR: could not insert module /lib/modules/3.2.0-4-486/kernel/fs/ext4/ext4.ko: Unknown symbol in module ) = 113 This implies that the wrong kernel image is being loaded. As you are using GRUB this is surprising. That was my first guess, so I did --reinstall of the kernel as soon as I had /usr on line. But to no avail. What does 'type insmod' say? === /sbin/insmod $ file /sbin/insmod /sbin/insmod is a symlink to /bin/kmod $ file /bin/kmon ELF 32-bit Build(sha1)=86da...ef68, stripped $ dpkg -s kmod ... Version: 18-3 === Sorry for the shorten output, but I don't have the notebook operational, yet (under 486 kernel); so I'm sending it from another machine typeing it in manually. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d65547.8090...@ztk-rp.eu
Bug#777243: Boot fails due to missing ext4 module
On Sat, 2015-02-07 at 09:36 +0100, Rafal Pietrak wrote: [...] Do these commands produce any output? debsums -c linux-image-3.2.0-4-486 debsums -c linux-image-3.16.0-4-586 both report OK (echo $? -- 0). If not, does modprobe start working if you run 'depmod' first? no, it didn't. (although I can see /lib/modules/3.2*/modules* files were touched). And a direct insmod /lub/modules/3.2.*/kernel/fs/ext4/ext4.ko doesn't work either. How does it fail? What error messages do you see (both at the shell and in the kernel log)? Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
