[Bug 180579] trackerd hangs in endless loop while indexing
Public bug reported: Binary package hint: tracker trackerd seems to endlessly index the same directory (although it is not a symbolic link loop). Some outputs: ---snip--- [EMAIL PROTECTED]:~$ trackerd -v Tracker version 0.6.3 Copyright (c) 2005-2007 by Jamie McCracken ([EMAIL PROTECTED]) [EMAIL PROTECTED]:~$ tracker-stats ---fetching index stats- default : 0 Files : 363704 Folders : 352989 Documents : 1504 Images : 1316 Music : 11 Videos : 9 Text : 1816 Development : 3647 Other : 2412 Emails : 5 EvolutionEmails : 5 ThunderbirdEmails : 0 KMailEmails : 0 EmailAttachments : 1 EvolutionAttachments : 1 KMailAttachments : 0 Conversations : 0 GaimConversations : 0 Applications : 361 [Note the interestingly high number of folders] [I switched trackerd to debug output for the following] [EMAIL PROTECTED]:~$ tail -15 .xsession-errors service id for Folders is 3 and sid is 351589 with mime Folder 0 files are pending with count 0 checking /home/baumi2/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de/hafas for 1 files file /home/baumi2/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de/hafas has fulltext 0 with service Folders Indexing /home/baumi2/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de/hafas with service Folders and mime Folder (new) service id for Folders is 3 and sid is 351590 with mime Folder 0 files are pending with count 0 checking /home/baumi2/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de/hafas for 1 files file /home/baumi2/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de/hafas has fulltext 0 with service Folders Indexing /home/baumi2/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de/hafas with service Folders and mime Folder (new) service id for Folders is 3 and sid is 351591 with mime Folder 0 files are pending with count 0 checking /home/baumi2/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de/hafas for 1 files ...Too much output, ignoring rest... [EMAIL PROTECTED]:~/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin$ ls -la total 184 drwxr-xr-x 4 baumi2 users 288 2004-10-24 19:44 . drwxr-xr-x 3 baumi2 users72 2004-10-24 19:43 .. drwxr-xr-x 3 baumi2 users72 2004-10-24 19:43 de -rw-r--r-- 1 baumi2 users 59669 2003-12-22 23:37 hafas.jar -rw-rw-rw- 1 baumi2 users 59827 2003-12-10 12:32 HafasPSION.SIS -rw-rw-rw- 1 baumi2 users 14531 2003-02-07 14:24 leggere.txt -rw-rw-rw- 1 baumi2 users 14290 2003-02-03 16:53 liesmich.txt -rw-rw-rw- 1 baumi2 users 14720 2003-02-07 14:00 lisezmoi.txt drwxr-xr-x 2 baumi2 users80 2004-10-24 19:43 META-INF -rw-rw-rw- 1 baumi2 users 14357 2003-02-07 13:20 readme.txt [EMAIL PROTECTED]:~/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de$ ls -la total 0 drwxr-xr-x 3 baumi2 users 72 2004-10-24 19:43 . drwxr-xr-x 4 baumi2 users 288 2004-10-24 19:44 .. drwxr-xr-x 3 baumi2 users 72 2004-10-24 19:43 hafas [EMAIL PROTECTED]:~/zaurus-down/hafas/javaviewer/DemoVersion 0.9c/bin/de/hafas$ ls -la total 1 drwxr-xr-x 3 baumi2 users 72 2004-10-24 19:43 . drwxr-xr-x 3 baumi2 users 72 2004-10-24 19:43 .. drwxr-xr-x 4 baumi2 users 504 2004-10-24 19:44 viewer - snip And "viewer" then contains some java class files and some resources. My guess would be that trackerd either gets confused by the hafas.jar file next to the unpacked version of it or by the MANIFEST.MF file in the META-INF directory (which seems to contains not completely correct path names to the class files). I can e-mail a tar of the directory in question to anyone interested but since it is a very old beta version of a tool from the german railways long gone from its website (which simply continued to lie around in my home directory) I don't want to post it on a public web site. ** Affects: tracker (Ubuntu) Importance: Undecided Status: New -- trackerd hangs in endless loop while indexing https://bugs.launchpad.net/bugs/180579 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392570] Re: kvm hanging on startup
I seem to have the same problem with Unutu 9.10, except that sudo modprobe kvm_amd npt=0 doesn't help (following dump is after # rmmod kvm_amd # rmmod kvm # modprobe kvm_amd npt=0 # modinfo kvm_amd filename: /lib/modules/2.6.31-16-generic/kernel/arch/x86/kvm/kvm-amd.ko license:GPL author: Qumranet srcversion: 9681CBC361395569DF6AB8A depends:kvm vermagic: 2.6.31-16-generic SMP mod_unload modversions parm: npt:int parm: nested:int # uname -a Linux gart 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux $ kvm -no-acpi -m 1280 -localtime -smb / /kvmwin/windows.img [ Note: Changing around the options to kvm doesn't really help although sometime one manages to get into beginning of windows boot before crash] $ dmesg [only the end of it of course] [ 329.358143] kvm: Nested Paging disabled [ 360.783334] [ cut here ] [ 360.783348] kernel BUG at /build/buildd/linux-2.6.31/arch/x86/kvm/../../../virt/kvm/kvm_main.c:2412! [ 360.783356] invalid opcode: [#1] SMP [ 360.783364] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq [ 360.783370] CPU 0 [ 360.783374] Modules linked in: kvm_amd kvm nls_iso8859_1 nls_cp437 vfat fat binfmt_misc ppdev nfs lockd nfs_acl auth_rpcgss sunrpc autofs4 snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm_oss snd_hwdep snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event iptable_filter snd_seq ip_tables snd_timer snd_seq_device lp snd i2c_piix4 amd64_edac_mod parport x_tables soundcore edac_core fglrx(P) snd_page_alloc reiserfs dm_raid45 xor usbhid sky2 [last unloaded: kvm] [ 360.783453] Pid: 5159, comm: kvm Tainted: P 2.6.31-16-generic #53-Ubuntu . [ 360.783460] RIP: 0010:[] [] kvm_handle_fault_on_reboot+0xd/0x20 [kvm] [ 360.783499] RSP: 0018:88011950fcb8 EFLAGS: 00010046 [ 360.783505] RAX: 8801154fe000 RBX: 88011049 RCX: 28022000 [ 360.783510] RDX: RSI: 88011950fce4 RDI: 28022000 [ 360.783516] RBP: 88011950fcb8 R08: R09: 000e [ 360.783521] R10: 0001 R11: R12: 88011b54c000 [ 360.783526] R13: 0007 R14: 88011b54c000 R15: 01a6ad60 [ 360.783533] FS: 7ff9ef0de910() GS:880028022000() knlGS:f69a9750 [ 360.783538] CS: 0010 DS: ES: CR0: 80050033 [ 360.783543] CR2: 0054d9d0 CR3: 0001195cd000 CR4: 06f0 [ 360.783549] DR0: DR1: DR2: [ 360.783554] DR3: DR6: 0ff0 DR7: 0400 [ 360.783561] Process kvm (pid: 5159, threadinfo 88011950e000, task 880119494410) [ 360.783565] Stack: [ 360.783568] 88011950fd18 a0531984 0082 88011049 [ 360.783577] <0> 88011950fd08 812788aa 88011049 88011049 [ 360.783585] <0> 88011b54c000 0007 88011b54c000 01a6ad60 [ 360.783595] Call Trace: [ 360.783611] [] svm_vcpu_run+0x154/0x440 [kvm_amd] [ 360.783639] [] vcpu_enter_guest+0x22a/0x5c0 [kvm] [ 360.783651] [] ? svm_vcpu_load+0x3e/0xb0 [kvm_amd] [ 360.783674] [] __vcpu_run+0x63/0x320 [kvm] [ 360.783698] [] kvm_arch_vcpu_ioctl_run+0x82/0x1c0 [kvm] [ 360.783721] [] kvm_vcpu_ioctl+0x473/0x5c0 [kvm] [ 360.783733] [] ? __sigqueue_free+0x38/0x40 [ 360.783743] [] ? __dequeue_signal+0xd9/0x1f0 [ 360.783751] [] ? dequeue_signal+0x3c/0x170 [ 360.783759] [] vfs_ioctl+0x1d/0xa0 [ 360.783766] [] do_vfs_ioctl+0x79/0x370 [ 360.783772] [] sys_ioctl+0x81/0xa0 [ 360.783782] [] system_call_fastpath+0x16/0x1b [ 360.783786] Code: c7 86 80 00 00 00 20 ba 52 a0 31 c0 48 89 e5 c9 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 80 3d 29 e7 02 00 00 55 48 89 e5 75 04 <0f> 0b eb fe eb fe 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 [ 360.783850] RIP [] kvm_handle_fault_on_reboot+0xd/0x20 [kvm] [ 360.783873] RSP [ 360.783879] ---[ end trace 641b3d53165eb621 ]--- Core is a AM3 (AMD AthlonII 64X2 245) in an AM2+ board in case that is relevant (but hardware seems otherwise to be stable). BTW, in case there are questions, I will be away from tomorrow till end of year. -- kvm hanging on startup https://bugs.launchpad.net/bugs/392570 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 810454] Re: At boot, users's home directory not availlable when use of a NAS.
I have the same problem. kern.log attached but it doesn't show anything because a) It seem the --verbose output does not go into kern.log (I saw much more during boot on the screen, mainly stemming from init) b) Even on screen nothing appeared between 33 and 77 seconds. As I am not a kernel hacker, any advise on how to get it more verbose? And into the log file. Thierry, you add it by pressing 'e' on the boot screen and then editing it in before booting. Advantage: You don't have to understand grub2 scripts which are for from obvious (grub and lilo were significantly easier to manipulate to one's wishes). ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/810454/+attachment/2279378/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810454 Title: At boot, users's home directory not availlable when use of a NAS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/810454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810454] Re: At boot, users's home directory not availlable when use of a NAS.
Well, it does get logged in the syslog. See attached (although I still don't see anything useful but then I stopped understanding startup with the departure of sysV init files). BTW, why is anacron started and stopped thrice during boot. I always wonder about that when seeing the messages scrolling up the screen. That does not look very efficient. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/810454/+attachment/2279389/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810454 Title: At boot, users's home directory not availlable when use of a NAS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/810454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
