Prev: CPU eaten by unknown code
Next: doc: kprobetrace: Add the explanation to remove probe points
From: Sedat Dilek on 24 Dec 2009 20:20
Hi,

I build linux-2.6.33-rc2 on a Debian/sid 32-bit host.
Unfortunately, this kernel falls in an unusable state (sort of loop)
and does not a normal startup.

With this setting (see below), I hoped to catch the early
boot-messages (but, no success):

# cat /etc/default/bootlogd
# Run bootlogd at startup ?
BOOTLOGD_ENABLE=Yes

Finally, I could take a picture [1].
It seems to be that latest ACPI patches are breaking my system (speculating).

Q: How can I log such early boot (error) messages to give a detailled log?

Hope this helps fixing the problem.

Kind Regards,
- Sedat -


[1] http://files.iniza.org/linux-kernel/DSCN2134.JPG
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: CPU eaten by unknown code
Next: doc: kprobetrace: Add the explanation to remove probe points