Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2734
Location: Gainesville, Florida

PostPosted: Wed Feb 02, 2011 5:43 am    Post subject: Reply with quote

Well, no luck. :cry:
Code:
Kernel Panic -not syncing  attempted to kill init!
Pid : 1 comm:  swapper Tainted : G  D         2.6.37 #1

My grub kernel line:
Code:
 kernel /boot/2.6.37 root=/dev/sda3 video=1280x1024-24@75 rootflags=commit=5 kztmem

I was very very careful compiling this one and all seemed to go normally this time, so I'm at a loss to explain the panic except for a patch problem.
I do enable KMS- could that be a problem? Any suggestions?

EDIT: Hmmm. I did forget to enable CONFIG_SCHED_AUTOGROUP. Could that cause a kernel panic since cgroup and other items are enabled?

Perhaps a short rundown of what specific kernel options are absolutely required when all these patches are used would help.
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19, gcc-4.8.2, kernel 3.14.0-gentoo (USE=experimental)
Back to top
View user's profile Send private message
tranquilcool
Veteran
Veteran


Joined: 25 Mar 2005
Posts: 1044

PostPosted: Wed Feb 02, 2011 9:13 am    Post subject: Reply with quote

kernelOfTruth wrote:
tranquilcool wrote:
GEN include/generated/bounds.h
CC arch/x86/kernel/asm-offsets.s
In file included from include/linux/suspend.h:8:0,
from arch/x86/kernel/asm-offsets_32.c:11,
from arch/x86/kernel/asm-offsets.c:2:
include/linux/mm.h:515:2: error: #error SECTIONS_WIDTH+NODES_WIDTH+ZONES_WIDTH > BITS_PER_LONG - NR_PAGEFLAGS
make[1]: *** [arch/x86/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2

am very much interested to know what is happening here and with zen and your
sources.
i have been investigating and no solutions so far.
the code seems to be same but apparently something else is not right.



ok,

try disabling NUMA (you most likely don't have a numa box)

if that does not help try to disable PAE,

whether that makes a change

from what I read on the net the memory model also seems to be involved in those kind of things so please post the memory model (flat, sparse you have available for selection)



if I understood correctly it's running out of pageflags


gotta go to sleep now ...


i switch from sparse memory option to flat and the kernel compiles
but then panics at boot.
then i removed the PAE option. compiles, boots and now is running fine.
thanks.

@wrc1944
try disabling PAE.

CONFIG_SCHED_AUTOGROUP has no use for a desktop machine.
_________________
this is a strange strange world.
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Wed Feb 02, 2011 10:55 am    Post subject: Reply with quote

tranquilcool wrote:


i switch from sparse memory option to flat and the kernel compiles
but then panics at boot.
then i removed the PAE option. compiles, boots and now is running fine.
thanks.

@wrc1944
try disabling PAE.



well, it's more of a temporary "quick fix" since (afaik) it'll disable NX protection and support for more than 4 GiB of RAM :(

tranquilcool wrote:


CONFIG_SCHED_AUTOGROUP has no use for a desktop machine.


are you kidding ? :?

this is the best improvement and invention since Con's SD-scheduler or BFS in mainline :D
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
tranquilcool
Veteran
Veteran


Joined: 25 Mar 2005
Posts: 1044

PostPosted: Wed Feb 02, 2011 11:18 am    Post subject: Reply with quote

kernelOfTruth wrote:
tranquilcool wrote:


i switch from sparse memory option to flat and the kernel compiles
but then panics at boot.
then i removed the PAE option. compiles, boots and now is running fine.
thanks.

@wrc1944
try disabling PAE.



well, it's more of a temporary "quick fix" since (afaik) it'll disable NX protection and support for more than 4 GiB of RAM :(

tranquilcool wrote:


CONFIG_SCHED_AUTOGROUP has no use for a desktop machine.


are you kidding ? :?

this is the best improvement and invention since Con's SD-scheduler or BFS in mainline :D



true. CONFIG_SCHED_AUTOGROUP is a desktop option. was confused with
some other stuff.
_________________
this is a strange strange world.
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Wed Feb 02, 2011 11:25 am    Post subject: Reply with quote

wrc1944 wrote:
Well, no luck. :cry:
Code:
Kernel Panic -not syncing  attempted to kill init!
Pid : 1 comm:  swapper Tainted : G  D         2.6.37 #1

My grub kernel line:
Code:
 kernel /boot/2.6.37 root=/dev/sda3 video=1280x1024-24@75 rootflags=commit=5 kztmem

I was very very careful compiling this one and all seemed to go normally this time, so I'm at a loss to explain the panic except for a patch problem.
I do enable KMS- could that be a problem? Any suggestions?

EDIT: Hmmm. I did forget to enable CONFIG_SCHED_AUTOGROUP. Could that cause a kernel panic since cgroup and other items are enabled?

Perhaps a short rundown of what specific kernel options are absolutely required when all these patches are used would help.


Quote:
title Gentoo-kernel-37-plus_v13 [lupus]
root (hd0,0)
kernel (hd0,0)/kernel-37-plus_v13_kztram dolvm root=/dev/ram0 init=/linuxrc ramdisk=8192 crypt_root=/dev/sda5 real_root=/dev/mapper/GENTOO1-ROOT real_resume=/dev/mapper/GENTOO1-SWAP resume=/dev/mapper/GENTOO1-SWAP tuxonice_resume=/dev/mapper/GENTOO1-SWAP udev ro elevator=deadline snd-hda-intel.enable_msi=1 fbcon=scrollback:256K pax_softmode=1 pax_nouderef clocksource=tsc usbcore.autosuspend=1 raid=noautodetect kztmem
initrd (hd0,0)/initramfs-37-plus_v13



all other flags except kztmem are superfluous or in cases I want to try out new grsecurity kernels so that I won't forget anything for the start (they won't do harm if the features are not included in the kernel) ;)


DO NOT enable KMS :idea:

I have a 5850 (evergreen) card and enabling it by default & having the radeon-module compiled in leads to hardlock / a kernel panic at the booting

so I tend to let it load later after the init or even load it manually with modeset - after that it works fine


dunno why - maybe missing firmware or something


I don't have time and care to investigate that for now ...
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Wed Feb 02, 2011 11:44 am    Post subject: Reply with quote

I've actually hesitated to write/talk about this but

guys, you could also try to use a 64bit kernel with 32bit userland:

32bit-userland on Gentoo amd64

there are also several threads in this forum


if your processor supports 64bit - that is ...


simply search for

64 bit kernel 32bit userland gentoo

via google:

site:forums.gentoo.org 64 bit kernel 32bit userland gentoo
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2734
Location: Gainesville, Florida

PostPosted: Wed Feb 02, 2011 2:32 pm    Post subject: Reply with quote

OK. Recompiled without PAE, and set CONFIG_SCHED_AUTOGROUP=y, rebooted and got the same kernel panic.

Then I added radeon.modeset=0 to the kernel line (edited in the grub boot screen), and got same kernel panic. :cry:

So, in my case neither PAE or KMS seems to be the problem, or do I need to completely disable KMS in kernel config, and NOT rely on the grub kernel line option radeon.modeset=0?

More reading raised more questions about disabling KMS, as regards to failure to start X problems, and other various poor performance issues.

I'm NOT using an initrd (haven't for years) on hundreds of manually compiled kernels in many distros with no problems. Is this an issue? My basic config is always finely tuned to my hardware, and almost never presents a problem, so I'm thinking this kernel panic must be one of these patches, or I'm simply not aware of a required kernel option. :?

I'm going back to the other Gentoo ~xf86 box, which doesn't have KMS enabled, and try fresh again now that I know I can at least get the kerenl to compile.

Any other ideas? :)
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19, gcc-4.8.2, kernel 3.14.0-gentoo (USE=experimental)
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Wed Feb 02, 2011 3:06 pm    Post subject: Reply with quote

