The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

Lockheed · 2012-07-20 13:17:59

Strange problem with the wifi network card, I have.

After I boot, the network card is being disabled about 1-2 minutes after the system starts, even when it is connected.
This issue exists only on linux-pf kernel. When I boot from regular arch kernel, it does not do it.

I used to have a script that would disable WiFi if it was not connected. But I have since removed it. Besides, it was not kernel-specific.

kokoko3k · 2012-07-20 15:03:11

nous wrote:

kokoko3k wrote:
Ops, you're right, i don't know why, but last time it worked.
...Any clue on why TOI crashes the kernel as soon as it tries to write the image to the disk on an nvidia system?
Works good on an intel one and i've already tried the procsettings suggestions from the wiki specific to nvidia.
No clue, it works fine on 2 nvidia boxen I own. I could email you my /etc/hibernate dir if you'd like.

Thanks!

kokoko3k
at
gmail
dot
com

Lockheed · 2012-07-20 16:18:41

I am having an issue trying to hibernate my laptop with TuxOnIce. I've done everything there was in the wiki, but I still get this:

$ sudo hibernate -F /etc/hibernate/tuxonice.conf
hibernate: TuxOnIce reported the following errors:
 - TuxOnIce was aborted (see dmesg).
 - Unknown error! (see dmesg?)

And dmesg shows no errors at all. And I am getting this during boot: I am getting this during boot:

TuxOnIce: No storage allocators have been registered. Hibernating will be disabled.

Lockheed · 2012-07-23 12:26:41

I cannot build vmware modules with pf kernel since 3.4 came live. Here's the error:

