public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: trouble daemon <troubledaemon@gmail.com>
Cc: linux-kernel@vger.kernel.org, aystarik@gmail.com, x86@kernel.org,
	586494@bugs.debian.org
Subject: Re: Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26
Date: Fri, 16 Sep 2011 16:48:20 -0500	[thread overview]
Message-ID: <20110916214820.GJ4683@elie> (raw)
In-Reply-To: <CAK82gMFdUy5Dm+FpkrjuEeP9W6BFfGL4U0h-FP8b6BmMHAH1Ww@mail.gmail.com>

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 installer chokes if I
> don't use noapic, however.
>
> If you are interested in some closure, I suppose I could take a shot
> at installing something a little more recent and see if I can get away
> with removing noapic though. Just let me know what kernel source
> (vanilla/deb sid/etc), version, or any particular .config options that
> you would like me to test, and I can see about pasting the console
> terminal output when running without noapic disabled.

Thanks!  Really, anything 3.0 or later would be interesting (mainline
is better than distro-patched), with a .config that panics in an older
version.  Testing with a stock Debian squeeze kernel would be
interesting, too.

  reply	other threads:[~2011-09-16 21:48 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 ` Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26 Jonathan Nieder
2011-09-12  7:23   ` trouble daemon
2011-09-16 21:48     ` Jonathan Nieder [this message]
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=20110916214820.GJ4683@elie \
    --to=jrnieder@gmail.com \
    --cc=586494@bugs.debian.org \
    --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