Re: [Alsa-devel] nm256: register strangeness related to lockups

On Sun, 2006-03-26 at 20:26 +0200, Christian Trefzer wrote:
Hi folks,

in the process of analyzing the frequent crashes during the snd-nm256
module insertion I stumbled across the following register values
(reading 32bit words at a time in a loop with pcitweak):

Just to make sure, you are testing with 1.0.11-rc4 or CVS? The nm256
lockup problems were thought to be fixed. Or is this a different bug?

Lee

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

Relevant Pages

  • nm256: register strangeness related to lockups
    ... module insertion I stumbled across the following register values ... tried to write back the "safer" values to the chip, but reading them ... Power Management version 1 ...
    (Linux-Kernel)
  • WRITE_REGISTER_BUFFER_UCHAR...
    ... I have a problem writting to my device, (possible also reading, not sure..): ... In my DispatchControl routine i do the following: ... // Register offset R/W Description ... I see that this is the memory resource adresse that is visable ...
    (microsoft.public.development.device.drivers)
  • Re: [RFC] Patch to fix cdrom being confused on using kdump
    ... I actually tried just reading the status register and then returning ... hda: status error: status=0x58 ... from the handler, which was resulting in the 'status error', I ...
    (Linux-Kernel)
  • Re: [RFC] Patch to fix cdrom being confused on using kdump
    ... I actually tried just reading the status register and then returning ... hda: status error: status=0x58 ... is in a confused state. ...
    (Linux-Kernel)