[Bug 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
Another environment where this happens is multi-seat using a USB-to-VGA display controllers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148454] Re: console-kit-daemon spawns too many threads
I think somebody should take a serious look at this. Have a look at this from the c-k-d status: VmPeak: 2091776 kB VmSize: 2091744 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 4012 kB VmRSS: 4012 kB VmData: 2052720 kB VmStk: 136 kB VmExe: 136 kB VmLib: 5820 kB VmPTE: 240 kB VmSwap:0 kB So it is using ~2GB for data?! Why does it need 2G? On a PC with 4G that's half of the memory. In #128 it was mentioned that consolekit will be merged in systemd. It's been 2 years since. When will it happen? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/148454 Title: console-kit-daemon spawns too many threads To manage notifications about this bug go to: https://bugs.launchpad.net/consolekit/+bug/148454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 232557] Re: console-kit-daemon leaks memory
It is insane. One user logged in and out. And 2G of memory is data- resident? PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 2155 ?Sl 0:00 1 0 2091744 4012 0.1 /usr/sbin/console-kit-daemon --no-daemon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/232557 Title: console-kit-daemon leaks memory To manage notifications about this bug go to: https://bugs.launchpad.net/consolekit/+bug/232557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243072] [NEW] hybrid_power turns on laptop display with lid closed
Public bug reported: The hybrid_power script turns on the laptop display, even if the lid is closed. I dock my laptop and leave it closed, there's an external (VGA) monitor connected. When I run the hybrid_power script, it correctly turns on the external display and incorrectly turns on the internal laptop display. This is regular, up to date 13.10. $ dpkg -l nvidia-prime ii nvidia-prime 0.4 all Tools to enable NVIDIA's Prime ** Affects: nvidia-prime (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/1243072 Title: hybrid_power turns on laptop display with lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1243072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210077] Re: Screen freeze and gabled after resume from suspend
Me too. Using nvidia-319-updates on regular 13.10, Dell Latitude E6530, 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GLM [NVS 5200M] (rev a1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210077 Title: Screen freeze and gabled after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1210077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivatesSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 Ah, so it is a duplicate of 1056381 ** This bug has been marked a duplicate of bug 1056381 error on x startup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivatesSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 So it seems the bug is actually in the qxl driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivatesSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 Seems to be the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=844463 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivatesSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 The patch here might actually fix it. http://www.mail-archive.com/spice-devel@lists.freedesktop.org/msg10334.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivateSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 ** Attachment added: "crash report from /var/crash" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+attachment/3349389/+files/_usr_bin_Xorg.0.crash ** Summary changed: - in kvm-spice X exits with assertion in dixPrivateSize + in kvm-spice X exits with assertion in dixPrivatesSize ** Bug watch added: Red Hat Bugzilla #844463 https://bugzilla.redhat.com/show_bug.cgi?id=844463 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivateSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 ** Attachment added: "related Xorg.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+attachment/3349388/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivateSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 ** Attachment added: "lightdm main logfile" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+attachment/3349387/+files/lightdm.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivateSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 ** Attachment added: "lightdm greeter logfile" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+attachment/3349386/+files/x-0-greeter.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] Re: in kvm-spice X exits with assertion in dixPrivateSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 ** Attachment added: "from /var/log/lightdm/" https://bugs.launchpad.net/bugs/1057713/+attachment/3349385/+files/x-0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057713 Title: in kvm-spice X exits with assertion in dixPrivatesSize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1057713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057713] [NEW] in kvm-spice X exits with assertion in dixPrivatesSize
*** This bug is a duplicate of bug 1056381 *** https://bugs.launchpad.net/bugs/1056381 Public bug reported: I have a virtual machine that uses kvm-spice with quantal in it (up to date with today). The login screen does not appear and the lightdm logfile shows a failed assertion. In /var/log/lightdm/x-0.log: X: ../../dix/privates.c:560: dixPrivatesSize: Assertion `!screen_specific_private[type]' failed. I'll attach the lightdm logfiles, Xorg logfiles as well as a crash file (of X) that is probably from the crash (as best as I can tell from the timestamp it is from the same minute). X uses the qxl driver. Using the cirrus driver doesn't cause a crash. Package information: ii lightdm 1.3.3-0ubuntu4 amd64Display Manager ii lightdm-remote-session-freerdp 1.0-0ubuntu1 amd64Session and configuration to login with FreeRDP ii lightdm-remote-session-uccsconfigure1.1-0ubuntu1 amd64Session and configuration to login to configure UCCS ii xserver-xorg1:7.7+1ubuntu3 amd64X.Org X server ii xserver-xorg-core 2:1.13.0-0ubuntu4 amd64Xorg X server - core server ii xserver-xorg-input-all 1:7.7+1ubuntu3 amd64X.Org X server -- input driver metapackage ii xserver-xorg-input-evdev1:2.7.3-0ubuntu1 amd64X.Org X server -- evdev input driver ii xserver-xorg-input-mouse1:1.7.2-2build1 amd64X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics1.6.2-1ubuntu5 amd64Synaptics TouchPad driver for X.Org server ii xserver-xorg-input-vmmouse 1:12.9.0-0ubuntu3 amd64X.Org X server -- VMMouse input driver to use with VMWare ii xserver-xorg-input-wacom1:0.17.0-0ubuntu2 amd64X.Org X server -- Wacom input driver ii xserver-xorg-video-all 1:7.7+1ubuntu3 amd64X.Org X server -- output driver metapackage ii xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 amd64X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-cirrus 1:1.5.1-0ubuntu2 amd64X.Org X server -- Cirrus display driver ii xserver-xorg-video-fbdev1:0.4.3-0ubuntu1 amd64X.Org X server -- fbdev display driver ii xserver-xorg-video-intel2:2.20.8-0ubuntu1 amd64X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-mach64 6.9.3-0ubuntu1 amd64X.Org X server -- ATI Mach64 display driver ii xserver-xorg-video-mga 1:1.6.0-0ubuntu1 amd64X.Org X server -- MGA display driver ii xserver-xorg-video-modesetting 0.5.0-0ubuntu1 amd64X.Org X server -- Generic modesetting driver ii xserver-xorg-video-neomagic 1:1.2.7-0ubuntu1 amd64X.Org X server -- Neomagic display driver ii xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1 amd64X.Org X server -- Nouveau display driver ii xserver-xorg-video-openchrome 1:0.3.1-0ubuntu1 amd64X.Org X server -- VIA display driver ii xserver-xorg-video-qxl 0.0.18~gitde66207-0ubuntu1 amd64X.Org X server -- QXL display driver ii xserver-xorg-video-r128 6.8.4-0ubuntu1 amd64X.Org X server -- ATI r128 display driver ii xserver-xorg-video-radeon 1:6.99.99~git20120913.8637f772-0ubuntu1 amd64X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-s3 1:0.6.5-0ubuntu1 amd64X.Org X server -- legacy S3 display driver ii xserver-xorg-video-savage 1:2.3.6-0ubuntu1 amd64X.Org X server -- Savage display driver ii xserver-xorg-video-siliconmotion1:1.7.7-0ubuntu1 amd64X.Org X server -- SiliconMotion display driver ii xserver-xorg-video-sis 1:0.10.7-0ubuntu1 amd64X.Org X server -- SiS display driver ii xserver-xorg-video-sisusb 1:0.9.6-0ubuntu1 amd64X.Org X se
[Bug 947617] Re: After update, lxc does not start
Serge, This container I created with oneiric with the lxc-sshd template. It worked there reasonably well (only needed to add a default route, which is missing). I've compared (visually) what oneiric created for mounting and what precise would have created. It seems there is only 1 difference. Oneiric did not include a mount for /proc, which precise does add. To me this looks like a regression after upgrading from oneiric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947617 Title: After update, lxc does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/947617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947617] Re: After update, lxc does not start
After the workaround, my container is running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947617 Title: After update, lxc does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/947617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947617] Re: After update, lxc does not start
For me this seems not fixed. ii apparmor 2.7.102-0ubuntu3 User-space parser utility for AppArmor ii lxc 0.7.5-3ubuntu56 Linux containers userspace tools root@kira:~# lxc-start -n jake lxc-start: failed to mount rootfs lxc-start: failed to setup rootfs for 'jake' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'jake' And in dmesg [92690.144338] type=1400 audit(1339010096.655:40): apparmor="DENIED" operation="mount" info="failed type match" error=-13 parent=3406 profile="/usr/bin/lxc-start" name="/var/tmp/lxc/jake/" pid=3429 comm="lxc-start" srcname="/var/lib/lxc/jake/rootfs/" flags="rw, rbind" I have not yet tried the workaround from comment 4, but will try that shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947617 Title: After update, lxc does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/947617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 983712] Re: WARNING: at /build/buildd/linux-3.2.0/drivers/net/wireless/brcm80211/brcmsmac/main.c:8234
Joseph, I was actually looking into why my kvm virtual machine was crashing and looked in the host dmesg and noticed the trace. At least in oneiric this didn't happen. I also don't know whether this happens regularly, but I will keep an eye on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983712 Title: WARNING: at /build/buildd/linux-3.2.0/drivers/net/wireless/brcm80211/brcmsmac/main.c:8234 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 983712] Re: WARNING: at /build/buildd/linux-3.2.0/drivers/net/wireless/brcm80211/brcmsmac/main.c:8234
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983712 Title: WARNING: at /build/buildd/linux-3.2.0/drivers/net/wireless/brcm80211/brcmsmac/main.c:8234 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 983712] [NEW] WARNING: at /build/buildd/linux-3.2.0/drivers/net/wireless/brcm80211/brcmsmac/main.c:8234
Public bug reported: [ 5852.288873] [ cut here ] [ 5852.288924] WARNING: at /build/buildd/linux-3.2.0/drivers/net/wireless/brcm80211/brcmsmac/main.c:8234 brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac]() [ 5852.288932] Hardware name: HP ProBook 6560b [ 5852.288936] Modules linked in: nls_utf8 isofs ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp kvm_intel kvm bnep rfcomm binfmt_misc nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc dm_crypt snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec bcma snd_hwdep arc4 snd_pcm snd_seq_midi brcmsmac mac80211 tpm_infineon snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device uvcvideo videodev v4l2_compat_ioctl32 snd brcmutil cfg80211 hp_accel crc8 lis3lv02d cordic soundcore psmouse serio_raw tpm_tis snd_page_alloc btusb bluetooth mei(C) dm_multipath joydev ppdev hp_wmi mac_hid sparse_keymap parport_pc input_polldev lp parport btrfs zlib_deflate libcrc32c usbhid hid firewire_ohci firewire_core sdhci_pci sdhci crc_itu_t wmi i915 e1000e drm_kms_helper drm i2c_algo_bit video [ 5852.289092] Pid: 16131, comm: kworker/u:1 Tainted: G C 3.2.0-23-generic #36-Ubuntu [ 5852.289097] Call Trace: [ 5852.289116] [] warn_slowpath_common+0x7f/0xc0 [ 5852.289125] [] warn_slowpath_null+0x1a/0x20 [ 5852.289150] [] brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac] [ 5852.289169] [] brcms_ops_flush+0x3b/0x60 [brcmsmac] [ 5852.289202] [] ieee80211_scan_work+0x12f/0x3e0 [mac80211] [ 5852.289213] [] ? finish_task_switch+0x4a/0xf0 [ 5852.289240] [] ? ieee80211_scan_rx+0x190/0x190 [mac80211] [ 5852.289251] [] process_one_work+0x11a/0x480 [ 5852.289261] [] worker_thread+0x164/0x370 [ 5852.289270] [] ? manage_workers.isra.29+0x130/0x130 [ 5852.289279] [] kthread+0x8c/0xa0 [ 5852.289289] [] kernel_thread_helper+0x4/0x10 [ 5852.289296] [] ? flush_kthread_worker+0xa0/0xa0 [ 5852.289305] [] ? gs_change+0x13/0x13 [ 5852.289310] ---[ end trace d3779c531c26d365 ]--- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: janevert 3312 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd472 irq 48' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:111d7605,103c1618,00100105 HDA:11c11040,103c3066,00100200 HDA:80862805,80860101,0010' Controls : 37 Simple ctrls : 13 Date: Tue Apr 17 09:03:21 2012 MachineType: Hewlett-Packard HP ProBook 6560b ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=UUID=056f40b2-ea70-4b37-8cf0-9f46720477e4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.04 dmi.board.name: 1619 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.41 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.04:bd05/10/2011:svnHewlett-Packard:pnHPProBook6560b:pvrA0001D02:rvnHewlett-Packard:rn1619:rvrKBCVersion97.41:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6560b dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/983712 Title: WARNING: at /build/buildd/linux-3.2.0/drivers/net/wireless/brcm80211/brcmsmac/main.c:8234 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: vgchange may deadlock in initramfs when VG present that's not used for rootfs
Had some time over x-mas. Adding --noudevsync fixes it for me. 5 consecutive reboots all worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: vgchange may deadlock in initramfs when VG present that's not used for rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: vgchange may deadlock in initramfs when VG present that's not used for rootfs
Serge, I've got the stock lvm2 package. So if that --noudevsync is in the stock package, then yes, it usually fails. The lvm2 is 2.02.66-4ubuntu3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: vgchange may deadlock in initramfs when VG present that's not used for rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802626] Re: vgchange may deadlock in initramfs when VG present that's not used for rootfs
A me too. I have /var and /home on two lvm partitions. /home only needs one of the two partitions, /var was recently extended and now needs both. It fails in most boots, more than 9 out of 10. The comment from #34 also applies for me, no problem with the 3.0.0-13 kernel. The thing I can add is that /var never gets activated. So I'd say that at least one vgchange is not executed. If I manually vgscan and vgchange and then exit the shell, the boot continues just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802626 Title: vgchange may deadlock in initramfs when VG present that's not used for rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 435452] Re: [Linux] ath5k disconnect and become unusable
This happens to an Acer Aspire 3650 laptop as well. But apparently the problem is that the driver does not handle interrupts well. So each time I load the ath5k module it gets 20001 interrupts and then dmesg reports about an unhandled interrupt. -- [Linux] ath5k disconnect and become unusable https://bugs.launchpad.net/bugs/435452 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
Re: [Bug 254946] Re: Atheros wireless doesn't work on boot
I should note, though, that I had to manually blacklist the ath_pci driver. Otherwise that still got loaded first. -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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
Re: [Bug 254946] Re: Atheros wireless doesn't work on boot
> Can you comment if you've tested installing linux-backports-modules- > intrepid? If you haven't, please test. Thanks Yes, I have installed it. Until now it has been behaving just fine (i.e. no more rmmod/sleep/modprobe needed). As far as I'm concerned, this is a good workaround for the bug. Thanks! -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
Leann, Thanks for the attention. ** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/22809355/lspci-vvnn.log -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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
Re: [Bug 273616] Re: kernel BUG when using USB in domU (xen)
Not at all. Unfortunately. Sean McRobbie wrote: > Did you get anywhere with this? Having the same problem and finding it > hard to fix. > > -- kernel BUG when using USB in domU (xen) https://bugs.launchpad.net/bugs/273616 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 254946] Re: Atheros wireless doesn't work on boot
sta...@stas:~$ cat /proc/version_signature Ubuntu 2.6.27-9.19-generic -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
** Attachment added: "dmesg.txt" http://launchpadlibrarian.net/21683891/dmesg.txt -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
I've upgraded the laptop to Intrepid. This is still an issue. I'll attach the intrepid dmesg. With Intrepid the bug is more problematic than before because now sometimes this only happens once NetworkManager wakes up after the interface re-apears. -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 269083] Re: gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
Rich, If somebody could catch the bug in the debugger then at least the full text can be found. It does not necessarily need to come from the g-p-m binary. It could be from any of the loaded libs or even have been loaded from configuration. But if this is text then one possible option how it got there is through a *sprintf call with a too short buffer and no return value checking. -- gnome-power-manager crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/269083 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
Re: [Bug 269083] Re: gnome-power-manager crashed with SIGSEGV in g_closure_invoke()
> Also as said before, somewhere, the engine pointer sent to > gpm_cell_array_charge_low_cb (where the segfault occurs). Strange thing > is athat the pointer Mike's valgrind log complains about > (0x3a54494d45202a2a) is exactly the same as the pointer it complains > about when I test it.. It is exactly the same probably because it is text: 3a : 54 T 49 I 4d M 45 E 20 space 2a * 2a * Hope this helps. -- Jan Evert -- gnome-power-manager crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/269083 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 280438] Re: package motion 3.2.9-6 failed to install/upgrade: subprocess post-installation script returned error exit status 1
me too. -- package motion 3.2.9-6 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/280438 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 278712] Re: 3.2.3 and qemu: could not init smb messaging context
Please note that there's a simple 'chmod g+rw /var/run/samba/message.tbd' fixes the access denied and thus prevents the whole stacktrace. But I just thought that I should report it anyways. -- 3.2.3 and qemu: could not init smb messaging context https://bugs.launchpad.net/bugs/278712 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 278712] [NEW] 3.2.3 and qemu: could not init smb messaging context
Public bug reported: Binary package hint: samba I've got win2k in a qemu vm and I'm using '-smb' with my home directory. When I try to reach that network drive, smbd crashes. The log is below. And w2k reports that the network path was not found. Smbd reports that it is dumping core in /var/log/samba/cores/smbd, but nothing shows up there. So there might be two bugs here, one being that it crashes, as in the log below. The second being that there is no coredump. Note that I 'chgrp adm /var/*/samba' and 'chmod g+rw /var/*/samba' to be able to run samba as a regular user. This is because of bug 50385. This is intrepid, uptodate to today, 5-oct-2008, it is 2:3.2.3-1ubuntu2. And this is a x86_64 install. If there's something else you'd like me to do, just ask. It is very easy to reproduce. This is all that is logged for the whole run in /var/log/samba/smbd.log: [2008/10/05 19:30:12, 0] smbd/server.c:main(1213) smbd version 3.2.3 started. Copyright Andrew Tridgell and the Samba Team 1992-2008 [2008/10/05 19:30:12, 0] lib/messages_local.c:messaging_tdb_init(96) ERROR: Failed to initialise messages database: Permission denied [2008/10/05 19:30:12, 0] lib/messages.c:messaging_init(204) messaging_tdb_init failed: NT_STATUS_ACCESS_DENIED [2008/10/05 19:30:12, 0] lib/util.c:smb_panic(1663) PANIC (pid 15018): Could not init smbd messaging context [2008/10/05 19:30:12, 0] lib/util.c:log_stack_trace(1767) BACKTRACE: 6 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x7f526f56ec5d] #1 /usr/sbin/smbd(smb_panic+0x5b) [0x7f526f56ed6b] #2 /usr/sbin/smbd(smbd_messaging_context+0x3f) [0x7f526f42d4d7] #3 /usr/sbin/smbd(main+0x68d) [0x7f526f42de8a] #4 /lib/libc.so.6(__libc_start_main+0xe6) [0x7f526c0a0466] #5 /usr/sbin/smbd [0x7f526f42cd89] [2008/10/05 19:30:12, 0] lib/fault.c:dump_core(201) dumping core in /var/log/samba/cores/smbd ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 3.2.3 and qemu: could not init smb messaging context https://bugs.launchpad.net/bugs/278712 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 273616] Re: kernel BUG when using USB in domU (xen)
It's actually linux-image-2.6.24-21-xen. Not just 'linux-image' as I wrote before. -- kernel BUG when using USB in domU (xen) https://bugs.launchpad.net/bugs/273616 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 273616] Re: kernel BUG when using USB in domU (xen)
I've checked for that 'comm: usb'. I can't seem to locate its executable (/proc/3490/exe exists, but ls reports 'cannot read symbolic link exe: No such file or directory') Anything else I can add? -- kernel BUG when using USB in domU (xen) https://bugs.launchpad.net/bugs/273616 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 273616] [NEW] kernel BUG when using USB in domU (xen)
Public bug reported: I've got a pci USB hub exported to a domU (to have cups drive it). As you can see below, it doesn't work very well. It's an single CPU amd64 machine with linux-image 2.6.24-21.42. Although the kernel is Ubuntu, the rest of this domU is debian testing (the combination worked very well when the USB was not exported to the domU). Dom0 is linux-image 2.6.24-21.42smb2 (from Stefan Baders PPA to work around that iov_iter_advance bug). xen is 3.3 from Ubuntu. [ 46.804468] Fatal DMA error! Please use 'swiotlb=force' [ 46.804534] [ cut here ] [ 46.804543] kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/arch/x86/kernel/pci-dma_32-xen.c:372! [ 46.804554] invalid opcode: [1] SMP [ 46.804574] CPU 0 [ 46.804589] Modules linked in: nfsd auth_rpcgss exportfs ipv6 ppdev parport_pc lp parport nfs lockd nfs_acl sunrpc af_packet dm_snapshot dm_mirror dm_mod evdev usblp ext3 jbd mbcache uhci_hcd usbcore [ 46.804751] Pid: 3490, comm: usb Not tainted 2.6.24-21-xen #1 [ 46.804755] RIP: e030:[] [] dma_map_single+0x18e/0x210 [ 46.804769] RSP: e02b:8800255ebd88 EFLAGS: 00010292 [ 46.804772] RAX: 003e RBX: 880002388040 RCX: 0001 [ 46.804776] RDX: RSI: RDI: [ 46.804779] RBP: 8800257b8000 R08: 000269945ac9 R09: [ 46.804782] R10: 8800018e3fe0 R11: 0001 R12: 2000 [ 46.804786] R13: 880023c2a070 R14: R15: [ 46.804795] FS: 7fcd8df7a6e0() GS:805c7000() knlGS: [ 46.804798] CS: e033 DS: ES: [ 46.804802] DR0: DR1: DR2: [ 46.804805] DR3: DR6: 0ff0 DR7: 0400 [ 46.804809] Process usb (pid: 3490, threadinfo 8800255ea000, task 880024551040) [ 46.804812] Stack: 880024b95a80 00d0 880023a43400 [ 46.804820] 880024b95a90 8800807b 0010 0010 [ 46.804826] 00d0 80299c0c 880025404940 257b8000 [ 46.804832] Call Trace: [ 46.804869] [] :usbcore:usb_hcd_submit_urb+0x1bb/0x8f0 [ 46.804875] [] kmem_cache_alloc+0xfc/0x120 [ 46.804884] [] cache_alloc_refill+0x8e/0x5f0 [ 46.804900] [] :usbcore:usb_get_urb+0xe/0x20 [ 46.804908] [] :usblp:usblp_write+0x196/0x370 [ 46.804915] [] vfs_write+0xed/0x190 [ 46.804920] [] sys_write+0x53/0x90 [ 46.804925] [] system_call+0x68/0x6d [ 46.804929] [] system_call+0x0/0x6d [ 46.804933] [ 46.804934] [ 46.804935] Code: 0f 0b eb fe 48 ba 00 00 00 00 ff ff ff ff e9 74 ff ff ff 48 [ 46.804953] RIP [] dma_map_single+0x18e/0x210 [ 46.804958] RSP [ 46.804991] ---[ end trace b9c6a7ee117b3b51 ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- kernel BUG when using USB in domU (xen) https://bugs.launchpad.net/bugs/273616 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 273223] [NEW] multisync assertion failed
Public bug reported: Binary package hint: multisync0.90 When I start multisync0.90, it prints the below when I attempt to add a member to a new group. (multisync0.90:446): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion `iter->user_data != NULL' failed The user interface pops up the (empty) member selection dialog. Initially this confused me because previously it worked just fine. Except the upgrade from hardy to intrepid happened to remove the opensync plugins. ii multisync-tools 0.92.0~svn355-1 PIM Synchronization Command Line Tools ii multisync0.90 0.92.0~svn355-1 PIM Synchronization Tool ii libopensync0 0.22-2 Synchronisation framework for email/pdas/and more ii libsyncml-utils 0.4.6-3 SyncML protocol library utilities ii libsyncml00.4.6-3 SyncML protocol library This is an Intrepid alpha (up to date to yesterday, sep 21 2008). ** Affects: multisync0.90 (Ubuntu) Importance: Undecided Status: New -- multisync assertion failed https://bugs.launchpad.net/bugs/273223 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 269766] [NEW] fontconfig cache updated four times during upgrade
Public bug reported: Binary package hint: fontconfig My laptop is intrepid (currently alpha). I noticed during upgrade of fontconfig that the cache was updated four times. See the output during apt-get below. Is it really necessary to do this four times? And that is even without updating/installing fonts, defoma or pango things. Would it be possible to do this through a trigger, such as done for libc6: Processing triggers for libc6 ... ldconfig deferred processing now taking place ? apt-get update -V information: fontconfig (2.6.0-1ubuntu2 => 2.6.0-1ubuntu3) fontconfig-config (2.6.0-1ubuntu2 => 2.6.0-1ubuntu3) libfontconfig1 (2.6.0-1ubuntu2 => 2.6.0-1ubuntu3) During apt-get processing: Preparing to replace libfontconfig1 2.6.0-1ubuntu2 (using .../libfontconfig1_2.6.0-1ubuntu3_amd64.deb) ... Unpacking replacement libfontconfig1 ... Preparing to replace fontconfig-config 2.6.0-1ubuntu2 (using .../fontconfig-config_2.6.0-1ubuntu3_all.deb) ... Unpacking replacement fontconfig-config ... : : Preparing to replace fontconfig 2.6.0-1ubuntu2 (using .../fontconfig_2.6.0-1ubuntu3_amd64.deb) ... Cleaning up font configuration of fontconfig... Cleaning up category cid.. Cleaning up category truetype.. Cleaning up category type1.. Updating fontconfig cache for /usr/share/fonts/truetype/ttf-indic-fonts-core /usr/share/fonts/truetype/ttf-sil-gentium /usr/share/fonts/truetype/thai /usr/share/fonts/truetype/ttf-lao /usr/share/fonts/truetype/ttf-arabeyes /usr/share/fonts/truetype/ttf-liberation /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/truetype/ttf-devanagari-fonts /usr/share/fonts/truetype/ttf-gujarati-fonts /usr/share/fonts/truetype/ttf-bengali-fonts /usr/share/fonts/type1/gsfonts /usr/share/fonts/truetype/dustin /usr/share/fonts/truetype/ttf-tamil-fonts /usr/share/fonts/truetype/ttf-bitstream-vera /usr/share/fonts/truetype/ttf-punjabi-fonts /usr/share/fonts/truetype/unfonts /usr/share/fonts/truetype/baekmuk /usr/share/fonts/truetype/ttf-kannada-fonts /usr/share/fonts/truetype/ttf-telugu-fonts /usr/share/fonts/truetype/freefont /usr/share/fonts/truetype/ttf-oriya-fonts /usr/share/fonts/truetype/arphic /usr/share/fonts/truetype/ttf-lucida /usr/share/fonts/truetype/ttf-malayalam-fonts /usr/share/fonts/truetype/kochi /usr/share/fonts/truetype/ttf-mgopen /usr/share/fonts/truetype/ttf-gentium /usr/share/fonts/truetype/msttcorefonts Updating fontconfig cache for /usr/share/fonts/truetype/ttf-indic-fonts-core /usr/share/fonts/truetype/ttf-sil-gentium /usr/share/fonts/truetype/thai /usr/share/fonts/truetype/ttf-lao /usr/share/fonts/truetype/ttf-arabeyes /usr/share/fonts/truetype/ttf-liberation /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/truetype/ttf-devanagari-fonts /usr/share/fonts/truetype/ttf-gujarati-fonts /usr/share/fonts/truetype/ttf-bengali-fonts /usr/share/fonts/type1/gsfonts /usr/share/fonts/truetype/dustin /usr/share/fonts/truetype/ttf-tamil-fonts /usr/share/fonts/truetype/ttf-bitstream-vera /usr/share/fonts/truetype/ttf-punjabi-fonts /usr/share/fonts/truetype/unfonts /usr/share/fonts/truetype/baekmuk /usr/share/fonts/truetype/ttf-kannada-fonts /usr/share/fonts/truetype/ttf-telugu-fonts /usr/share/fonts/truetype/freefont /usr/share/fonts/truetype/ttf-oriya-fonts /usr/share/fonts/truetype/arphic /usr/share/fonts/truetype/ttf-lucida /usr/share/fonts/truetype/ttf-malayalam-fonts /usr/share/fonts/truetype/kochi /usr/share/fonts/truetype/ttf-mgopen /usr/share/fonts/truetype/ttf-gentium /usr/share/fonts/truetype/msttcorefonts Unpacking replacement fontconfig ... : : Setting up mesa-utils (7.1-1ubuntu2) ... Setting up fontconfig-config (2.6.0-1ubuntu3) ... Setting up libfontconfig1 (2.6.0-1ubuntu3) ... Setting up tk8.5 (8.5.3-1) ... : Setting up compiz (1:0.7.7+git20080807-0ubuntu7) ... Setting up fontconfig (2.6.0-1ubuntu3) ... Updating font configuration of fontconfig... Cleaning up category cid.. Cleaning up category truetype.. Cleaning up category type1.. Updating category type1.. Updating category truetype.. Updating category cid.. Updating fontconfig cache for /usr/share/fonts/truetype/ttf-indic-fonts-core /usr/share/fonts/truetype/ttf-sil-gentium /usr/share/fonts/truetype/thai /usr/share/fonts/truetype/ttf-lao /usr/share/fonts/truetype/ttf-arabeyes /usr/share/fonts/truetype/ttf-liberation /usr/share/fonts/truetype/ttf-dejavu /usr/share/fonts/truetype/ttf-devanagari-fonts /usr/share/fonts/truetype/ttf-gujarati-fonts /usr/share/fonts/truetype/ttf-bengali-fonts /usr/share/fonts/type1/gsfonts /usr/share/fonts/truetype/dustin /usr/share/fonts/truetype/ttf-tamil-fonts /usr/share/fonts/truetype/ttf-bitstream-vera /usr/share/fonts/truetype/ttf-punjabi-fonts /usr/share/fonts/truetype/unfonts /usr/share/fonts/truetype/baekmuk /usr/share/fonts/truetype/ttf-kannada-fonts /usr/share/fonts/truetype/ttf-telugu-fonts /usr/share/fonts/truetype/freefont /usr/share/fonts/truetype/ttf-oriya-fonts /usr/share/fonts/truetype/arphic /usr/share/fonts/truetype
[Bug 242330] Re: [i915] GL screensaver crashes X server (using mergedFB)
Hi, no progress for a while. With the backtrace, is this still incomplete? I've moved on to intrepid (which uses the -intel driver instead of -i810), so it'll be hard to test, confirm or check things. -- [i915] GL screensaver crashes X server (using mergedFB) https://bugs.launchpad.net/bugs/242330 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 254946] Re: Atheros wireless doesn't work on boot
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) Status: New => Confirmed -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
My guess is that, because it works after an rmmd/modprobe, trying the suggestions in https://help.ubuntu.com/community/DebuggingIRQProblems is no longer necessary. -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
** Attachment added: "version.log" http://launchpadlibrarian.net/16559555/version.log -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
** Attachment added: "uname-a.log" http://launchpadlibrarian.net/16559554/uname-a.log -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/16559549/lspci-vvnn.log -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
** Attachment added: "interrupts.log" http://launchpadlibrarian.net/16559547/interrupts.log -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] Re: Atheros wireless doesn't work on boot
** Attachment added: "dmesg.log" http://launchpadlibrarian.net/16559544/dmesg.log -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 254946] [NEW] Atheros wireless doesn't work on boot
Public bug reported: My wifes laptop has this wlan interface 09:02.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) On most boots it doesn't work right after boot and a rmmod/modprobe of ath_pci makes it works again (sometimes needs to be repeated). The dmesg shows this when it doesn't work: [ 62.801364] irq 20: nobody cared (try booting with the "irqpoll" option) [ 62.801425] Pid: 0, comm: swapper Tainted: P2.6.24-19-generic #1 [ 62.801591] [] __report_bad_irq+0x24/0x80 [ 62.801696] [] ktime_get+0x18/0x40 [ 62.801763] [] note_interrupt+0x27b/0x2c0 [ 62.801824] [] rcu_needs_cpu+0x32/0x40 [ 62.801950] [] handle_IRQ_event+0x30/0x60 [ 62.802038] [] handle_fasteoi_irq+0x86/0xe0 [ 62.802126] [] do_IRQ+0x3b/0x70 [ 62.802245] [] common_interrupt+0x23/0x30 [ 62.802354] [] __is_prefetch+0x9b/0x240 [ 62.802433] [] acpi_idle_enter_bm+0x25b/0x2ce [processor] [ 62.802613] [] cpuidle_idle_call+0x7c/0xb0 [ 62.802677] [] cpu_idle+0x45/0xd0 [ 62.802735] [] start_kernel+0x31f/0x3b0 [ 62.802793] [] unknown_bootoption+0x0/0x1e0 [ 62.802921] === [ 62.802935] handlers: [ 62.802947] [] (ath_intr+0x0/0xcb0 [ath_pci]) [ 62.803037] Disabling IRQ #20 Note that the atheros card is the only user of int 20. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) Status: Confirmed -- Atheros wireless doesn't work on boot https://bugs.launchpad.net/bugs/254946 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 252728] Re: Jiffies too low for acceptable ppoll accuracy
The reporter is having expectations from the kernel which are not satisfied. In this case that (realttime) behavior is for a large part defined by the kernel configuration. And that has consciously been decided upon by the kernel team. As such not a bug. However, we do not need to let the reporter down and can still help him achieve his goal. ** Changed in: linux (Ubuntu) Status: New => Invalid ** bug changed to question: https://answers.launchpad.net/ubuntu/+source/linux/+question/40609 ** Summary changed: - Jiffies too low for acceptable ppoll accuracy + How to achieve low latency sleeps. -- How to achieve low latency sleeps. https://bugs.launchpad.net/bugs/252728 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 252728] Re: Jiffies too low for acceptable ppoll accuracy
Kay, With RHEL 1000Hz I would expect <1ms delays. So there's something funny as well. As for ppol using ns precision to specify the timeout is the future. Otherwise you end up changing the interface every 2 years (due to Moores law). As for your unique key, you could simply use the uptime. That starts counting at startup. (see man sysinfo) Your last paragraph really is key, I guess. You want standard packages, yet achieve low latency. Given the above, I don't think this is a bug in the kernel. The kernel configuration was consciously decided upon by the Ubuntu kernel team. What you are seeing is due to that decision. So I'll convert it into a question and we can continue there. -- How to achieve low latency sleeps. https://bugs.launchpad.net/bugs/252728 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 252573] Re: Please backport kernel fix for ad-hoc networks
** Tags added: cherry-pick -- Please backport kernel fix for ad-hoc networks https://bugs.launchpad.net/bugs/252573 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 252573] Re: Please backport kernel fix for ad-hoc networks
I've got this problem as well. I can't (using hardy 2.6.24-19) associate with an ad-hoc network that consists of 2.4 and 2.6.early systems. (don't know how to connect wpa-supplicant) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) Status: New => Confirmed -- Please backport kernel fix for ad-hoc networks https://bugs.launchpad.net/bugs/252573 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 252728] Re: Jiffies too low for acceptable ppoll accuracy
Umm, should've been more clear perhaps... Grep for PREEMPT on the ubuntu and redhat kernel configurations (usually located in /boot/config*). Also of interest are then the various HZ related config items (hint grep HZ /boot/config-..). And a diff between the redhat dmesg and ubuntu dmesg could also be revealing (for example different clock sources). And which version is the RH kernel? -- Jiffies too low for acceptable ppoll accuracy https://bugs.launchpad.net/bugs/252728 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 252728] Re: Jiffies too low for acceptable ppoll accuracy
Hi Kay, There are a couple of things you could check and/or add here as you provide very little information. First of all, your kernel, -4, is relatively old. At the moment -16 is the released kernel and -19 is the latest security update. Could you please test with that one? Could you please add some information about your hardware? And attaching a dmesg would also be good. Also, the -generic kernel is geared towards desktop usage. So it provides a certain balance between realtime behaviour and throughput. One of these choices involves the preemption model within the kernel. -generic uses the voluntary preemption. You could try the -rt kernels, which have a higher preemption level, which may affect throughput. I also wonder whether ppoll really is the interface to use. The ubuntu kernels all have high res timers enabled. It is best for you to research the web about how to use these. You should be able to get below microsecond values, IIRC, on relatively modern hardware. Finally, I'm not sure whether checking an ELF note is the best way to determine the current HZ value of the kernel. First of all, that ps tool also needs to work on older kernels and second because in 2.6 there is no longer a relation between the user space HZ and the kernel HZ. -- Jiffies too low for acceptable ppoll accuracy https://bugs.launchpad.net/bugs/252728 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 242330] Re: [i915] GL screensaver crashes X server (using mergedFB)
There seems to be no dbg package for the i810 driver.
Here's a gdb trace:
#0 0x7f3bd6d43ddb in __glXDRIleaveServer (rendering=)
at ../../../GL/glx/glxdri.c:151
pGlxPix = (__GLXpixmap *) 0x4720676e6967616d
j = 0
screen = (__GLXDRIscreen * const) 0x8bc7d0
lastOverride = 1380015948
i = 1
#1 0x7f3bd6d146b8 in __glXleaveServer (rendering=1 '\001')
at ../../../GL/glx/glxext.c:491
No locals.
#2 0x7f3bd6d14c59 in __glXDispatch (client=0xdb3280)
at ../../../GL/glx/glxext.c:557
stuff = (xGLXSingleReq *) 0xc687e0
opcode =
proc = (__GLXdispatchSingleProcPtr) 0x7f3bd6d10f80 <__glXDisp_Render>
cl = (__GLXclientState *) 0xd34c30
retval = 1
#3 0x0044eaaf in Dispatch () at ../../dix/dispatch.c:502
clientReady =
result =
client = (ClientPtr) 0xdb3280
nready = 0
start_tick = 180
#4 0x00436b9d in main (argc=10, argv=0x7fffe2044288,
---Type to continue, or q to quit---
envp=) at ../../dix/main.c:452
i = 2
error = 0
xauthfile =
alwaysCheckForInput = {0, 1}
--
[i915] GL screensaver crashes X server (using mergedFB)
https://bugs.launchpad.net/bugs/242330
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 242330] Re: [i915] GL screensaver crashes X server (using mergedFB)
Bryce, It is hardy already. What makes you think otherwise? To start with these are the package versions (I guess I forgot them)... ii xserver-xgl 1:1.1.99.1~git20080115-0ubuntu1 GL-based X server ii xserver-xorg 1:7.3+10ubuntu10.2the X.Org X server ii xserver-xorg-core 2:1.4.1~git20080131-1ubuntu9.2Xorg X server - core server ii xserver-xorg-video-i810 2:1.7.4-0ubuntu7 X.Org X server -- Intel i8xx, i9xx display driver -- [i915] GL screensaver crashes X server (using mergedFB) https://bugs.launchpad.net/bugs/242330 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 225223] Re: OOo 2.4 opens documents semi readonly
Since there are two people having this problem and there appears to be a patch... ** Changed in: openoffice.org (Ubuntu) Status: New => Confirmed -- OOo 2.4 opens documents semi readonly https://bugs.launchpad.net/bugs/225223 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 243449] [NEW] screensaver ignores mouse action on second display
Public bug reported: I've got a dual-monitor system without xinerama. So there are two displays, :0.0 and :0.1. Whenever I'm working for longer periods on the .1 display using only the mouse then screensaver kicks in just as if it didn't notice the mouse usage. This is a x86_64 gutsy install with, among others, ii gnome-screensaver 2.22.2-0ubuntu1 GNOME screen saver and locker ii xserver-xorg 1:7.3+10ubuntu10 the X.Org X server ii xserver-xorg-core 2:1.4.1~git20080131-1ubuntu9.2Xorg X server - core server ii xserver-xorg-input-evdev 1:1.2.0-1ubuntu2 X.Org X server -- evdev input driver ii xserver-xorg-input-kbd 1:1.2.2-3ubuntu1 X.Org X server -- keyboard input driver ii xserver-xorg-input-mouse 1:1.2.3-2 X.Org X server -- mouse input driver I'll attach the xorg.conf I use. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- screensaver ignores mouse action on second display https://bugs.launchpad.net/bugs/243449 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 243449] Re: screensaver ignores mouse action on second display
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/15639514/xorg.conf ** Changed in: gnome-screensaver (Ubuntu) Sourcepackagename: None => gnome-screensaver -- screensaver ignores mouse action on second display https://bugs.launchpad.net/bugs/243449 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 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
I'm seeing this both on dom0 and domU with ...-19.34. As far as I can tell, there's no relation between seeing this on dom0 and domU. However, there seem to be no side-effects. (this is an amd64 install on both dom0 and domU and xen 3.2.1 from debian) dom0: Jun 26 14:02:06 quark kernel: [187781.880995] clocksource/0: Time went backwards: ret=ac186aa11cf0 delta=-36099370 shadow=ac183af22f78 offset=31d8212e domu: Jun 25 17:02:03 suzy2 kernel: [111734.752716] clocksource/0: Time went backwards: ret=6754298ec3ef delta=-64141945 shadow=675421edd381 offset=b7493a5 -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 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 242330] [NEW] GL screensaver crashes X server
Public bug reported: I recently started using a new X configuration (is it called mergedFB?). And since then the screen saver crashes the X server with this trace: Backtrace: 0: /usr/bin/X(xf86SigHandler+0x6a) [0x48402a] 1: /lib/libc.so.6 [0x7f84cb773100] 2: /usr/lib/xorg/modules/extensions//libglx.so [0x7f84c9f4eddb] 3: /usr/lib/xorg/modules/extensions//libglx.so(__glXleaveServer+0x18) [0x7f84c9f1f6b8] 4: /usr/lib/xorg/modules/extensions//libglx.so [0x7f84c9f1fc59] 5: /usr/bin/X(Dispatch+0x2ef) [0x44eaaf] 6: /usr/bin/X(main+0x47d) [0x436b9d] 7: /lib/libc.so.6(__libc_start_main+0xf4) [0x7f84cb75f1c4] 8: /usr/bin/X(FontFileCompleteXLFD+0x279) [0x435ed9] Fatal server error: Caught signal 11. Server aborting Previously with the xinerama configuration or a simple single-screen configuration this would not happen. I've checked that with the simple 'blank screen' screen saver the X server does not crash. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- GL screensaver crashes X server https://bugs.launchpad.net/bugs/242330 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 242330] Re: GL screensaver crashes X server
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/15533718/xorg.conf -- GL screensaver crashes X server https://bugs.launchpad.net/bugs/242330 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 242330] Re: GL screensaver crashes X server
** Attachment added: "Xorg.0.log.old" http://launchpadlibrarian.net/15533719/Xorg.0.log.old -- GL screensaver crashes X server https://bugs.launchpad.net/bugs/242330 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 242330] Re: GL screensaver crashes X server
I also checked the dmesg. It appears to contain just one line that *might* be related: [ 6832.432571] [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 11 emitted: 16 I don't think this appears each time the X server crashes, which is the reason for the 'might'. -- GL screensaver crashes X server https://bugs.launchpad.net/bugs/242330 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 225223] Re: OOo 2.4 opens documents semi readonly
me too. Sometimes. A simple, three word, document does not have this. But a larger, 8 page one, does. These two are stored side by side in the same directory... -- OOo 2.4 opens documents semi readonly https://bugs.launchpad.net/bugs/225223 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 225223] Re: OOo 2.4 opens documents semi readonly
Forgot to add... this is hardy but x86_64. It's the same openoffice version. The document that has the problem uses a TOC and outline numbering. There are no frames or pictures. And there are some tables in there as well. What else can I do to help investigate? -- OOo 2.4 opens documents semi readonly https://bugs.launchpad.net/bugs/225223 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 218126] Re: xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
@Tim, Hirano, I believe that Hiranos last comment (comment 19) is that 17.31 only contains a partial fix. Any idea when 17.32 with the correct fix is coming? (BTW, Hirano is right about the line with BUG being incorrect. Original has [i] and fix has [j]. This BUG is producing the traces at netfront.c:855) -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 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 218126] Re: xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
Chris, Wolfgang, Roger, I'm not entirely sure about this, but it might be necessary to turn off checksum offload in all doms on the same machine. If I remember correctly, it is required to turn off the offload in dom0 as well. I know I have it off in all domUs and dom0. -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 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 218126] Re: xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
Chris has a point there, about checksumming. I have no problems with the 17.31 kernel on an amd64 domU. And dom0 is running the hardy kernel (-16.xx), also amd64. I'm using debians hypervisor (3.2.0-3~bpo4+2). And I DO have checksumming offload off (as described using /etc/network/interfaces). It was necessary with previous kernels and I didn't even think about it. There is a difference between checksum offload on and off. With offload OFF I have a througput (domU->dom0) 18M/s; with offload on it is only 12 (using an 36M file). >From domU to domU (same host) it doesn't matter whether offload is on or off. But still no BUG. -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 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 50385] Re: samba can't be launched by a normal user (qemu related)
After the workaround I did, samba started and was usable from a w2k in qemu. (I did start chmodding only one file and manually starting smbd and then it complained about another one and then another one...) I don't know what's incomplete about this bug and I can confirm that it still exists with hardy packages: qemu 0.9.1-1ubuntu1, samba 3.0.28a- 1ubuntu4. ** Changed in: qemu (Ubuntu) Status: Incomplete => Confirmed -- samba can't be launched by a normal user (qemu related) https://bugs.launchpad.net/bugs/50385 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 218126] Re: xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
For me the image from proposed (17.31) works for and amd64 domU. I can ssh into the domU. (note that this debian etch/testing domU previously worked ok using 2.6.18 and I only replaced the kernel) -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 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 218126] Re: xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
kibe, it would be really useful to have the full trace. I suspect that it is present in 'dmesg'. Because it is now cut-off by the prompt. Thanks. -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 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 218126] Re: xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
Russell, what kernel are you currently using? I.e. does that domU work with a different kernel? Thanks. -- xen guest kernel bug: 'kernel BUG at /build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785' https://bugs.launchpad.net/bugs/218126 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 50385] Re: samba can't be launched by a normal user (qemu related)
Me too. As a really ugly workaround I thought about this... (1) disable samba to run as daemon (add 'exit' in /etc/default/samba) (2) sudo chmod a+rw /var/run/samba/*.tdb /var/lib/samba/*.tdb This totally ruins the samba security, I expect. That's why I disabled samba to start as a daemon. -- samba can't be launched by a normal user (qemu related) https://bugs.launchpad.net/bugs/50385 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 227033] Re: linux kernel socket deadlock (ndiswrapper?)
Did you try the debug parameter of ndiswrapper? Also the output of 'ndiswrapper -v' and 'ndiswrapper -l' would be interesting. Also, your problem might have been fixed in ndiswrapper 1.51: http://sourceforge.net/project/shownotes.php?release_id=562382&group_id=93482 Perhaps somewhere you can find a package to test it... -- linux kernel socket deadlock (ndiswrapper?) https://bugs.launchpad.net/bugs/227033 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
Re: [Bug 220246] Re: kernel panic - not syncing: attempted to kill init!
Matthias, Matthias Andersson wrote: > I ran the command update-initramfs -vu 2.6.24-16-386 and it seems to > have hit the spot. > What could had corrupted the old configuration, some error on shutdown or? > > //Matthias I've occaisionally had this as well. The ones I could trace were all caused by disk full situations. And one or two unclean shutdowns (I have /boot on an nfs server in dom0 so it can get to the files needed to boot) where data had not been send out yet. -- Jan Evert ** Attachment added: "smime.p7s" http://launchpadlibrarian.net/13825525/smime.p7s -- kernel panic - not syncing: attempted to kill init! https://bugs.launchpad.net/bugs/220246 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 220246] Re: kernel panic - not syncing: attempted to kill init!
It appears that your initrd is incomplete. Would you please check that there is enough disk space in /boot? (try df -h /boot) And also check the size of the initrd: ls -l /boot/initrd*; compare it with other versions. You can try recreating the initrd with 'update-initramfs -u 2.6.24-16-generic'. Add a -v for verbose output. -- kernel panic - not syncing: attempted to kill init! https://bugs.launchpad.net/bugs/220246 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 204010] Re: networking not working
Given that there are two reports that there's a setup where other kernel versions work but this one does not, I'd say it is confirmed that there's a bug in this kernel. ** Also affects: linux-source-2.6.24 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Sourcepackagename: linux-source-2.6.24 => linux Status: New => Confirmed -- networking not working https://bugs.launchpad.net/bugs/204010 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 146924] Re: "Time went backwards" + freeze for domU's with kernel 2.6.22-xen
Gareth, me too. I just tried (on my domU to fool around with) the latest rawhide kernel-xen. Runs just fine (for the last 30 or minutes and there's a lockdep warning early in dmesg -- so there's not much trust). [EMAIL PROTECTED]:~$ uname -r 2.6.25-0.18.rc8.fc9.x86_64.xen -- "Time went backwards" + freeze for domU's with kernel 2.6.22-xen https://bugs.launchpad.net/bugs/146924 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 204010] Re: networking not working
I just realized that this bug is on xen-3.2. But I guess this is wrong. I have a etch(64) domU with 2.6.18-5 on it. I have another domU with eth(64) userspace which I use for playing and testing. I've used this with the eth kernel (2.6.18), the feisty or gutsy 2.6.22 and now the hardy 2.6.24. The thing is, I don't use the ubuntu xen, but the etch backports one And still the hardy kernel doesn't do networking. So that's another hint that there's something with the kernel, not the hypervisor. I would say this is a problem of the hardy xen kernel. -- networking not working https://bugs.launchpad.net/bugs/204010 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 204010] Re: networking not working
So I tried it myself. It took actually a lot less effort than I expected! I downloaded the current xen kernel from (1), search for kernel-xen, and used alien to extract it (alien -g). The package also contains xen itself, I think, so don't convert and install! I manually copied part of /boot from the rpm and /lib/modules/2.6.25-something to the appropriate places. The xen block driver is a module again, xen-blkfront. So I had to add that to /etc/initramfs/modules. First boot I had to find out that the block device is now named xvdb1 instead of sdb1. Second boot worked just fine. Including the network That all took less than 15 minutes afer I found the rpm. Now if somebody would compare the code in Ubuntu with the srpm from (2)... (1)ftp://download.fedora.redhat.com/pub/fedora/linux/development/x86_64/os/Packages/ (2)ftp://download.fedora.redhat.com/pub/fedora/linux/development/source/SRPMS/ -- networking not working https://bugs.launchpad.net/bugs/204010 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 204010] Re: networking not working
Perhaps someboby should try a redhat kernel. Their status page (http://fedoraproject.org/wiki/Features/XenPvops) says it works... After that it just the same game: spot the difference. -- networking not working https://bugs.launchpad.net/bugs/204010 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 190870] Re: 2.6.24-7 does not start as xen domU
So it was not really a bug, just that the block access is now as a module instead of built-in. So I'm setting it to invalid (that's about the best I can guess). Also in 2.6.24.-16 it is back to built-in. And the networking is better handled in #204010. ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 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 204010] Re: networking not working
Another "me too". Deti, in -16 they finally decided to make the front- and backends into the kernel instead of modules. So the /etc/initramfs/modules workaround is no longer needed. -- networking not working https://bugs.launchpad.net/bugs/204010 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 190876] Re: wav file doesn't play properly on gusty-64
With hardy (due in 12 days) this is no longer a problem. -- wav file doesn't play properly on gusty-64 https://bugs.launchpad.net/bugs/190876 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 153878] Re: [gutsy] dualhead + locking system xorg crashes (915GM) (i810 driver)
I upgraded my laptop to hardy (which is due in some 12days). This is no longer a problem. GL based screensavers only show on one screen, but at least don't crash the session. -- [gutsy] dualhead + locking system xorg crashes (915GM) (i810 driver) https://bugs.launchpad.net/bugs/153878 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
Re: [Bug 190870] Re: 2.6.24-7 does not start as xen domU
MaurÃcio Magalhães wrote: > > Ignore my previous post, because it worked > > Workaround: > add to /etc/initramfs-tools/modules: > xenblk > blktap > blkbck > > and launch update-initramfs -u > > Tanks > > Actually you only need xenblk in a domU. I am interested whether you get the network operational. I can't get it to receive anything. And I'm stuck there. Thanks, Jan Evert -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 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 26119] Re: Possible fake host protected area (hpa) detected in ide drive causing SectorIdNotFound
I'm not so bold as to re-open this bug. But I really want you people to seriously consider my case. I've got this amd64 box with xen on it (running amd64 arch). The dom0 crashes exactly as Jorge Juan shows above (in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/26119/comments/30). Up till now there is NO NEWER dom0 kernel so really this is stuck at 2.6.18. Given that the patch appears to be really small and with a very limited scope I really hope that you reconsider the won't fix status of this bug. (why do I want to upgrade from 2.6.18? well, there's a SATA controller in there that I'm dying to use and 2.6.18 doesn't handle that very well and I'm hoping that 2.6.22 does much better) Thanks, Jan Evert -- Possible fake host protected area (hpa) detected in ide drive causing SectorIdNotFound https://bugs.launchpad.net/bugs/26119 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190870] Re: 2.6.24-7 does not start as xen domU
2.6.24-12 still has the same network problem. It appears to drop all received packets on the floor. Without any explanation. -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 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 190870] Re: 2.6.24-7 does not start as xen domU
This is the matching interface in dom0: vif12.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff::feff:/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:68 errors:0 dropped:27 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1640 (1.6 KiB) TX bytes:8565 (8.3 KiB) I wonder why those 27 tx frames were dropped... Also, the rx packets were successfully received by the dhcp server. At least some of the tx packets are responses. -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 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 190870] Re: 2.6.24-7 does not start as xen domU
The workaround described by Lionel works. Only xenblk is needed to make a domU boot. Next stop: getting the network interface operational... It first does this: Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated...[ 17.336715] netfront: Initialising virtual ethernet driver. done. And then somewhat later: Setting up networking Configuring network interfaces...Internet Software Consortium DHCP Client 2.0pl5 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved. Please contribute if you find this software useful. For info, please visit http://www.isc.org/dhcp-contrib.html [ 20.297349] NET: Registered protocol family 17 Listening on LPF/eth0/00:11:09:84:95:20 Sending on LPF/eth0/00:11:09:84:95:20 Sending on Socket/fallback/fallback-net DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 No DHCPOFFERS received. Trying recorded lease 192.168.1.114 PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data. --- 192.168.1.11 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms No working leases in persistent database. Exiting. Failed to bring up eth0. done. -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 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 190870] Re: 2.6.24-7 does not start as xen domU
linux-image-2.6.24-10-xen same story. Still need to get around adding the xen block backend to the initrd (dayjob needs time as well). -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 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 190870] Re: 2.6.24-7 does not start as xen domU
Also found out that the block backend in the kernel config (in -8) in Ubuntu is a module, while in debian it is build-in. So I'll also be making an initrd that has blkback in it. This is, of course, very likely the show stopper. Might make sense to set this to build-in simply because otherwise this package is useless? -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 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 190870] Re: 2.6.24-7 does not start as xen domU
Attempted http://archive.ubuntu.com/ubuntu/pool/universe/l/linux/linux-image-2.6.24-8-xen_2.6.24-8.13_amd64.deb. No such luck. The console looks the same. -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190870] Re: 2.6.24-7 does not start as xen domU
When rummaging through sysfs, I noticed this: (initramfs) ls -l /sys/bus/xen/devices/vbd-2065/ -r--r--r--1 004096 Feb 12 17:31 devtype -r--r--r--1 004096 Feb 12 17:31 nodename drwxr-xr-x2 00 0 Feb 12 17:31 power lrwxrwxrwx1 00 0 Feb 12 17:31 subsystem -> ../../../bus/xen -rw-r--r--1 004096 Feb 11 07:53 uevent while a normal domU has this: suzy2:~# ls -l /sys/bus/xen/devices/vbd-2053/ total 0 lrwxrwxrwx 1 root root0 Feb 12 18:33 block:sda5 -> ../../../block/sda5 lrwxrwxrwx 1 root root0 Feb 12 18:33 bus -> ../../../bus/xen -r--r--r-- 1 root root 4096 Feb 12 18:33 devtype lrwxrwxrwx 1 root root0 Feb 12 18:33 driver -> ../../../bus/xen/drivers/vbd -r--r--r-- 1 root root 4096 Feb 12 18:33 nodename drwxr-xr-x 2 root root0 Jan 8 21:34 power lrwxrwxrwx 1 root root0 Feb 12 18:33 subsystem -> ../../../bus/xen --w--- 1 root root 4096 Feb 12 18:33 uevent So the driver and block:xxx links are missing. I noticed that CONFIG_SYSFS_DEPRECATED is not set in the config. Might that have anything to do with this? -- 2.6.24-7 does not start as xen domU https://bugs.launchpad.net/bugs/190870 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153878] Re: [gutsy] dualhead + locking system xorg crashes (915GM) (i810 driver)
I appear to have this as well, although the backtrace is slightly different (earlier in _mesa_update_state_locked and an extra level): Backtrace: 0: /usr/bin/X(xf86SigHandler+0x6d) [0x48672d] 1: /lib/libc.so.6 [0x7fefc28f67d0] 2: /usr/lib/xorg/modules/extensions//libGLcore.so(xmesa_update_state+0x42) [0x7fef9f69f8a2] 3: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state_locked+0x455) [0x7fef9f5c3d25] 4: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_update_state+0x11) [0x7fef9f5c4121] 5: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_Clear+0x108) [0x7fef9f55f2e8] 6: /usr/lib/xorg/modules/extensions//libglx.so(DoRender+0x13b) [0x7fefc18e945b] 7: /usr/lib/xorg/modules/extensions//libglx.so [0x7fefc18ed00d] 8: /usr/bin/X(Dispatch+0x1db) [0x4514eb] 9: /usr/bin/X(main+0x45d) [0x439f4d] 10: /lib/libc.so.6(__libc_start_main+0xf4) [0x7fefc28e2b44] 11: /usr/bin/X(FontFileCompleteXLFD+0x231) [0x439249] It is with the i810 driver and dual head with different sizes for the monitors (the laptop has native 1440x900 and the CRT is a normal one using 1280x1024). Also, using the 'blank screen' screensaver doesn't crash. And the 'flying ubuntu' screen saver doesn't crash. My guess would be that GL based screensavers crash. And DRI is not available for me on this specific setup. This is with gutsy: ii xserver-xorg-video-i810 2:1.7.4-0ubuntu5 X.Org X server -- Intel i8xx, i9xx display driver ii gnome-screensaver 2.20.0-0ubuntu4.2 a screen saver and locker ii xscreensaver-data 4.24-5ubuntu3 data files to be shared among screensaver frontends ii xscreensaver-gl 4.24-5ubuntu3 GL(Mesa) screen hacks for xscreensaver Feel free to ask more specific information. I just don't know what else is relevant here. I also don't mind trying a patched .deb or installing debug packages. -- [gutsy] dualhead + locking system xorg crashes (915GM) (i810 driver) https://bugs.launchpad.net/bugs/153878 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190870] [NEW] 2.6.24-7 does not start as xen domU
Public bug reported: Binary package hint: linux-image-2.6.24-7-xen I decided to try to use this package (amd64 arch) for a domU, odo, on a xen server. For fun. Odo, FYI, is the domU used to test with and play around. The other domU handles all the mail and nfs serving. The server is debian stable (dom0, quark, is etch with kernel 2.6.18-5 and xen is 3.0.3) all amd64. Unfortunately it doesn't even start properly. As far as I can tell this is caused by "XENBUS: Device with no driver: device/vbd/2065" just before the initrd scripts start. The vbd/2065 is configured in the configuration file to show up as sdb1. On dom0 this vbd is an lvm volume. Probably you'd like to know that the odo userspace is also debian etch. There was a hitch when installing this kernel due to module-init-tools (this package wants 3.3-pre11, I believe). I force-depends-version-ed dpkg when installing the kernel. So there is still the old module-init-tools (3.3-pre4 from etch). I decided not to install that (yet) because it depends on a newer libc (unfortunately). Better to start small with disrupting the system (-: I'm not sure what other info to provide. Feel free to ask. Here's the console from the create: quark:~# xm create -c odo.cfg Using config file "/etc/xen/odo.cfg". Started domain odo [0.00] Linux version 2.6.24-7-xen ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-1ubuntu1)) #1 SMP Thu Feb 7 02:53:39 UTC 2008 (Ubuntu 2.6.24-4.6-generic) [0.00] Command line: root=/dev/sdb1 ro [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 1080 (usable) [0.00] end_pfn_map = 67584 [2892231.778961] Zone PFN ranges: [2892231.778963] DMA 0 -> 4096 [2892231.778965] DMA324096 -> 1048576 [2892231.778967] Normal1048576 -> 1048576 [2892231.778969] Movable zone start PFN for each node [2892231.778970] early_node_map[1] active PFN ranges [2892231.778972] 0:0 ->67584 [2892231.789869] No mptable found. [2892231.795008] PERCPU: Allocating 22368 bytes of per cpu data [2892231.795041] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 0 [2892231.795046] Kernel command line: root=/dev/sdb1 ro [2892231.795753] Initializing CPU#0 [2892231.795924] PID hash table entries: 2048 (order: 11, 16384 bytes) [2892231.795964] Xen reported: 1800.063 MHz processor. [0.031186] console [xvc0] enabled [0.031230] Console: colour dummy device 80x25 [0.031608] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) [0.032090] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) [0.032166] Software IO TLB disabled [0.035548] Memory: 233896k/270336k available (2467k kernel code, 27924k reserved, 1313k data, 216k init) [0.119710] Calibrating delay using timer specific routine.. 4511.89 BogoMIPS (lpj=9023785) [0.119777] Security Framework initialized [0.119786] SELinux: Disabled at boot. [0.119795] AppArmor: AppArmor initialized [0.119800] Failure registering capabilities with primary security module. [0.119824] Mount-cache hash table entries: 256 [0.119969] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [0.119973] CPU: L2 Cache: 512K (64 bytes/line) [0.119992] SMP alternatives: switching to UP code [0.120587] Freeing SMP alternatives: 22k freed [0.120758] Early unpacking initramfs... done [0.143866] Brought up 1 CPUs [0.144579] net_namespace: 120 bytes [0.144592] failed to set up cpufreq notifier [0.156712] Time: 165:165:165 Date: 165/165/65 [0.156763] NET: Registered protocol family 16 [0.157560] Brought up 1 CPUs [0.157579] PCI: Fatal: No config space access function found [0.157587] PCI: setting up Xen PCI frontend stub [0.158149] ACPI: Interpreter disabled. [0.158161] Linux Plug and Play Support v0.97 (c) Adam Belay [0.158214] pnp: PnP ACPI: disabled [0.158334] xen_mem: Initialising balloon driver. [0.158850] Setting mem allocation to 262144 kiB [0.159188] PCI: System does not support PCI [0.159197] PCI: System does not support PCI [0.166227] NET: Registered protocol family 8 [0.166236] NET: Registered protocol family 20 [0.166343] AppArmor: AppArmor Filesystem Enabled [0.166801] NET: Registered protocol family 2 [0.169620] Time: xen clocksource has been installed. [0.201576] IP route cache hash table entries: 4096 (order: 3, 32768 bytes) [0.201810] TCP established hash table entries: 16384 (order: 6, 262144 bytes) [0.201994] TCP bind hash table entries: 16384 (order: 6, 262144 bytes) [0.202191] TCP: Hash tables configured (established 16384 bind 16384) [0.202195] TCP reno registered [0.213649] checking if image is initramfs... it is [0.237192] Freeing initrd memory: 17500k freed [0.253805] audit: initializing netlink socket (disabled) [0.253828] audit(1202716419.689:1): initialized [
