From: ebiederm@xmission.com (Eric W. Biederman)
To: Lee Revell <rlrevell@joe-job.com>
Cc: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>,
linux-kernel@vger.kernel.org
Subject: Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)
Date: Sat, 30 Jul 2005 20:19:00 -0600 [thread overview]
Message-ID: <m1fytv1zvv.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1122054941.877.6.camel@mindpipe> (Lee Revell's message of "Fri, 22 Jul 2005 13:55:41 -0400")
Lee Revell <rlrevell@joe-job.com> writes:
> On Fri, 2005-07-22 at 15:18 +0200, Ralf Hildebrandt wrote:
>> * Denis Vlasenko <vda@ilport.com.ua>:
>>
>> > Not happening here on 2.6.12:
>>
>> 2.6.12 didn't have kexec (unless it's a -mm kernel)
>> So how could you boot using kexec then?
>>
>
> Is kexec supposed to be transparent to all the subsystems, or does ALSA
> have to know how to stop all DMA in order for kexec to work?
It is fairly transparent. device_shutdown on reboot should stop
DMA but that is not kexec specific. kexec may be the only way
the code path is easily tested.
The basic requirement from the kexec side is that the drivers
be able to bring back the device from the state they left it
on reboot.
So in essence it is transparent. But if your driver is not
robust you can have problems.
The fact the new kernel was coming up indicates that kexec
worked but the driver did not successfully initialize,
the hardware from the state it placed it in during shutdown.
Eric
next prev parent reply other threads:[~2005-07-31 2:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 18:06 Ralf Hildebrandt
2005-07-22 6:25 ` Ralf Hildebrandt
2005-07-22 13:14 ` Denis Vlasenko
2005-07-22 13:18 ` Ralf Hildebrandt
2005-07-22 17:55 ` Lee Revell
2005-07-22 18:02 ` Ralf Hildebrandt
2005-07-31 2:20 ` Eric W. Biederman
2005-07-31 2:19 ` Eric W. Biederman [this message]
2005-09-04 17:17 ` Ralf Hildebrandt
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=m1fytv1zvv.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=Ralf.Hildebrandt@charite.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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
all inboxes | Powered by JetHome®