No sound in Acer Aspire 5742z

Bug #676362 reported by Melvin Garcia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

My mother just bought this computer and asked me to install Ubuntu. i'm currently testing it using "System Testing" and there's no sound device detected.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: alsa-base 1.0.23+dfsg-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
AlsaDevices:
 total 0
 crw-rw----+ 1 root audio 116, 3 2010-11-16 23:58 seq
 crw-rw----+ 1 root audio 116, 2 2010-11-16 23:58 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices: aplay: device_list:235: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:235: no soundcards found...
AudioDevicesInUse:
 Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Cannot stat file /proc/5050/fd/21: Stale NFS file handle
 Cannot stat file /proc/5050/fd/37: Stale NFS file handle
 Cannot stat file /proc/5050/fd/44: Stale NFS file handle
CheckboxCommand: cat /proc/asound/cards
CheckboxDescription:
 Detecting your sound device(s):

 $output

 Is this correct?
CheckboxTest: list_audio_devices
Date: Wed Nov 17 04:13:03 2010
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SourcePackage: alsa-driver
dmi.bios.date: 08/11/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.04
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 5742Z
dmi.board.vendor: Acer
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.modalias: dmi:bvnAcer:bvrV1.04:bd08/11/2010:svnAcer:pnAspire5742Z:pvrV1.04:rvnAcer:rnAspire5742Z:rvrV1.04:cvnAcer:ct10:cvrV1.04:
dmi.product.name: Aspire 5742Z
dmi.product.version: V1.04
dmi.sys.vendor: Acer

Revision history for this message
Melvin Garcia (virtualspectre8) wrote :
Revision history for this message
Daniel T Chen (crimsun) wrote :
Download full text (3.5 KiB)

[ 27.109882] intel ips 0000:00:1f.6: No CPUID match found.
[ 27.109893] BUG: unable to handle kernel NULL pointer dereference at 00000008
[ 27.109898] IP: [<f8098452>] ips_detect_cpu+0x62/0x180 [intel_ips]
[ 27.109904] *pde = 00000000
[ 27.109907] Oops: 0000 [#1] SMP
[ 27.109910] last sysfs file: /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/name
[ 27.109914] Modules linked in: intel_ips(+) snd_page_alloc v4l1_compat led_class serio_raw squashfs aufs nls_iso8859_1 nls_cp437 vfat fat dm_raid45 xor btrfs zlib_deflate crc32c libcrc32c i915 drm_kms_helper usb_storage drm ahci tg3 libahci intel_agp i2c_algo_bit video output agpgart
[ 27.109935]
[ 27.109939] Pid: 3003, comm: modprobe Not tainted 2.6.35-22-generic #33-Ubuntu Aspire 5742Z/Aspire 5742Z
[ 27.109942] EIP: 0060:[<f8098452>] EFLAGS: 00010286 CPU: 0
[ 27.109945] EIP is at ips_detect_cpu+0x62/0x180 [intel_ips]
[ 27.109947] EAX: 00c800c8 EBX: 00000000 ECX: 00c800c8 EDX: 00000000
[ 27.109950] ESI: f631de04 EDI: f6080100 EBP: f631de14 ESP: f631dde4
[ 27.109952] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 27.109954] Process modprobe (pid: 3003, ti=f631c000 task=f6312610 task.ti=f631c000)
[ 27.109956] Stack:
[ 27.109957] f8099efc f8099e9e f719b1f0 f631de14 c020c441 f631de08 c05c7979 f8098eef
[ 27.109963] <0> 00000000 f6080100 f71c0000 fffffff4 f631de4c f8098f2a c027165d f631de4c
[ 27.109968] <0> c0270c07 f631de4c c027100a f631de38 f71c0000 f71c0060 c036bb1e f71c0000
[ 27.109975] Call Trace:
[ 27.109985] [<c020c441>] ? kmem_cache_alloc_notrace+0x91/0xb0
[ 27.109992] [<c05c7979>] ? mutex_lock+0x19/0x40
[ 27.109995] [<f8098eef>] ? ips_probe+0x1f/0x690 [intel_ips]
[ 27.109999] [<f8098f2a>] ? ips_probe+0x5a/0x690 [intel_ips]
[ 27.110005] [<c027165d>] ? sysfs_add_one+0x1d/0x110
[ 27.110008] [<c0270c07>] ? sysfs_new_dirent+0x67/0x100
[ 27.110012] [<c027100a>] ? sysfs_addrm_finish+0x1a/0xb0
[ 27.110018] [<c036bb1e>] ? pci_match_device+0xbe/0xd0
[ 27.110022] [<c036b9b3>] ? local_pci_probe+0x13/0x20
[ 27.110024] [<c036c968>] ? pci_device_probe+0x68/0x90
[ 27.110029] [<c0400550>] ? really_probe+0x50/0x150
[ 27.110033] [<c0407bc7>] ? pm_runtime_barrier+0x57/0xb0
[ 27.110036] [<c040068c>] ? driver_probe_device+0x3c/0x60
[ 27.110039] [<c0400731>] ? __driver_attach+0x81/0x90
[ 27.110042] [<c03ffb53>] ? bus_for_each_dev+0x53/0x80
[ 27.110045] [<c040041e>] ? driver_attach+0x1e/0x20
[ 27.110047] [<c04006b0>] ? __driver_attach+0x0/0x90
[ 27.110050] [<c03ffde5>] ? bus_add_driver+0xd5/0x280
[ 27.110053] [<c036c8a0>] ? pci_device_remove+0x0/0x40
[ 27.110056] [<c0400a2a>] ? driver_register+0x6a/0x130
[ 27.110059] [<c036cba5>] ? __pci_register_driver+0x45/0xb0
[ 27.110063] [<f809d017>] ? ips_init+0x17/0x19 [intel_ips]
[ 27.110067] [<c0101132>] ? do_one_initcall+0x32/0x1a0
[ 27.110071] [<f809d000>] ? ips_init+0x0/0x19 [intel_ips]
[ 27.110077] [<c0180c2b>] ? sys_init_module+0x9b/0x1e0
[ 27.110083] [<c0218fa2>] ? sys_write+0x42/0x70
[ 27.110086] [<c05c90a4>] ? syscall_call+0x7/0xb
[ 27.110088] Code: 3e 09 c8 90 ba f5 9d 09 f8 b8 0c 52 81 c0 e8...

Read more...

affects: alsa-driver (Ubuntu) → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Melvin,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kernel-sound
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
787B (787b) wrote :

This problem is solved after installing the latest updates. Still does not work after a fresh install, but updates fix it.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.