public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid.aziz@hp.com>
To: "Christian Schaubschläger" <christian.schaubschlaeger@gmx.at>
Cc: kexec@lists.infradead.org
Subject: Re: Problem with kexec on i386, linux-3.5
Date: Fri, 07 Sep 2012 14:29:27 -0600	[thread overview]
Message-ID: <504A5927.2090605@hp.com> (raw)
In-Reply-To: <500EE046.2000705@gmx.at>

On 07/24/2012 11:49 AM, Christian Schaubschläger wrote:
> Hello list,
>
> I'm not sure if this is the correct place to post this; if it's not, 
> I'd like to apologize.
>
> Here's a short description of my problem:
>
> I have a tiny protected-/real mode program, which I start using kexec 
> (kexec-tools 2.0.3 released 05 April 2012). At some point this program 
> makes a call to extended-int13 to read data from the disk. Now 
> starting with linux-3.5-rc1 (and at least up to linux-3.5) this 
> extended int13 call does not work any more. Apparently the call 
> returns with error code 0x80, which means "timeout (not ready)".
>
> I have two machines here, both with Intel chipsets (one CougarPoint, 
> one older ICH7-M), and I see the same behaviour on both machines.
>
> When I use older kernels (starting from 2.6.something up to 3.4.6), 
> everything works fine.
>
> Now I'm not sure if this is a kernel issue, or a kexec issue, or a 
> mistake by myself. Maybe someone has a hint for me...
>
> If required, of course, I can provide more detailed information about 
> my hardware, kernel config, etc. (since I'm not sure if this is the 
> correct place, I wanted to keep this message short for now).
>

Hello Christian,

Are you not loading the driver for your disk drive controller when the 
new kernel boots up, even though you are not using the driver for disk 
I/O? If yes, the driver should have re-enabled Bus Master bit in its 
init routine. If you are loading the driver, which driver is it? I can 
take a look at it and see if there is anything missing in the 
initialization routine. Can you also include output from "lspci -v" from 
your machine?

Thanks
-- 
Khalid

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2012-09-07 20:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 17:49 Problem with kexec on i386, linux-3.5 Christian Schaubschläger
2012-08-14  3:31 ` Eric W. Biederman
2012-08-16 12:41   ` Christian Schaubschläger
2012-08-16 19:22     ` Eric W. Biederman
2012-08-17  6:58       ` Christian Schaubschläger
2012-09-07 15:16         ` Khalid Aziz
2012-09-07 20:29 ` Khalid Aziz [this message]
2012-09-10  6:00   ` Christian Schaubschläger
2012-09-10 16:29     ` Khalid Aziz

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=504A5927.2090605@hp.com \
    --to=khalid.aziz@hp.com \
    --cc=christian.schaubschlaeger@gmx.at \
    --cc=kexec@lists.infradead.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