wrc1944 wrote:
OK. Recompiled without PAE, and set CONFIG_SCHED_AUTOGROUP=y, rebooted and got the same kernel panic.

Then I added radeon.modeset=0 to the kernel line (edited in the grub boot screen), and got same kernel panic. :cry:

So, in my case neither PAE or KMS seems to be the problem, or do I need to completely disable KMS in kernel config, and NOT rely on the grub kernel line option radeon.modeset=0?

More reading raised more questions about disabling KMS, as regards to failure to start X problems, and other various poor performance issues.

I'm NOT using an initrd (haven't for years) on hundreds of manually compiled kernels in many distros with no problems. Is this an issue? My basic config is always finely tuned to my hardware, and almost never presents a problem, so I'm thinking this kernel panic must be one of these patches, or I'm simply not aware of a required kernel option. :?

I'm going back to the other Gentoo ~xf86 box, which doesn't have KMS enabled, and try fresh again now that I know I can at least get the kerenl to compile.

Any other ideas? :)


yes,

it might be a little difficult or counter-productive to compare a 32bit to a 64bit config

but: here you are <-- my kernel-config inside


and


as I already wrote:

there's always the option of running a 64bit kernel on 32bit userland

or

migrating to 64bit ;)


several times in the past I had tried to migrate back to 32bit (because of the smaller binaries) but there was way too much hassle and other 32bit-specific issues involved

so I'm settling for 64bit for now :)
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2734
Location: Gainesville, Florida

PostPosted: Wed Feb 02, 2011 3:57 pm    Post subject: Reply with quote

Thanks much! :D I'll adapt your config file for my hardware, and try that on my main Gentoo box.

On my other non-KMS ~xf86 Gentoo box, I just edited my config file per what I learned on the other box, but on make modules, I get:
Code:
  CC [M]  lib/lzo/lzo1x_decompress.o
  LD [M]  lib/lzo/lzo_compress.o
  LD [M]  lib/lzo/lzo_decompress.o
  Building modules, stage 2.
  MODPOST 78 modules
ERROR: "tmem_put" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "xv_malloc" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "xv_free" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "xv_get_object_size" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_destroy_pool" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_new_pool" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_get" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_flush_object" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_flush_page" [drivers/staging/kztmem/kztmem.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
wrc@gentoo ~/kern/linux-2.6.37-plusv13 $
I expected this one to at least compile OK, but looks like I must have missed a config option? :roll: I know I set the kztmem option just like in the other box that compiled OK. :?
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19, gcc-4.8.2, kernel 3.14.0-gentoo (USE=experimental)
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Wed Feb 02, 2011 4:10 pm    Post subject: Reply with quote

wrc1944 wrote:
Thanks much! :D I'll adapt your config file for my hardware, and try that on my main Gentoo box.

