From: Pavel Machek <pavel@ucw.cz>
To: Pekka Pietikainen <pp@ee.oulu.fi>
Cc: "David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Dealing with buggy hardware (was: b44 and 4g4g)
Date: Thu, 10 Jun 2004 23:12:17 +0200 [thread overview]
Message-ID: <20040610211217.GA6634@elf.ucw.cz> (raw)
In-Reply-To: <20040610203442.GA27762@ee.oulu.fi>
Hi!
> > This should hit machines with 2GB ram too, right?
> > Is it possible to find if it hits me? I get hard lockups on
> > 2GB machine with b44, but they take ~5min.. few hours to
> > reproduce...
> >
> > It seems to me like this should hit very quickly.
> > --
> > 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
> >
> Yikes!
>
> With the 4:4 VM split it definately is instantaneous with > 1GB of memory, I
> triggered it with 1.25G myself and never noticed anything wrong with just
> 1GB (allocation starts from the top it seems). With the standard 1:3 split I
> don't think anything > 1GB ever gets used for skbuffs, but maybe there
> are circumstances where this can happen?
Okay, this is probably other problem. When the bug hit, what are the symptoms?
> (Or the issue isn't fully understood yet, figuring out what breaks and what
> doesn't was basically just trial and error :-/ )
Can you try the driver from broadcom? bcom4400, or how is it
called. Its extremely ugly, but might get this kind of stuff right...
Pavel
--
People were complaining that M$ turns users into beta-testers...
...we turn them into developers, and they seem to like it that way!
next prev parent reply other threads:[~2004-06-10 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040531202104.GA8301@ee.oulu.fi>
2004-06-05 20:06 ` Pekka Pietikainen
2004-06-05 20:19 ` David S. Miller
2004-06-09 12:29 ` Pekka Pietikainen
2004-06-10 20:05 ` Pavel Machek
2004-06-10 20:34 ` Pekka Pietikainen
2004-06-10 21:12 ` Pavel Machek [this message]
2004-06-11 6:17 ` Pekka Pietikainen
2004-06-11 9:45 ` Pavel Machek
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=20040610211217.GA6634@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pp@ee.oulu.fi \
/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®