)
trouble daemon wrote:
Greetings,
Hello Adam and Bjorn. I am sending this email to you as suggested by
Jonathan regarding a problem that I was having with Linux on a pair of
old Dell PowerEdge 4200 machines that I own (yes, they still run!).
I have left the most recent reply between
Heya,
On Fri, Sep 16, 2011 at 5:48 PM, Jonathan Nieder jrnie...@gmail.com wrote:
trouble daemon wrote:
As for later kernels, I have no idea tbh. Currently they seem to run
flawless with noapic, so that is what I use when installing and
running them. I do know that the Debian Squeeze
Hello,
On Mon, Sep 12, 2011 at 2:56 AM, Jonathan Nieder jrnie...@gmail.com wrote:
Sorry we dropped the ball on this. Dan, any news (e.g., do later
kernels do any better)? Alexey, any ideas for tracking this down?
No worries, not like these machines are useful for much beyond museum
pieces
Gah, I messed up the reportbug settings in my vm and accidentally set
it to troub...@gmail.com instead of troubledae...@gmail.com. Could
someone fix this please?
Thanks, and sorry!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
As requested by Andrew, I did a kernel bisect and tracked the patch
which introduced the problem
due to the following commit from the linux git branch:
$ git bisect bad
f8924e770e048429ae13bfabe1ddad9bf1e64df7 is first bad commit
commit f8924e770e048429ae13bfabe1ddad9bf1e64df7
Author: Alexey
Package: bsign
Version: 0.4.5
Severity: minor
I was checking out the bsign man page, and was following the example syntax
for creating and verifying a hash, but I got stumped when it said:
$ bsign --check-hash /bin/bash
$ parse error 2 at word 132635
It seems that upon closer inspection,
On Wed, Jun 23, 2010 at 9:35 PM, Ben Hutchings b...@decadent.org.uk wrote:
I'm afraid I don't know much about interrupt routing so I don't think I
can get useful information out of it.
That's okay, the important thing is that noapic works at least.
I see that you also wrote to LKML and that
Ben,
Another option that may be worth trying is 'noapic'.
Wow, that worked just fine actually on 2.6.26 stock kernel. Thanks a lot!
I am curious though, what in the world changed since 2.6.18 and lower
versions that might have required noapic? I've seen the option needed
by so many people on
BTW, I also attached the dmesg for 2.6.26 working just
for reference to anyone else who might stumble upon this bug, and for
your curiosity as well.
ooops, forgot the attachement. Attached as promised!
troubled
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing
Ben,
My guess is that something has gone wrong with interrupt routing. Can
you try adding 'acpi=noirq' to the kernel parameters?
Okay, I tied acpi=noirq with the stock lenny 2.6.26 kernel, and it
looks like the same exact problem still. I can capture a dmesg for
that as well if you want
Ok, I am currently compiling the 2.6.32 debianized kernel with the
config from the lenny package.
Ooops, small correction. What I meant to say was that I am compiling
the 2.6.32 source from squeeze using the squeeze config in the .deb,
not the lenny config. ie: it should end up effectively a
Package: linux-2.6
Version: 2.6.26-22lenny1
Severity: important
I am using a pair of Dell PowerEdg 4200's that have been working with
debian since 2002 or so, 100% perfectly. However, since testing out
Lenny with a 2.6.26 kernel, it seems that both systems panic in an
unbootable fashion with
12 matches
Mail list logo
