Re: ALSA, snd_intel8x0m and kexec() don't work together (2.6.13-rc3-git4 and 2.6.13-rc3-git3)

[ebiederm@xmission.com (Eric W. Biederman)]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/