On Sunday 09 April 2006 02:57, Yann Dirson wrote:
> Did you find the time to get a look at newer patch version ?
> FWIW, I'm uploading a 2.6.16 version right now.
> If you cannot look at it, I'll tag this report as non reproducible and
> close it.
Nope. I never did, unfortunately,
Shawn.
Hi Shawn,
Did you find the time to get a look at newer patch version ?
FWIW, I'm uploading a 2.6.16 version right now.
If you cannot look at it, I'll tag this report as non reproducible and
close it.
Best regards,
--
Yann Dirson<[EMAIL PROTECTED]> |
Debian-related: <[EMAIL PROTECTED]> | Su
On Thu, Nov 03, 2005 at 03:00:31PM -0700, Shawn Willden wrote:
> I'm pretty swamped at the moment, but over the next few days I'll try
> building
> it for straight i386 and see if that works any differently. I have replaced
> my bad RAM with good stuff, so I've largely lost interest... but I'll
On Thursday 03 November 2005 11:47 am, Yann Dirson wrote:
> This is an amd64 kernel, right ? I expect that such a kernel would
> not be completely supported, since the upstream says about 2.6.13 support:
>
> "In progress. Trying to incorporate x86_64 support."
Interesting. I just looked at the k
Hi Shawn,
On Thu, Oct 06, 2005 at 11:16:59AM -0600, Shawn Willden wrote:
> My kernel config is just a copy of the 2.6.11 AMD K8 package config,
> except with badram turned on, obviously.
This is an amd64 kernel, right ? I expect that such a kernel would
not be completely supported, since the ups
Package: kernel-patch-badram
Version: 2.6.12.0-1
Severity: important
I just added 2GB of RAM to my system (for a total of 3GB), and
memtest86 reports that I have a bad region of memory. The
badram pattern suggested by memtest86 is 0x5c8e400c,0xfffc.
I do plan on exchanging these bad DIMM
6 matches
Mail list logo