On my other non-KMS ~xf86 Gentoo box, I just edited my config file per what I learned on the other box, but on make modules, I get:
Code:
  CC [M]  lib/lzo/lzo1x_decompress.o
  LD [M]  lib/lzo/lzo_compress.o
  LD [M]  lib/lzo/lzo_decompress.o
  Building modules, stage 2.
  MODPOST 78 modules
ERROR: "tmem_put" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "xv_malloc" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "xv_free" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "xv_get_object_size" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_destroy_pool" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_new_pool" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_get" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_flush_object" [drivers/staging/kztmem/kztmem.ko] undefined!
ERROR: "tmem_flush_page" [drivers/staging/kztmem/kztmem.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
wrc@gentoo ~/kern/linux-2.6.37-plusv13 $
I expected this one to at least compile OK, but looks like I must have missed a config option? :roll: I know I set the kztmem option just like in the other box that compiled OK. :?


seems like you forgot at least zram
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2734
Location: Gainesville, Florida

PostPosted: Wed Feb 02, 2011 4:20 pm    Post subject: Reply with quote

In my haste, I stupidly just clicked once in xconfig and made them modules, instead of twice to built them in. :oops: I'm loosing my mind trying to get this to work. :roll:

OK- SUCCESS! After fixing up my kernel config (NO KMS enabled in kernel, cgroups with auto set, zram and kztmem enabled under staging drivers, kztmem on grub kernel line, and all other needed kernel options, everything compiled/installed/booted with no problems. Finally! Of course, what did I expect? :wink:

However I'm curious as to what the new and unusual dmesg output means??? :o What happened to all the usual stuff in dmesg? :o
Code:
wrc@gentoo ~ $ uname -a
Linux gentoo 2.6.37-plusv13 #1 PREEMPT Tue Feb 1 23:23:00 EST 2011 i686 AMD Athlon(tm) XP 3000+ AuthenticAMD GNU/Linux
wrc@gentoo ~ $ dmesg
ztmem/kztmem.c:274 0xb02e7c68()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7c68>] ? 0xb02e7c68
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7c68>] ? 0xb02e7c68
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b0187b4a>] ? 0xb0187b4a
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc335 ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:228 0xb02e796c()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e796c>] ? 0xb02e796c
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e796c>] ? 0xb02e796c
 [<b02e7cb7>] ? 0xb02e7cb7
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b0187b4a>] ? 0xb0187b4a
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc336 ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:168 0xb02e7259()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7259>] ? 0xb02e7259
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7259>] ? 0xb02e7259
 [<b02e8188>] ? 0xb02e8188
 [<b02e8c0b>] ? 0xb02e8c0b
 [<b02e844e>] ? 0xb02e844e
 [<b02e850f>] ? 0xb02e850f
 [<b016ddb6>] ? 0xb016ddb6
 [<b014eb8d>] ? 0xb014eb8d
 [<b014ec61>] ? 0xb014ec61
 [<b0155963>] ? 0xb0155963
 [<b0155a1e>] ? 0xb0155a1e
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b0187b4a>] ? 0xb0187b4a
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc337 ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:274 0xb02e7c68()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7c68>] ? 0xb02e7c68
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7c68>] ? 0xb02e7c68
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b0187b4a>] ? 0xb0187b4a
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc338 ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:228 0xb02e796c()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e796c>] ? 0xb02e796c
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e796c>] ? 0xb02e796c
 [<b02e7cb7>] ? 0xb02e7cb7
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b0187b4a>] ? 0xb0187b4a
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc339 ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:168 0xb02e7259()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7259>] ? 0xb02e7259
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7259>] ? 0xb02e7259
 [<b02e8188>] ? 0xb02e8188
 [<b02e8c0b>] ? 0xb02e8c0b
 [<b02e844e>] ? 0xb02e844e
 [<b02e850f>] ? 0xb02e850f
 [<b016ddb6>] ? 0xb016ddb6
 [<b014eb8d>] ? 0xb014eb8d
 [<b014ec61>] ? 0xb014ec61
 [<b0155963>] ? 0xb0155963
 [<b0155a1e>] ? 0xb0155a1e
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b0187b4a>] ? 0xb0187b4a
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc33a ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:274 0xb02e7c68()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7c68>] ? 0xb02e7c68
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7c68>] ? 0xb02e7c68
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b0187b4a>] ? 0xb0187b4a
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc33b ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:228 0xb02e796c()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e796c>] ? 0xb02e796c
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e796c>] ? 0xb02e796c
 [<b02e7cb7>] ? 0xb02e7cb7
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b0187b4a>] ? 0xb0187b4a
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc33c ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:168 0xb02e7259()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7259>] ? 0xb02e7259
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7259>] ? 0xb02e7259
 [<b02e8188>] ? 0xb02e8188
 [<b0189bf4>] ? 0xb0189bf4
 [<b02e8c0b>] ? 0xb02e8c0b
 [<b0189bf4>] ? 0xb0189bf4
 [<b02e844e>] ? 0xb02e844e
 [<b02e850f>] ? 0xb02e850f
 [<b016ddb6>] ? 0xb016ddb6
 [<b014eb8d>] ? 0xb014eb8d
 [<b014ec61>] ? 0xb014ec61
 [<b0155963>] ? 0xb0155963
 [<b0155a1e>] ? 0xb0155a1e
 [<b01d9ca9>] ? 0xb01d9ca9
 [<b0155bad>] ? 0xb0155bad
 [<b0155bf5>] ? 0xb0155bf5
 [<b0155c61>] ? 0xb0155c61
 [<b0155c88>] ? 0xb0155c88
 [<b01c78a6>] ? 0xb01c78a6
 [<b017ea71>] ? 0xb017ea71
 [<b019123d>] ? 0xb019123d
 [<b016e4e1>] ? 0xb016e4e1
 [<b01776da>] ? 0xb01776da
 [<b016e5b1>] ? 0xb016e5b1
 [<b016e712>] ? 0xb016e712
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc33d ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:274 0xb02e7c68()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7c68>] ? 0xb02e7c68
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7c68>] ? 0xb02e7c68
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b01d9ca9>] ? 0xb01d9ca9
 [<b0155bad>] ? 0xb0155bad
 [<b0155bf5>] ? 0xb0155bf5
 [<b0155c61>] ? 0xb0155c61
 [<b0155c88>] ? 0xb0155c88
 [<b01c78a6>] ? 0xb01c78a6
 [<b017ea71>] ? 0xb017ea71
 [<b019123d>] ? 0xb019123d
 [<b016e4e1>] ? 0xb016e4e1
 [<b01776da>] ? 0xb01776da
 [<b016e5b1>] ? 0xb016e5b1
 [<b016e712>] ? 0xb016e712
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc33e ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:228 0xb02e796c()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e796c>] ? 0xb02e796c
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e796c>] ? 0xb02e796c
 [<b02e7cb7>] ? 0xb02e7cb7
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b01d9ca9>] ? 0xb01d9ca9
 [<b0155bad>] ? 0xb0155bad
 [<b0155bf5>] ? 0xb0155bf5
 [<b0155c61>] ? 0xb0155c61
 [<b0155c88>] ? 0xb0155c88
 [<b01c78a6>] ? 0xb01c78a6
 [<b017ea71>] ? 0xb017ea71
 [<b019123d>] ? 0xb019123d
 [<b016e4e1>] ? 0xb016e4e1
 [<b01776da>] ? 0xb01776da
 [<b016e5b1>] ? 0xb016e5b1
 [<b016e712>] ? 0xb016e712
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc33f ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:168 0xb02e7259()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7259>] ? 0xb02e7259
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7259>] ? 0xb02e7259
 [<b02e8188>] ? 0xb02e8188
 [<b02e8c0b>] ? 0xb02e8c0b
 [<b02e844e>] ? 0xb02e844e
 [<b02e850f>] ? 0xb02e850f
 [<b016ddb6>] ? 0xb016ddb6
 [<b014eb8d>] ? 0xb014eb8d
 [<b014ec61>] ? 0xb014ec61
 [<b0155963>] ? 0xb0155963
 [<b0155a1e>] ? 0xb0155a1e
 [<b01c7687>] ? 0xb01c7687
 [<b019123d>] ? 0xb019123d
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b016f09f>] ? 0xb016f09f
 [<b016f0d1>] ? 0xb016f0d1
 [<b016f781>] ? 0xb016f781
 [<b016f8e1>] ? 0xb016f8e1
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc340 ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:274 0xb02e7c68()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e7c68>] ? 0xb02e7c68
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e7c68>] ? 0xb02e7c68
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b01c7687>] ? 0xb01c7687
 [<b019123d>] ? 0xb019123d
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b016f09f>] ? 0xb016f09f
 [<b016f0d1>] ? 0xb016f0d1
 [<b016f781>] ? 0xb016f781
 [<b016f8e1>] ? 0xb016f8e1
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc341 ]---
------------[ cut here ]------------
WARNING: at drivers/staging/kztmem/kztmem.c:228 0xb02e796c()
Hardware name: KT600-8237
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit snd_seq snd_pcm_oss snd_mixer_oss nls_cp850 snd_via82xx usbhid snd_ac97_codec ac97_bus snd_pcm via_agp snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi uhci_hcd ehci_hcd usbcore ath5k agpgart snd_seq_device snd i2c_viapro ath
Pid: 2701, comm: virtuoso-t Tainted: G        W   2.6.37-plusv13 #1
Call Trace:
 [<b011bb6e>] ? 0xb011bb6e
 [<b02e796c>] ? 0xb02e796c
 [<b011bb8e>] ? 0xb011bb8e
 [<b02e796c>] ? 0xb02e796c
 [<b02e7cb7>] ? 0xb02e7cb7
 [<b02e8e60>] ? 0xb02e8e60
 [<b02e7339>] ? 0xb02e7339
 [<b02e73a0>] ? 0xb02e73a0
 [<b016de21>] ? 0xb016de21
 [<b0155970>] ? 0xb0155970
 [<b0155a1e>] ? 0xb0155a1e
 [<b01c7687>] ? 0xb01c7687
 [<b019123d>] ? 0xb019123d
 [<b0155bad>] ? 0xb0155bad
 [<b01c938b>] ? 0xb01c938b
 [<b017d8b2>] ? 0xb017d8b2
 [<b017e038>] ? 0xb017e038
 [<b01776c5>] ? 0xb01776c5
 [<b016f09f>] ? 0xb016f09f
 [<b016f0d1>] ? 0xb016f0d1
 [<b016f781>] ? 0xb016f781
 [<b016f8e1>] ? 0xb016f8e1
 [<b0102790>] ? 0xb0102790
