This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.28. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
Rename the pagerange_is_ram() to pat_pagerange_is_ram() and add the
track legacy 1MB region as non RAM condition.
But the lowest 640K are most definitely RAM.
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
On Mon, 23 Mar 2009 10:49:45 +
Alan Cox a...@lxorguk.ukuu.org.uk wrote:
Rename the pagerange_is_ram() to pat_pagerange_is_ram() and
add the track legacy 1MB region as non RAM condition.
But the lowest 640K are most definitely RAM.
not all of it ;)
ram is defined as the kernel
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.28. Please verify if it still should be listed and let me
know
(either way).
Bug-Entry :
On Sun, 22 Mar 2009 13:37:35 +0100
Markus m4rkus...@web.de wrote:
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.28. Please verify if it still should be listed and
* Alan Cox a...@lxorguk.ukuu.org.uk wrote:
On Sun, 22 Mar 2009 13:37:35 +0100
Markus m4rkus...@web.de wrote:
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from
Still valid for 2.6.29-rc8-git5.
And not really likely to change until someone with a pwc camera adds
lots
of printks to the code to work out why this happens.
Or does a bisection to figure out the bad commit, because the report
says that 2.6.28 worked.
The 'howto bisect'
* Markus m4rkus...@web.de wrote:
Still valid for 2.6.29-rc8-git5.
And not really likely to change until someone with a pwc camera adds
lots
of printks to the code to work out why this happens.
Or does a bisection to figure out the bad commit, because the report
says that
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.28. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.28. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
10 matches
Mail list logo