Fedora 10 vs Dell Latitude E6500: sound vanishing after a while
wwp
subscript at free.fr
Mon Mar 30 12:59:11 UTC 2009
Hello there,
few sounds after rebooting, sound doesn't play anymore in my Fedora 10,
kept up-to-date using yum. Hardware is a Dell Latitude E6500, featuring,
according to `lspci -vv`:
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
Subsystem: Dell Device 024f
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 0: Memory at f6adc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- RBE- FLReset+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Capabilities: [130] Root Complex Link <?>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-inte
Pulseaudio is enabled, as I didn't change the default way F10 manage
sound. Here's what /var/log/messages contains about sound and alsa
since my last reboot.
`grep -iE "imklog|pulse|sound|snd|audio|alsa" /var/log/messages`:
pulseaudio[3434]: module-alsa-sink.c: Increasing wakeup watermark to 243.94 ms
[repeated]
pulseaudio[3434]: module-alsa-sink.c: Increasing wakeup watermark to 243.94 ms
kernel: imklog 3.21.10, log source = /proc/kmsg started.
kernel: ALSA sound/pci/hda/hda_codec.c:2325: hda_codec: model 'ref' is selected
bluetoothd[2473]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
pulseaudio[3442]: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
pulseaudio[3442]: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
pulseaudio[3442]: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
pulseaudio[3469]: pid.c: Stale PID file, overwriting.
pulseaudio[3518]: pid.c: Daemon already running.
pulseaudio[3469]: module-alsa-sink.c: Increasing wakeup watermark to 40.00 ms
pulseaudio[3469]: module-alsa-sink.c: Increasing wakeup watermark to 80.00 ms
pulseaudio[3469]: module-alsa-sink.c: Increasing wakeup watermark to 160.00 ms
pulseaudio[3469]: module-alsa-sink.c: Increasing wakeup watermark to 243.94 ms
[repeated]
pulseaudio[3469]: module-alsa-sink.c: Increasing wakeup watermark to 243.94 ms
I addition, I also see those messages below, at random positions in the
log file:
pulseaudio[3585]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers.
pulseaudio[3585]: protocol-native.c: Failed to push data into queue
pulseaudio[3585]: asyncq.c: q overrun, queuing locally
kernel: ALSA sound/pci/hda/hda_intel.c:609: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x021f000a
I noticed that with PCM output set to max, the master volume settings
are only acceptable between 50% (audible by quiet night) and 100%
(loud). Everything below 50% is not audible.
Any hint? Is there something to tune or to report to the alsa team?
Regards,
--
wwp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20090330/686f2c57/attachment-0001.bin
More information about the users
mailing list