---[ end trace a0d28f350e4fc342 ]---
wrc@gentoo ~ $

_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19, gcc-4.8.2, kernel 3.14.0-gentoo (USE=experimental)
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Wed Feb 02, 2011 5:17 pm    Post subject: Reply with quote

those messages are most probably due to you having enabled lock debugging (especially spinlocks; e.g. CONFIG_DEBUG_SPINLOCK=y) in kernel debug options

all of them are

ASSERT_SPINLOCK(&zbpg->lock);
(from the code)

assert_spinlock - or assert gets called when the assertion/declaration is false

so it seems there are necessary locks which are not working

it could be due to the lockless patchsets included in my patch(set) or a general problem


I have disabled most or all of the debug-options to get maximum space so I didn't/won't see those messages


now if I only knew whether those statements shall get me to be concerned about it :?

I haven't seen any data loss or corruption yet :idea:


related stuff:
http://www.mail-archive.com/debian-kernel@lists.debian.org/msg06620.html
http://www.mail-archive.com/debian-bugs-closed@lists.debian.org/msg207451.html
http://lists.xensource.com/archives/html/xen-bugs/2009-05/msg00020.html
http://web.archiveorange.com/archive/v/TqOTnhcsGxR9XJPWE4zu
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2734
Location: Gainesville, Florida

