[Bug 1571786] Re: Broadcom 43602 requires module to be reloaded to work
Same here with DELL XPS15 9550. in case of failure Network Manager recognizes the Wifi adapter as "PCI ethernet" not as Wifi adapter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571786 Title: Broadcom 43602 requires module to be reloaded to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
Just tested it with the current Wily version and the bug still persists.
So I had a look into the systemd service script and I was able to fix it
for myself, simply copy this to file
/lib/systemd/system/watchdog.service :
[Unit]
Description=watchdog daemon
Conflicts=wd_keepalive.service
After=multi-user.target
OnFailure=wd_keepalive.service
[Service]
Type=forking
EnvironmentFile=/etc/default/watchdog
ExecStartPre=/bin/sh -c '[ -z "${watchdog_module}" ] || [ "${watchdog_module}"
= "none" ] || /sbin/modprobe $watchdog_module'
ExecStart=/bin/sh -c '[ $run_watchdog != 1 ] || exec /usr/sbin/watchdog
$watchdog_options'
ExecStopPost=/bin/sh -c '[ $run_wd_keepalive != 1 ] || false'
[Install]
WantedBy=multi-user.target
How do I submit patches/fixes to the Canonical repos so that fix get
into the distro ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't start on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
Tried that before but I get the following messages : Synchronizing state for watchdog.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d watchdog defaults Executing /usr/sbin/update-rc.d watchdog enable The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448917] Re: apt-get -o quiet=1 dist-upgrade isn't quiet anymore
Oops, no need for such a (kind of) rude answer =( Yes, I mean the "(Reading database..." messages and I have not looked into the code of apt to tell where they come from. All I know is that the call to apt-get with quiet option isn't quiet anymore, the behaviourof apt-get from a user point of view has changed from Utopic to Vivid, so this is a valid bug report for this package and the version mentioned. It is a real life problem as it breaks at least the package cron-apt as I mentioned in the bug report above. The maintainer of it should now decide how to proceed with it... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448917 Title: apt-get -o quiet=1 dist-upgrade isn't quiet anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1448917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
The problem happens on several KVM machines with (virtual) Intel 6300ESB WatchDog. Here's the driver load log from dmesg : [37539.207098] i6300esb: Intel 6300ESB WatchDog Timer Driver v0.05 [37539.210190] i6300esb: initialized (0xc907c000). heartbeat=30 sec (nowayout=0) I've attached the watchdog.conf that worked since the initial install of the VMs. ** Attachment added: "watchdog.conf" https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+attachment/4386335/+files/watchdog.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] [NEW] watchdogd doesn't start on boot
Public bug reported: Description:Ubuntu 15.04 Release:15.04 watchdog: Installed: 5.14-3 Candidate: 5.14-3 Version table: *** 5.14-3 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status Expected: Watchdog daemon starts on system boot. Current: After updating from Utopic to Vivid the watchdog daemon doesn't start. A manual service watchdog start after boot up starts the daemon normally. There seems to be a problem with the transition of the init scripts from Upstart to SystemD. ** Affects: watchdog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448917] [NEW] apt-get -o quiet=1 dist-upgrade isn't quiet anymore
Public bug reported: Description:Ubuntu 15.04 Release:15.04 apt: Installed: 1.0.9.7ubuntu4 Candidate: 1.0.9.7ubuntu4 Version table: *** 1.0.9.7ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Current: Until updating from Utopic to Vivid apt-get with command line parameter "-o quiet 1" did not output the progress as formatted text. Since the update the progress is written to stdout as formatted text. This breaks a lot of scripts, e.g. the cron-apt package with mail send enabled. The attached text is no longer text only and will be encoded as binary, so the mail is unreadable. Expected: Same behaviour as with version from Utopic, no progress output ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output of apt-get with quiet=1 parameter" https://bugs.launchpad.net/bugs/1448917/+attachment/4385375/+files/apt-get.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448917 Title: apt-get -o quiet=1 dist-upgrade isn't quiet anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1448917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot
Same here with an 14.10 AMD64 installation on a KVM machine. The workaround with "mount -a" in rc.local doesn't help much for daemons that need the mounted NFS share at startup. They're failing when the mount isn't present at boot time. I've stopped further deployment of Utopic until this bug has been fixed. It is really a showstopper and needs a fix very soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 869408] Re: gnome-shell hangs when switching to a running VMWare Player Window in Activities menu
I can confirm that this bug is still here with kernel 3.5.0-18-generic and Quantal release using VMWare Workstation 9.0.0 build-812388. It freezes very often, several times a day. Pretty unusable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/869408 Title: gnome-shell hangs when switching to a running VMWare Player Window in Activities menu To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/869408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601299] Re: maverick btrfs slow install
Still present in Natty, latest nightly build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/601299 Title: maverick btrfs slow install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660989] Re: maverick: omnibook kernel module is defective, causes crash and fails to load - laptop media keys don't work (e.g. on XE3)
Same here with Toshiba Satego X200, even when I force ectype to 12, which worked in lucid flawlessly. Here's the dmesg output : [9.506982] omnibook: Forced load with EC type 12. [9.529496] general protection fault: [#1] SMP [9.529501] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/device:1a/uevent [9.529505] CPU 0 [9.529506] Modules linked in: omnibook(+) lp parport usbhid hid uvesafb sdhci_pci sdhci firewire_ohci ahci led_class firewire_core crc_itu_t video intel_agp r8169 mii output libahci [9.529523] [9.529526] Pid: 508, comm: modprobe Not tainted 2.6.35-24-generic #42-Ubuntu ISRAA/SATEGO X200 [9.529529] RIP: 0010:[] [] omnibook_init+0x3c/0x1d6 [omnibook] [9.529540] RSP: 0018:880139129d18 EFLAGS: 00010206 [9.529542] RAX: 483f8b4808ec8348 RBX: a00d3a60 RCX: [9.529545] RDX: 0068 RSI: 880136b68200 RDI: a00d3a60 [9.529547] RBP: 880139129d38 R08: 80d0 R09: 880136b68200 [9.529549] R10: R11: dead00200200 R12: a00da538 [9.529552] R13: a00da538 R14: R15: 00405056 [9.529554] FS: 7fd426032700() GS:880001e0() knlGS: [9.529557] CS: 0010 DS: ES: CR0: 8005003b [9.529559] CR2: 7f4123064250 CR3: 00013a222000 CR4: 06f0 [9.529562] DR0: DR1: DR2: [9.529564] DR3: DR6: 0ff0 DR7: 0400 [9.529567] Process modprobe (pid: 508, threadinfo 880139128000, task 8801391216e0) [9.529569] Stack: [9.529570] 0004 4ec4ec4ec4ec4eda a00d2f88 [9.529574] <0> 880139129d58 a00da315 a00d2f88 88013958a810 [9.529578] <0> 880139129d68 81389b37 880139129d98 813886a8 [9.529583] Call Trace: [9.529590] [] omnibook_probe+0xfa/0x16a [omnibook] [9.529596] [] platform_drv_probe+0x17/0x20 [9.529599] [] really_probe+0x68/0x190 [9.529602] [] driver_probe_device+0x45/0x70 [9.529605] [] ? __device_attach+0x0/0x60 [9.529608] [] __device_attach+0x53/0x60 [9.529611] [] bus_for_each_drv+0x68/0x90 [9.529614] [] device_attach+0x8f/0xb0 [9.529617] [] bus_probe_device+0x2d/0x50 [9.529622] [] device_add+0x317/0x440 [9.529626] [] platform_device_add+0x128/0x1e0 [9.529631] [] ? omnibook_module_init+0x0/0x116 [omnibook] [9.529637] [] omnibook_module_init+0xf2/0x116 [omnibook] [9.529641] [] do_one_initcall+0x3c/0x1a0 [9.529646] [] sys_init_module+0xbb/0x200 [9.529651] [] system_call_fastpath+0x16/0x1b [9.529653] Code: 41 54 53 48 89 fb 0f 84 ad 01 00 00 4c 8b 6f 48 45 31 f6 4d 85 ed 0f 84 a1 00 00 00 eb 31 85 05 66 a3 ff ff 74 25 49 8b 44 24 08 <48> 8b 40 40 48 85 c0 74 0b 49 8d 7c 24 08 ff d0 85 c0 75 0c 49 [9.529687] RIP [] omnibook_init+0x3c/0x1d6 [omnibook] [9.529693] RSP [9.529696] ---[ end trace c2709abc3565828c ]--- [9.590139] Detected Toshiba ACPI Bluetooth device - installing RFKill handle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660989 Title: maverick: omnibook kernel module is defective, causes crash and fails to load - laptop media keys don't work (e.g. on XE3) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505469] Re: Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek]
Bug is fixed in the latest daily build of Maverick (20100723). Great work and thank you ! -- Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek] https://bugs.launchpad.net/bugs/505469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505469] Re: Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek]
I experience the same problem with the current daily build (20100709) of Maverick on the same notebook. It comes with current ALSA version 1.0.23. Lucid with ALSA backports package is affected too. The bug has been reported upstream at https://bugtrack.alsa-project.org /alsa-bug/view.php?id=4862 but the report hasn't been changed since then. ** Bug watch added: ALSA Bug Tracker #4862 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4862 -- Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek] https://bugs.launchpad.net/bugs/505469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 463829] Re: No sound on Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG
Still the same issue with Lucid and my CL X-Fi Extreme Audio Notebook. 02:00.0 PCI bridge: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG PCI to PCIe Bridge 03:00.0 Audio device: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG -- No sound on Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG https://bugs.launchpad.net/bugs/463829 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505469] Re: Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek]
** Attachment removed: "WifiSyslog.txt" http://launchpadlibrarian.net/37676193/WifiSyslog.txt ** Attachment removed: "IwConfig.txt" http://launchpadlibrarian.net/37676184/IwConfig.txt ** Attachment removed: "XsessionErrors.txt" http://launchpadlibrarian.net/37676194/XsessionErrors.txt -- Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek] https://bugs.launchpad.net/bugs/505469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505469] Re: Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek]
** Attachment added: "dmesg output after kernel null pointer access" http://launchpadlibrarian.net/37676174/dmesg.txt ** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/37676175/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/37676176/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/37676177/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/37676178/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/37676179/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/37676180/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.1.txt" http://launchpadlibrarian.net/37676181/Card0.Codecs.codec.1.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/37676182/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/37676183/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/37676184/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/37676185/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/37676186/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/37676187/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/37676188/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/37676189/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/37676190/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/37676191/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/37676192/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/37676193/WifiSyslog.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/37676194/XsessionErrors.txt -- Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek] https://bugs.launchpad.net/bugs/505469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505469] [NEW] Null pointer reference in alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek]
Public bug reported: Binary package hint: linux-backports-modules-alsa-karmic-generic After updating to todays new alsa backports modules (2.6.31-18-31) the kernel is crashing with a null pointer access. Here are the relevant lines from dmesg : [ 19.920843] BUG: unable to handle kernel NULL pointer dereference at (null) [ 19.920848] IP: [] alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek] [ 19.920860] PGD 0 [ 19.920862] Oops: [#1] SMP [ 19.920865] last sysfs file: /sys/devices/pci:00/:00:1e.0/:0c:04.0/pcmcia_socket/pcmcia_socket0/available_resources_setup_done [ 19.920869] CPU 0 [ 19.920870] Modules linked in: snd_hda_codec_realtek arc4 ecb snd_hda_intel(+) snd_hda_codec pcmcia iwlagn snd_hwdep iptable_filter iwlcore ip_tables snd_pcm_oss nvidia(P) mac80211 sdhci_pci sdhci psmouse uvcvideo snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss videodev snd_seq_midi snd_rawmidi snd_seq_midi_event serio_raw x_tables rndis_wlan snd_seq yenta_socket snd_timer rsrc_nonstatic joydev snd_seq_device pcmcia_core v4l1_compat tifm_7xx1 led_class v4l2_compat_ioctl32 tifm_core snd soundcore rndis_host cdc_ether usbnet snd_page_alloc cfg80211 lp parport dm_raid45 xor usbhid ohci1394 ieee1394 r8169 mii video output intel_agp [ 19.920914] Pid: 963, comm: work_for_cpu Tainted: P 2.6.31-18-generic #55-Ubuntu SATEGO X200 [ 19.920917] RIP: 0010:[] [] alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek] [ 19.920923] RSP: 0018:880127c31d50 EFLAGS: 00010246 [ 19.920926] RAX: RBX: 880127c23400 RCX: [ 19.920928] RDX: RSI: 88013857a480 RDI: 880127c23400 [ 19.920930] RBP: 880127c31db0 R08: fff4 R09: [ 19.920932] R10: 0002 R11: R12: 880125c2c000 [ 19.920934] R13: 88013857a480 R14: R15: 0001 [ 19.920937] FS: () GS:880028022000() knlGS: [ 19.920939] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [ 19.920941] CR2: CR3: 01001000 CR4: 06f0 [ 19.920943] DR0: DR1: DR2: [ 19.920946] DR3: DR6: 0ff0 DR7: 0400 [ 19.920948] Process work_for_cpu (pid: 963, threadinfo 880127c3, task 880129388000) [ 19.920950] Stack: [ 19.920951] 880127c31d80 880127c23400 880125c2c000 0001 [ 19.920955] <0> 880125c2c008 0001 880127c31db0 880127c23400 [ 19.920959] <0> 880127f80458 0004 0001 [ 19.920964] Call Trace: [ 19.920974] [] snd_hda_codec_build_controls+0x50/0x60 [snd_hda_codec] [ 19.920980] [] snd_hda_build_controls+0x28/0x90 [snd_hda_codec] [ 19.920987] [] azx_probe+0xaa4/0xb6b [snd_hda_intel] [ 19.920991] [] ? azx_send_cmd+0x0/0x1b0 [snd_hda_intel] [ 19.920996] [] ? azx_get_response+0x0/0x290 [snd_hda_intel] [ 19.921000] [] ? azx_attach_pcm_stream+0x0/0x1c0 [snd_hda_intel] [ 19.921004] [] ? azx_bus_reset+0x0/0x90 [snd_hda_intel] [ 19.921008] [] ? azx_power_notify+0x0/0x80 [snd_hda_intel] [ 19.921015] [] ? do_work_for_cpu+0x0/0x30 [ 19.921019] [] local_pci_probe+0x12/0x20 [ 19.921022] [] do_work_for_cpu+0x13/0x30 [ 19.921026] [] kthread+0xa6/0xb0 [ 19.921030] [] child_rip+0xa/0x20 [ 19.921033] [] ? kthread+0x0/0xb0 [ 19.921035] [] ? child_rip+0x0/0x20 [ 19.921037] Code: 89 c5 0f 84 c0 00 00 00 45 8b 55 50 45 85 d2 0f 84 ce 00 00 00 31 d2 45 31 f6 eb 31 66 0f 1f 44 00 00 49 63 ce 4c 89 ee 48 89 df <0f> b7 0c 48 e8 ee ab fd ff 85 c0 0f 88 e5 fe ff ff 41 83 c6 01 [ 19.921070] RIP [] alc_build_controls+0x159/0x4e0 [snd_hda_codec_realtek] [ 19.921077] RSP [ 19.921079] CR2: [ 19.921081] ---[ end trace 12c6f2a66d658de0 ]--- Reverting back to 2.6.31-17 or remove backports package fixes the crash. Output from aplay -l : List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: ALC268 Digital [ALC268 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nraecher 2439 F pulseaudio /dev/snd/pcmC0D0p: nraecher 2439 F...m pulseaudio CRDA: country 98: (2402 - 2483 @ 40), (N/A, 20) Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf750 irq 22' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1179ff0a,0013 HDA:11c11040,11790001,00100200' Controls : 22 Simple ctrls : 13 Date: Sun Jan 10 14:10:44 2010 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=9538ac42-fd51-40a4-b9d8-383681ffe554 MachineType: TOSHIBA SATEGO X200 NonfreeKernelMo
