[Bug 1915012] [NEW] Enable HDR10_PLUS in x265
Public bug reported: In order to allow encoding in material while preserving HDR10+ data, please enable option "ENABLE_HDR10_PLUS". Works (for me) for: Description:Ubuntu 20.10 Release:20.10 x265: Installed: 3.4-2 Candidate: 3.4-2 Version table: *** 3.4-2 500 500 http://ubuntu.mirror.lrz.de/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status When re-encoding video recorded using HDR10+, the additional metadata must be preserved for the target file. While using ffmpeg, which relies on libx265, the following warning appears using the distribution standard package: x265 [warning]: --dhdr10-info disabled. Enable HDR10_PLUS in cmake. ** Affects: x265 (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/1915012 Title: Enable HDR10_PLUS in x265 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x265/+bug/1915012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798683] Re: Mediathekview does not start because it cannot find its main class
The package "libjide-oss-java", which is a dependency of "mediathekview" does not provide a symlink for the required classpath entry "/usr/share/java/jide-oss.jar". This leads to the class-not-found error, instead of complaining about the missing classpath library. Temporary workaround: sudo ln -s /usr/share/java/jide-oss-3.7.4.jar /usr/share/java/jide- oss.jar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798683 Title: Mediathekview does not start because it cannot find its main class To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediathekview/+bug/1798683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425972]
Hi, sorry to revive this old thread, but what is the actual replacement for "-remote" from a functional point of view? I am asking because "-new-tab" and "-new-window" just don't respect the "-P" profile switch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425972 Title: Firefox no longer supports -remote parameter To manage notifications about this bug go to: https://bugs.launchpad.net/emacs/+bug/1425972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 342433] Re: hexdump :: irregular illegal seek
Hi Ralph, could you please download and execute the updated test script I have provided to verify that your version is running correctly? I just tested again on an Ubuntu 11.04 that has bsdmainutils 8.2.2 (which fails, but is OK since not an LTS release): $ testHexdump.sh ABCD +-+ | HEXDUMP test script v 1.2 | +-+ | System: Ubuntu 11.04 (natty) | BSD main utils version: 8.2.2 +- | Using test string ABCD | Cycles: 1 | Executions per cycle: 1000 +- Executing test 'echo'... :) stable Executing test 'echo ... | hexdump'... :) stable Executing test 'echo ... | hexdump -x'... :) stable Executing test 'echo ... | hexdump -x -s 1'... :( 61 / 1000 executions failed Executing test 'echo ... | sed ... | iconv ... | hexdump -x -s 2'... :( 70 / 1000 executions failed Executing test 'echo ... | xxd -s 1'... :) stable Executing test 'echo ... | od -x -j 1'... :) stable ...on the other hand an 11.10 installation with bsdmainutils 8.2.3 seems to be fine: $ ./bin/testHexdump.sh ABCD +-+ | HEXDUMP test script v 1.2 | +-+ | System: Ubuntu 11.10 (oneiric) | BSD main utils version: 8.2.3 +- | Using test string ABCD | Cycles: 1 | Executions per cycle: 1000 +- Executing test 'echo'... :) stable Executing test 'echo ... | hexdump'... :) stable Executing test 'echo ... | hexdump -x'... :) stable Executing test 'echo ... | hexdump -x -s 1'... :) stable Executing test 'echo ... | sed ... | iconv ... | hexdump -x -s 2'... :) stable Executing test 'echo ... | xxd -s 1'... :) stable Executing test 'echo ... | od -x -j 1'... :) stable ** Attachment added: Test script v1.2 https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/342433/+attachment/2700784/+files/testHexdump.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/342433 Title: hexdump :: irregular illegal seek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/342433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 748709] Re: general protection fault: 0000 [#1] SMP
And here is another one with the Natty kernel: ...although the message is different the call trace looks quite similar (shrink dcache vs. shrink icache)... [97899.170400] BUG: unable to handle kernel NULL pointer dereference at 0070 [97899.177089] IP: [81038bd9] __ticket_spin_lock+0x9/0x20 [97899.180017] PGD 1bacca067 PUD 1471b9067 PMD 0 [97899.180017] Oops: 0002 [#1] SMP [97899.180017] last sysfs file: /sys/devices/pci:00/:00:14.4/:06:06.0/net/eth1/speed [97899.180017] CPU 1 [97899.180017] Modules linked in: cdc_acm ip6table_filter ip6_tables 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 parport_pc ppdev dm_crypt binfmt_misc snd_hda_codec_hdmi n fs lockd fscache nfs_acl auth_rpcgss snd_hda_codec_realtek sunrpc snd_usb_audio kvm_amd snd_usbmidi_lib kvm snd_seq_midi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_rawmidi snd_seq_midi_event snd_seq joydev psmouse bridge snd_seq_device stp sp5100_tco i2c_piix4 serio_raw edac_core edac_mce_amd k10temp snd_timer snd usb_stora ge uas it87 hwmon_vid snd_page_alloc soundcore lp parport hid_sony usbhid hid radeon ttm drm_kms_helper drm xhci_hcd pata_jmicron firewire_ohci i2c_algo_bit firewire_core crc_itu_t pata_atiixp e1000 ahci r8169 libahci [97899.180017] [97899.180017] Pid: 66, comm: kswapd0 Not tainted 2.6.38-10-generic #46-Ubuntu Gigabyte Technology Co., Ltd. GA-790XTA-UD4/GA-790XTA-UD4 [97899.180017] RIP: 0010:[81038bd9] [81038bd9] __ticket_spin_lock+0x9/0x20 [97899.180017] RSP: 0018:88021b2abc80 EFLAGS: 00010202 [97899.180017] RAX: 0001 RBX: 0001 RCX: 81a3f120 [97899.180017] RDX: 88006d5884b8 RSI: 0080 RDI: 0070 [97899.180017] RBP: 88021b2abc80 R08: R09: 8800cf97ee50 [97899.180017] R10: R11: 0001 R12: 0070 [97899.180017] R13: 880035963e50 R14: 880035964010 R15: 88021b2abcf0 [97899.180017] FS: 7fd6179f0780() GS:8800cfa4() knlGS:f69cf880 [97899.180017] CS: 0010 DS: ES: CR0: 8005003b [97899.180017] CR2: 0070 CR3: 0001d998e000 CR4: 06e0 [97899.180017] DR0: DR1: DR2: [97899.180017] DR3: DR6: 0ff0 DR7: 0400 [97899.180017] Process kswapd0 (pid: 66, threadinfo 88021b2aa000, task 88021b2a16e0) [97899.180017] Stack: [97899.180017] 88021b2abc90 815c311e 88021b2abcc0 81195d5b [97899.180017] 880035963e50 880035963ec8 005a 0080 [97899.180017] 88021b2abd30 8117eba4 0007 004b [97899.180017] Call Trace: [97899.180017] [815c311e] _raw_spin_lock+0xe/0x20 [97899.180017] [81195d5b] remove_inode_buffers+0x3b/0xb0 [97899.180017] [8117eba4] prune_icache+0x1a4/0x2f0 [97899.180017] [8117ed45] shrink_icache_memory+0x55/0x60 [97899.180017] [8111c76c] shrink_slab+0x11c/0x180 [97899.180017] [8111f556] balance_pgdat+0x2d6/0x6d0 [97899.180017] [8111fa93] kswapd+0x143/0x1b0 [97899.180017] [8111f950] ? kswapd+0x0/0x1b0 [97899.180017] [81087866] kthread+0x96/0xa0 [97899.180017] [8100ce24] kernel_thread_helper+0x4/0x10 [97899.180017] [810877d0] ? kthread+0x0/0xa0 [97899.180017] [8100ce20] ? kernel_thread_helper+0x0/0x10 [97899.180017] Code: 00 00 48 c7 c2 de 89 03 81 48 c7 c1 e1 89 03 81 e9 dd fe ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 55 b8 00 00 01 00 48 89 e5 f0 0f c1 07 0f b7 d0 c1 e8 10 39 c2 74 07 f3 90 0f b7 17 eb f5 [97899.180017] RIP [81038bd9] __ticket_spin_lock+0x9/0x20 [97899.180017] RSP 88021b2abc80 [97899.180017] CR2: 0070 [97899.375191] ---[ end trace 455fc990db0719c9 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/748709 Title: general protection fault: [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/748709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742516] Re: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK theme)
Quite funny (from a software development PoV) that... a) ...some theme is able to break software b) ...that the theme integration is supposed to be rock solid (otherwise would've been shielded) c) ...that there is no fall-back mechanism Cheers, Ancoron -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742516 Title: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK theme) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/742516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 748709] Re: general protection fault: 0000 [#1] SMP
This also affects me, but started just two days ago (2011-08-18). I've also tried a different kernel (2.6.38 in Natty 3.0.0 vanilla with custom config), however, with no change. Up to now I was unable to say what causes this problem, but the call stack suspects kswapd once again (seems to be a source of a lot of problems since kernel 2.6.35). This is the dmesg output: [74528.204537] general protection fault: [#1] SMP [74528.204631] CPU 2 [74528.204665] Modules linked in: binfmt_misc ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables dm_crypt ppdev nfs lockd auth_rpcgss nfs_acl sunrpc kvm_amd kvm snd_hda_codec_hdmi snd_hda_codec_realtek snd_usb_audio snd_usbmidi_lib snd_seq_dummy snd_hda_intel snd_seq_oss snd_hda_codec snd_seq_midi snd_hwdep snd_pcm_oss snd_rawmidi snd_mixer_oss snd_seq_midi_event usb_storage snd_pcm snd_seq snd_seq_device joydev uinput snd_timer snd it87 hwmon_vid psmouse sp5100_tco soundcore serio_raw k10temp snd_page_alloc i2c_piix4 bridge lp stp parport hid_sony usbhid hid e1000 pata_atiixp radeon pata_jmicron r8169 mii ttm xhci_hcd ahci libahci fbcon tileblit font bitblit softcursor drm_kms_helper drm i2c_algo_bit [74528.205948] [74528.205976] Pid: 32, comm: kswapd0 Not tainted 3.0.0-chaoz #8 Gigabyte Technology Co., Ltd. GA-790XTA-UD4/GA-790XTA-UD4 [74528.206152] RIP: 0010:[81171ec8] [81171ec8] iput+0x68/0x1c0 [74528.206281] RSP: 0018:880220979b40 EFLAGS: 00010246 [74528.206366] RAX: 0001 RBX: 8800232af018 RCX: 8800232af0b8 [74528.206478] RDX: 0001 RSI: 8800232af038 RDI: 8800232af038 [74528.206590] RBP: 880220979b60 R08: 7018 R09: 017a1724b80c [74528.206702] R10: fe67e939cdbd2e03 R11: ea0003e6c3c0 R12: 8800232af038 [74528.206814] R13: 8000 R14: 88002326d0c0 R15: 8800232af018 [74528.206928] FS: 7f3095b52700() GS:88022fc8() knlGS:f69a3880 [74528.207055] CS: 0010 DS: ES: CR0: 8005003b [74528.207146] CR2: 01cb5e40 CR3: 000220f59000 CR4: 06e0 [74528.207258] DR0: DR1: DR2: [74528.207370] DR3: DR6: 0ff0 DR7: 0400 [74528.207483] Process kswapd0 (pid: 32, threadinfo 880220978000, task 880d96d0) [74528.207610] Stack: [74528.207643] 88002326d180 8800232af018 88002326d0c0 88002326d0c0 [74528.207768] 880220979b90 8116e3f0 880220979b90 88002326d180 [74528.207892] 88002326d1dc 880220979c10 880220979be0 8116e5ad [74528.208016] Call Trace: [74528.208062] [8116e3f0] d_kill+0x100/0x140 [74528.208145] [8116e5ad] shrink_dentry_list+0x17d/0x1f0 [74528.208243] [8116e7ce] __shrink_dcache_sb+0x1ae/0x1e0 [74528.208342] [8116e958] shrink_dcache_memory+0x158/0x1d0 [74528.208445] [8110b05d] shrink_slab+0x11d/0x190 [74528.208534] [8110e582] balance_pgdat+0x572/0x720 [74528.208626] [8110e83d] kswapd+0x10d/0x360 [74528.208709] [81081240] ? wake_up_bit+0x40/0x40 [74528.208798] [8110e730] ? balance_pgdat+0x720/0x720 [74528.208890] [81080ae6] kthread+0x96/0xa0 [74528.208971] [81590824] kernel_thread_helper+0x4/0x10 [74528.209068] [81080a50] ? flush_kthread_worker+0xb0/0xb0 [74528.209167] [81590820] ? gs_change+0x13/0x13 [74528.209249] Code: 4c 89 e6 e8 eb 1a 15 00 85 c0 75 17 48 8b 1c 24 4c 8b 64 24 08 4c 8b 6c 24 10 4c 8b 74 24 18 c9 c3 66 90 f6 43 28 08 4c 8b 6b 18 4d 8b 75 30 0f 85 19 01 00 00 4d 85 f6 74 79 49 8b 46 20 48 85 [74528.209678] RIP [81171ec8] iput+0x68/0x1c0 [74528.209763] RSP 880220979b40 [74528.311450] ---[ end trace c8c5b5270fa56a91 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/748709 Title: general protection fault: [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/748709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532174] Re: [Lucid] sun-java6-plugin not recognized by firefox anymore
@Thag: You are into something completely different. This bug just handles the registration of the sun-java plugin. Looking at the stacktrace you provided I see that you are already using the plugin. But on your side something prevents it from remotely loading classes on demand: Caused by: java.net.ConnectException: Connection timed out So do you already checked your firewall rules or e.g. your proxy/nat/routing? Looks like something in between just drops the packets that the plugin sends. -- [Lucid] sun-java6-plugin not recognized by firefox anymore https://bugs.launchpad.net/bugs/532174 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 608218] Re: You have old broken userspace please consider updating mesa
Also occurring in Lucid. -- You have old broken userspace please consider updating mesa https://bugs.launchpad.net/bugs/608218 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 602405] [NEW] No DEB packages when setlocalversion echos non-empty
Public bug reported: Binary package hint: kernel-package I use make-kpkg for compiling my kernels and building DEB packages, which I can then transfer over to other machines. I'm using upstream sources for this (e.g. the torvalds git tree). The thing is that there is a script scripts/setlocalversion which might generate output like a simple + in cases the source differs from the upstream version (e.g. self included patches aso.). If that is the case the generated version string looks like 2.6.35-rc4-amd64+ if the appended version string is just -amd64. This was not a problem before but now I get the following situation: when make-kpkg runs it replaces the placeholders inside the debian/control file with the version string unmodified and so the additional + sign don't make it into the debian/control file and one will get the same error as in issue #58307, comment #7: dpkg-gencontrol -DArchitecture=amd64 -isp\ -plinux-image-2.6.35-rc4-amd64+ -P/srv/dev/kernel/torvalds/linux-2.6/debian/linux-image-2.6.35-rc4-amd64+/ dpkg-gencontrol: error: package linux-image-2.6.35-rc4-amd64+ not in control info make[2]: *** [debian/stamp/binary/linux-image-2.6.35-rc4-amd64+] Error 255 make[2]: Leaving directory `/srv/dev/kernel/torvalds/linux-2.6' make[1]: *** [debian/stamp/binary/pre-linux-image-2.6.35-rc4-amd64+] Error 2 make[1]: Leaving directory `/srv/dev/kernel/torvalds/linux-2.6' make: *** [kernel-image] Error 2 The output explains this: ... sed -e 's/=V/2.6.35-rc4-amd64/g' \ -e 's/=D/2.6.35-rc4-amd64+-10.00.Custom/g' -e 's/=A/amd64/g' \ -e 's/=SA//g' \ -e 's/=I//g'\ -e 's/=CV/2.6/g'\ -e 's/=M/Unknown Kernel Package Maintainer unkn...@unconfigured.in.etc.kernel-pkg.conf/g' \ -e 's/=ST/linux/g' -e 's/=B/x86_64/g'\ /usr/share/kernel-package/Control debian/control ... And as the placeholder for the package includes V: Package: =ST- image-=V=SA it surely can't make it in. So in the end the version string that is generated into include/config/kernel.release: echo 2.6.35-rc4-amd64$(/bin/bash scripts/setlocalversion /srv/dev/kernel/torvalds/linux-2.6) include/config/kernel.release ...does not match the variable version that is used in /usr/share /kernel-package/ruleset/minimal.mk: test -f debian/control || sed -e 's/=V/$(version)/g' \ ** Affects: kernel-package (Ubuntu) Importance: Undecided Status: New -- No DEB packages when setlocalversion echos non-empty https://bugs.launchpad.net/bugs/602405 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 602405] Re: No DEB packages when setlocalversion echos non-empty
** Attachment added: Complete log of make-kpkg with KBUILD_VERBOSE=1 http://launchpadlibrarian.net/51476458/build.log -- No DEB packages when setlocalversion echos non-empty https://bugs.launchpad.net/bugs/602405 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 602405] Re: No DEB packages when setlocalversion echos non-empty
Additional note: neither make-kpkg clean nor make distclean nor manually editing the debian/control file before running make-kpkg fixes this issue. The only thing one can do is to completely vanish all local changes to the upstream sources which is not possible if you want to test some patches. -- No DEB packages when setlocalversion echos non-empty https://bugs.launchpad.net/bugs/602405 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 602405] Re: No DEB packages when setlocalversion echos non-empty
$ lsb_release -rd Description:Ubuntu 10.04 LTS Release:10.04 $ dpkg -s kernel-package | egrep '^Version' Version: 12.032 -- No DEB packages when setlocalversion echos non-empty https://bugs.launchpad.net/bugs/602405 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 535572] Re: System hard locks with Lucid
Hi Charlie,
your hardware setup seems to differ a lot from mine. I presume the
problem I reported here deals with some AMD-related things (CPU or some
never Hardware on the board where support was incomplete in kernel
2.6.32).
I currently use 2.6.35-rc3 and since 2.6.34 I didn't experience any
freezes again.
However, to verify that you have the same problem as I did please put
the following into a script and run it in a terminal (let it run until
you experience the freeze again and upload the produced log here):
#!/bin/sh
logfile=ticks-`date +'%F-%H-%M-%S'`.log
time=0
while [ 0 ]; do
oldtime=$time
time=`date +'%s.%N'`
sec=`echo $time | sed -e 's/^\([0-9]\+\)\..*$/\1/g'`
ms=`echo $time | sed -e 's/^.*\.\([0-9]\{3\}\).*$/\1/g'`
pretty=`date --date 1970-01-01 $sec sec +'%F %T'`.$ms
echo ($time - $oldtime - 1) * 1000 | bc -l | xargs printf [$pretty]
missed %1.0f ms\n | tee -a $logfile
sleep 1
done
--
System hard locks with Lucid
https://bugs.launchpad.net/bugs/535572
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 535572] Re: System hard locks with Lucid
If your freeze happened during file system activity did the system swap heavily? I ask because we have another bug here: #561210 Although the summary tells something else the main reason for those freezes seem to be heavy swapping issues, And so your freeze could be related to that too. To test that you could make your system consume all memory (maybe already swapping some MiB's). And then start such a file copy job as you did before. If it freezes then or makes your mouse pointer movement stuttering or the system less responsive then chances are good that it is your issue too. -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 561210] Re: Writing big files to NFS target causes system lock up
@Jim: That looks to me like a test case :) All this information leads me to the same conclusion that those blocking behavior occurs most commonly when the system runs out of free RAM and starts to swap heavily. I'm currently running a vanilla kernel 2.6.35-rc3 and with that I wasn't able to reproduce some blocking here, but what I noticed was that when the system starts this heavy swapping even my hardware accelerated mouse cursor get stuck sometimes (reminds me on an old crappy windows box I used to have). And this plus the fact that the whole user interface (at least with KDE4) locks up sometimes points me to something that isn't necessarily related to NFS itself. As every file operation in Linux also uses the system memory to speed up things it could be that the priority of what gets swapped out and what swapped in doesn't suite the individual needs. In the worst case if something like plasma-desktop is chosen to be swapped out then parts of it immediately are scheduled for swap-in as plasma-desktop updates periodically. That way the wrong swapping strategy could introduce this issue. On the other hand I don't understand why the hell is some heavy swapping able to interfere a hardware accelerated mouse cursor? This lonely symptom leads me to another pointer: interrupt handling. But then I don't know enough about that thing to go any further. I just issued a test on my 2.6.35-rc3 box: - set up an NFS mount with rsize=128,wsize=128 - make the system memory (4GB) almost completely used by other processes (very few file cache/buffered) - issue a gunzip of a 4.1 GiB file from the NFS mount to the NFS mount And now guess what? Yes, I got those hung tasks again even with a much newer kernel, so the problem isn't addressed upstream and can't be in lucid. Although this time it is a bit different because I don't get NFS related backtraces here. Instead (and what I currently think is more of a reason to this problem) I always get some calls for memory allocation and/or paging requests. So the system is heavily swapping and the swapping needs time as we all know. But instead just waiting for the scheduled operation to complete it blocks and therefore interferes user interaction at all. To verify that problem I just made up some KVM's on my machine at work (a 6-core AMD64, 8GiB RAM) and even without having any NFS mounts or exports I got some very similar behavior. Although I didn't provoke a complete lockup yet (well, I need to do some work there), I also got temporarily freezing hardware accelerated mouse cursor and completely non-responsive desktop (at least for some seconds up to a minute). Here it goes for my machine with kernel 2.6.35-rc3: [240602.803784] INFO: task kwin:2102 blocked for more than 120 seconds. [240602.803787] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [240602.803789] kwin D 0 2102 2100 0x [240602.803793] 8801281d93d8 0086 880073c09cc8 00015840 [240602.803796] 8801281d9fd8 00015840 8801281d9fd8 88012a2196d0 [240602.803798] 00015840 00015840 8801281d9fd8 00015840 [240602.803800] Call Trace: [240602.803806] [81032ca9] ? default_spin_lock_flags+0x9/0x10 [240602.803809] [810eda70] ? sync_page+0x0/0x50 [240602.803812] [81534327] io_schedule+0x47/0x70 [240602.803814] [810edaad] sync_page+0x3d/0x50 [240602.803816] [81534bdf] __wait_on_bit+0x5f/0x90 [240602.803818] [810edc63] wait_on_page_bit+0x73/0x80 [240602.803821] [8107a720] ? wake_bit_function+0x0/0x40 [240602.803824] [810fb266] shrink_page_list+0x176/0x580 [240602.803826] [8106b430] ? process_timeout+0x0/0x10 [240602.803828] [81032ca9] ? default_spin_lock_flags+0x9/0x10 [240602.803830] [8107a877] ? finish_wait+0x67/0x90 [240602.803832] [8110552e] ? congestion_wait+0x7e/0x90 [240602.803834] [8107a6e0] ? autoremove_wake_function+0x0/0x40 [240602.803837] [810fbd54] shrink_inactive_list+0x6e4/0x7f0 [240602.803839] [81047e18] ? update_curr+0xf8/0x1e0 [240602.803842] [810f5f7a] ? determine_dirtyable_memory+0x1a/0x30 [240602.803844] [810f6027] ? get_dirty_limits+0x27/0x2f0 [240602.803846] [8105197c] ? try_to_wake_up+0xcc/0x400 [240602.803848] [810fc1cb] shrink_zone+0x36b/0x4b0 [240602.803850] [810fc403] do_try_to_free_pages+0xf3/0x440 [240602.803852] [810fc8f8] try_to_free_pages+0x68/0x70 [240602.803854] [810f4428] __alloc_pages_nodemask+0x3e8/0x6f0 [240602.803857] [81444bef] ? __alloc_skb+0x4f/0x170 [240602.803859] [8112ae52] kmalloc_large_node+0x62/0xb0 [240602.803861] [8112e6fc] __kmalloc_node_track_caller+0x13c/0x1f0 [240602.803864] [81440a64] ? sock_alloc_send_pskb+0x1d4/0x340 [240602.803866] [81444c23] __alloc_skb+0x83/0x170 [240602.803868]
[Bug 561210] Re: Writing big files to NFS target causes system lock up
Jeremy, I disagree with the status change to Fix Released as it is not fixed. The problem still occurs. It didn't occur for my main workstation here as I have raised the rsize/wsize to 32MB on the NFS mounts here and I am just issuing one to two NFS transactions at a time, so it didn't come up in the first place. However, even if I raise the rsize/wsize I still can reproduce this issue by throwing a bit more work in parallel for the NFS mounts. On a standard NFS mount just a cp of a 400 MB file from the NFS mount to the same is sufficient to raise this issue again. This doesn't occur every time but around every second or third run at least. I'll try to test the workload required for my 32MB mounts to get stuck too. After that I'll be able to build a small script as a test case for that. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
Well, today on one of my machine here at home this issue is back: [616201.460064] INFO: task kswapd0:52 blocked for more than 120 seconds. [616201.460072] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [616201.460079] kswapd0 D 052 2 0x [616201.460090] 880128d2f720 0046 00015bc0 00015bc0 [616201.460100] 88012af8df80 880128d2ffd8 00015bc0 88012af8dbc0 [616201.460108] 00015bc0 880128d2ffd8 00015bc0 88012af8df80 [616201.460117] Call Trace: [616201.460153] [a03a62b0] ? nfs_wait_bit_uninterruptible+0x0/0x20 [nfs] [616201.460166] [8153eb87] io_schedule+0x47/0x70 [616201.460192] [a03a62be] nfs_wait_bit_uninterruptible+0xe/0x20 [nfs] [616201.460201] [8153f3df] __wait_on_bit+0x5f/0x90 [616201.460211] [811346a6] ? __slab_free+0x96/0x120 [616201.460235] [a03a62b0] ? nfs_wait_bit_uninterruptible+0x0/0x20 [nfs] [616201.460243] [8153f488] out_of_line_wait_on_bit+0x78/0x90 [616201.460252] [81085360] ? wake_bit_function+0x0/0x40 [616201.460277] [a03a629f] nfs_wait_on_request+0x2f/0x40 [nfs] [616201.460302] [a03aa6af] nfs_wait_on_requests_locked+0x7f/0xd0 [nfs] [616201.460329] [a03abaee] nfs_sync_mapping_wait+0x9e/0x1a0 [nfs] [616201.460354] [a03abc71] nfs_wb_page+0x81/0xe0 [nfs] [616201.460376] [a039ab2f] nfs_release_page+0x5f/0x80 [nfs] [616201.460384] [810f2bb2] try_to_release_page+0x32/0x50 [616201.460392] [81101833] shrink_page_list+0x453/0x5f0 [616201.460402] [8113b419] ? mem_cgroup_del_lru+0x39/0x40 [616201.460409] [81100517] ? isolate_lru_pages+0x227/0x260 [616201.460417] [81101cdd] shrink_inactive_list+0x30d/0x7e0 [616201.460426] [810116c0] ? __switch_to+0xd0/0x320 [616201.460434] [81076e2c] ? lock_timer_base+0x3c/0x70 [616201.460441] [810778b5] ? try_to_del_timer_sync+0x75/0xd0 [616201.460449] [81102241] shrink_list+0x91/0xf0 [616201.460455] [81102437] shrink_zone+0x197/0x240 [616201.460463] [811034c9] balance_pgdat+0x659/0x6d0 [616201.460470] [81100550] ? isolate_pages_global+0x0/0x50 [616201.460477] [8110363e] kswapd+0xfe/0x150 [616201.460485] [81085320] ? autoremove_wake_function+0x0/0x40 [616201.460492] [81103540] ? kswapd+0x0/0x150 [616201.460498] [81084fa6] kthread+0x96/0xa0 [616201.460506] [810141ea] child_rip+0xa/0x20 [616201.460513] [81084f10] ? kthread+0x0/0xa0 [616201.460520] [810141e0] ? child_rip+0x0/0x20 This was an extract job for a rather small archive (just ~ 400 MiB) from the NAS, to the NAS (I know this is bad practice). What also came up is that again KDE4 completely freezes, until the lock is released: [616201.460551] INFO: task plasma-desktop:7429 blocked for more than 120 seconds. [616201.460556] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [616201.460561] plasma-deskto D 0 7429 1 0x [616201.460570] 88012766b158 0086 00015bc0 00015bc0 [616201.460579] 880127acdf80 88012766bfd8 00015bc0 880127acdbc0 [616201.460587] 00015bc0 88012766bfd8 00015bc0 880127acdf80 [616201.460595] Call Trace: [616201.460619] [a03a62b0] ? nfs_wait_bit_uninterruptible+0x0/0x20 [nfs] [616201.460628] [8153eb87] io_schedule+0x47/0x70 [616201.460651] [a03a62be] nfs_wait_bit_uninterruptible+0xe/0x20 [nfs] [...] When the lock is released all apps are going back to usual work. I wouldn't mind if the NFS transfer hangs for some time waiting for the target to complete some work but it just interferes any interaction with the machine so this is a real show-stopper. However, there was a difference how those NFS export got mounted. The machine that still is fine mounts like this: rw,rsize=32768,wsize=32768,hard,intr,noatime ...and the machine that just showed this issue again mounts like: rw,hard,intr,noatime So I wouldn't expect that setting the sizes changes anything but please give it a try if you haven't done so before. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
@Christoph: If you still experience this bug please do that apport- collect thing. For me it is fine here. Tested with two different amd64 machines accessing a single NAS (1 Gb network, software-RAID-5 on busybox NAS, write speed 20 - 30 MiB/s). Also simultaneous read/write access doesn't yield any problem here. How I mount them: rw,rsize=32768,wsize=32768,hard,intr,noatime -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 535572] Re: System hard locks with Lucid
For some time now the system runs somewhat stable. I enabled Cool Quite in the BIOS but disabled C1E support. If I enable C1E support than I immediately get those big lags back (doesn't depend on a specific kernel as I tested 2.6.32 up to 2.6.34) and I presume that after some time the machine would lock again. With C1E disabled I get the following output from my script which is much nicer: ... [2010-05-28 07:05:21.500] missed 27 ms [2010-05-28 07:05:22.528] missed 28 ms [2010-05-28 07:05:23.555] missed 27 ms [2010-05-28 07:05:24.583] missed 28 ms [2010-05-28 07:05:25.610] missed 27 ms [2010-05-28 07:05:26.637] missed 27 ms [2010-05-28 07:05:27.665] missed 28 ms [2010-05-28 07:05:28.693] missed 27 ms [2010-05-28 07:05:29.720] missed 27 ms [2010-05-28 07:05:30.747] missed 27 ms [2010-05-28 07:05:31.774] missed 27 ms [2010-05-28 07:05:32.802] missed 28 ms [2010-05-28 07:05:33.829] missed 27 ms [2010-05-28 07:05:34.858] missed 29 ms [2010-05-28 07:05:35.885] missed 27 ms [2010-05-28 07:05:36.913] missed 27 ms ... So the lags are now considered to be stable (26-29ms). But C1E support is a nice thing regarding power management so this still is an issue and probably will be for Ubuntu 10.10. ** Changed in: linux (Ubuntu) Status: Expired = Incomplete ** Tags removed: kj-expired -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] Re: System hard locks with Lucid
apport information ** Tags added: apport-collected ** Description changed: I'm currently using Kubuntu Lucid Alpha 3 with latest updates applied and the more recent xorg drivers from the xorg-edgers PPA on launchpad as this machine has a AMD/ATI Radeon HD4770 (RV740) and only the 2.6.33 kernel has the initialization fix to run this system at all (of course vesa could be used otherwise but that is a waste of resources). The system comes up in UMS only (KMS is still broken with this card). It runs fine for a while and then hard locks at some point. There is nothing in the logs. If I wouldn't run the clock at my Logitech G15 LCD keyboard I wouldn't know when it locked up. I monitor the system to exclude failing hardware. Beside those hard locks I discovered some other oddities: - KVM kernel modules (kvm, kvm-amd) doesn't load at boot time (not even with forcing them through /etc/modules) - g15daemon starts but then just whipes away, LCD is black after that Hardware: - AMD Phenom II X4 955 (3.2GHz) - 2x 2GB DDR3 RAM (1333MHz) - Gigabyte GA-790XTA-UD4 motherboard - AMD/ATI Radeon HD4770 (RV740) - Dell WFP3007 30 LCD (2560x1600) - 2x 500GB (Hitachi Deskstar T7K500, no RAID) I've even updated the BIOS in hope that it fixes the issue. $ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' +Mixer name : 'Realtek ALC889' +Components : 'HDA:10ec0889,1458a102,0014' +Controls : 41 +Simple ctrls : 23 + Card1.Amixer.info: + Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19' +Mixer name : 'ATI R6xx HDMI' +Components : 'HDA:1002aa01,00aa0100,00100100' +Controls : 4 +Simple ctrls : 1 + Card1.Amixer.values: + Simple mixer control 'IEC958',0 +Capabilities: pswitch pswitch-joined penum +Playback channels: Mono +Mono: Playback [off] + DistroRelease: Ubuntu 10.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=81ddb40a-ad96-4059-8bba-e18c013d5c48 + InstallationMedia: Kubuntu 10.04 Lucid Lynx - Alpha amd64 (20100225) + MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4 + Package: linux (not installed) + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=aac3cf7c-104c-4af2-930a-b848744a59c0 ro crashkernel=384M-2G:64M,2G-:128M quiet splash radeon.modeset=0 + ProcEnviron: + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 + Regression: No + RelatedPackageVersions: linux-firmware 1.34 + Reproducible: Yes + RfKill: + + Tags: lucid filesystem needs-upstream-testing + Uname: Linux 2.6.32-22-generic x86_64 + UserGroups: + + dmi.bios.date: 12/14/2009 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: F3a + dmi.board.name: GA-790XTA-UD4 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3a:bd12/14/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: + dmi.product.name: GA-790XTA-UD4 + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/49248884/AlsaDevices.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/49248885/AplayDevices.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/49248886/ArecordDevices.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/49248887/BootDmesg.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/49248890/Card0.Amixer.values.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/49248893/CurrentDmesg.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/49248891/Card0.Codecs.codec.0.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/49248900/PciMultimedia.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/49248901/ProcCpuinfo.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] Card1.Codecs.codec.0.txt
apport information ** Attachment added: Card1.Codecs.codec.0.txt http://launchpadlibrarian.net/49248892/Card1.Codecs.codec.0.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] IwConfig.txt
apport information ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/49248894/IwConfig.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/49248896/Lspci.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] UdevDb.txt
apport information ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/49248905/UdevDb.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] UdevLog.txt
apport information ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/49248906/UdevLog.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] Lsusb.txt
apport information ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/49248897/Lsusb.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/49248917/WifiSyslog.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] Re: System hard locks with Lucid
Those apport-collect is from the Lucid kernel running with C1E enabled. -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/49248902/ProcInterrupts.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 535572] ProcModules.txt
apport information ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/49248903/ProcModules.txt -- System hard locks with Lucid https://bugs.launchpad.net/bugs/535572 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 564559] Re: URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display
@thehighhat: as described in the freedesktop bug on my side it works with UMS (radeon.modeset=0 boot command, I think nomodeset has been deprecated). Although I use the xorg-edgers PPA drivers, not the official Lucid ones. Give it a shot. This bug is clearly about radeon and just provides a fix for radeon KMS, so if there is a similar problem for nVidia cards please file a new bug. Also I see that there hasn't been filed a bug on freedesktop.org for the nouveau driver lately. Please file there first. -- URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display https://bugs.launchpad.net/bugs/564559 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 564559] Re: URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display
@Steve: You are 100% right, Sir. Mixed that up with some other things in my brain... :-) @thehighhat: The fix for the duallink DVI radeon KMS is not using UMS and the xorg-edgers PPA. It is just a workaround for now and only for radeon. The real fix is the patch I provided wit comment #2. If your radeon setup doesn't work with UMS please file a new bug here and on freedesktop.org. If your radeon setup doesn't work with KMS even if you build the Lucid kernel with the patch included (see here for instructions: https://help.ubuntu.com/community/Kernel/Compile) then you'll also have to file a new bug. As I said already I checked the nouveau project and there is no bug regarding duallink DVI in the last few months. However there is a bug report from 2009-09-08 that seems to be interesting: https://bugs.freedesktop.org/show_bug.cgi?id=23495 There one of the developers states: ... Now, we don't know exactly how to program dual-link as of yet ... So your nVidia setup might be a bit of a problem though. Did you test nouveau with the latest mainstream kernel as suggested by the xorg- edgers PPA? You can also use the latest DRM for testing: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/current/ Please test those with your setup. It will help provide a better fix. ** Bug watch added: freedesktop.org Bugzilla #23495 http://bugs.freedesktop.org/show_bug.cgi?id=23495 -- URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display https://bugs.launchpad.net/bugs/564559 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 561554] Re: [KMS] Desktop freeze + radeon_fence_wait errors
Apparently I don't have access to the X1550 system anymore (new job). Additionally in my home system with the HD4770 this is still an issue. Therefore I'm currently using 2.6.34 from torvalds GIT that doesn't have such problems. In addition it doesn't suffer from #564559 which is still not integrated although it should happen weeks ago. -- [KMS] Desktop freeze + radeon_fence_wait errors https://bugs.launchpad.net/bugs/561554 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 564559] Re: URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display
Apparently not in 2.6.32-22. On 04/21/2010 11:59 AM, Andy Whitcroft wrote: Applied to Lucid. -apw So I thought it would make it into 2.6.32-22, which got released on 2010-04-28, but the only changes are: linux (2.6.32-22.33) lucid-proposed; urgency=low [ Andy Whitcroft ] * SAUCE: ACPI: EC: Allow multibyte access to EC (v3) - LP: #526354 [ Tim Gardner ] * ubuntu: rtl8192se -- update to version 0015.0127.2010 - LP: #567016 -- Andy Whitcroft a...@canonical.com Mon, 19 Apr 2010 11:06:35 +0100 So we have to wait... -- URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display https://bugs.launchpad.net/bugs/564559 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 500077] Re: k10temp: there is no support for k10-thermal-sensors in kernel 2.6.32
Nearly perfect! + The multiple kernel feature, very nice and convenient. But I have some upstream kernels installed that already have the module compiled and enabled, so you should check for that and disable integration for those kernels. In addition I noticed that it only integrates the module into kernels that are at the version I currently run and above, but e.g. I have the stock Lucid kernel 2.6.32-21-generic but I currently run 2.6.32.11+drm33.2-duallink-fix (like stock kernel plus a patch, same config). And here it doesn't update the stock kernel. Is it because - is lower than .? Anyway it just loads fine after installation: $ uname -r 2.6.32.11+drm33.2-duallink-fix $ sudo modprobe k10temp $ sensors it8720-isa-0228 Adapter: ISA adapter in0: +1.02 V (min = +0.00 V, max = +4.08 V) in1: +1.49 V (min = +0.00 V, max = +4.08 V) in2: +3.36 V (min = +0.00 V, max = +4.08 V) in3: +3.04 V (min = +0.00 V, max = +4.08 V) in4: +3.02 V (min = +0.00 V, max = +4.08 V) in5: +1.94 V (min = +0.00 V, max = +4.08 V) in6: +4.08 V (min = +0.00 V, max = +4.08 V) in7: +2.18 V (min = +0.00 V, max = +4.08 V) Vbat:+3.25 V fan1:712 RPM (min =0 RPM) fan2: 0 RPM (min =0 RPM) fan3: 0 RPM (min =0 RPM) fan5: 0 RPM (min =0 RPM) temp1: +44.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +29.0°C (low = +127.0°C, high = +70.0°C) sensor = thermal diode temp3: +39.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor cpu0_vid: +0.413 V k10temp-pci-00c3 Adapter: PCI adapter temp1: +35.1°C (high = +70.0°C, crit = +79.0°C) Thanx for that! -- k10temp: there is no support for k10-thermal-sensors in kernel 2.6.32 https://bugs.launchpad.net/bugs/500077 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 538259] Re: G-keys don't work on Logitech G15 keyboard
** Tags added: lucid -- G-keys don't work on Logitech G15 keyboard https://bugs.launchpad.net/bugs/538259 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 538259] Re: G-keys don't work on Logitech G15 keyboard
Made a patch against current lucid package. @OP: could you test that one please? Shall give us the opportunity to get this one into an SRU. ** Patch added: make-g-keys-work-again.patch http://launchpadlibrarian.net/46395768/make-g-keys-work-again.patch -- G-keys don't work on Logitech G15 keyboard https://bugs.launchpad.net/bugs/538259 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 561210] Re: Writing big files to NFS target causes system lock up
Just made some tests with some ISO's (690 MiB - 3.7 GiB) and the issue seems to be fixed. Now I got consistent read/write speed back again. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
Yepp, the upstream commit seams to be this one: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bb6fbc4548b9ae7ebbd06ef72f00229df259d217 But in addition this one should also be considered for a backport: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d812e575822a2b7ab1a7cadae2571505ec6ec2bd So, let's backport them and see if they really fix the issue... -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
Well, just to see that 2.6.32.11 is already the current version for Lucid. So it should be fine. If it is not then it is a problem elsewhere. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 564559] Re: URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display
Kubuntu and Ubuntu are the same in terms of kernel/drm/kms stuff. If you get a black screen after the boot splash you are not affected by this bug. In addition this bug is about a dual-link DVI issue and has nothing to do with dual-head setups (remember, dual-link DVI is for digital signals higher than WUXGA [1920 × 1200]). So you'll have to see if there is another bug available that looks like yours or just file a new one. -- URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display https://bugs.launchpad.net/bugs/564559 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 564559] Re: URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display
Confirmed over here too, so all seems fine. Adam is correct complaining about the description. Nevertheless another problem solved for the final release. :-) Now if someone can point me to the KMS KDE4 effects performance issue? -- URGENT for upcoming release: Resolutions requiring dual link DVI on radeon result in no display https://bugs.launchpad.net/bugs/564559 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 564559] Re: URGENT for upcomming release: Resolutions requiring dual link DVI on radeon result in no display
This is a patch made according to the upstream patch and it fixes the issue with KMS and DualLink monitors. According to upstream the fix should be included in the final 2.6.34. ** Patch added: Patch according to upstream that fixes 2.6.32-21 http://launchpadlibrarian.net/44573476/duallink-fix.patch ** Bug watch added: freedesktop.org Bugzilla #27001 http://bugs.freedesktop.org/show_bug.cgi?id=27001 ** Also affects: linux via http://bugs.freedesktop.org/show_bug.cgi?id=27001 Importance: Unknown Status: Unknown -- URGENT for upcomming release: Resolutions requiring dual link DVI on radeon result in no display https://bugs.launchpad.net/bugs/564559 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 561789] Re: Freeze with KMS enabled on Radeon RV350
Looks exactly like my problem (although I didn't ever get this directly after X start): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/561554 -- Freeze with KMS enabled on Radeon RV350 https://bugs.launchpad.net/bugs/561789 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 561554] Re: [KMS] Desktop freeze + radeon IB schedule errors
Just some very similar thing occurred with a completely different setup: - ATI Radeon HD4770 - Dell 3007WFP-HC (2560x1600) The first error message is the same: [ 859.792340] [drm:radeon_fence_wait] *ERROR* fence(880086501240:0x00042766) 510ms timeout going to reset GPU So I think this is the same issue, although the resulting output differs a lot (could just be different code paths between r500 and r700 GPU driver/drm code). Attached is the kern.log of the complete session. The driver itself drops at some point: [mi] EQ overflowing. The server is probably stuck in an infinite loop. Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a9e68] 1: /usr/bin/X (mieqEnqueue+0x1f4) [0x4a8f24] 2: /usr/bin/X (xf86PostMotionEventP+0xc4) [0x4705d4] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f9589219000+0x402f) [0x7f958921d02f] 4: /usr/bin/X (0x40+0x757a7) [0x4757a7] 5: /usr/bin/X (0x40+0x117493) [0x517493] 6: /lib/libpthread.so.0 (0x7f958d2c3000+0xf8f0) [0x7f958d2d28f0] 7: /usr/bin/X (0x40+0x58120) [0x458120] 8: /lib/libpthread.so.0 (0x7f958d2c3000+0xf8f0) [0x7f958d2d28f0] 9: /lib/libc.so.6 (ioctl+0x7) [0x7f958c075197] 10: /lib/libdrm.so.2 (drmIoctl+0x28) [0x7f958a6265b8] 11: /lib/libdrm.so.2 (drmCommandWriteRead+0x1c) [0x7f958a6267fc] 12: /lib/libdrm_radeon.so.1 (0x7f9589f13000+0x16d9) [0x7f9589f146d9] 13: /lib/libdrm_radeon.so.1 (0x7f9589f13000+0x1724) [0x7f9589f14724] 14: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f958a118000+0xbd570) [0x7f958a1d5570] 15: /usr/lib/xorg/modules/libexa.so (0x7f9589adc000+0x84c8) [0x7f9589ae44c8] 16: /usr/bin/X (0x40+0x152eb4) [0x552eb4] 17: /usr/bin/X (0x40+0x3b0ef) [0x43b0ef] 18: /usr/bin/X (0x40+0x3985c) [0x43985c] 19: /usr/bin/X (0x40+0x2602a) [0x42602a] 20: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f958bfb5c4d] 21: /usr/bin/X (0x40+0x25bd9) [0x425bd9] ** Attachment added: kern.log (RV740 KMS session) http://launchpadlibrarian.net/44579432/kern.rv740.log ** Summary changed: - [KMS] Desktop freeze + radeon IB schedule errors + [KMS] Desktop freeze + radeon_fence_wait errors -- [KMS] Desktop freeze + radeon_fence_wait errors https://bugs.launchpad.net/bugs/561554 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 561554] Re: [KMS] Desktop freeze + radeon_fence_wait errors
Although I've built my own kernel here with the RV740 it only includes the patch from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/564559 and so is in all other aspects the same Lucid Kernel. -- [KMS] Desktop freeze + radeon_fence_wait errors https://bugs.launchpad.net/bugs/561554 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 561554] Re: [KMS] Desktop freeze + radeon IB schedule errors
This does only occur when using KMS. Not with UMS. Seems to be a kernel drm issue introduced by another 2.6.33 drm pull. Will see if it's the same with a newer kernel. -- [KMS] Desktop freeze + radeon IB schedule errors https://bugs.launchpad.net/bugs/561554 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 561554] Re: [KMS] Desktop freeze + radeon IB schedule errors
...still occurs with 2.6.32-21. -- [KMS] Desktop freeze + radeon IB schedule errors https://bugs.launchpad.net/bugs/561554 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 545426] Re: SDL support broken when using apparmor
Oh well, I see. Sorry I misunderstood some things here. -- SDL support broken when using apparmor https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545426] Re: SDL support broken when using apparmor
Oh well, I see. Sorry I misunderstood some things here. -- SDL support broken when using apparmor https://bugs.launchpad.net/bugs/545426 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 545426] Re: SDL support broken when using apparmor
Well, to be correct we should read the domain configuration as well as the storage pool definitions to correctly set up apparmor rules (just open them as required and by demand, not by foresight). Additionally what if someone decides to have an iscsi mounted filesystem on /opt or using some NFS storage on /net? Even /var/local or some complete custom paths are possible. So opening read access to all those things just vanishes the benefit of using apparmor. Call me paranoid but I think such a quick hack is not appropriate here, also it is for an LTS release that gets used on servers where security is of top level priority. -- SDL support broken when using apparmor https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545426] Re: SDL support broken when using apparmor
Well, to be correct we should read the domain configuration as well as the storage pool definitions to correctly set up apparmor rules (just open them as required and by demand, not by foresight). Additionally what if someone decides to have an iscsi mounted filesystem on /opt or using some NFS storage on /net? Even /var/local or some complete custom paths are possible. So opening read access to all those things just vanishes the benefit of using apparmor. Call me paranoid but I think such a quick hack is not appropriate here, also it is for an LTS release that gets used on servers where security is of top level priority. -- SDL support broken when using apparmor https://bugs.launchpad.net/bugs/545426 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 545426] Re: SDL support broken when using apparmor
Just tested it with kernel 2.6.32-20-generic (amd64) and libvirt0 0.7.5-5ubuntu21. $ sudo virsh -c qemu:///system define /srv/virtual/aria.xml Domain aria defined from /srv/virtual/aria.xml $ sudo virsh -c qemu:///system start aria error: Failed to start domain aria error: internal error unable to start guest: libvir: Security Labeling error : error calling aa_change_profile() [ 1445.385111] type=1503 audit(1271092691.039:30): operation=open pid=4883 parent=1224 profile=/usr/lib/libvirt/virt-aa-helper requested_mask=r:: denied_mask=r:: fsuid=0 ouid=0 name=/srv/virtual/aria-win2k3.img [ 1445.385453] type=1503 audit(1271092691.039:31): operation=open pid=4883 parent=1224 profile=/usr/lib/libvirt/virt-aa-helper requested_mask=r:: denied_mask=r:: fsuid=0 ouid=0 name=/srv/virtual/win2003-x64.iso [ 1445.407237] device vnet0 entered promiscuous mode [ 1445.408771] virbr0: topology change detected, propagating [ 1445.408780] virbr0: port 1(vnet0) entering forwarding state [ 1445.453859] virbr0: port 1(vnet0) entering disabled state [ 1445.482558] device vnet0 left promiscuous mode [ 1445.482568] virbr0: port 1(vnet0) entering disabled state [ 1445.608828] type=1505 audit(1271092691.259:32): operation=profile_remove info=profile does not exist error=-2 pid=4898 name=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 namespace=root The mentioned profile doesn't get loaded (libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815) although it exists: $ ls -1 /etc/apparmor.d/libvirt/libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815* /etc/apparmor.d/libvirt/libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 /etc/apparmor.d/libvirt/libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815.files ...and has appropriate lines in it: $ grep '/srv/virtual/' /etc/apparmor.d/libvirt/libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815.files /srv/virtual/aria-win2k3.img rw, /srv/virtual/win2003-x64.iso r, deny /srv/virtual/win2003-x64.iso w, So I just added appropriate lines into /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper for my custom storage pool (should I open a bug for that?): $ grep '/srv/virtual' /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper /srv/virtual/ r, /srv/virtual/** r, ...reloaded the apparmor service and now it works. Now I'm waiting for a resolution to Bug #513273 to finally get an SDL VM running out of the virt-manager. Thanx a lot so far! Fix confirmed! :-) -- SDL support broken when using apparmor https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561210] [NEW] Writing big files to NFS target causes system lock up
Public bug reported: I'm experiencing complete system lock ups occasionally when writing big files to an NFS target. I can't remember that I had such issues with Jaunty, but at least Karmic and Lucid are affected in the exact same way. In most cases just the mv or cp process hangs for a while, but sometimes the whole system freezes, including X. Although some things keep running (e.g. the clock on my G15 Keyboard LCD display doesn't freeze, so the g15daemon keeps running as usual), I'm unable to get the system back to a normal state. Even waiting a whole night for the NFS task to finish doesn't succeed. In such a case the NFS server side is completely idle, not receiving any data from the client. I have to hard reset the client machine to get a working system again. The server is a Busybox NAS system with the following exports options: rw,no_wdelay,no_root_squash,insecure_locks,no_subtree_check The clients are mounting with these options: rw,rsize=32768,wsize=32768,hard,intr,noatime All machines are connected through a LevelOne GSW-0803T 8-port GBit switch with Cat6e cables. No wireless here. No other issues with networking here. The client machines are both AMD64 AMD Quad-Cores, both have GigaByte mainboards using the internal GBit Ethernet connector for networking. Some time ago I also used a Dell Inspiron (32-bit Pentium-M system) notebook with a 100MBit connection on this network without such issues. The following gets logged during one of those lock-ups: INFO: task mv:26028 blocked for more than 120 seconds. echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. mvD 0 26028 2040 0x 880100198f08 0086 00015b80 00015b80 880001dc83c0 880100199fd8 00015b80 880001dc8000 00015b80 880100199fd8 00015b80 880001dc83c0 Call Trace: [a0418280] ? nfs_wait_bit_uninterruptible+0x0/0x20 [nfs] [8153e697] io_schedule+0x47/0x70 [a041828e] nfs_wait_bit_uninterruptible+0xe/0x20 [nfs] [8153eeef] __wait_on_bit+0x5f/0x90 [81013cae] ? apic_timer_interrupt+0xe/0x20 [a0418280] ? nfs_wait_bit_uninterruptible+0x0/0x20 [nfs] [8153ef98] out_of_line_wait_on_bit+0x78/0x90 [81085340] ? wake_bit_function+0x0/0x40 [a041826f] nfs_wait_on_request+0x2f/0x40 [nfs] [a041c66f] nfs_wait_on_requests_locked+0x7f/0xd0 [nfs] [a041daae] nfs_sync_mapping_wait+0x9e/0x1a0 [nfs] [a041dc31] nfs_wb_page+0x81/0xe0 [nfs] [a040cb17] nfs_release_page+0x57/0x70 [nfs] [810f2a52] try_to_release_page+0x32/0x50 [811016a3] shrink_page_list+0x453/0x5f0 [81101b4d] shrink_inactive_list+0x30d/0x7e0 [810fbcda] ? determine_dirtyable_memory+0x1a/0x30 [810fbd87] ? get_dirty_limits+0x27/0x2f0 [811020b1] shrink_list+0x91/0xf0 [811022a7] shrink_zone+0x197/0x240 [811023c2] shrink_zones+0x72/0x100 [811024ce] do_try_to_free_pages+0x7e/0x330 [8110287f] try_to_free_pages+0x6f/0x80 [811003c0] ? isolate_pages_global+0x0/0x50 [810f992a] __alloc_pages_slowpath+0x27a/0x580 [810f9d8e] __alloc_pages_nodemask+0x15e/0x1a0 [8112cc07] alloc_pages_current+0x87/0xd0 [81132728] new_slab+0x248/0x310 [81134fb9] __slab_alloc+0x169/0x2d0 [810f5ab5] ? mempool_alloc_slab+0x15/0x20 [811354e4] kmem_cache_alloc+0xe4/0x150 [810f5ab5] mempool_alloc_slab+0x15/0x20 [810f5c53] mempool_alloc+0x63/0x140 [81085300] ? autoremove_wake_function+0x0/0x40 [a041ce70] nfs_writedata_alloc+0x20/0xc0 [nfs] [a041cf32] nfs_flush_one+0x22/0xf0 [nfs] [a0418097] nfs_pageio_doio+0x37/0x80 [nfs] [a0418134] nfs_pageio_add_request+0x54/0x100 [nfs] [a041c47d] nfs_page_async_flush+0x9d/0xf0 [nfs] [a041c557] nfs_do_writepage+0x87/0x90 [nfs] [a041cc9e] nfs_writepages_callback+0x1e/0x40 [nfs] [810fcac7] write_cache_pages+0x227/0x4d0 [a041cc80] ? nfs_writepages_callback+0x0/0x40 [nfs] [a041cc09] nfs_writepages+0xb9/0x130 [nfs] [a041cf10] ? nfs_flush_one+0x0/0xf0 [nfs] [810fcdc1] do_writepages+0x21/0x40 [810f40ab] __filemap_fdatawrite_range+0x5b/0x60 [810f43df] filemap_fdatawrite+0x1f/0x30 [810f4425] filemap_write_and_wait+0x35/0x50 [a041055b] nfs_setattr+0x15b/0x180 [nfs] [810f4c26] ? generic_file_aio_read+0xb6/0x1d0 [81013b0e] ? common_interrupt+0xe/0x13 [810f36de] ? find_get_page+0x1e/0xa0 [810f50c9] ? filemap_fault+0xb9/0x460 [8106c4a7] ? current_fs_time+0x27/0x30 [8115b7db] notify_change+0x16b/0x350 [8116a16c] utimes_common+0xdc/0x1b0 [812b6eba] ? __up_read+0x9a/0xc0 [8116a2e1] do_utimes+0xa1/0xf0 [81543378] ? do_page_fault+0x158/0x3b0 [8116a442]
[Bug 561210] Re: Writing big files to NFS target causes system lock up
** Attachment added: uname -a http://launchpadlibrarian.net/43888905/uname-a.log -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
** Attachment added: dmesg http://launchpadlibrarian.net/43888909/dmesg.log -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
** Attachment added: cat /proc/version_signature http://launchpadlibrarian.net/43888977/version.log -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
** Attachment added: sudo lspci -vnvn http://launchpadlibrarian.net/43888979/lspci-vnvn.log -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
** Attachment added: /var/log/syslog http://launchpadlibrarian.net/43888982/syslog -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561554] [NEW] [KMS] Desktop freeze + radeon IB schedule errors
Public bug reported: Upgrading the kernel from 2.6.32-19-generic to 2.6.32-20-generic resulted in a desktop freeze after just 30 minutes of work. $ uname -a Linux purgatory 2.6.32-20-generic #29-Ubuntu SMP Fri Apr 9 20:35:00 UTC 2010 x86_64 GNU/Linux $ lsmod | egrep '(radeon|fb)' fbcon 39270 72 tileblit2487 1 fbcon font8053 1 fbcon bitblit 5811 1 fbcon vga16fb12757 0 vgastate9857 1 vga16fb radeon739547 2 ttm60815 1 radeon drm_kms_helper 30710 1 radeon drm 198866 4 radeon,ttm,drm_kms_helper i2c_algo_bit6024 1 radeon The card is a ATI Radeon X1550: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV505 CE [Radeon X1550 64-bit] [1002:715f] Subsystem: Micro-Star International Co., Ltd. Device [1462:0680] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 26 Region 0: Memory at e000 (64-bit, prefetchable) [size=256M] Region 2: Memory at fdff (64-bit, non-prefetchable) [size=64K] Region 4: I/O ports at ee00 [size=256] Expansion ROM at fdfc [disabled] [size=128K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 64ns, L1 1us ClockPM- Suprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Address: fee0100c Data: 4189 Kernel driver in use: radeon Kernel modules: radeon ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: drm lucid -- [KMS] Desktop freeze + radeon IB schedule errors https://bugs.launchpad.net/bugs/561554 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 561554] Re: [KMS] Desktop freeze + radeon IB schedule errors
This is the complete session after the kernel upgrade. I was just inside Thunderbird managing some message filters, so it is not a suspend/resume problem, although similar symptoms as in Bug #548377. In addition I never had such problems before kernel 2.6.32-20. ** Attachment added: kern.log http://launchpadlibrarian.net/43927182/kern.log -- [KMS] Desktop freeze + radeon IB schedule errors https://bugs.launchpad.net/bugs/561554 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 545426] Re: SDL support broken when using apparmor
Just tested it with kernel 2.6.32-20-generic (amd64) and libvirt0 0.7.5-5ubuntu21. $ sudo virsh -c qemu:///system define /srv/virtual/aria.xml Domain aria defined from /srv/virtual/aria.xml $ sudo virsh -c qemu:///system start aria error: Failed to start domain aria error: internal error unable to start guest: libvir: Security Labeling error : error calling aa_change_profile() [ 1445.385111] type=1503 audit(1271092691.039:30): operation=open pid=4883 parent=1224 profile=/usr/lib/libvirt/virt-aa-helper requested_mask=r:: denied_mask=r:: fsuid=0 ouid=0 name=/srv/virtual/aria-win2k3.img [ 1445.385453] type=1503 audit(1271092691.039:31): operation=open pid=4883 parent=1224 profile=/usr/lib/libvirt/virt-aa-helper requested_mask=r:: denied_mask=r:: fsuid=0 ouid=0 name=/srv/virtual/win2003-x64.iso [ 1445.407237] device vnet0 entered promiscuous mode [ 1445.408771] virbr0: topology change detected, propagating [ 1445.408780] virbr0: port 1(vnet0) entering forwarding state [ 1445.453859] virbr0: port 1(vnet0) entering disabled state [ 1445.482558] device vnet0 left promiscuous mode [ 1445.482568] virbr0: port 1(vnet0) entering disabled state [ 1445.608828] type=1505 audit(1271092691.259:32): operation=profile_remove info=profile does not exist error=-2 pid=4898 name=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 namespace=root The mentioned profile doesn't get loaded (libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815) although it exists: $ ls -1 /etc/apparmor.d/libvirt/libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815* /etc/apparmor.d/libvirt/libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 /etc/apparmor.d/libvirt/libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815.files ...and has appropriate lines in it: $ grep '/srv/virtual/' /etc/apparmor.d/libvirt/libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815.files /srv/virtual/aria-win2k3.img rw, /srv/virtual/win2003-x64.iso r, deny /srv/virtual/win2003-x64.iso w, So I just added appropriate lines into /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper for my custom storage pool (should I open a bug for that?): $ grep '/srv/virtual' /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper /srv/virtual/ r, /srv/virtual/** r, ...reloaded the apparmor service and now it works. Now I'm waiting for a resolution to Bug #513273 to finally get an SDL VM running out of the virt-manager. Thanx a lot so far! Fix confirmed! :-) -- SDL support broken when using apparmor https://bugs.launchpad.net/bugs/545426 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 546874] Re: passwd - can't login, change password (pam_winbind pam-auth-update profile)
Same here, Lucid Beta 1 (latest kernel, latest updates) on AMD64. As above 'sudo pam-auth-update' plus disabling winbind does the trick. -- passwd - can't login, change password (pam_winbind pam-auth-update profile) https://bugs.launchpad.net/bugs/546874 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 545426] Re: SDL support broken
@Marc: please, let us not think for others. If someone has a reason to do so it should be completely up to him/her. I'm using KDE4 currently, and yes, running anything with sudo inside a terminal does get it displayed on the screen just like expected. Also I can run the KVM command line directly on the terminal with sudo and SDL gets set up correctly. -- SDL support broken https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545426] Re: SDL support broken
@Marc: please, let us not think for others. If someone has a reason to do so it should be completely up to him/her. I'm using KDE4 currently, and yes, running anything with sudo inside a terminal does get it displayed on the screen just like expected. Also I can run the KVM command line directly on the terminal with sudo and SDL gets set up correctly. -- SDL support broken https://bugs.launchpad.net/bugs/545426 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 401514] Re: No console framebuffer support for modern ATI Radeon HD cards.
I need to resurrect this one as it affects me at least with the latest Lucid (Beta 1): $ uname -a Linux workstation 2.6.32-17-generic #26-Ubuntu SMP Sat Mar 20 02:23:45 UTC 2010 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 $ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 The problem what I see here is that the framebuffer devices (/dev/fb[0-9]) get only set up when the system boots with Kernel Mode Setting. I do think so because I have a machine with a Radeon X card running with KMS. There I automatically get the device nodes /dev/fb0 and /dev/fb1. Also the kernel modules get loaded automatically which results in a nice graphical plymouth and high resolution VTs. Another machine I have does have a Radeon HD4770 (RV740) for which KMS support is still broken. To use this card I have to boot with KMS disabled (radeon.modeset=0 kernel option), which results in the rather stone-age text boot splash and with no high resolution VT's. Additionally after boot-up I don't have a /dev/fb* device which results in at least DirectFB to fail: ~~| DirectFB 1.2.8 |~~ (c) 2001-2008 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2010-02-03 18:27) (*) Direct/Memcpy: Using Generic 64bit memcpy() (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed -- No such file or directory (!) DirectFB/FBDev: Error opening framebuffer device! (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable. (!) DirectFB/Core: Could not initialize 'system_core' core! -- Initialization error! After struggling a lot with kernel modules and boot options I finally found by accident that adding the fbdev kernel option allows my system to provide framebuffer devices, graphical boot and high resolution VT's. This is the complete boot line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=aac3cf7c-104c-4af2 -930a-b848744a59c0 ro quiet splash radeon.modeset=0 video=uvesafb:2560x1600-60 fbdev -- No console framebuffer support for modern ATI Radeon HD cards. https://bugs.launchpad.net/bugs/401514 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 401514] Re: No console framebuffer support for modern ATI Radeon HD cards.
The dmesg output from a boot with UMS and fbdev. ** Attachment added: dmesg.log http://launchpadlibrarian.net/42004323/dmesg.log -- No console framebuffer support for modern ATI Radeon HD cards. https://bugs.launchpad.net/bugs/401514 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 401514] Re: No console framebuffer support for modern ATI Radeon HD cards.
Although the KMS situation will improve with every kernel release there will always be cards that are not running well (if at all) with KMS and the users choice to use UMS e.g. for graphics performance (gaming, 3d modeling, etc.). So there should be framebuffers available by default even if the user and/or the video driver code chooses UMS. This would provide high resolution colored VT's and graphical splash to nearly any system and the user just don't have to care about anything. I demonstrated (although with my very special system setup) that it is possible. -- No console framebuffer support for modern ATI Radeon HD cards. https://bugs.launchpad.net/bugs/401514 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 545426] Re: SDL support broken
Regarding the /dev/fb* rule: me too! We wouldn't need that as long as KVM wouldn't choose the DirectFB fallback. It seems that the X-stuff required for KVM doesn't get set up correctly by libvirt. I already thought of just adding the rules if required. But this would mean another patch for .../src/security/virt-aa-helper.c to update the domain specific profile. -- SDL support broken https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545426] Re: SDL support broken
No, I'm not starting without an X session. But it seems to me that libvirt isn't X-session aware at all. -- SDL support broken https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545426] Re: SDL support broken
Regarding the /dev/fb* rule: me too! We wouldn't need that as long as KVM wouldn't choose the DirectFB fallback. It seems that the X-stuff required for KVM doesn't get set up correctly by libvirt. I already thought of just adding the rules if required. But this would mean another patch for .../src/security/virt-aa-helper.c to update the domain specific profile. -- SDL support broken https://bugs.launchpad.net/bugs/545426 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 545426] Re: SDL support broken
No, I'm not starting without an X session. But it seems to me that libvirt isn't X-session aware at all. -- SDL support broken https://bugs.launchpad.net/bugs/545426 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 545426] [NEW] SDL support broken
Public bug reported: Although SDL works perfectly with QEMU/KVM itself the appropriate support using libvirt is completely broken. System info: $ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 $ uname -a Linux workstation 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux $ apt-cache policy libvirt0 libvirt0: Installed: 0.7.5-5ubuntu13 Candidate: 0.7.5-5ubuntu13 Version table: *** 0.7.5-5ubuntu13 0 500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Example domain XML excerpt: $ virsh -c qemu:///system dumpxml aria | grep graphics graphics type='sdl' display=':0.0' xauth='/home/myself/.Xauthority'/ ...virsh invocation: $ sudo virsh -c qemu:///system start aria error: Failed to start domain aria error: monitor socket did not show up.: Connection refused Contents of /var/log/libvirt/qemu/aria.log: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin XAUTHORITY=/home/myself/.Xauthority DISPLAY=:0.0 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 2048 -smp 4 -name aria -uuid a4294a0d-a75a-a377-ddcd-7e35d5720815 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/aria.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/srv/virtual/aria-win2k3.img,if=ide,index=0,boot=on,format=raw -drive file=/srv/virtual/win2003-x64.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=52:54:00:76:e9:1d,vlan=0,name=nic.0 -net tap,fd=49,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -usbdevice tablet -vga std char device redirected to /dev/pts/7 pci_add_option_rom: failed to find romfile pxe-rtl8139.bin No protocol specified No protocol specified ~~| DirectFB 1.2.8 |~~ (c) 2001-2008 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2010-02-03 18:27) (*) Direct/Memcpy: Using libc memcpy() (!) Direct/Util: opening '/dev/fb0' failed -- Permission denied (!) DirectFB/FBDev: Error opening framebuffer device! (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable. (!) DirectFB/Core: Could not initialize 'system_core' core! -- Initialization error! Could not initialize SDL - exiting Taking that logged command-line and executing it in a terminal works perfectly (at least the X window shows up and without parameter -S the VM boots fine). ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- SDL support broken https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545426] Re: SDL support broken
$ dmesg | grep audit [ 6046.037322] type=1505 audit(1269377190.495:54): operation=profile_load pid=17852 name=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 [ 6046.144800] type=1503 audit(1269377190.606:55): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=::r denied_mask=::r fsuid=0 ouid=1000 name=/home/myself/.Xauthority [ 6046.145062] type=1503 audit(1269377190.606:56): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=::r denied_mask=::r fsuid=0 ouid=1000 name=/home/myself/.Xauthority [ 6046.145147] type=1503 audit(1269377190.606:57): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=rw:: denied_mask=rw:: fsuid=0 ouid=0 name=/dev/fb0 [ 6046.145190] type=1503 audit(1269377190.606:58): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=r:: denied_mask=r:: fsuid=0 ouid=0 name=/proc/17858/cmdline [ 6046.147198] type=1503 audit(1269377190.606:59): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=rw:: denied_mask=rw:: fsuid=0 ouid=0 name=/dev/fb0 [ 6076.374039] type=1505 audit(1269377220.835:60): operation=profile_remove pid=18209 name=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 namespace=root So the first step would be to add the xauth=XXX path to the domains profile definition. And additionally /dev/fb* for DirectFB fallback, if no X environment is available. -- SDL support broken https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545426] Re: SDL support broken
There's also a bug upstream that looks related (although with SELinux): https://bugzilla.redhat.com/show_bug.cgi?id=536693 ** Bug watch added: Red Hat Bugzilla #536693 https://bugzilla.redhat.com/show_bug.cgi?id=536693 -- SDL support broken https://bugs.launchpad.net/bugs/545426 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 544846] [NEW] RTL8111/8168 Ethernet link-down
Public bug reported: System info: $ uname -a Linux workstation 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 2.6.32-16.25-generic $ lspci | grep RTL 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) $ dmesg | grep RTL [2.837919] eth0: RTL8168d/8111d at 0xc9664000, XX:XX:XX:XX:XX:XX, XID 083000c0 IRQ 31 Very often the Ethernet Controller doesn't get initialized properly and goes down without reason with a running system. When the hardware comes up, I can see at my 8-Port GBit-Switch that the link is there (defaulting to 100MBit/s). But when the r8169 module gets loaded the link goes down completely and no network connection can be established. Unloading/loading the module manually doesn't solve the problem. Sometimes the system runs fine for some weeks including several reboots (warm and/or cold), but as soon as I can see the following messages in /var/log/messages I know that successfully getting network access again will be a struggle including several cold boots: $ egrep '(r8169|eth0)' /var/log/messages Mar 21 16:40:30 workstation kernel: [2.821763] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Mar 21 16:40:30 workstation kernel: [2.821781] r8169 :05:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 Mar 21 16:40:30 workstation kernel: [2.823172] eth0: RTL8168d/8111d at 0xc967c000, XX:XX:XX:XX:XX:XX, XID 083000c0 IRQ 31 Mar 21 16:40:30 workstation kernel: [ 16.662250] r8169: eth0: link up Mar 21 16:40:30 workstation kernel: [ 16.662254] r8169: eth0: link up Mar 22 01:27:13 workstation kernel: [31620.982879] r8169: eth0: link down Mar 22 01:28:01 workstation kernel: [31668.502155] r8169: eth0: link up Mar 22 01:28:02 workstation kernel: [31670.043507] r8169: eth0: link down Mar 22 01:28:29 workstation kernel: [31696.578837] r8169: eth0: link up Mar 22 01:29:27 workstation kernel: [31760.247082] r8169: eth0: link down Mar 22 01:29:34 workstation kernel: [31767.080210] r8169: eth0: link up Mar 22 01:30:14 workstation kernel: [31807.031054] r8169: eth0: link down Mar 22 01:30:17 workstation kernel: [31809.923406] r8169: eth0: link up Mar 22 01:30:21 workstation kernel: [31813.871178] r8169: eth0: link down Mar 22 01:33:13 workstation kernel: [31986.073775] r8169: eth0: link up Mar 22 01:33:40 workstation kernel: [32013.098730] r8169: eth0: link down Mar 22 01:33:43 workstation kernel: [32015.851555] r8169: eth0: link up Mar 22 01:34:22 workstation kernel: [32055.633543] r8169: eth0: link down Mar 22 01:37:39 workstation kernel: [32251.975170] r8169: eth0: link up Mar 22 01:38:24 workstation kernel: [32297.136849] r8169: eth0: link down Mar 22 01:38:27 workstation kernel: [32300.127630] r8169: eth0: link up Mar 22 01:38:30 workstation kernel: [32303.258175] r8169: eth0: link down Mar 22 01:38:33 workstation kernel: [32306.498423] r8169: eth0: link up Mar 22 01:38:39 workstation kernel: [32312.450663] r8169: eth0: link down Mar 22 01:43:14 workstation kernel: [32587.106862] r8169: eth0: link up Mar 22 01:43:19 workstation kernel: [32592.098047] r8169: eth0: link down Mar 22 01:43:22 workstation kernel: [32595.006513] r8169: eth0: link up Mar 22 01:43:28 workstation kernel: [32600.975273] r8169: eth0: link down Mar 22 01:43:34 workstation kernel: [32607.358942] r8169: eth0: link up Mar 22 01:43:47 workstation kernel: [32619.706388] r8169: eth0: link down Mar 22 01:46:50 workstation kernel: [32802.727276] r8169: eth0: link up Mar 22 01:46:51 workstation kernel: [32804.616517] r8169: eth0: link down Mar 22 01:46:54 workstation kernel: [32807.505907] r8169: eth0: link up Mar 22 01:46:55 workstation kernel: [32808.166330] r8169: eth0: link down Mar 22 01:46:58 workstation kernel: [32810.948519] r8169: eth0: link up Mar 22 01:46:59 workstation kernel: [32812.256254] r8169: eth0: link down Mar 22 01:47:39 workstation kernel: [32852.579433] r8169: eth0: link up Mar 22 01:47:40 workstation kernel: [32853.399194] r8169: eth0: link down Mar 22 01:47:43 workstation kernel: [32856.219448] r8169: eth0: link up Mar 22 01:47:44 workstation kernel: [32856.838918] r8169: eth0: link down Mar 22 01:48:29 workstation kernel: [32902.478151] r8169: eth0: link up Mar 22 01:48:52 workstation kernel: [32925.419981] r8169: eth0: link down Mar 22 01:51:06 workstation kernel: [33058.690231] r8169: eth0: link up Mar 22 01:51:06 workstation kernel: [33059.556407] r8169: eth0: link down Mar 22 01:51:09 workstation kernel: [33061.694128] r8169: eth0: link up Mar 22 01:51:10 workstation kernel: [33063.250432] r8169: eth0: link down Mar 22 01:51:13 workstation kernel: [33066.208246] r8169: eth0: link up Mar 22 01:51:14 workstation kernel: [33067.214503] r8169: eth0: link down Mar 22 01:54:28 workstation kernel: [33260.880329] r8169: eth0: link up Mar 22 01:54:30 workstation kernel: [33262.945607] r8169: eth0: link down Mar 22 01:54:54 workstation
[Bug 544846] Re: RTL8111/8168 Ethernet link-down
** Attachment added: lspci -vnvn http://launchpadlibrarian.net/41691924/lspci-vnvn.txt -- RTL8111/8168 Ethernet link-down https://bugs.launchpad.net/bugs/544846 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 544846] Re: RTL8111/8168 Ethernet link-down
/var/log/messages full excerpt including ethernet ups/downs during runtime without reason. ** Attachment added: /var/log/messages http://launchpadlibrarian.net/41691811/messages -- RTL8111/8168 Ethernet link-down https://bugs.launchpad.net/bugs/544846 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 544846] Re: RTL8111/8168 Ethernet link-down
Another machine on the same network connected to the same switch doesn't have such problems (running Karmic instead of Lucid). The problem may be that the other machine has an RTL8168c/8111c while the machine with problems has RTL8168d/8111d: mys...@fine:~$ dmesg | grep RTL [2.368804] eth0: RTL8168c/8111c at 0xc966a000, 00:24:1d:d1:85:c5, XID 3c4000c0 IRQ 27 mys...@workstation:~$ dmesg | grep RTL [2.837919] eth0: RTL8168d/8111d at 0xc9664000, 6c:f0:49:53:43:74, XID 083000c0 IRQ 31 So it seems the driver just includes fixes up to revision 02 of the device but doesn't apply them for revision 03: mys...@fine:~$ lspci | grep RTL 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) mys...@workstation:~$ lspci | grep RTL 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) -- RTL8111/8168 Ethernet link-down https://bugs.launchpad.net/bugs/544846 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 545426] [NEW] SDL support broken
Public bug reported: Although SDL works perfectly with QEMU/KVM itself the appropriate support using libvirt is completely broken. System info: $ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 $ uname -a Linux workstation 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux $ apt-cache policy libvirt0 libvirt0: Installed: 0.7.5-5ubuntu13 Candidate: 0.7.5-5ubuntu13 Version table: *** 0.7.5-5ubuntu13 0 500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Example domain XML excerpt: $ virsh -c qemu:///system dumpxml aria | grep graphics graphics type='sdl' display=':0.0' xauth='/home/myself/.Xauthority'/ ...virsh invocation: $ sudo virsh -c qemu:///system start aria error: Failed to start domain aria error: monitor socket did not show up.: Connection refused Contents of /var/log/libvirt/qemu/aria.log: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin XAUTHORITY=/home/myself/.Xauthority DISPLAY=:0.0 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 2048 -smp 4 -name aria -uuid a4294a0d-a75a-a377-ddcd-7e35d5720815 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/aria.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/srv/virtual/aria-win2k3.img,if=ide,index=0,boot=on,format=raw -drive file=/srv/virtual/win2003-x64.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=52:54:00:76:e9:1d,vlan=0,name=nic.0 -net tap,fd=49,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -usbdevice tablet -vga std char device redirected to /dev/pts/7 pci_add_option_rom: failed to find romfile pxe-rtl8139.bin No protocol specified No protocol specified ~~| DirectFB 1.2.8 |~~ (c) 2001-2008 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2010-02-03 18:27) (*) Direct/Memcpy: Using libc memcpy() (!) Direct/Util: opening '/dev/fb0' failed -- Permission denied (!) DirectFB/FBDev: Error opening framebuffer device! (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable. (!) DirectFB/Core: Could not initialize 'system_core' core! -- Initialization error! Could not initialize SDL - exiting Taking that logged command-line and executing it in a terminal works perfectly (at least the X window shows up and without parameter -S the VM boots fine). ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- SDL support broken https://bugs.launchpad.net/bugs/545426 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 545426] Re: SDL support broken
$ dmesg | grep audit [ 6046.037322] type=1505 audit(1269377190.495:54): operation=profile_load pid=17852 name=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 [ 6046.144800] type=1503 audit(1269377190.606:55): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=::r denied_mask=::r fsuid=0 ouid=1000 name=/home/myself/.Xauthority [ 6046.145062] type=1503 audit(1269377190.606:56): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=::r denied_mask=::r fsuid=0 ouid=1000 name=/home/myself/.Xauthority [ 6046.145147] type=1503 audit(1269377190.606:57): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=rw:: denied_mask=rw:: fsuid=0 ouid=0 name=/dev/fb0 [ 6046.145190] type=1503 audit(1269377190.606:58): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=r:: denied_mask=r:: fsuid=0 ouid=0 name=/proc/17858/cmdline [ 6046.147198] type=1503 audit(1269377190.606:59): operation=open pid=17858 parent=1 profile=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 requested_mask=rw:: denied_mask=rw:: fsuid=0 ouid=0 name=/dev/fb0 [ 6076.374039] type=1505 audit(1269377220.835:60): operation=profile_remove pid=18209 name=libvirt-a4294a0d-a75a-a377-ddcd-7e35d5720815 namespace=root So the first step would be to add the xauth=XXX path to the domains profile definition. And additionally /dev/fb* for DirectFB fallback, if no X environment is available. -- SDL support broken https://bugs.launchpad.net/bugs/545426 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 226273] Re: Local SDL window does not work
This bug depends on https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/545426 -- Local SDL window does not work https://bugs.launchpad.net/bugs/226273 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 545426] Re: SDL support broken
There's also a bug upstream that looks related (although with SELinux): https://bugzilla.redhat.com/show_bug.cgi?id=536693 ** Bug watch added: Red Hat Bugzilla #536693 https://bugzilla.redhat.com/show_bug.cgi?id=536693 -- SDL support broken https://bugs.launchpad.net/bugs/545426 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 226273] Re: Local SDL window does not work
As a test (should have done this in the first place) I started the VM manually via the stated command line from the log file in /var/log/libvirt/qemu/. KVM/QEMU uses SDL by default and it opens just fine and I can use the VM as usual. So this has nothing to do with KVM/QEMU itself. As starting the VM using virt-manager or the virsh command fails it must have something to do with those. Instead it seems that libvirt does not use and/or forward the DISPLAY environment variable (or the specified one in the appropriate graphics/ tag) when SDL is specified for a VM. This is documented here: http://libvirt.org/formatdomain.html#elementsGraphics So if it doesn't work it's a bug in libvirt. -- Local SDL window does not work https://bugs.launchpad.net/bugs/226273 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 226273] Re: Local SDL window does not work
OK, here are my machine specs (maybe this is some conditional thing): - AMD Phenom II X4 955 (@ 3.2 GHz) - 2x 2 GiB DDR3 RAM (@ 1.333 GHz) - Gigabyte GA-790XTA-UD4 (RD790/SB750) - AMD Radeon HD4770 - 500 GB Hitachi Deskstar T7K500 $ uname -m x86_64 Non-standard repositories: - xorg-edgers I'll try with other kernels. -- Local SDL window does not work https://bugs.launchpad.net/bugs/226273 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 532174] Re: [Lucid] sun-java6-plugin not recognized by firefox anymore
confirmed. Issue the following on AMD64 platforms: sudo update-alternatives --install /usr/lib/mozilla/plugins/mozilla- javaplugin.so mozilla-javaplugin.so /usr/lib/jvm/java-6-sun/jre/lib/amd64/libnpjp2.so 1 -- [Lucid] sun-java6-plugin not recognized by firefox anymore https://bugs.launchpad.net/bugs/532174 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 226273] Re: Local SDL window does not work
OK, no success with other kernels (tried 2.6.33 and 2.6.34-rc1). @Marc: How did you setup the framebuffer device on your machines? I don't know if it is relevant but I have to state that I'm not using KMS (because the HD4770 still isn't supported) and so I have to revert to UMS via radeon.modeset=0 command line. And so I only get the plymouth text splash thing. That is somewhat strange as even grub2 is configured for another resolution (1920x1440). Running vbeinfo inside grub also yields a ton of available resolutions so the VESA stuff should be working correctly. Although I must admit that non of the resolutions listed by that complies to the official resolutions of my monitor delivered via EDID (which are 1280x800 and 2560x1600). Running hwinfo --framebuffer shows up this: 02: None 00.0: 11001 VESA Framebuffer [Created at bios.464] Unique ID: rdCR.zobvqQpNPrC Hardware Class: framebuffer Model: (C) 1988-2005, ATI Technologies Inc. RV740 Vendor: (C) 1988-2005, ATI Technologies Inc. Device: RV740 SubVendor: ATI ATOMBIOS SubDevice: Revision: 01.00 Memory Size: 16 MB Memory Range: 0xd000-0xd0ff (rw) Mode 0x0300: 640x400 (+640), 8 bits Mode 0x0301: 640x480 (+640), 8 bits ... I don't have comprehensive knowledge about the Linux internals here but that output seems to me like there should be framebuffer support available. -- Local SDL window does not work https://bugs.launchpad.net/bugs/226273 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 226273] Re: Local SDL window does not work
I'm making progress. At least I got a /dev/fb0 now: $ ls -l /dev/fb* crw-rw 1 root video 29, 0 2010-03-21 14:08 /dev/fb0 What I did was adding fbdev at the end of my boot line. In addition I got high resolution VTs. Still not the monitors native resolution but a massive improvement. This fbdev seems to be valid only for EFI, but at least for me that works, although I've got a standard Award BIOS. In addition I got the graphical boot splash from plymouth without KMS. The backside is, that still I am unable to start a VM using SDL: (*) DirectFB/Core: Single Application Core. (2010-02-03 18:27) (*) Direct/Memcpy: Using Generic 64bit memcpy() (!) Direct/Util: opening '/dev/fb0' failed -- Permission denied (!) DirectFB/FBDev: Error opening framebuffer device! (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable. (!) DirectFB/Core: Could not initialize 'system_core' core! -- Initialization error! Could not initialize SDL - exiting It doesn't make a difference if I try to start it with my user account or with sudo, permission denied in both cases. -- Local SDL window does not work https://bugs.launchpad.net/bugs/226273 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 226273] Re: Local SDL window does not work
Ah... ...now I get the point of SDL. OK, then the DirectFB issue is a complete different story and should be reported separately. -- Local SDL window does not work https://bugs.launchpad.net/bugs/226273 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 226273] Re: Local SDL window does not work
I can confirm this one in Lucid Beta 1 with the following messages: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 2048 -smp 4 -name aria -uuid a4294a0d-a75a-a377-ddcd-7e35d5720815 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/aria.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/srv/virtual/aria-win2k3.img,if=ide,index=0,boot=on,format=raw -drive file=/srv/virtual/win2003-x64.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=52:54:00:76:e9:1d,vlan=0,name=nic.0 -net tap,fd=54,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -usbdevice tablet -vga std char device redirected to /dev/pts/7 ~~| DirectFB 1.2.8 |~~ (c) 2001-2008 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2010-02-03 18:27) (*) Direct/Memcpy: Using Generic 64bit memcpy() (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed -- No such file or directory (!) DirectFB/FBDev: Error opening framebuffer device! (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable. (!) DirectFB/Core: Could not initialize 'system_core' core! -- Initialization error! Could not initialize SDL - exiting Output from 'dpkg -l | grep sdl': ii libsdl-image1.2 1.2.10-1 image loading library for Simple DirectMedia ii libsdl-mixer1.2 1.2.8-6build1 mixer library for Simple DirectMedia Layer 1 ii libsdl-net1.2 1.2.7-2 network library for Simple DirectMedia Layer ii libsdl1.2debian 1.2.14-4ubuntu1 Simple DirectMedia Layer ii libsdl1.2debian-alsa 1.2.14-4ubuntu1 Simple DirectMedia Layer (with X11 and ALSA -- Local SDL window does not work https://bugs.launchpad.net/bugs/226273 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 226273] Re: Local SDL window does not work
yepp: $ echo $DISPLAY :0 -- Local SDL window does not work https://bugs.launchpad.net/bugs/226273 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
