From: Larry Finger <Larry.Finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ray Lee <ray-lk@madrabbit.org>
Subject: Problem with DMA on x86_64 with 3 GB RAM
Date: Sun, 19 Nov 2006 00:15:14 -0600 [thread overview]
Message-ID: <455FF672.4070502@lwfinger.net> (raw)
In-Reply-To: <455F4271.1060405@madrabbit.org>
I am trying to debug a bcm43xx DMA problem on an x86_64 system with 3 GB RAM. Depending on the
particular chip and its implementation, dma transfers may use 64-, 32-, or 30-bit addressing, with
the problem interface using 30-bit addressing. From test prints, the correct mask (0x3FFFFFFF) is
supplied to pci_set_dma_mask and pci_set_consistent_dma_mask. Neither call returns an error. In
addition, several x86_64 systems with more than 1 GB RAM have worked with the current code.
If the system is booted with mem=1024M on the command line, it operates normally; however, it gets a
kernel NULL pointer dereference and panics when booted with either 2 or 3 GB RAM.
The config parameters in the processor section are as follows:
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_ZONE_DMA32=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_DMI=y
CONFIG_AUDIT_ARCH=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
I would appreciate any tips on debugging this problem. Are there any quantities that should be
dumped, etc?
Thanks,
Larry
next prev parent reply other threads:[~2006-11-19 6:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 19:01 bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble? Ray Lee
2006-11-15 19:15 ` Michael Buesch
2006-11-15 19:15 ` Michael Buesch
2006-11-15 19:41 ` Ray Lee
2006-11-16 2:51 ` Larry Finger
2006-11-16 2:51 ` Larry Finger
2006-11-16 5:51 ` Ray Lee
2006-11-16 18:17 ` Larry Finger
[not found] ` <455CAB2F.1060709-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-11-16 19:16 ` Michael Buesch
2006-11-16 19:36 ` Ray Lee
[not found] ` <455CBDD7.6000507-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>
2006-11-16 22:40 ` Larry Finger
2006-11-16 23:26 ` Ray Lee
[not found] ` <ae017dc00611161526v6bcbddc2ve2c7e10963d25c3b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-11-17 1:13 ` Larry Finger
2006-11-18 11:24 ` Joseph Fannin
2006-11-18 16:55 ` Johannes Berg
2006-11-18 16:55 ` Johannes Berg
2006-11-18 17:05 ` Larry Finger
2006-11-18 17:05 ` Larry Finger
2006-11-18 17:27 ` Ray Lee
2006-11-18 18:30 ` Adrian Bunk
2006-11-21 6:21 ` Ray Lee
2006-11-18 19:02 ` Larry Finger
2006-11-19 16:01 ` Michael Buesch
2006-12-12 4:06 ` ieee80211 sleeping in invalid context Ray Lee
2006-12-12 9:14 ` Michael Buesch
2006-12-12 17:51 ` Ray Lee
2006-12-12 18:31 ` Larry Finger
2006-12-12 18:31 ` Larry Finger
2006-11-19 6:15 ` Larry Finger [this message]
2006-11-21 4:38 ` Problem with DMA on x86_64 with 3 GB RAM Ray Lee
2006-11-21 11:28 ` Alan
2006-11-21 16:34 ` Larry Finger
2006-11-21 10:30 ` Andi Kleen
2006-11-21 16:37 ` Larry Finger
2006-11-21 16:46 ` Andi Kleen
2006-11-21 18:27 ` Alan
2006-11-21 18:31 ` Andi Kleen
2006-11-21 20:04 ` Alan
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=455FF672.4070502@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.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.