PostPosted: Wed Feb 02, 2011 5:54 pm    Post subject: Reply with quote

kernelOfTruth wrote:
Quote:
now if I only knew whether those statements shall get me to be concerned about it :?

I haven't seen any data loss or corruption yet :idea:

Well, I just started the big full kde-4.5.5-kde-4.6.0 updates booted to your kernel, so I guess that'll be a good test. :wink:

I'l check on that CONFIG_DEBUG_SPINLOCK=y you mention, but IIRC it isn't enabled. I always build the leanest kernel possible, so I disable debug stuff unless I really have a specific reason to have it enabled. I'll let you know shortly- got some other things to do for a few hours while kde updates run.

OK- no CONFIG_DEBUG_SPINLOCK item found (only spinlock except for the IO Schedulers unset items) is this one, # CONFIG_RWSEM_GENERIC_SPINLOCK is not set, but I do have these other debug items set:
Code:
#
# Automatically generated make config: don't edit
# Linux/i386 2.6.37 Kernel Configuration
# Wed Feb  2 08:58:33 2011
#
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y

#
# Kernel Performance Events And Counters
#
CONFIG_SLUB_DEBUG=y
CONFIG_HAVE_DMA_API_DEBUG=y


#
# Processor type and features
#
CONFIG_X86_DEBUGCTLMSR=y

#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE_OHCI_DEBUG=y

#
# Kernel hacking
#
CONFIG_DEBUG_BUGVERBOSE=y

_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19, gcc-4.8.2, kernel 3.14.0-gentoo (USE=experimental)
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2734
Location: Gainesville, Florida

PostPosted: Wed Feb 02, 2011 8:42 pm    Post subject: Reply with quote

I've finally discovered the problem on my main Gentoo box. Pretty obscure.

It has 8GB ram, so I've always selected under Processor type and features->High memory support 64GB, which allows 32 bit systems to use more than 4GB. This box has 2 ~x86 and one ~amd64 Gentoo installs, each on its own partition). While I do have a 64bit cpu, I'm running a 32bit Gentoo install and trying to compile this new kernel on it.
Code:
64GB (HIGHMEM64G)

CONFIG_HIGHMEM64G:

Select this if you have a 32-bit processor and more than 4
gigabytes of physical RAM.

Easy to miss this, but it also enforces PAE even if you disable it manually in your config file, or with xconfig/menuconfig.
Code:
Symbol: HIGHMEM64G [=n]
Type : boolean
Prompt: 64GB
Defined at arch/x86/Kconfig:1037
Depends on: <choice> && !M386 [=n] && !M486 [=n]
Location:
-> Processor type and features
-> High Memory Support (<choice> [=y])
Selects: X86_PAE [=n]


In any case, this (along with the KMS being enabled) was preventing compiling the plusv13 kernel. I thought I had disabled PAE, but didn't realize that selecting 64GB high memory was overriding my no PAE setting. :lol:

Anyway, I've now got this new kernel on my main box, and will give it a good try for a few days and see what happens.

BTW- a few dmesg snippets (now shows somewhat normal output), showing relevant stuff, including the 32bit non-PAE less memory now available):
Code:
wrc@gentoo ~ $ dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.37-plusv13 (wrc@gentoo) (gcc version 4.5.2 (Gentoo 4.5.2 p1.0, pie-0.4.5) ) #1 SMP PREEMPT Wed Feb 2 15:05:02 EST 2011
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
 BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e7000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000cffb0000 (usable)
 BIOS-e820: 00000000cffb0000 - 00000000cffc0000 (ACPI data)
 BIOS-e820: 00000000cffc0000 - 00000000cfff0000 (ACPI NVS)
 BIOS-e820: 00000000cfff0000 - 00000000d0000000 (reserved)
 BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000230000000 (usable)
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
DMI present.
DMI: AOD790GX/128M/To Be Filled By O.E.M., BIOS P1.80 12/15/2009
---------------------------------------

2439MB HIGHMEM available.
887MB LOWMEM available.
  mapped low ram: 0 - 377fe000
  low ram: 0 - 377fe000
