On Wed, Oct 25, 2023 at 07:11:26PM +0200, Lukas Wunner wrote:
> On Wed, Oct 25, 2023 at 10:30:07AM -0600, Logan Gunthorpe wrote:
> > In addition to the above, P2PDMA transfers are only allowed by the
> > kernel for traffic that flows through certain host bridges that are
> > known to work. For
https://bugzilla.kernel.org/show_bug.cgi?id=48451
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Sat, Sep 29, 2012 at 4:09 PM, Stephan Schreiber i...@fs-driver.org wrote:
Hello Bjorn,
thank you very much for the patch.
I tested it; it works.
(typing mistake: it must read PCI_COMMAND_MEMORY instead of PCI_COMMAND_MEM
at one location;
some hunks of the patch couldn't be applied
9038dd3b3c4c9e4c7ca0118c8df398c4c646ab58
Author: Bjorn Helgaas bhelg...@google.com
Date: Mon Sep 24 17:16:28 2012 -0600
vsprintf: Add support for IORESOURCE_UNSET in %pR
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index 0e33754..b6c 100644
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
On Thu, Sep 20, 2012 at 8:16 AM, Stephan Schreiber i...@fs-driver.org wrote:
description of the symptoms which you have already read on the initial
RFC/PATCH==
Kernel 3.2.23 with Debian patches (Debian Wheezy, testing)
Debian bug#679545
On Sun, Sep 16, 2012 at 10:39 AM, Stephan Schreiber i...@fs-driver.org wrote:
[0.065516] pci :00:1f.1: [8086:24cb] type 0 class 0x000101
[0.065530] pci :00:1f.1: reg 10: [io 0x-0x0007]
[0.065541] pci :00:1f.1: reg 14: [io 0x-0x0003]
[0.065552] pci
in short: the bios is broken, it return wrong segment in DSDT.
I *think* what Yinghai is saying is:
- MMCONFIG is not used either in 2.6.26 or 2.6.32.
- BIOS reports these host bridges via DSDT PNP0A08 devices:
[PCI0] leading to segment bus 00
[PCI1] leading to segment
On Tue, Feb 14, 2012 at 1:53 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi Ralf,
Ralf Jung wrote[1]:
after upgrading to version 3.2.0-1 of the kernel, one of the two error
messages during startup is gone - the corresponding patch by Bjorn Helgaas
has
been accepted upstream.
However
On Fri, Aug 26, 2011 at 8:16 AM, Ralf Jung ralfjun...@gmx.de wrote:
Hi Bjorn,
Here's a test patch for the TCO timer issue. That SP5100 watchdog
driver is a mess -- it gropes around at hard-coded places in I/O port
space -- so while I think this patch will fix the message, the
watchdog
On Tue, Aug 23, 2011 at 6:13 PM, Bjorn Helgaas bhelg...@google.com wrote:
Your error is SP5100 TCO timer: mmio address 0xbafe00 already in
use. (Same error, but different address.) That looks like it's in
the middle of your RAM, i.e., it looks completely bogus. Given the
ugliness
Hi Ralf, can you attach the complete dmesg log to the bug report,
please? I see a snippet (starting with Bluetooth: SCO socket layer
initialized), but there's a lot of useful information before that.
The dmesg command only shows the most recent part of the log, so if
the kernel's buffer has
Thanks! These tests:
if ((dev-vendor == PCI_VENDOR_ID_AMD) || (dev-device ==
PCI_DEVICE_ID_AMD_GOLAM_7450))
are clearly wrong. I suspect was intended instead of ||, but
this code seems to have been that way since the beginning, so I
Ralf, can you attach your /proc/iomem contents, too? I looked at the
SP5100 TCO timer: mmio address 0xfec000f0 already in use message,
but I don't see why that address is in use.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Here's a test patch for the TCO timer issue. That SP5100 watchdog
driver is a mess -- it gropes around at hard-coded places in I/O port
space -- so while I think this patch will fix the message, the
watchdog itself still may not work. If you can verify that the
watchdog works, that would be
Your error is SP5100 TCO timer: mmio address 0xbafe00 already in
use. (Same error, but different address.) That looks like it's in
the middle of your RAM, i.e., it looks completely bogus. Given the
ugliness of the sp5100_tco driver, that doesn't surprise me. Possibly
the BIOS configured it
Thanks for this patch. Here's a small fix to the usage message:
--- mail.orig 2008-05-15 15:50:14.0 -0600
+++ mail2008-05-15 15:51:21.0 -0600
@@ -21,7 +21,7 @@
usage()
{
- printf $Usage: quilt mail {--mbox file|--send} [-m text] [--prefix
prefix] [--sender
I sent Matt this patch, which solves the problem for me:
To complement the character class matched by a bracket expression,
the exclamation mark seems more widely accepted than circumflex.
Bash accepts either, but dash, ksh, and The Open Group shell command
language spec accept only exclamation
On Thu, 2005-01-13 at 17:59 -0500, Branden Robinson wrote:
On Fri, Dec 31, 2004 at 12:18:29AM -0800, David Mosberger wrote:
Branden I wonder how many domains we should look for before we give
Branden up. I get the feeling doing an ftw() on /proc/pci/pci is
Branden not a good idea.
18 matches
Mail list logo
