Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
To: linux-mips@linux-mips.org
Subject: Tests of 2.6.23-rc8 on SGI O2
Date: Fri, 28 Sep 2007 11:57:07 +0200	[thread overview]
Message-ID: <1190973427.11251.17.camel@scarafaggio> (raw)

Hi all,
I compiled and tested the latest kernel (from git) for mips on an SGI
O2, in order to check if it fixes a few problems my current kernel has.

The first problem is that a PCI board with a PCI-to-PCI bridge is not
correctly managed. The second problem is the CONFIG_BUILD_ELF64 options
that made all new kernels since 2.6.20 unbootable.

Of course unsetting CONFIG_BUILD_ELF64 worked, and the new kernel booted
correctly.

About the first problem, once the machine booted, the lspci command stil
does not list the available devices on the board. The only listed device
is the PCI bridge.

The relevant parts in syslog are these lines

[...]
Sep 29 00:42:49 sgi kernel: SCSI subsystem initialized
Sep 29 00:42:49 sgi kernel: PCI: Bridge: 0000:00:03.0
Sep 29 00:42:49 sgi kernel:   IO window: disabled.
Sep 29 00:42:49 sgi kernel:   MEM window: disabled.
Sep 29 00:42:49 sgi kernel:   PREFETCH window: disabled.
Sep 29 00:42:49 sgi kernel: PCI: Setting latency timer of device 0000:00:03.0 to 64
Sep 29 00:42:49 sgi kernel: Time: MIPS clocksource has been installed.
Sep 29 00:42:49 sgi kernel: NET: Registered protocol family 2
[...]

Is this a normal behaviour? Should/can I "enable" these windows in any
way?

I also noticed two new problems in this kernel:
A. the connection via an e100 network board is *really* slow: an ssh
connection with public keys take about 40 seconds before the prompt
appear.
B. recompiling with 8mb of frame buffer give an unusable display and
fill my syslog of these messages:
[...]
Sep 27 08:59:18 sgi kernel: CRIME memory error at 0x1800ace0 ST 0x02010000<INV,GBE,NONFATAL>
Sep 27 08:59:18 sgi kernel: CRIME memory error at 0x1800c8e0 ST 0x02010000<INV,GBE,NONFATAL>
Sep 27 08:59:18 sgi kernel: CRIME memory error at 0x1800e4e0 ST 0x02010000<INV,GBE,NONFATAL>
[...]

Thanks a lot,
Giuseppe

             reply	other threads:[~2007-09-28  9:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  9:57 Giuseppe Sacco [this message]
2007-09-28 10:33 ` Tests of 2.6.23-rc8 on SGI O2 Kaj-Michael Lang
2007-09-28 10:33   ` Kaj-Michael Lang
2007-09-30  8:34 ` Using PCI bridges on sgi-ip32 [was: Re: Tests of 2.6.23-rc8 on SGI O2] Giuseppe Sacco
2007-10-01 15:05   ` Maciej W. Rozycki
2007-10-02  1:01     ` Using PCI bridges on sgi-ip32: CONFIG_PCI_DEBUG Giuseppe Sacco
2007-10-02 11:39       ` Maciej W. Rozycki

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=1190973427.11251.17.camel@scarafaggio \
    --to=giuseppe@eppesuigoccas.homedns.org \
    --cc=linux-mips@linux-mips.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