From: Andi Kleen <ak@muc.de>
To: Peter Buckingham <peter@pantasys.com>
Cc: "David S. Miller" <davem@davemloft.net>,
jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: Mystery packet killing tg3
Date: 5 May 2005 20:31:44 +0200
Date: Thu, 5 May 2005 20:31:44 +0200 [thread overview]
Message-ID: <20050505183144.GD24386@muc.de> (raw)
In-Reply-To: <427A6426.40104@pantasys.com>
On Thu, May 05, 2005 at 11:21:26AM -0700, Peter Buckingham wrote:
> Andi Kleen wrote:
> >In what initialization exactly? YOu mean changing the pci_set_dma_mask()
> >in the e1000 driver?
>
> exactly.
That should be impossible. Or it sounds like a serious
hardware problem. DAC should normally always work with all e1000 AFAIK.
Most likely you have some hardware problem and it is somehow magically
worked around by IOMMU remapping. One difference is that
the remapping makes all IO slower, perhaps the changed timing
works around some bug.
Or there is a posting problem somewhere that is worked
around by the additional config accesses in IOMMU.
Have you contacted the e1000 maintainters?
> >>Kernel panic - not syncing: Cannot allocate iommu bitmap
> >
> >
> >Hmm, that must be a different problem in the IOMMU code
> >not related to the e1000. Probably it got confused somehow.
> >Why did you get the idea the ethernet driver has anything to do with
> >it?
>
> i don't think it has anything to do with the e1000 actually. we only see
> this when the serial console redirection is enabled. It was the only
> dmesg I had lying around that had the IOMMU not forced. We run our
> systems diskless so it's not easy to get the boot log when the ethernet
> device is not working correctly. I can try to get a system with a hard
> drive and give you the dmesg from that instead (probably more useful ;-)
It sounds like something is wrong with your hardware.
-Andi
next prev parent reply other threads:[~2005-05-05 18:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 23:24 Mystery packet killing tg3 Stephen Hemminger
2005-05-03 3:02 ` David S. Miller
2005-05-03 21:05 ` Stephen Hemminger
2005-05-03 21:13 ` David S. Miller
2005-05-03 20:41 ` Michael Chan
2005-05-03 22:03 ` David S. Miller
2005-05-03 21:28 ` Michael Chan
2005-05-03 22:53 ` David S. Miller
2005-05-03 22:45 ` Stephen Hemminger
2005-05-03 22:39 ` David S. Miller
2005-05-03 22:59 ` Stephen Hemminger
2005-05-03 21:29 ` Stephen Hemminger
2005-05-04 18:30 ` Andi Kleen
2005-05-04 18:44 ` Peter Buckingham
2005-05-05 11:43 ` Andi Kleen
2005-05-05 16:20 ` Stephen Hemminger
2005-05-05 18:01 ` Andi Kleen
2005-05-05 17:09 ` Peter Buckingham
2005-05-05 17:32 ` Rick Jones
2005-05-05 17:38 ` Peter Buckingham
2005-05-05 17:45 ` John Heffner
2005-05-05 18:06 ` Andi Kleen
2005-05-05 18:21 ` Peter Buckingham
2005-05-05 18:31 ` Andi Kleen [this message]
2005-05-05 18:40 ` Peter Buckingham
2005-05-05 18:56 ` Andi Kleen
2005-05-05 19:02 ` Peter Buckingham
2005-05-05 19:24 ` Andi Kleen
2005-05-04 19:41 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 6:09 Michael Chan
2005-05-04 6:27 Michael Chan
2005-05-04 22:51 ` Stephen Hemminger
2005-05-04 22:30 ` Michael Chan
[not found] ` <20050505113356.0f1b4c00.davem@davemloft.net>
2005-05-05 19:56 ` Michael Chan
2005-05-05 21:42 ` David S. Miller
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=20050505183144.GD24386@muc.de \
--to=ak@muc.de \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=peter@pantasys.com \
/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).