Bug#582487: FYI: A workaround

["Kingsley G. Morse Jr." <kingsley@loaner.com>]

Thank you for sharing your detailed thoughts.

I may owe you an apology for being too terse in my
bug report.

It seems to me that it may be important to
explain:

    1.) I encountered a stack trace like the one
    in bug#582487 after adding RAM, and then
    pretty much every time I booted the computer.

    My stack trace was consistent.

    It looked like the one in bug#582487.

    2.) I encountered a bug on a different machine
    than the one(s) in bug#582487 and bug#582088.

    I have an MSI (Micro Star) MS-6712 (KT4V)
    motherboard, but the bug report you merged
    (#582088) to says "Eee PC 1000HG, fuse".

At the moment, it seems to me that bug#582487 and
#582088 are different, and I humbly suggest
un-merging them.

Thanks,
Kingsley

On 12/22/11 14:49, Jonathan Nieder wrote:
> Kingsley G. Morse Jr. wrote:
> 
> > I happened to notice it has a different stack
> > trace than bug 582487.
> >
> > If I asked you nicely, would you please elaborate
> > on why you think they're the same bug?
> 
> Sure.  It's because they both are examples of inconsistent state
> pointing to memory corruption, each only happened once, and both
> happened on the same machine.