mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guy Martin <gmsoft@tuxicoman.be>
To: linux-kernel@vger.kernel.org
Subject: 64bit kernel not booting with CONFIG_PRINTK_TIME=y
Date: Wed, 16 Jul 2008 20:45:52 +0200	[thread overview]
Message-ID: <20080716204552.56270e7c@tuxicoman.be> (raw)



Hi all,


I've been trying several times to boot a 64bit kernel with
CONFIG_PRINTK_TIME=y and each time it failed.

This is the output of my L2000 when trying to do so :

Information: No console specified on kernel command line. This is
normal. PALO will choose the console currently used by firmware
(serial). Command line for kernel: 'root=/dev/md1 console=ttyS0
palo_kernel=2/vmlinux' Selected kernel: /vmlinux from partition 2
ELF64 executable
Entry 00100000 first 00100000 n 2
Segment 0 load 00100000 size 4997120 mediaptr 0x1000
Segment 1 load 00634000 size 640576 mediaptr 0x4c5000
Branching to kernel entry point 0x00100000.  If this is the last
message you see, you may need to switch your console.  This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org


************* SYSTEM ALERT **************
SYSTEM NAME: uninitialized
DATE: 07/16/2008 TIME: 17:47:39
ALERT LEVEL: 7 = reserved

REASON FOR ALERT
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated   SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
       FLASH    FLASH         OFF       ON         ON
LED State: Running non-OS code.  Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x0000007000FF6292 000000F0 F0000000 - type  0 = Data Field Unused
0x5800087000FF6292 00006C06 10112F27 - type 11 = Timestamp 07/16/2008
17:47:39 A: ack read of this entry - X: Disable all future alert
messages Anything else skip redisplay the log entry
->Choice:Timeout!  
*****************************************



Recompiling with CONFIG_PRINTK_TIME=n makes it works straight away.

How can this be troubleshooted ? Any idea what the problem could be ?

I'm using gcc-4.2.4 with kernel 2.6.26 but I've have had very same
results with gcc-4.1.2 and 2.6.25.


Cheers,
  Guy

-- 
Guy Martin
Gentoo Linux - HPPA port lead


             reply	other threads:[~2008-07-16 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 18:45 Guy Martin [this message]
2008-07-16 18:56 ` Kyle McMartin
2008-07-17 18:33   ` Kyle McMartin
     [not found] <20080717190502.74c238d5@bleh.bxl.tuxicoman.be>
2008-07-19 21:54 ` Kyle McMartin
2008-07-19 23:04   ` Kyle McMartin
2008-07-20  9:23     ` Guy Martin
2008-07-29  4:29       ` Kyle McMartin
2008-07-29 17:42         ` Guy Martin
  -- strict thread matches above, loose matches on Subject: below --
2008-07-16 17:58 Guy Martin

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=20080716204552.56270e7c@tuxicoman.be \
    --to=gmsoft@tuxicoman.be \
    --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

all inboxes | Powered by JetHome®