From: "Dave Young" <hidave.darkstar@gmail.com>
To: "Folkert van Heusden" <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.26] OOPS in elv_next_request
Date: Fri, 31 Oct 2008 09:22:52 +0800 [thread overview]
Message-ID: <a8e1da0810301822k3402e753m482d98f4530419a0@mail.gmail.com> (raw)
In-Reply-To: <20081030142550.GB11214@vanheusden.com>
On Thu, Oct 30, 2008 at 10:25 PM, Folkert van Heusden
<folkert@vanheusden.com> wrote:
>> > While running my http://vanheusden.com/pyk/ script (which randomly
>> > inserts and removes modules) I triggered the folllowing oops in a 2.6.26
>> > kernel on a Celeron 400 (Mendocino):
>> >
>> > [ 4768.664021] Floppy drive(s): fd0 is 1.44M
> ...
>> > [ 4768.720058] ---[ end trace 6a50caff78c47574 ]---
>> > [ 4769.658313] Floppy drive(s): fd0 is 1.44M
>> > [ 4789.656060] no cont in shutdown!
>>
>> Hi, could you try the attached test patch? sorry for using attachment
>> as there's some problem for my mail client to reply.
>
> As your patch is based on 2.6.27 I compiled the 2.6.27 kernel with it. But
> something odd is going on: when 2.6.27 boots, right after the initrd loading
> the screen-resolution gets changed or so, so that most text is no longer
> visible. Also the system seems to halt. Unfortunately too early for
> netconsole to emit the errors.
Yes, the patch is based on 2.6.27, but it can be applied to 2.6.26
without problem.
Could you try it with 2.6.26 again?
BTW, for 2.6.27, did you set vga=normal or other things?
--
Regards
dave
next prev parent reply other threads:[~2008-10-31 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 9:04 Folkert van Heusden
2008-10-28 5:11 ` Dave Young
2008-10-28 15:05 ` Folkert van Heusden
2008-10-30 14:25 ` Folkert van Heusden
2008-10-31 1:22 ` Dave Young [this message]
2008-10-31 10:03 ` Folkert van Heusden
2008-11-01 16:12 ` Folkert van Heusden
2008-11-12 2:30 ` Dave Young
2008-11-16 12:36 ` Folkert van Heusden
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=a8e1da0810301822k3402e753m482d98f4530419a0@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®