From: Rick Warner <rick@microway.com>
To: linux-kernel@vger.kernel.org
Subject: Re: very strange issue with sata,<4G Ram, and ext3
Date: Wed, 4 May 2005 15:29:54 -0400 [thread overview]
Message-ID: <200505041529.54502.rick@microway.com> (raw)
In-Reply-To: <200504291045.58893.rick@microway.com>
Just sending out a ping on this.. anyone have any ideas?
On Friday 29 April 2005 10:45 am, you wrote:
> On Thursday 28 April 2005 06:48 pm, Alan Cox wrote:
> > On Iau, 2005-04-28 at 17:16, Rick Warner wrote:
> > > On these systems, we are getting ext2 errors from the initrd during
> > > the untarring. Soon after, we start getting seg faults on random
> > > things (looks like stuff caused by the still running dhcp client), and
> > > then a continuous stream of segfaults on the restore script itself
> > > (restore[1]).
> >
> > This sounds almost like the pxe/boot code is still using ram that the
> > kernel has now used (eg the PXE layer or pxe booter forgot to close the
> > client and
> > its still DMAing happily into the kernel)
>
> This morning, we tried updating to a newer pxelinux (3.07) and had the same
> results. We then tried using etherboot with a mknbi tagged image and also
> had the same results. Since we are getting the same problem on 3
> different motherboards with 2 different network adapters, I have not looked
> into updating the boot rom on the nics. Should I?
>
> What should I look into next? I have attached a serial console log of the
> system and errors. The slashes and pipes you see are from a spinning bar
> thing. If you want output that is cleaned up without that, I can provide
> it.
--
Richard Warner
Lead Systems Integrator
Microway, Inc
(508)732-5517
next prev parent reply other threads:[~2005-05-04 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 16:16 very strange issue with sata,<4G Ram, and ext3 Rick Warner
2005-04-28 17:32 ` Rick Warner
2005-04-28 22:48 ` Alan Cox
2005-04-29 14:45 ` Rick Warner
2005-05-04 19:29 ` Rick Warner [this message]
2005-05-05 15:00 ` Alan Cox
2005-05-05 21:37 ` Krzysztof Halasa
2005-05-06 13:39 ` Rick Warner
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=200505041529.54502.rick@microway.com \
--to=rick@microway.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.