mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: KML <linux-kernel@vger.kernel.org>
Subject: Did sombody leave the debugging on for latest 2.6 bk's ?
Date: Sun, 05 Oct 2003 04:27:36 +0200	[thread overview]
Message-ID: <1065320855.11114.262.camel@nosferatu.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

Hi

Get below all over the place.  I have not changed anything particular
on the box, and its not been doing this with test5 kernels.  Anything
specific I can look at ?  Hardware issues that is shown now with
debugging turned up or something ?

-------
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
nt: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
syslogd: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
cc1: page allocation failure. order:2, mode:0x20
------


Thanks,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2003-10-05  2:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1065320855.11114.262.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome