From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: trouble daemon <troubledaemon@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dell PowerEdge 4200 scsi, worked in 2.6.18, not in 2.6.26 (LOW PRIORITY help request)
Date: Tue, 22 Jun 2010 12:13:29 -0400 [thread overview]
Message-ID: <20100622161329.GA14978@phenom.dumpdata.com> (raw)
In-Reply-To: <AANLkTim7_OzJfwbtk0fE5ScH8zZwZ_uJeo5pJFOhkHu_@mail.gmail.com>
> Ultimately, I was wondering if anyone might be able to take a look at
> my dmesg's that might have any idea as to what feature might be new in
> .26 that could be responsible for the panic. Sadly, it takes about 5
> hours to do a clean run of make-kpkg in debian on these machines, and
> I am not setup for distcc or cross compile on my x64 machine yet, so
> it is a painful experience to recompile over and over to try figure
> out what kernel feature it might be that is causing this.
It looks as the fdc driver is stuck in a loop and the init process never
gets pass this stage.
To see if that is the culprit, find the floppy.ko and rename it to say
floppy.ko.bak. Then recreate the initramfs.
The more worrying is the irqs firring. Try to use the 'irqpoll'
parameter as it suggests.
next prev parent reply other threads:[~2010-06-22 16:13 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 [this message]
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
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=20100622161329.GA14978@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=troubledaemon@gmail.com \
/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