itional information that was provided by the
BIOS engineer who I have also been talking to about the problem,
I have decided to propose:
1. Elimination of the default expansion ROM memory allocation
attempts with old behavior accessible via pci=rom boot
option.
2. Revert my "Avoi
the problem,
I have decided to propose:
1. Elimination of the default expansion ROM memory allocation
attempts with old behavior accessible via pci=rom boot
option.
2. Revert my Avoid creating P2P prefetch window for
expansion ROMs change to eliminate the type of
regressions that Jan
Hi Jan,
On Tue, Nov 27, 2007 at 09:28:25AM +, Jan Beulich wrote:
> >A kernel without the patch always forced creation of a prefetch
> >window for expansion ROMs which was incorrect on systems where
> >insufficient memory resources are available for both non-prefetch
> >and prefetch windows.
Hi Jan,
On Tue, Nov 27, 2007 at 09:28:25AM +, Jan Beulich wrote:
A kernel without the patch always forced creation of a prefetch
window for expansion ROMs which was incorrect on systems where
insufficient memory resources are available for both non-prefetch
and prefetch windows. On the
On Mon, Nov 26, 2007 at 02:15:45PM -0800, Greg KH wrote:
> On Mon, Nov 26, 2007 at 01:59:54PM -0800, Gary Hade wrote:
> > Greg,
> > Without a closer look at the code and the information I
> > requested above I am not 100% certain that my expansion ROM
> > allocation fix is incomplete but it seems
On Mon, Nov 26, 2007 at 01:59:54PM -0800, Gary Hade wrote:
> Greg,
> Without a closer look at the code and the information I
> requested above I am not 100% certain that my expansion ROM
> allocation fix is incomplete but it seems pretty likely that
> it is. If you feel that the possible
nel option?
>
> I have to admit I didn't even know about that option;
It is quite new. It was added with a separate patch that I
submitted at the same time as the "Avoid creating P2P prefetch
window for expansion ROMs" patch.
Prior to constraining PCI memory resource allocati
with a separate patch that I
submitted at the same time as the Avoid creating P2P prefetch
window for expansion ROMs patch.
Prior to constraining PCI memory resource allocations to what
_CRS returned, the BIOS unassigned mem resources (including
that required for expansion ROMs) were being
On Mon, Nov 26, 2007 at 01:59:54PM -0800, Gary Hade wrote:
Greg,
Without a closer look at the code and the information I
requested above I am not 100% certain that my expansion ROM
allocation fix is incomplete but it seems pretty likely that
it is. If you feel that the possible regression
On Mon, Nov 26, 2007 at 02:15:45PM -0800, Greg KH wrote:
On Mon, Nov 26, 2007 at 01:59:54PM -0800, Gary Hade wrote:
Greg,
Without a closer look at the code and the information I
requested above I am not 100% certain that my expansion ROM
allocation fix is incomplete but it seems pretty
>>> Greg KH <[EMAIL PROTECTED]> 21.11.07 00:14 >>>
>On Tue, Nov 20, 2007 at 03:49:43AM -0700, Jan Beulich wrote:
>> This patch (in its incarnation in our SLE10SP2 tree) is causing resource
>> allocation failures on one of my machines.
>
>Does the latest 2.6.23 kernel also cause these same
Greg KH [EMAIL PROTECTED] 21.11.07 00:14
On Tue, Nov 20, 2007 at 03:49:43AM -0700, Jan Beulich wrote:
This patch (in its incarnation in our SLE10SP2 tree) is causing resource
allocation failures on one of my machines.
Does the latest 2.6.23 kernel also cause these same problems?
The patch
On Tue, Nov 20, 2007 at 03:49:43AM -0700, Jan Beulich wrote:
> This patch (in its incarnation in our SLE10SP2 tree) is causing resource
> allocation failures on one of my machines.
Does the latest 2.6.23 kernel also cause these same problems?
> The condition for this is that besides ROMs behind
This patch (in its incarnation in our SLE10SP2 tree) is causing resource
allocation failures on one of my machines. The condition for this is that
besides ROMs behind a bridge not having their base addresses assigned
there's no extra space available in the non-prefetch window to
accommodate the
This patch (in its incarnation in our SLE10SP2 tree) is causing resource
allocation failures on one of my machines. The condition for this is that
besides ROMs behind a bridge not having their base addresses assigned
there's no extra space available in the non-prefetch window to
accommodate the
On Tue, Nov 20, 2007 at 03:49:43AM -0700, Jan Beulich wrote:
This patch (in its incarnation in our SLE10SP2 tree) is causing resource
allocation failures on one of my machines.
Does the latest 2.6.23 kernel also cause these same problems?
The condition for this is that besides ROMs behind a
16 matches
Mail list logo
