On Sun, 2014-01-12 at 19:15 +0100, Émeric MASCHINO wrote: > 2014/1/7 Ben Hutchings <email@example.com>: > > On Mon, 2014-01-06 at 10:15 +0100, Émeric MASCHINO wrote: > > > > I don't understand that - I still have 3.2 installed on this unstable > > (i386) system and can still boot it. How does it go wrong? > > It seems to crash with something wrong with systemd. > You're getting in loop a callstack similar to the one starting at > 32.334142, every ~28 seconds. > And you can wait forever, never reaching login: [...] > [ 32.239142] Unable to handle kernel paging request at virtual address 40039f8 > 0a0000032 > [ 32.334142] systemd-udevd: Oops 11012296146944  > [ 32.338131] Modules linked in: > [ 32.338131] > [ 32.338131] Pid: 47, CPU 0, comm: systemd-udevd > [ 32.338131] psr : 00001210085a6010 ifs : 8000000000000001 ip : [<a0000001002 > 41e51>] Not tainted (3.2.0-4-mckinley Debian 3.2.51-1a~test) > [ 32.338131] ip is at mntget+0x11/0x60 So this is a crash, not an incompatibility with the newer systemd. [...] > > I really need to know whether -O1 works for 3.2; I can't just > > speculatively change it in a stable update. > > I understand that. Can you test the 3.2 kernel with sysvinit, in case this is a bug that's specifically provoked by systemd? Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got.
Description: This is a digitally signed message part