Massive delay of Mulitmedia / Volume buttons on Asus N90Sc Notebook
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
1. press (e.g) MUTE Button on Keyboard/Multimedia Button
2. wait about 20 seconds
3. Sound is muted.
- With Lucid everything was OK.
- Due to Bug #653626 I must use the bootoption pci=noacpi to boot successfully. (perhaps this causes this bug)
I ran the commands "xev" and "acpi_listen" to get the events, but they have massive delay too.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: SIS966 [HDA SIS966], device 0: ALC663 Analog [ALC663 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: thomas 1744 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SIS966'/'HDA SIS966 at 0xf9ff4000 irq 18'
Mixer name : 'Realtek ALC663'
Components : 'HDA:10ec0663,
Controls : 16
Simple ctrls : 8
Date: Fri Oct 22 14:59:25 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: ASUSTeK Computer Inc. N90SC
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
LANG=de_AT.utf8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: linux
dmi.bios.date: 01/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 205
dmi.board.
dmi.board.name: N90SC
dmi.board.vendor: ASUS CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: N90SC
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
tankdriver, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you please run the following command in the development release from a Terminal (Applications- >Accessories- >Terminal) , as it will automatically gather and attach updated debug information to this report:
apport-collect -p linux <replace- with-bug- number>
Also, could you please test the latest upstream kernel available following https:/ /wiki.ubuntu. com/KernelMainl ineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: testing
needs-upstream-
This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text: testing
needs-upstream-
If this bug is fixed in the mainline kernel, please add the following tags: fixed-upstream fixed-upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
If the mainline kernel does not fix this bug, please add the following tags: bug-exists- upstream bug-exists- upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: unable- to-test- upstream unable- to-test- upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
Please let us know your results. Thank you for your understanding.
Helpful Bug Reporting Tips: /help.ubuntu. com/community/ ReportingBugs
https:/