That's what I would have done except I ran into a problem.
With a completely clean install of Debian and every major version of the
Linux kernel I haven't run into this error again. Of coarse I was
running bare base of Debian with only the ssh server installed. This
error has yet to come up again. I am now on the Kernel version 3.3.0 and
I have slowly restored everything one at a time, and checked to see if
the stability has been broken by each thing I install. So far nothing.
The only major part I haven't install that may be the cause is the
non-free firmware tg3. So if I install that any still nothing wrong then
I don't know. Other then the possibility that there is something
different with the kernel.org versions and the ones that I have been
downloading from Debian. Or it could have been some improper
configuration of the kernel at the start.
On 04/06/2012 10:46 AM, Jonathan Nieder wrote:
Kieron Gillespie wrote:
I am right now testing one major kernel version at a time, and on
the 3.0.0-1 I got
Just to be clear, if each time you test the version halfway between
the newest known-good and oldest known-bad kernel then you only have
to test log(n) kernels instead of n. :)
That's neither here nor there, though.
Thanks for the update.
Jonathan
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