make[1]: Leaving directory `/usr/src/linux-3.4-pf'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.4-pf/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.4-pf'
  CC [M]  /tmp/vmware-root/modules/vmnet-only/hub.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/driver.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/userif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/netif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/filter.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
/tmp/vmware-root/modules/vmnet-only/filter.c:60:16: error: ‘THIS_MODULE’ undeclared here (not in a function)
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/filter.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/tmp/vmware-root/modules/vmnet-only/netif.c: In function ‘VNetNetIfSetup’:
/tmp/vmware-root/modules/vmnet-only/netif.c:134:7: error: unknown field ‘ndo_set_multicast_list’ specified in initializer
/tmp/vmware-root/modules/vmnet-only/netif.c:134:7: warning: initialization from incompatible pointer type [enabled by default]
/tmp/vmware-root/modules/vmnet-only/netif.c:134:7: warning: (near initialization for ‘vnetNetifOps.ndo_validate_addr’) [enabled by default]
/tmp/vmware-root/modules/vmnet-only/userif.c: In function ‘VNetCsumCopyDatagram’:
/tmp/vmware-root/modules/vmnet-only/userif.c:520:3: error: incompatible type for argument 1 of ‘kmap’
In file included from /tmp/vmware-root/modules/vmnet-only/userif.c:26:0:
include/linux/highmem.h:49:21: note: expected ‘struct page *’ but argument is of type ‘const struct <anonymous>’
/tmp/vmware-root/modules/vmnet-only/userif.c:523:3: error: incompatible type for argument 1 of ‘kunmap’
In file included from /tmp/vmware-root/modules/vmnet-only/userif.c:26:0:
include/linux/highmem.h:55:20: note: expected ‘struct page *’ but argument is of type ‘const struct <anonymous>’
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/netif.o] Error 1
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/userif.o] Error 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/linux-3.4-pf'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Unable to install vmnet

kokoko3k · 2012-07-23 14:55:37

Sorry to bump this, but to me strace is still broken:

slimer gopreload # strace -f -F -e trace=open,access ls
strace: Bad OS release string: '3.4-pf'
slimer gopreload # uname -a
Linux slimer 3.4-pf #1 SMP PREEMPT Mon Jul 23 13:51:54 CEST 2012 i686 GNU/Linux
slimer gopreload # pacman -Q |grep linux\-pf
linux-pf-core2 3.4.5-1
linux-pf-headers-core2 3.4.5-1

nous · 2012-07-23 19:06:39

Lockheed wrote:

I cannot build vmware modules with pf kernel since 3.4 came live. Here's the error:

I use virtualbox-bin from the AUR and compile with 'dkms autoinstall'.

nous · 2012-07-23 19:07:46

kokoko3k wrote:

Sorry to bump this, but to me strace is still broken:

slimer gopreload # strace -f -F -e trace=open,access ls
strace: Bad OS release string: '3.4-pf'
slimer gopreload # uname -a
Linux slimer 3.4-pf #1 SMP PREEMPT Mon Jul 23 13:51:54 CEST 2012 i686 GNU/Linux
slimer gopreload # pacman -Q |grep linux\-pf
linux-pf-core2 3.4.5-1
linux-pf-headers-core2 3.4.5-1

Use strace-patched.

Lockheed · 2012-07-23 19:19:01

nous wrote:

Lockheed wrote:
I cannot build vmware modules with pf kernel since 3.4 came live. Here's the error:
I use virtualbox-bin from the AUR and compile with 'dkms autoinstall'.

How will virtualbox-bin help me with vmware? I already have vmbox up and running. I need vmware, too.

nous · 2012-07-23 20:58:42

Lockheed wrote:

nous wrote:
Lockheed wrote:
I cannot build vmware modules with pf kernel since 3.4 came live. Here's the error:
I use virtualbox-bin from the AUR and compile with 'dkms autoinstall'.
How will virtualbox-bin help me with vmware? I already have vmbox up and running. I need vmware, too.

I'm sorry, I misread.

The Compiler · 2012-08-12 11:29:39

Can't compile the latest version:

[...]
  CC      drivers/staging/zcache/zcache-main.o
In file included from include/linux/fcntl.h:4:0,
                 from include/linux/fs.h:1216,
                 from include/linux/highmem.h:4,
                 from drivers/staging/zcache/zcache-main.c:25:
/tmp/yaourt-tmp-florian/aur-linux-pf/src/linux-3.5/arch/x86/include/asm/fcntl.h:1:31: fatal error: asm-generic/fcntl.h: No such file or directory
compilation terminated.
make[3]: *** [drivers/staging/zcache/zcache-main.o] Error 1
make[2]: *** [drivers/staging/zcache] Error 2
make[1]: *** [drivers/staging] Error 2
make: *** [drivers] Error 2

Anyone has an idea what could be going wrong?

nous · 2012-08-15 11:28:50

The Compiler wrote:

Can't compile the latest version:

[...]
  CC      drivers/staging/zcache/zcache-main.o
In file included from include/linux/fcntl.h:4:0,
                 from include/linux/fs.h:1216,
                 from include/linux/highmem.h:4,
                 from drivers/staging/zcache/zcache-main.c:25:
/tmp/yaourt-tmp-florian/aur-linux-pf/src/linux-3.5/arch/x86/include/asm/fcntl.h:1:31: fatal error: asm-generic/fcntl.h: No such file or directory
compilation terminated.
make[3]: *** [drivers/staging/zcache/zcache-main.o] Error 1
make[2]: *** [drivers/staging/zcache] Error 2
make[1]: *** [drivers/staging] Error 2
make: *** [drivers] Error 2

Anyone has an idea what could be going wrong?

Does the same happen when compiling outside yaourt?

Lockheed · 2012-08-15 12:15:44

Since one year, I have been trying to make TOI work on linux-pf kernel, and still nothing. This is the most recent error:

TuxOnIce: No extra_pages_allowance entry available. Not setting.
TuxOnIce: No no_multithreaded_io entry available. Not setting.
Your kernel does not appear to have TuxOnIce support compiled in.
Please follow the HOWTO linked from http://www.tuxonice.net/ for instructions
on how to compile TuxOnIce into your kernel.
hibernate: Aborting.

Last edited by Lockheed (2012-08-15 12:16:14)

Lockheed · 2012-08-15 16:20:14

Also, I am getting this upon boot:

ERROR: tux-on-ice syntax detected but no support found.

Lockheed · 2012-08-16 19:39:21

Was TOI support removed form linux-pf?

jakob · 2012-08-16 19:56:14

Lockheed wrote:

Was TOI support removed form linux-pf?

at least on version 3.5.1-1 from [pfkernel] it isn't, I use it all the time…

Lockheed · 2012-08-17 22:33:55

It would be really nice of one of the -pf developpers could comment on my issues, because I don't know if I did something wrong (I can't see why, as I did noting different) or was the support for TOI dropped from the kernel. Or what?

nous · 2012-08-18 12:42:56

Lockheed wrote:

It would be really nice of one of the -pf developpers could comment on my issues, because I don't know if I did something wrong (I can't see why, as I did noting different) or was the support for TOI dropped from the kernel. Or what?

Hey, this is a free time project, remember? If you compile your kernel it's all your fault; stick with the provided binaries.

Lockheed · 2012-08-18 12:50:00

nous wrote:

Lockheed wrote:
It would be really nice of one of the -pf developpers could comment on my issues, because I don't know if I did something wrong (I can't see why, as I did noting different) or was the support for TOI dropped from the kernel. Or what?
Hey, this is a free time project, remember? If you compile your kernel it's all your fault; stick with the provided binaries.

Turned out that TOI has been disabled by the default config in newest pf kernel. Strange thing to make, but whatever. After enabling it, it works again.

jakob · 2012-08-18 12:53:23

Lockheed wrote:

Turned out that TOI has been disabled by the default config in newest pf kernel. Strange thing to make, but whatever. After enabling it, it works again.

I don't see what you mean, "zcat /proc/config.gz | grep" TOI yields:

CONFIG_TOI_CORE=m
CONFIG_TOI_FILE=m
CONFIG_TOI_SWAP=m
CONFIG_TOI_CRYPTO=m
CONFIG_TOI_USERUI=m
CONFIG_TOI_USERUI_DEFAULT_PATH="/usr/sbin/tuxoniceui"
CONFIG_TOI_DEFAULT_IMAGE_SIZE_LIMIT=-2
# CONFIG_TOI_KEEP_IMAGE is not set
CONFIG_TOI_REPLACE_SWSUSP=y
# CONFIG_TOI_IGNORE_LATE_INITCALL is not set
CONFIG_TOI_DEFAULT_WAIT=25
CONFIG_TOI_DEFAULT_EXTRA_PAGES_ALLOWANCE=7000
# CONFIG_TOI_CHECKSUM is not set
CONFIG_TOI=y
CONFIG_TOI_EXPORTS=y
CONFIG_TOI_ZRAM_SUPPORT=y
CONFIG_TOIM3232_DONGLE=m

(linux-pf-core2-3.5.1-1)

So, TOI is there as a module as usual, and you have to configure it yourself…

Last edited by jakob (2012-08-18 12:54:46)

Lockheed · 2012-08-18 12:54:49

It was disabled in the package I pulled from AUR. Anyway, no matter.

Is there any advantage of compiling is as a module over compiling it as a integral part of kernel?

martadinata · 2012-08-20 03:11:26

how to use this aufs3

Edit : sorry my fault, didn't compile using aufs download from repo fine...

Last edited by martadinata (2012-08-20 07:10:36)

post-factum · 2012-08-23 20:14:43

nous, I couldn't get pf-kernel from binary dropbox repo boot on second laptop. Using LVM2 and dm-crypt there. Have you compiled kernel w/o crypt support? Why?

Last edited by post-factum (2012-08-23 20:15:04)

nous · 2012-08-24 05:42:03

post-factum wrote:

nous, I couldn't get pf-kernel from binary dropbox repo boot on second laptop. Using LVM2 and dm-crypt there. Have you compiled kernel w/o crypt support? Why?

I always use the stock -ARCH config and only modify the options related to your patchset. From what I see, crypt target support (dm-crypt) is there. But I remember I saw a thread on arch-dev-public about systemd and encrypted LVM not getting along and another one about broken encrypted LVM with 3.5.2. Right now, only the initial thread message appears on the mailing list archive, so I'm pasting below:

Geert Hendrickx <geert@hendrickx.be> via archlinux.us   19:29 (13 hours ago)		
                                     to General 

On Thu, Aug 23, 2012 at 16:10:26 +0200, Tobias Powalowski wrote:
 > Hi guys,
 > 3.5.x is not yet ready to move to [core],
 > - ext4 regression is not fixed yet, will be fixed in 3.5.3
 > - watchdogs are completely broken
 >   I'm not sure how much of a showstopper the watchdogs are, so please
 >   shout out if this is a real problem.
 > If you have any other showstopper please let me know.

Since upgrading to 3.5.x, my system with mdraid mirror boots with either
 a degraded RAID array, or not auto-discovering the RAID at all.

 The disks are fine, confirmed by both SMART selftest and badblocks scan.
 Downgraded back to 3.4.9 and the problem went away.

 Anyone else experienced this?  My setup should be common, with /boot on
 /dev/md0 over sda1+sdb1, and the rest on LVM on /dev/md1 over sda2+sdb2.

% zcat /proc/config.gz |grep -i dm_crypt
CONFIG_DM_CRYPT=m
% pacman -Qo /boot/vmlinuz-linux-pf 
/boot/vmlinuz-linux-pf is owned by linux-pf-core2 3.5.2-4

Lockheed · 2012-08-25 14:19:28

I am currently running a kernel with BFS/BFQ and I'm wondering if running IRQBalance also is redundant, or if BFQ does not handle IRQ balancing.

Would it be wise to run both at the same time?

nous · 2012-08-25 15:16:45

Lockheed wrote:

I am currently running a kernel with BFS/BFQ and I'm wondering if running IRQBalance also is redundant, or if BFQ does not handle IRQ balancing.
Would it be wise to run both at the same time?

I don't see them related in any way, but I might be wrong.

Arch Linux

#551 2012-07-20 13:17:59

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#552 2012-07-20 15:03:11

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#553 2012-07-20 16:18:41

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#554 2012-07-23 12:26:41

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#555 2012-07-23 14:55:37

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#556 2012-07-23 19:06:39

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#557 2012-07-23 19:07:46

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#558 2012-07-23 19:19:01

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#559 2012-07-23 20:58:42

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#560 2012-08-12 11:29:39

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#561 2012-08-15 11:28:50

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#562 2012-08-15 12:15:44

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#563 2012-08-15 16:20:14

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#564 2012-08-16 19:39:21

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#565 2012-08-16 19:56:14

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#566 2012-08-17 22:33:55

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#567 2012-08-18 12:42:56

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#568 2012-08-18 12:50:00

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#569 2012-08-18 12:53:23

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#570 2012-08-18 12:54:49

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#571 2012-08-20 03:11:26

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#572 2012-08-23 20:14:43

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#573 2012-08-24 05:42:03

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#574 2012-08-25 14:19:28

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

#575 2012-08-25 15:16:45

Re: The linux-pf thread; BFS/CK, TuxOnIce, BFQ, AUFS3

Board footer