From: Jonathan Nieder <jrnieder@gmail.com>
To: trouble daemon <troubledaemon@gmail.com>
Cc: linux-kernel@vger.kernel.org, aystarik@gmail.com, x86@kernel.org
Subject: Re: Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26
Date: Mon, 12 Sep 2011 01:56:18 -0500 [thread overview]
Message-ID: <20110912065618.GA23340@elie> (raw)
In-Reply-To: <AANLkTim7_OzJfwbtk0fE5ScH8zZwZ_uJeo5pJFOhkHu_@mail.gmail.com>
(resending with a newer address for Alexey - sorry for the noise)
Hi,
trouble daemon wrote:
> I am using a pair of Dell PowerEdg 4200's that have been working with
> debian since 2002 or so, 100% perfectly.
[...]
> - 2.6.26 kernel that panics (latest unmodified debian kernel):
> http://pastebin.ca/1886636
> - 2.6.18 kernel that works (latest unmodified debian kernel):
> http://pastebin.ca/1886641
pastebin.ca doesn't seem to exist any more, alas.
[...]
> Ben Hutchings wrote:
>> Another option that may be worth trying is 'noapic'.
>
> Wow, that worked just fine actually on 2.6.26 stock kernel. Thanks a lot!
[...]
> f8924e770e048429ae13bfabe1ddad9bf1e64df7 is first bad commit
> commit f8924e770e048429ae13bfabe1ddad9bf1e64df7
> Author: Alexey Starikovskiy <astarikovskiy@suse.de>
> Date: Fri Apr 4 23:42:21 2008 +0400
>
> x86: unify mp_bus_info
[...]
> I have verified that checking out the patch just before this one works
> fine on the machines.
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?
Thanks,
Jonathan
next prev parent reply other threads:[~2011-09-12 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 20:22 Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26 (LOW PRIORITY help request) trouble daemon
2010-06-22 16:13 ` Konrad Rzeszutek Wilk
2010-06-22 17:36 ` trouble daemon
2011-09-12 6:56 ` Jonathan Nieder [this message]
2011-09-12 7:23 ` Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26 trouble daemon
2011-09-16 21:48 ` Jonathan Nieder
2011-09-24 4:09 ` trouble daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110912065618.GA23340@elie \
--to=jrnieder@gmail.com \
--cc=aystarik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=troubledaemon@gmail.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox