On Fri, 2012-11-02 at 23:37 +0400, jaakov jaakov wrote: > I turned on +x in /etc/init.d/acpi-support and did some final > screenshots with "acpi=off quiet elevator=noop" with kernel 3.2.0-4. > Then I removed, as you suggested, "acpi=off", made screenshots and > tried to produce a sys log. > > Photos Foto-0130, Foto-0131, Foto-0132 show the final stages of > booting with acpi=off. > > Photos Foto-0133, Foto-0134, Foto-0135, Foto-0136, Foto-0137, > Foto-0138 show some stages of the booting process without acpi=off. There is definitely some memory corruption, but it's not going to be easy to work out what caused it. For my future reference: Foto-0135 shows an assertion failure in slab's cache_alloc_refill(): /* * The slab was either on partial or free list so * there must be at least one object available for * allocation. */ BUG_ON(slabp->inuse >= cachep->num); Foto-0136,0137 show a page fault in fpu_copy(). Foto-0138 maybe shows another page fault. > Alas, it seems that SysRq did not produce the right effect, see the > last line on Foto-0138. [...] Sorry, I was running a custom kernel (3.2.33-rc1) when I checked this. You used the right keys but this feature is disabled by default in Debian packaged kernels, due to security concerns. You can re-enable it by adding this line to /etc/sysctl.conf: kernel.sysrq = 1 But this will only produce interesting information if the kernel didn't already crash as shown in your photos 0135-0138. Can you tell me the model of laptop you are using? Can you also test Linux 3.6.6 when it is available (it should be in experimental in a few days). Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot
Attachment:
signature.asc
Description: This is a digitally signed message part