linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Heilman <jamie@audible.transient.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: BriQ & Linux 2.6
Date: Sat, 22 May 2004 12:36:39 -0700	[thread overview]
Message-ID: <20040522193639.GO8520@audible.transient.net> (raw)
In-Reply-To: <1085209944.9234.7.camel@gaston>


Benjamin Herrenschmidt wrote:
> Linux console starts at 9600 while the briq firmware use a different
> speed (I don't remember which). Try adding the speed ot the kernel
> command line

Sure ... ok I see whats going on, ages ago, when my briq ran 2.2 it
was always spoken to at 38400, but the kernel seemed to think it was
actually 9600.  As long as everything (init, setserial, getty, kernel)
agreed it was 9600 but you actually connected at 38400 all was well.
Now I see that things are trying to present a truer picture.  I still
had everything set to 9600, so the kernel was running at true 9600
and was garble, but init and getty would work OK.  I just poked
at my apps, now they all agree on 38400 and everything works now.
So that explains that, misconfiguration on my part; easy fix.

> >           RX packets:118521 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:1 errors:57244 dropped:0 overruns:0 carrier:57244
> >
> > ...and yet, strangly I don't seem to be having any obvious network
> > performance problems.
>
> Interesting. I keep seeing reports of problems with pcnet32 driver,
> that's weird though.

Yeah, quite.  It doesn't do that using the 2.4.24 kernel from TI,
which has pcnet32.c version 1.27a.  There have been a lot of changes
since then though.  The only one that caught my eye was that back then
the 79C973 was flagged to activate tx error recovery, and in the newer
driver it isn't.  I might play around with that and some higher
debugging levels later.

Right now the more immediate problem is that any amount of disk IO
that approaches significant triggers an immediate reboot.  Which is
obviously not cool.  I'm doing some SMART tests on the drive, we'll
see if that has any interesting feedback.

--
Jamie Heilman                     http://audible.transient.net/~jamie/
"You came all this way, without saying squat, and now you're trying
 to tell me a '56 Chevy can beat a '47 Buick in a dead quarter mile?
 I liked you better when you weren't saying squat kid." -Buddy

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-22 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21  7:40 BriQ & Linux 2.6 Jamie Heilman
2004-05-21 23:10 ` Benjamin Herrenschmidt
2004-05-21 23:35   ` Jamie Heilman
2004-05-22  4:14     ` Benjamin Herrenschmidt
2004-05-22  6:45       ` Jamie Heilman
2004-05-22  7:12         ` Benjamin Herrenschmidt
2004-05-22 19:36           ` Jamie Heilman [this message]
2004-05-24  6:47             ` Jamie Heilman
2004-05-25 23:30         ` Benjamin Herrenschmidt
2004-05-26  0:00           ` Jamie Heilman

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=20040522193639.GO8520@audible.transient.net \
    --to=jamie@audible.transient.net \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).