2.6.13-rc3-mm3 acpi compile problems
Hello, i get this warnings when compiling: CC drivers/acpi/utilities/utalloc.o drivers/acpi/utilities/utalloc.c: In function `acpi_ut_create_caches': drivers/acpi/utilities/utalloc.c:107: warning: passing arg 3 of `acpi_ut_create_list' from incompatible pointer type drivers/acpi/utilities/utalloc.c:113: warning: passing arg 3 of `acpi_ut_create_list' from incompatible pointer type drivers/acpi/utilities/utalloc.c: In function `acpi_ut_allocate': drivers/acpi/utilities/utalloc.c:324: warning: passing arg 2 of `acpi_ut_trace_u32' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:342: warning: passing arg 2 of `acpi_ut_ptr_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:345: warning: passing arg 2 of `acpi_ut_ptr_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c: In function `acpi_ut_callocate': drivers/acpi/utilities/utalloc.c:374: warning: passing arg 2 of `acpi_ut_trace_u32' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:382: warning: passing arg 2 of `acpi_ut_ptr_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:391: warning: passing arg 2 of `acpi_ut_ptr_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:397: warning: passing arg 2 of `acpi_ut_ptr_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c: In function `acpi_ut_free_and_track': drivers/acpi/utilities/utalloc.c:573: warning: passing arg 2 of `acpi_ut_trace_ptr' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:580: warning: passing arg 2 of `acpi_ut_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:592: warning: passing arg 3 of `acpi_ut_debug_print' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:598: warning: passing arg 3 of `acpi_ut_debug_print' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:600: warning: passing arg 2 of `acpi_ut_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c: In function `acpi_ut_track_allocation': drivers/acpi/utilities/utalloc.c:673: warning: passing arg 2 of `acpi_ut_trace_ptr' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:679: warning: passing arg 2 of `acpi_ut_status_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:692: warning: passing arg 3 of `acpi_ut_debug_print' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:722: warning: passing arg 2 of `acpi_ut_status_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c: In function `acpi_ut_remove_allocation': drivers/acpi/utilities/utalloc.c:752: warning: passing arg 2 of `acpi_ut_trace' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:762: warning: passing arg 2 of `acpi_ut_status_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:767: warning: passing arg 2 of `acpi_ut_status_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:787: warning: passing arg 3 of `acpi_ut_debug_print' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:791: warning: passing arg 2 of `acpi_ut_status_exit' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c: In function `acpi_ut_dump_allocations': drivers/acpi/utilities/utalloc.c:880: warning: passing arg 2 of `acpi_ut_trace' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:937: warning: passing arg 3 of `acpi_ut_debug_print' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:941: warning: passing arg 3 of `acpi_ut_debug_print' discards qualifiers from pointer target type drivers/acpi/utilities/utalloc.c:946: warning: passing arg 2 of `acpi_ut_exit' discards qualifiers from pointer target type CC drivers/acpi/utilities/utdebug.o make[3]: *** Deleting file `drivers/acpi/utilities/utdebug.o' make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. make[2]: *** wait: No child processes. Stop. make[2]: *** Waiting for unfinished jobs make[2]: *** wait: No child processes. Stop. make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make: *** [drivers] Error 2 Kind regards Flo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: system freezes for 0.2 to 0.5 seconds when reading /proc/acpi/thermal_zone/THRM/temperature
Hello, On Wed, 27 Jul 2005 16:16:05 -0700 Andrew Morton <[EMAIL PROTECTED]> wrote: > Florian Engelhardt <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > first of all, sorry for the long headline. > > second: > > Every time, i try to do the following: > > cat /proc/acpi/thermal_zone/THRM/temperature > > the whole system looks up for a short period of time (something > > about 0.5s). realy everything, video and audio encoding, mouse and > > keyboard input, firefox playing a flash animation, ... > > I am also getting the following: > > Losing some ticks... checking if CPU frequency changed. > > > > maybe these two things are belonging to each other. > > > > I am using a 2.6.12-rc3-mm1 kernel on a amd64 with a nvidia nforce4 > > mainboard. > > It might help if you were to generate a kernel profile: > > readprofile -r returns: /proc/profile: No such file or directory do i have to activate something special during kernel configuration? btw: i saw that mm2 is available. Are there any changes in it, which could solve this problem? flo > for i in $(seq 10) > do > cat /proc/acpi/thermal_zone/THRM/temperature > done > readprofile -n -v -m /boot/System.map | sort -n +2 | tail -40 > > -- "I may have invented it, but Bill made it famous" David Bradley, who invented the (in)famous ctrl-alt-del key combination - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
system freezes for 0.2 to 0.5 seconds when reading /proc/acpi/thermal_zone/THRM/temperature
Hello, first of all, sorry for the long headline. second: Every time, i try to do the following: cat /proc/acpi/thermal_zone/THRM/temperature the whole system looks up for a short period of time (something about 0.5s). realy everything, video and audio encoding, mouse and keyboard input, firefox playing a flash animation, ... I am also getting the following: Losing some ticks... checking if CPU frequency changed. maybe these two things are belonging to each other. I am using a 2.6.12-rc3-mm1 kernel on a amd64 with a nvidia nforce4 mainboard. kind regards flo -- "I may have invented it, but Bill made it famous" David Bradley, who invented the (in)famous ctrl-alt-del key combination - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
powersave not working with amd64 on nforce 4 board
Hello, powersaving is not working with a 2.6.12-rc3-mm1 kernel and a amd64 3500+ on a nvidia nforce 4 mainboard. syslog tells me the following about it: ... ACPI: Processor [CPU0] (supports 8 throttling states) ... powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.40.2) acpi_processor-0252 [04] acpi_processor_get_per: Error evaluating _PSS powernow-k8: BIOS error - no PSB or ACPI _PSS objects acpi_processor-0252 [04] acpi_processor_get_per: Error evaluating _PSS kind regards flo -- "I may have invented it, but Bill made it famous" David Bradley, who invented the (in)famous ctrl-alt-del key combination - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: freezes with reiser4 in a raid1 with 2.6.11-rc5-mm1
Hello, On Wed, 02 Mar 2005 14:38:59 +0400 Brad Campbell <[EMAIL PROTECTED]> wrote: > Florian Engelhardt wrote: > > > > I activated the raid (/dev/md0), then mounted it, and after > > that i was starting nfs. I was able to mount the share > > on my desktop, creating direcrotys was no problem, but > > as soon as i was copying a file to the share, the server > > freezed. > > Creating files localy (while loged in via ssh) is leading > > to the process is staying in state D. > > Sometimes, when i start nfsd, the system reboots immediately, > > sometimes not. > > At the momment, most of the processes are in state D, reboot > > does not work, and i am not at home, so i am unable to reboot > > the machine manualy. > > Neat trick which I only discovered in desparation last week when > battling a RAID lockup on the -rc4-mm1 kernel on a remote box. > > I was also having hard lockup issues, but reseating all my PCI cards > appear to have rectified that one. Well, there are not much PCI-Cards in this server and reseating them didnt fix it. > As root. echo b > /proc/sysrq-trigger > > Of course only if you have alt-sysrq built in. Thanks for that, i was able to reboot the machine with that trick, but i couldnt find anything bad in the messages file. I made some further tests with the server: Deactivating the raid, and formating the hd´s (hdc and hdd) with reiser4, mounting them and sharing them via nfs and ftp worked great, no freezes, no reboots, everything perfect, even the performance. But as soon, as i activated the raid, the server freezed, or rebooted. Maybe this problem is not a bug in a single component (eg: nfs or reiser4), i think it is the combination of linux raid with reiser4, but i dont know. I will try to get the raid up and running with ext3 and/or jfs. Then we know exactly, if it is the combination of raid and reiser4. Kind regards Florian Engelhardt -- "I may have invented it, but Bill made it famous" David Bradley, who invented the (in)famous ctrl-alt-del key combination - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
freezes with reiser4 in a raid1 with 2.6.11-rc5-mm1
Hello, i´m having some trouble here with my testing server. It uses the 2.6.11-rc5-mm1 kernel, there are three hd´s in it (all reiser4), hda is the system and boot disk, hdc and hdd are in a raid 1 (via the kernel´s multiple device driver). Without the raid, the system works as expected, but when activating the raid, the system wents unstable and in some cases it freezes or reboots. I activated the raid (/dev/md0), then mounted it, and after that i was starting nfs. I was able to mount the share on my desktop, creating direcrotys was no problem, but as soon as i was copying a file to the share, the server freezed. Creating files localy (while loged in via ssh) is leading to the process is staying in state D. Sometimes, when i start nfsd, the system reboots immediately, sometimes not. At the momment, most of the processes are in state D, reboot does not work, and i am not at home, so i am unable to reboot the machine manualy. Every process that trys to do any IO operations on the raid remains now in state D. Are there any Problems known with reiser4, linux raid and nfs? Kind Regards Florian Engelhardt PS: I am not on the list, so please CC me - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