---------------------------------------------------

ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup.
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
------------------------------------------------------

zram: num_devices not specified. Using default: 1
zram: Creating 1 devices ...
kztmem: cleancache enabled using kernel transcendent memory and compression buddies
kztmem: frontswap enabled using kernel transcendent memory and xvmalloc
--------------------------------------------


EXT3-fs (sda3): using internal journal
kztmem: created ephemeral tmem pool, id=0
EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 60 seconds
EXT3-fs (sda5): using internal journal
kztmem: created ephemeral tmem pool, id=1
EXT3-fs (sda5): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 60 seconds
EXT3-fs (sda6): using internal journal
kztmem: created ephemeral tmem pool, id=2
EXT3-fs (sda6): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 60 seconds
EXT3-fs (sda7): using internal journal
kztmem: created ephemeral tmem pool, id=3
EXT3-fs (sda7): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 20 seconds
EXT3-fs (sda8): using internal journal
kztmem: created ephemeral tmem pool, id=4
EXT3-fs (sda8): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 20 seconds
EXT3-fs (sda9): using internal journal
kztmem: created ephemeral tmem pool, id=5
EXT3-fs (sda9): mounted filesystem with journal data mode
r8169 0000:02:00.0: eth1: link up
r8169 0000:02:00.0: eth1: link up
Adding 289164k swap on /dev/sda2.  Priority:-1 extents:1 across:289164k FS
kztmem: created persistent tmem pool, id=6
pci 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to userspace modesetting.
pci 0000:01:00.0: setting latency timer to 64
[drm] Initialized radeon 1.33.0 20080528 for 0000:01:00.0 on minor 0
[drm] Setting GART location based on new memory map
[drm] Loading RV730 CP Microcode
[drm] Resetting GPU
[drm] writeback test succeeded in 1 usecs
start_kdeinit (2627): /proc/2627/oom_adj is deprecated, please use /proc/2627/oom_score_adj instead.
python2.7[2735]: segfault at f ip b753a3a0 sp bfc08178 error 4 in sip.so[b7537000+14000]
wrc@gentoo


One drawback seems to be running this type kernel I'm missing out on all the new drm/radeon/kms update and fixes constantly coming out all the time. Or, is there a way around this?
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19, gcc-4.8.2, kernel 3.14.0-gentoo (USE=experimental)
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Wed Feb 02, 2011 9:09 pm    Post subject: Reply with quote

wrc1944 wrote:


One drawback seems to be running this type kernel I'm missing out on all the new drm/radeon/kms update and fixes constantly coming out all the time. Or, is there a way around this?


if you don't need page-flipping right now 2.6.37 still is enough

you can get most of the latest changes by

re-emerging

libdrm, mesa and xf86-video-ati

(9999 == live) ebuilds
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Thu Feb 03, 2011 1:30 am    Post subject: Reply with quote

@wrc1944:

ok, according to Dan Magenheimer, the creator of kztmem, who is very helpful, btw (thanks !)

the messages should be harmless in terms of doing bad things to your files

I also saw no BUG_ON messages in the code - so some verbose things to get to know it better :)



Guys, if you're missing support for your favorite filesystem in kztmem (e.g. XFS or reiserfs) or comments which might be useful for the continued development and improvement for kztmem,

so post it on its thread on lkml: [PATCH V1 0/3] drivers/staging: kztmem: dynamic page cache/swap

(linux kernel mailing list)


kztmem is kind of an evolution to Nitin Gupta's [PATCH 0/8] zcache: page cache compression support

which showed some really impressive benchmark results:

Quote:
* Performance numbers:
- Tested using iozone filesystem benchmark
- 4 CPUs, 1G RAM
- Read performance gain: ~2.5X
- Random read performance gain: ~3X
- In general, performance gains for every kind of I/O


so it's ideal use case would be boxes which has relatively more CPU power than RAM available (e.g. where you can't upgrade RAM but can spare some CPU performance),
e.g. mobile devices, subnotebooks, tablets, etc.


a perfect example would be a laptop where you would want to reduce harddisk-access or even send it to standby and run a swap in cache (ramzswap) - in this case kztmem would be a nice addition

a real-world example where I'm currently using ramzswap in my mobile phone: ULTIMATE SUPER OPTIMIZED Kernel


so this patch has really potential :D

gotta go to sleep now ;)
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2734
Location: Gainesville, Florida

PostPosted: Thu Feb 03, 2011 5:31 pm    Post subject: Reply with quote

Update on kernel:
FWIW, on my main Gentoo box, with this kernel I'm having problems with the xorg-server crashing and sending me immediately to the kdm login screen. It happens randomly every 10-20 minutes, and I can't really tie it to any specific action, browser, or application. 2.6.37-ck1 and 2.6.38-rc's don't do this, and can't recall any other kernel ever doing this either. It's so unpredictable that it's not really usable like it is- can't trust it not to suddenly crash X at any time, and often.

Any ideas as to what might be the problem? A specific patch in the set? It's not a hardware problem, as all other distros on this box work fine, and the same Gentoo install booted to other kernels (with KMS enabled) don't exhibit this behavior either. I'm thinking it has something to do with having to disable the KMS feature on with this kernel. Not sure if my binary distros have KMS or not- will check later.

