View previous topic :: View next topic |
Author |
Message |
r2dtu Tux's lil' helper
Joined: 23 Aug 2002 Posts: 87
|
Posted: Sat Dec 05, 2009 1:23 pm Post subject: |
|
|
FYI reiser4 with cryptocompress is broken on 2.6.32-zen1. I don't blame zen though. I think it is generally broken on 2.6.32.
The errors happen when writing to reiser4 compressed partition. Once files are written to under 2.6.32 they become broken. The reiser4 volume can't be written to (or unmounted) once you try to read a file that has been broken. It is quite annoying since fsck.reiser4 can't fix it (segfaults). The only solution I've found is to delete the broken files. |
|
Back to top |
|
|
NotQuiteSane Guru
Joined: 30 Jan 2005 Posts: 488 Location: Klamath Falls, Jefferson, USA, North America, Midgarth
|
Posted: Sat Dec 05, 2009 1:33 pm Post subject: |
|
|
i'm getting this error:
Code: | pixel linux # make menuconfig
HOSTCC scripts/kconfig/mconf.o
scripts/kconfig/mconf.c:318: error: static declaration of 'get_symbol_str' follows non-static declaration
scripts/kconfig/lkc_proto.h:20: error: previous declaration of 'get_symbol_str' was here
make[1]: *** [scripts/kconfig/mconf.o] Error 1
make: *** [menuconfig] Error 2
pixel linux # |
Any suggestions for correcting it? _________________ These opinions are mine, mine I say! Piss off and get your own.
As I see it -- An irregular blog, Improved with new location
To delete French language packs from system use 'sudo rm -fr /' |
|
Back to top |
|
|
cheater1034 Veteran
Joined: 09 Sep 2004 Posts: 1558
|
Posted: Sat Dec 05, 2009 2:30 pm Post subject: |
|
|
Settle down guys, I just made the base yesterday - I said i'm ironing out problems still It's not like i released it yet.
For the reiser4 problem, definitely give me more details and i'll report it to reiser4-ml or even better if you posted it on there yourself (i took reiser4 exactly from dec. 4 mmotm) _________________ IRC!: #zen-sources on irc.rizon.net
zen-kernel.org
--
Lost in android development land. |
|
Back to top |
|
|
r2dtu Tux's lil' helper
Joined: 23 Aug 2002 Posts: 87
|
Posted: Sat Dec 05, 2009 2:52 pm Post subject: |
|
|
cheater1034 wrote: | For the reiser4 problem, definitely give me more details and i'll report it to reiser4-ml or even better if you posted it on there yourself (i took reiser4 exactly from dec. 4 mmotm) |
This is a trace of 2.6.31-zen9 reading a file that was broken by 2.6.32
Code: | Dec 5 12:49:41 r2d2 kernel: ------------[ cut here ]------------
Dec 5 12:49:41 r2d2 kernel: kernel BUG at fs/reiser4/plugin/item/ctail.c:672!
Dec 5 12:49:41 r2d2 kernel: invalid opcode: 0000 [#1] SMP
Dec 5 12:49:41 r2d2 kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/controlC0/uevent
Dec 5 12:49:41 r2d2 kernel: CPU 0
Dec 5 12:49:41 r2d2 kernel: Modules linked in: snd_seq snd_seq_device acpi_cpufreq btusb bluetooth usb_storage arc4 ecb snd_hda_codec_conexant cryptomgr aead pcompress cryp
to_blkcipher crypto_hash crypto_algapi snd_hda_intel snd_hda_codec snd_hwdep iwl3945 iwlcore snd_pcm mac80211 snd_timer led_class snd soundcore snd_page_alloc cfg80211 sr_mo
d psmouse cdrom sg r8169 pcspkr evdev ehci_hcd uhci_hcd
Dec 5 12:49:41 r2d2 kernel: Pid: 5040, comm: kdm Not tainted 2.6.31-zen9-08452-gdc768a1 #5 ESPRIMO Mobile V5505
Dec 5 12:49:41 r2d2 kernel: RIP: 0010:[<ffffffff81138240>] [<ffffffff81138240>] do_readpage_ctail+0x2a0/0x3d0
Dec 5 12:49:41 r2d2 kernel: RSP: 0018:ffff8800b7c5da28 EFLAGS: 00010246
Dec 5 12:49:41 r2d2 kernel: RAX: 0000000000000283 RBX: ffffea00027db6e0 RCX: 0000000000000000
Dec 5 12:49:41 r2d2 kernel: RDX: 4000000000000000 RSI: 0000000000000000 RDI: ffff8800bbe75000
Dec 5 12:49:41 r2d2 kernel: RBP: ffff8800b7c5daf8 R08: 0000000000000000 R09: 00000000000288aa
Dec 5 12:49:41 r2d2 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff8800b9ef57c0
Dec 5 12:49:41 r2d2 kernel: R13: 0000000000000283 R14: 0000000000000002 R15: 0000000000000000
Dec 5 12:49:41 r2d2 kernel: FS: 00007fb638bba700(0000) GS:ffff880001555000(0000) knlGS:0000000000000000
Dec 5 12:49:41 r2d2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Dec 5 12:49:41 r2d2 kernel: CR2: 00007fb638bbe7dd CR3: 00000000b7d02000 CR4: 00000000000006f0
Dec 5 12:49:41 r2d2 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 5 12:49:41 r2d2 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 5 12:49:41 r2d2 kernel: Process kdm (pid: 5040, threadinfo ffff8800b7c5c000, task ffff8800bf2b3410)
Dec 5 12:49:41 r2d2 kernel: Stack:
Dec 5 12:49:41 r2d2 kernel: ffff8800b7c5daf8 ffffea00027db6e0 ffff8800b7c5daf8 0000000000000000
Dec 5 12:49:41 r2d2 kernel: <0> ffff8800b9ef57c0 0000000000000000 ffff8800b7c5daf8 ffffffff81138473
Dec 5 12:49:41 r2d2 kernel: <0> ffffea00027db6e0 ffff8800b7c5dc38 ffff8800b9ef58d8 ffff8800b7c5daf8
Dec 5 12:49:41 r2d2 kernel: Call Trace:
Dec 5 12:49:41 r2d2 kernel: [<ffffffff81138473>] ? ctail_readpages_filler+0x103/0x2a0
Dec 5 12:49:41 r2d2 kernel: [<ffffffff81138370>] ? ctail_readpages_filler+0x0/0x2a0
Dec 5 12:49:41 r2d2 kernel: [<ffffffff8107ee49>] ? read_cache_pages+0x99/0x100
Dec 5 12:49:41 r2d2 kernel: [<ffffffff8109d9a3>] ? __kmalloc+0x183/0x1f0
Dec 5 12:49:41 r2d2 kernel: [<ffffffff81136b64>] ? readpages_ctail+0xf4/0x350
Dec 5 12:49:41 r2d2 kernel: [<ffffffff812cbaa0>] ? rtnl_dump_all+0x0/0xd0
Dec 5 12:49:41 r2d2 kernel: [<ffffffff811262c9>] ? readpages_cryptcompress+0x49/0x90
Dec 5 12:49:41 r2d2 kernel: [<ffffffff8107e859>] ? __do_page_cache_readahead+0x189/0x230
Dec 5 12:49:41 r2d2 kernel: [<ffffffff8107e91c>] ? ra_submit+0x1c/0x30
Dec 5 12:49:41 r2d2 kernel: [<ffffffff810771c8>] ? generic_file_aio_read+0x378/0x610
Dec 5 12:49:41 r2d2 kernel: [<ffffffff810a1572>] ? do_sync_read+0xe2/0x120
Dec 5 12:49:41 r2d2 kernel: [<ffffffff811078f6>] ? reiser4_txn_end+0x176/0x660
Dec 5 12:49:41 r2d2 kernel: [<ffffffff810514c0>] ? autoremove_wake_function+0x0/0x30
Dec 5 12:49:41 r2d2 kernel: [<ffffffff811058a6>] ? reiser4_grab+0x66/0xd0
Dec 5 12:49:41 r2d2 kernel: [<ffffffff8112623b>] ? read_cryptcompress+0x7b/0xc0
Dec 5 12:49:41 r2d2 kernel: [<ffffffff81124c84>] ? reiser4_read_careful+0x74/0x170
Dec 5 12:49:41 r2d2 kernel: [<ffffffff810a19a5>] ? vfs_read+0xb5/0x1a0
Dec 5 12:49:41 r2d2 kernel: [<ffffffff810a1ffe>] ? sys_read+0x4e/0x90
Dec 5 12:49:41 r2d2 kernel: [<ffffffff8100b3ab>] ? system_call_fastpath+0x16/0x1b
Dec 5 12:49:41 r2d2 kernel: Code: 0b 08 45 31 ff e9 b6 fd ff ff e8 1c 70 1f 00 f0 0f ba 2b 00 19 c0 85 c0 0f 84 a2 fd ff ff 48 89 df e8 c5 d9 f3 ff e9 95 fd ff ff <0f> 0b eb fe f6 03 08 74 72 48 8b bd 80 00 00 00 e8 9b 84 fe ff
Dec 5 12:49:41 r2d2 kernel: RIP [<ffffffff81138240>] do_readpage_ctail+0x2a0/0x3d0
Dec 5 12:49:41 r2d2 kernel: RSP <ffff8800b7c5da28>
|
Seems Edward is aware of some issues http://marc.info/?l=reiserfs-devel&m=125974376101360&w=2 |
|
Back to top |
|
|
Kollin Veteran
Joined: 25 Feb 2006 Posts: 1139 Location: Sofia/Bulgaria
|
Posted: Sat Dec 05, 2009 3:46 pm Post subject: |
|
|
yeah reiser4 is always broken till at least stable3 or 4 on every release _________________ "Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..." |
|
Back to top |
|
|
cheater1034 Veteran
Joined: 09 Sep 2004 Posts: 1558
|
Posted: Sat Dec 05, 2009 5:21 pm Post subject: |
|
|
Please try the following patch on top of 2.6.32-zen1 (zen-stable master, that's the one that's broken now right?)
This is the patch we sent to edward and he seemed to ignore it in favor of something different, but I'm not so sure so please try it over zen-stable master and report back, i'm ready to push it if it works.
http://omploader.org/vMng3eg (reiser4-test.patch)
Thanks _________________ IRC!: #zen-sources on irc.rizon.net
zen-kernel.org
--
Lost in android development land. |
|
Back to top |
|
|
seqizz Tux's lil' helper
Joined: 14 Jan 2008 Posts: 103
|
Posted: Sat Dec 05, 2009 6:00 pm Post subject: |
|
|
When i want to power off, sometimes, my laptop finishes all the 'init 0' stuff and prints "[Power Off]", and waits.. Until i press the power off button. Why is this happening? |
|
Back to top |
|
|
albright Advocate
Joined: 16 Nov 2003 Posts: 2588 Location: Near Toronto
|
Posted: Sat Dec 05, 2009 6:11 pm Post subject: |
|
|
I am happy to report that with git stable zen 2.6.32 my
tuxonice problem is fixed
many thanks
(now if I could only figure out why googleearth will only
run in opengl software emulation mode ... but that is
not a zen problem) _________________ .... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme) |
|
Back to top |
|
|
r2dtu Tux's lil' helper
Joined: 23 Aug 2002 Posts: 87
|
Posted: Sat Dec 05, 2009 7:07 pm Post subject: |
|
|
cheater1034 wrote: | Please try the following patch on top of 2.6.32-zen1 (zen-stable master, that's the one that's broken now right?)
This is the patch we sent to edward and he seemed to ignore it in favor of something different, but I'm not so sure so please try it over zen-stable master and report back, i'm ready to push it if it works.
http://omploader.org/vMng3eg (reiser4-test.patch)
|
This is what I get with the patch applied:
Code: | WARNING: at fs/fs-writeback.c:588 writeback_inodes_wb+0x5ab/0x5b0()
Hardware name: ESPRIMO Mobile V5505
Modules linked in:
Pid: 4519, comm: umount Not tainted 2.6.32zen1-06557-g153a514 #1
Call Trace:
[<ffffffff8103ca63>] ? warn_slowpath_common+0x73/0xb0
[<ffffffff810c68bb>] ? writeback_inodes_wb+0x5ab/0x5b0
[<ffffffff8111b793>] ? reiser4_sync_inodes+0x83/0x110
[<ffffffff810c6fa2>] ? sync_inodes_sb+0x22/0x110
[<ffffffff810ca936>] ? __sync_filesystem+0x26/0x90
[<ffffffff810caa64>] ? sync_filesystems+0xc4/0x110
[<ffffffff810caafc>] ? sys_sync+0x1c/0x40
[<ffffffff8100b3ab>] ? system_call_fastpath+0x16/0x1b
---[ end trace 01e7cb9101f19a05 ]---
|
|
|
Back to top |
|
|
Waninkoko Guru
Joined: 13 May 2005 Posts: 549
|
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Sat Dec 05, 2009 9:43 pm Post subject: |
|
|
System locked up a few hours after I started a few things before I went to sleep. The panic was partially on my screen this morning and I noted that it complained about preemption. Disabled by goign to server profile, but I still get this when I hit up sync right after booting:
Code: | Dec 5 13:35:38 Atlas kernel: [ 119.921672] ------------[ cut here ]------------
Dec 5 13:35:38 Atlas kernel: [ 119.921675] WARNING: at fs/fs-writeback.c:588 0xffffffff810afc4b()
Dec 5 13:35:38 Atlas kernel: [ 119.921677] Modules linked in: coretemp it87 hwmon_vid hwmon btrfs crc32c libcrc32c dm_mod snd_
hda_codec_realtek nvidia(P) snd_hda_intel snd_hda_codec rtc_cmos rtc_core firewire_ohci firewire_core firmware_class snd_hwdep s
nd_pcm snd_timer snd soundcore usbhid snd_page_alloc i2c_i801 uhci_hcd rtc_lib crc_itu_t ehci_hcd i2c_core usbcore sata_sil24 [l
ast unloaded: microcode]
Dec 5 13:35:38 Atlas kernel: [ 119.921697] Pid: 2051, comm: sync Tainted: P 2.6.32-rc8-zen1-Btrfs #2
Dec 5 13:35:38 Atlas kernel: [ 119.921699] Call Trace:
Dec 5 13:35:38 Atlas kernel: [ 119.921701] [<ffffffff810afc4b>] ? 0xffffffff810afc4b
Dec 5 13:35:38 Atlas kernel: [ 119.921702] [<ffffffff81034e07>] 0xffffffff81034e07
Dec 5 13:35:38 Atlas kernel: [ 119.921704] [<ffffffff81034e3f>] 0xffffffff81034e3f
Dec 5 13:35:38 Atlas kernel: [ 119.921705] [<ffffffff810afc4b>] 0xffffffff810afc4b
Dec 5 13:35:38 Atlas kernel: [ 119.921706] [<ffffffff810afe36>] 0xffffffff810afe36
Dec 5 13:35:38 Atlas kernel: [ 119.921707] [<ffffffff81102c91>] 0xffffffff81102c91
Dec 5 13:35:38 Atlas kernel: [ 119.921709] [<ffffffff810af153>] 0xffffffff810af153
Dec 5 13:35:38 Atlas kernel: [ 119.921710] [<ffffffff810b3a12>] 0xffffffff810b3a12
Dec 5 13:35:38 Atlas kernel: [ 119.921711] [<ffffffff810b3b1d>] 0xffffffff810b3b1d
Dec 5 13:35:38 Atlas kernel: [ 119.921712] [<ffffffff810b3bcc>] 0xffffffff810b3bcc
Dec 5 13:35:38 Atlas kernel: [ 119.921714] [<ffffffff8100b26b>] 0xffffffff8100b26b
Dec 5 13:35:38 Atlas kernel: [ 119.921715] ---[ end trace 357179636caae1af ]---
Dec 5 13:35:39 Atlas kernel: [ 120.931835] ------------[ cut here ]------------ |
I *think* this is btrfs. I know when I normalled execute sync on a fresh boot a few btrfs-cache processes go nuts for a minute or two, but only one of them show and lasts for about 3 seconds.
Edit: I have 2 reiser4 partitions; one for / and one for /home. Never had a problem with them and they still seems to be okay. _________________ Atlas (HDTV PVR, HTTP & Media server)
http://mobrienphotography.com/ |
|
Back to top |
|
|
r2dtu Tux's lil' helper
Joined: 23 Aug 2002 Posts: 87
|
Posted: Sat Dec 05, 2009 9:58 pm Post subject: |
|
|
I've reverted the previous one. This one doesn't compile:
Code: | fs/reiser4/super_ops.c: In function 'reiser4_sync_inodes':
fs/reiser4/super_ops.c:421: error: 'sb' undeclared (first use in this function)
fs/reiser4/super_ops.c:421: error: (Each undeclared identifier is reported only once
fs/reiser4/super_ops.c:421: error: for each function it appears in.)
|
|
|
Back to top |
|
|
rahulthewall Veteran
Joined: 01 Nov 2007 Posts: 1264 Location: Zürich
|
Posted: Sat Dec 05, 2009 10:22 pm Post subject: |
|
|
Hi,
Just a small request. Currently uname -a reports the kernel version as 2.6.32zen1 . This causes the script /lib/udev/shell-compat-KV.sh to return an error (error returned is 32zen1). This script is used during the boot process when udev is started. So if you could change the kernel version number to 2.6.32-zen1 I think this problem would be resolved.
Cheers
Rahul _________________ Who shall guard the guards? |
|
Back to top |
|
|
Waninkoko Guru
Joined: 13 May 2005 Posts: 549
|
Posted: Sun Dec 06, 2009 12:10 am Post subject: |
|
|
r2dtu wrote: |
I've reverted the previous one. This one doesn't compile:
Code: | fs/reiser4/super_ops.c: In function 'reiser4_sync_inodes':
fs/reiser4/super_ops.c:421: error: 'sb' undeclared (first use in this function)
fs/reiser4/super_ops.c:421: error: (Each undeclared identifier is reported only once
fs/reiser4/super_ops.c:421: error: for each function it appears in.)
|
|
Whoops, just replace "sb" with "super". |
|
Back to top |
|
|
cheater1034 Veteran
Joined: 09 Sep 2004 Posts: 1558
|
Posted: Sun Dec 06, 2009 3:19 am Post subject: |
|
|
rahulthewall wrote: | Hi,
Just a small request. Currently uname -a reports the kernel version as 2.6.32zen1 . This causes the script /lib/udev/shell-compat-KV.sh to return an error (error returned is 32zen1). This script is used during the boot process when udev is started. So if you could change the kernel version number to 2.6.32-zen1 I think this problem would be resolved.
Cheers
Rahul |
Thanks that was my mistake, it's fixed now. _________________ IRC!: #zen-sources on irc.rizon.net
zen-kernel.org
--
Lost in android development land. |
|
Back to top |
|
|
Gibbo_07 n00b
Joined: 15 Nov 2009 Posts: 38 Location: Brisbane, AU
|
Posted: Sun Dec 06, 2009 8:52 am Post subject: |
|
|
cp+paste from another thread where info wasn't going anywhere useful.
My experience today upon trying this shiny new kernel from git (my first zen kernel actually), rebooted and all seemed perfect until after ~15mins got a hard lock - was tarring up files so thought perhaps stress related anomaly then upon reboot 15mins into a movie and starting an emerge it went again. Gave it one more chance and same again got maybe 10mins out of it, no warnings no log just dead. Only thing I can think is I was writing to my reiser4 portage partition at the time, as per the issues noted above perhaps this has something to do with it?
Be nice to know i'm not alone and it's less likely to be my config as I sure spent my time with it and would be lost as to what my problem might be :/
I used pappy's 2.6.32-zen0 seed and changed only what I know should work for me.
Similar experiences?
Edit: lots |
|
Back to top |
|
|
r2dtu Tux's lil' helper
Joined: 23 Aug 2002 Posts: 87
|
Posted: Sun Dec 06, 2009 8:57 am Post subject: |
|
|
Waninkoko wrote: | r2dtu wrote: |
I've reverted the previous one. This one doesn't compile:
Code: | fs/reiser4/super_ops.c: In function 'reiser4_sync_inodes':
fs/reiser4/super_ops.c:421: error: 'sb' undeclared (first use in this function)
fs/reiser4/super_ops.c:421: error: (Each undeclared identifier is reported only once
fs/reiser4/super_ops.c:421: error: for each function it appears in.)
|
|
Whoops, just replace "sb" with "super". |
replacing just "sb" with "super" still wouldn't compile. So I've replaced "sb->umount" with "super->s_umount". This compiles but the system hangs when trying to unmount a reiser4 volume. |
|
Back to top |
|
|
Mr. Tao Tux's lil' helper
Joined: 20 Jul 2007 Posts: 147
|
Posted: Sun Dec 06, 2009 11:08 am Post subject: |
|
|
I installed 2.6.31-zen9 from portage using same .config as in zen8, which AFAIK was stable and this is what I got today. I restarted afs-client and I'm able to work again (2 hours so far): Quote: | Dec 6 10:07:15 localhost kernel: [50878.594559] ------------[ cut here ]------------
Dec 6 10:07:15 localhost kernel: [50878.594566] WARNING: at mm/slqb.c:2418 kmem_cache_destroy+0x209/0x240()
Dec 6 10:07:15 localhost kernel: [50878.594569] Hardware name: Precision WorkStation T7500
Dec 6 10:07:15 localhost kernel: [50878.594570] Modules linked in: libafs(P-) coretemp adt7473 fuse ohci1394 8250_pnp 8250 serial_core rtc_cmos parport_pc nvidia(P) usb_storage iTCO_wdt rtc_core rtc_lib parport dcdbas tg3 ieee1394 i2c_i801 pcspkr libphy wmi
Dec 6 10:07:15 localhost kernel: [50878.594590] Pid: 11503, comm: modprobe Tainted: P 2.6.31-zen9-custom-makalinux #1
Dec 6 10:07:15 localhost kernel: [50878.594593] Call Trace:
Dec 6 10:07:15 localhost kernel: [50878.594600] [<ffffffff810413a8>] warn_slowpath_common+0x78/0xb0
Dec 6 10:07:15 localhost kernel: [50878.594604] [<ffffffff810413ef>] warn_slowpath_null+0xf/0x20
Dec 6 10:07:15 localhost kernel: [50878.594607] [<ffffffff810d0f09>] kmem_cache_destroy+0x209/0x240
Dec 6 10:07:15 localhost kernel: [50878.594634] [<ffffffffa0a6c015>] afs_destroy_inodecache+0x15/0x20 [libafs]
Dec 6 10:07:15 localhost kernel: [50878.594657] [<ffffffffa0a7ef7d>] cleanup_module+0x2d/0x81 [libafs]
Dec 6 10:07:15 localhost kernel: [50878.594662] [<ffffffff8108cf00>] ? __synchronize_sched+0x50/0x60
Dec 6 10:07:15 localhost kernel: [50878.594666] [<ffffffff810553e0>] ? wakeme_after_rcu+0x0/0x10
Dec 6 10:07:15 localhost kernel: [50878.594670] [<ffffffff8106c1a9>] ? module_refcount+0x49/0x60
Dec 6 10:07:15 localhost kernel: [50878.594674] [<ffffffff8106d110>] sys_delete_module+0x1b0/0x270
Dec 6 10:07:15 localhost kernel: [50878.594678] [<ffffffff8105c009>] ? up_read+0x9/0x10
Dec 6 10:07:15 localhost kernel: [50878.594682] [<ffffffff8153650e>] ? do_page_fault+0x1ae/0x3d0
Dec 6 10:07:15 localhost kernel: [50878.594687] [<ffffffff8100b46b>] system_call_fastpath+0x16/0x1b
Dec 6 10:07:15 localhost kernel: [50878.594690] ---[ end trace 22051258e493be38 ]---
Dec 6 10:07:15 localhost kernel: [50878.594691] ------------[ cut here ]------------
Dec 6 10:07:15 localhost kernel: [50878.594694] WARNING: at mm/slqb.c:2419 kmem_cache_destroy+0x11d/0x240()
Dec 6 10:07:15 localhost kernel: [50878.594696] Hardware name: Precision WorkStation T7500
Dec 6 10:07:15 localhost kernel: [50878.594698] Modules linked in: libafs(P-) coretemp adt7473 fuse ohci1394 8250_pnp 8250 serial_core rtc_cmos parport_pc nvidia(P) usb_storage iTCO_wdt rtc_core rtc_lib parport dcdbas tg3 ieee1394 i2c_i801 pcspkr libphy wmi
Dec 6 10:07:15 localhost kernel: [50878.594714] Pid: 11503, comm: modprobe Tainted: P W 2.6.31-zen9-custom-makalinux #1
Dec 6 10:07:15 localhost kernel: [50878.594716] Call Trace:
Dec 6 10:07:15 localhost kernel: [50878.594720] [<ffffffff810413a8>] warn_slowpath_common+0x78/0xb0
Dec 6 10:07:15 localhost kernel: [50878.594723] [<ffffffff810413ef>] warn_slowpath_null+0xf/0x20
Dec 6 10:07:15 localhost kernel: [50878.594726] [<ffffffff810d0e1d>] kmem_cache_destroy+0x11d/0x240
Dec 6 10:07:15 localhost kernel: [50878.594749] [<ffffffffa0a6c015>] afs_destroy_inodecache+0x15/0x20 [libafs]
Dec 6 10:07:15 localhost kernel: [50878.594772] [<ffffffffa0a7ef7d>] cleanup_module+0x2d/0x81 [libafs]
Dec 6 10:07:15 localhost kernel: [50878.594776] [<ffffffff8108cf00>] ? __synchronize_sched+0x50/0x60
Dec 6 10:07:15 localhost kernel: [50878.594780] [<ffffffff810553e0>] ? wakeme_after_rcu+0x0/0x10
Dec 6 10:07:15 localhost kernel: [50878.594784] [<ffffffff8106c1a9>] ? module_refcount+0x49/0x60
Dec 6 10:07:15 localhost kernel: [50878.594787] [<ffffffff8106d110>] sys_delete_module+0x1b0/0x270
Dec 6 10:07:15 localhost kernel: [50878.594790] [<ffffffff8105c009>] ? up_read+0x9/0x10
Dec 6 10:07:15 localhost kernel: [50878.594794] [<ffffffff8153650e>] ? do_page_fault+0x1ae/0x3d0
Dec 6 10:07:15 localhost kernel: [50878.594798] [<ffffffff8100b46b>] system_call_fastpath+0x16/0x1b
Dec 6 10:07:15 localhost kernel: [50878.594800] ---[ end trace 22051258e493be39 ]--- |
|
|
Back to top |
|
|
rahulthewall Veteran
Joined: 01 Nov 2007 Posts: 1264 Location: Zürich
|
Posted: Sun Dec 06, 2009 1:20 pm Post subject: |
|
|
cheater1034 wrote: | rahulthewall wrote: | Hi,
Just a small request. Currently uname -a reports the kernel version as 2.6.32zen1 . This causes the script /lib/udev/shell-compat-KV.sh to return an error (error returned is 32zen1). This script is used during the boot process when udev is started. So if you could change the kernel version number to 2.6.32-zen1 I think this problem would be resolved.
Cheers
Rahul |
Thanks that was my mistake, it's fixed now. |
Cool. Works now. _________________ Who shall guard the guards? |
|
Back to top |
|
|
keenblade Veteran
Joined: 03 Oct 2004 Posts: 1087
|
Posted: Sun Dec 06, 2009 4:39 pm Post subject: |
|
|
seqizz wrote: | When i want to power off, sometimes, my laptop finishes all the 'init 0' stuff and prints "[Power Off]", and waits.. Until i press the power off button. Why is this happening? |
I think there is an ACPI bug with your laptop bios. Check if there is an update for your bios. _________________ Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1" |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Mon Dec 07, 2009 10:33 am Post subject: |
|
|
2.6.32-zen0. Same problem as with 2.6.32-rc8-zen1
Boot, execute sync. I get this.
I have 4 disks.
A partition from each is combined in LVM2. Another partition from each is raid0'd with btrfs. the LVM2 grouping is formatted with btrfs.
Edit
http://pastebin.com/m5726722c <-- I was told I omited frame pointers on accident, fixed now.
http://pastebin.com/m7a8afe1 <-- my .config unless I'm missing something else I shouldn't _________________ Atlas (HDTV PVR, HTTP & Media server)
http://mobrienphotography.com/
Last edited by DigitalCorpus on Mon Dec 07, 2009 11:01 am; edited 2 times in total |
|
Back to top |
|
|
bollucks l33t
Joined: 27 Oct 2004 Posts: 606
|
Posted: Mon Dec 07, 2009 10:54 am Post subject: |
|
|
DigitalCorpus wrote: | Okay, so playing with Xfce4 a bit with rr_interval set to 18 (that is defautl for a quad core). Unfortunately the paradigm of more cores == less latency is not true. I' had 2, 4-thread mencoder encodes in the backgorund. One niced to 19 and the other at -10. I had to drop r_interval down to ~6 in order to not have a choppy display when dragging around windows et al. Kind of an extreme case, but if you choose seemless latency, keep the rr_interval in the kernel set to 6 or below. Keep in mind the post-boot rr_interval seems to be calculated as in kernel rr_interval * (# cpus's - 1 ). Just an FYI for you all. |
Dude, nice -10 is a decidedly useless thing to do an a video encode. Why are you minus nicing it? You're telling it to use many times more CPU than your foreground processes. -nice is for "root to override system when it's being Denial Of Service attacked". It is not for normal users as it drowns out everything else. The bad behaviour is due to the way you're using nice. I'm assuming you're confused thinking that -10 will somehow make it faster than 0. That's basically wrong. If nothing is running on your machine, nice -20 runs no faster than nice +19. Nice 19 uses 3% of the cpu nice 0 uses only when both nice 0 and nice 19 tasks are running. You do not have to negative nice anything in normal use. The fact it ran smoothly at any rr interval is amazing. |
|
Back to top |
|
|
DigitalCorpus Apprentice
Joined: 30 Jul 2007 Posts: 283
|
Posted: Mon Dec 07, 2009 11:12 am Post subject: |
|
|
bollucks wrote: | DigitalCorpus wrote: | Okay, so playing with Xfce4 a bit with rr_interval set to 18 (that is defautl for a quad core). Unfortunately the paradigm of more cores == less latency is not true. I' had 2, 4-thread mencoder encodes in the backgorund. One niced to 19 and the other at -10. I had to drop r_interval down to ~6 in order to not have a choppy display when dragging around windows et al. Kind of an extreme case, but if you choose seemless latency, keep the rr_interval in the kernel set to 6 or below. Keep in mind the post-boot rr_interval seems to be calculated as in kernel rr_interval * (# cpus's - 1 ). Just an FYI for you all. |
Dude, nice -10 is a decidedly useless thing to do an a video encode. Why are you minus nicing it? You're telling it to use many times more CPU than your foreground processes. -nice is for "root to override system when it's being Denial Of Service attacked". It is not for normal users as it drowns out everything else. The bad behaviour is due to the way you're using nice. I'm assuming you're confused thinking that -10 will somehow make it faster than 0. That's basically wrong. If nothing is running on your machine, nice -20 runs no faster than nice +19. Nice 19 uses 3% of the cpu nice 0 uses only when both nice 0 and nice 19 tasks are running. You do not have to negative nice anything in normal use. The fact it ran smoothly at any rr interval is amazing. |
I'm running this box mostly as a server. Now that may be the intended use for nice when it was created, but say I have something else in mind. I want to have a couple encodes going. One I want done but I dont' care when and I dont' want it to bother me. I know bumping it to 19 will accomplish that just fine. On ther other hand I had another set that I wanted to take priority over anything else I was doing, even if I called a bit on the CPU, which was bound to happen, even on my quad. I know that if I have any single taks going that -20 and 19 will still have the task execute in the same duration given the system is idle otherwise. from what I've read about nice levels, the mathematical explanation works out to a 5% drop in requested CPU usage with each bump of the nice level, sans schedulign overhead. I run mostly a server and I dont' mind if my GUI suffers a bit. It took me a year to put a GUI on here. If I still had full GUI interactivity and could determine what the lowest value of rr_interval is for the BFS scheduler for my preferences while preferenceign a groups of tasks (I load up to about 14 to 16 threads), then thats awesome imho. Every new task starts at 0. Why renice them to 10 to achive the scheduling priority I want when I can just make my top task -20 if it doesn't hurt the system? I could renice bash to 10, but when I'm done, I dont' want to have to remember to change it back. Thanks to BFS I can do this. CFS previously failed which is why you're so amazed probably. _________________ Atlas (HDTV PVR, HTTP & Media server)
http://mobrienphotography.com/ |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Mon Dec 07, 2009 2:10 pm Post subject: |
|
|
DigitalCorpus wrote: | Why renice them to 10 to achive the scheduling priority I want when I can just make my top task -20 if it doesn't hurt the system? |
Because encoding a video at -20 means you're starving all your kernel threads, which run at nice=0, of CPU time. It does hurt the system, and it doesn't magically make the CPU encode video faster. You might possibly save a few fractions of a second while missing a few critical ACPI events as a result. |
|
Back to top |
|
|
r2dtu Tux's lil' helper
Joined: 23 Aug 2002 Posts: 87
|
|
Back to top |
|
|
|