On my other box (the one still updating to kde-4.6.0), I'm having various graphical corruption problems, and the kde compile it taking way longer than usual (like at least 50% longer). However, I'm not ready to suspect the kernel yet, as this box is way underpowered and trying to run a new larger monitor. After kde finishes up (if ever :lol: ), I'll be able to tell more about it- don't want to implicate the kernel just yet. This old athon-xp box is currently at it's full cpu limit with the kde compile, and pretty much struggling to redraw the display with any action taken with an old radeon 9000 pro 64mb card. Awaiting a new motherboard/cpu with ddr3 ram, so next week when I do the upgrade I'll test this kernel some more with a decent system.
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19, gcc-4.8.2, kernel 3.14.0-gentoo (USE=experimental)
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Thu Feb 03, 2011 6:14 pm    Post subject: Reply with quote

wrc1944 wrote:
Update on kernel:
FWIW, on my main Gentoo box, with this kernel I'm having problems with the xorg-server crashing and sending me immediately to the kdm login screen. It happens randomly every 10-20 minutes, and I can't really tie it to any specific action, browser, or application. 2.6.37-ck1 and 2.6.38-rc's don't do this, and can't recall any other kernel ever doing this either. It's so unpredictable that it's not really usable like it is- can't trust it not to suddenly crash X at any time, and often.

Any ideas as to what might be the problem? A specific patch in the set? It's not a hardware problem, as all other distros on this box work fine, and the same Gentoo install booted to other kernels (with KMS enabled) don't exhibit this behavior either. I'm thinking it has something to do with having to disable the KMS feature on with this kernel. Not sure if my binary distros have KMS or not- will check later.

On my other box (the one still updating to kde-4.6.0), I'm having various graphical corruption problems, and the kde compile it taking way longer than usual (like at least 50% longer). However, I'm not ready to suspect the kernel yet, as this box is way underpowered and trying to run a new larger monitor. After kde finishes up (if ever :lol: ), I'll be able to tell more about it- don't want to implicate the kernel just yet. This old athon-xp box is currently at it's full cpu limit with the kde compile, and pretty much struggling to redraw the display with any action taken with an old radeon 9000 pro 64mb card. Awaiting a new motherboard/cpu with ddr3 ram, so next week when I do the upgrade I'll test this kernel some more with a decent system.


it might be related to the kernel or graphics driver by itself

post the error message of /var/log/Xorg.0.log or /var/log/Xorg.0.log.old (if any)

could you be more specific ?

which hardware are you referring to when meaning "main gentoo box" or "old athlon" (e.g. graphics card, architecture [32bit/64bit], processor, opensource-driver, ...)
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 2734
Location: Gainesville, Florida

PostPosted: Thu Feb 03, 2011 6:49 pm    Post subject: Reply with quote

'Mainbox" is the one in my forum signature, and the specific gentoo install is 32bit. This is the one where x was crashing with your kernel.

The other athlon-xp box is an old testing box, 32bit, radeon 9000 pro 64mb card, which since yesterday has been updating kde (struggling) booted to your kernel.

I looked at all xorg log files, and xsession.errors files on main box, and there was nothing there related to the time when I was running your kernel on the Main box, so no clues there.

I'll know more about the other box when it's done with kde, I can reboot, and it becomes somewhat useable again. Right now all resources are exhausted and it's unresponsive.
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19, gcc-4.8.2, kernel 3.14.0-gentoo (USE=experimental)
Back to top
View user's profile Send private message
DigitalCorpus
Apprentice
Apprentice


Joined: 30 Jul 2007
Posts: 245

PostPosted: Sat Feb 05, 2011 6:49 am    Post subject: Reply with quote

kOT! remember me? Nice kernel patchset. I just wanted to chime in my two cents and say that the performance issues of disk I/O (I'm still using a mix of r4, xfs, and btrfs) that started a little in .35, got way worse in the latter portion or .36, are completely alleviated in .37. I'm back to the nostalgic high responsiveness and performance of BFS + BFQ. I know r4 isn't something you'll be using soon due to you current workloads, but if you have time to give BFS some love again, you may like it. For a make -j4 on my kernel, it's about 5% faster, but unlike CFS, I can call up disk intensive commands with minimal impact on both (such as an emerge update). Take Care!
_________________
Atlas (HDTV PVR, HTTP & Media server)
http://atlas.selfip.net/Info/
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sat Feb 05, 2011 4:42 pm    Post subject: Reply with quote

DigitalCorpus wrote:
kOT! remember me? Nice kernel patchset. I just wanted to chime in my two cents and say that the performance issues of disk I/O (I'm still using a mix of r4, xfs, and btrfs) that started a little in .35, got way worse in the latter portion or .36, are completely alleviated in .37. I'm back to the nostalgic high responsiveness and performance of BFS + BFQ. I know r4 isn't something you'll be using soon due to you current workloads, but if you have time to give BFS some love again, you may like it. For a make -j4 on my kernel, it's about 5% faster, but unlike CFS, I can call up disk intensive commands with minimal impact on both (such as an emerge update). Take Care!


Hi DigitalCorpus,

of course I remember you - you're THE Reiser4 expert ! Of course after me (just joking :P )

glad to see you again, buddy

ok, think I'll give (at least) BFQ a try and (if it works) BFS also
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sat Feb 05, 2011 4:44 pm    Post subject: Reply with quote

Everyone's advised to update to v14

* either for feature-related reasons (BFQ, Reiser4)
* or data-safety and stability- and performance-related (with ext4) [to be able to activate multiple page-io submission again - ENABLE AT YOUR OWN RISK via mblk_io_submit mount-option (will be activated by default >2.6.39 in upstream, again]

Update3:
Quote:
changes (for v13 -> v14):
14 Stochastic Fair Blue (SFB) network scheduler. -> 2 "Remove stub tcf function from sfb"

Reverted: 2.6.37_20_5_directed-yield_v7

20 2.6.38_patches/7 CFS -> 10_new_additional fixes (rc3+) ->
1 [tip:sched_core] sched: Limit the scope of clear_buddies
2 [tip:sched_core] sched: Use a buddy to implement yield_task_fair()
3 [tip:sched_core] sched: Add yield_to(task, preempt) functionality
4 [tip:sched_urgent] sched: Fix update_curr_rt()
5 [PATCH v2] cgroup_freezer: add per freezer duty ratio control
6 [tip:sched_urgent] sched, docs: Update schedstats documentation to version 15

Reverted: 23 post-2.6.37-fixes/4 ext4 -> 10_Fix invalid free of cache->name after ext4_mb_init() error
23 post-2.6.37-fixes/4 ext4 -> 11_new_
1 [PATCH] ext4: fix panic on module unload when stopping lazyinit thread
2 [PATCH] ext4: fix up ext4 error handling
3 ext4: Fix data corruption with multi-block writepages support [ now multiple page-io submission[b] (mblk_io_submit) should be save to activate again]
4 [PATCH] ext4: make grpinfo slab cache names static

27 even more fixes -> 6_new_ksoftirqd -> [PATCH] softirq: Avoid stack switch from ksoftirqd
27 even more fixes -> 7 x86, mtrr -> [tip:x86_urgent] x86, mtrr: Avoid MTRR reprogramming on BP during boot on UP platforms

added reiser4
added slqb (from git.zen-kernel.org repository)
added BFQ (from git.zen-kernel.org repository)



_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
tranquilcool
Veteran
Veteran


Joined: 25 Mar 2005
Posts: 1044

PostPosted: Sat Feb 05, 2011 10:58 pm    Post subject: Reply with quote

kernelOfTruth wrote:
Everyone's advised to update to v14

* either for feature-related reasons (BFQ, Reiser4)
* or data-safety and stability- and performance-related (with ext4) [to be able to activate multiple page-io submission again - ENABLE AT YOUR OWN RISK via mblk_io_submit mount-option (will be activated by default >2.6.39 in upstream, again]

Update3:
Quote:
changes (for v13 -> v14):
14 Stochastic Fair Blue (SFB) network scheduler. -> 2 "Remove stub tcf function from sfb"

Reverted: 2.6.37_20_5_directed-yield_v7

20 2.6.38_patches/7 CFS -> 10_new_additional fixes (rc3+) ->
1 [tip:sched_core] sched: Limit the scope of clear_buddies
2 [tip:sched_core] sched: Use a buddy to implement yield_task_fair()
3 [tip:sched_core] sched: Add yield_to(task, preempt) functionality
4 [tip:sched_urgent] sched: Fix update_curr_rt()
5 [PATCH v2] cgroup_freezer: add per freezer duty ratio control
6 [tip:sched_urgent] sched, docs: Update schedstats documentation to version 15

Reverted: 23 post-2.6.37-fixes/4 ext4 -> 10_Fix invalid free of cache->name after ext4_mb_init() error
23 post-2.6.37-fixes/4 ext4 -> 11_new_
1 [PATCH] ext4: fix panic on module unload when stopping lazyinit thread
2 [PATCH] ext4: fix up ext4 error handling
3 ext4: Fix data corruption with multi-block writepages support [ now multiple page-io submission[b] (mblk_io_submit) should be save to activate again]
4 [PATCH] ext4: make grpinfo slab cache names static

27 even more fixes -> 6_new_ksoftirqd -> [PATCH] softirq: Avoid stack switch from ksoftirqd
27 even more fixes -> 7 x86, mtrr -> [tip:x86_urgent] x86, mtrr: Avoid MTRR reprogramming on BP during boot on UP platforms

added reiser4
added slqb (from git.zen-kernel.org repository)
added BFQ (from git.zen-kernel.org repository)

no BFS? just curious as to why.



_________________
this is a strange strange world.
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sun Feb 06, 2011 12:47 am    Post subject: Reply with quote

tranquilcool wrote:


no BFS? just curious as to why.




the changes from 2.6.38 made it too complicated to get it working with the current kernel


I'm very busy so trying to get it to work with those changes isn't an option for me


I originally had planned to make it available, too, but there were several problems right from the start during attempted compiling


so to get it working I would have had to revert all (probably not all - but most) CFS changes
_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5610
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sun Feb 06, 2011 2:19 am    Post subject: Reply with quote

Quote:
Update4:

2.6.37_plus_v14_zram-data-corruption_fix.patch (1.13 KB)
pastebin.com (mirror)

fa4b7b6c43473e6a9f7c87e4a913c5b9 2.6.37_plus_v14_zram-data-corruption_fix.patch

this fixes a data corruption issue with zram
if you're using kztmem and NOT zram - NO data corruption has occured for you
kztmem only needs zram enabled due to its usage of xvmalloc

_________________
Unofficial minimal livecd x86/amd64 w/reiser4+truecrypt (by Neo2)
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6  Next
Page 2 of 6

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum