Large numbers of "bioset" processes in recent kernels

Message

OscarTalks · #1 Post by **OscarTalks** » Wed 13 Sep 2017, 10:25

Is anyone else finding that they have lots of these bioset kernel processes showing up?
This apparently only applies to kernel 4.4.x and later.
If you are running one of these, could you have a look in Pprocess?

CPU and RAM all seems OK and everything runs well, but I was wondering what causes this. Is it a normal feature or something which needs changing in the kernel configuration?

I normally run Puppies with older kernels but recently compiled 4.4.87 for use in my StretchPup testing and noticed this was happening. I also did a kernel swap to 4.4.x in 32bit Slacko-6.9.9.9 and same thing. There are some similar reports on the net, no-one seemed too concerned but I didn't see an explanation that I could understand.

#2 Post by **Flash** » Wed 13 Sep 2017, 12:16

Bioset only shows up one time in Pprocess in Quirky Werewolf 64 bit. That's kernel 4.2.6.

I googled bioset and found this:

Seems like a kernel working thread involved in block I/O. See:
https://answers.launchpad.net/ubuntu/+question/272922

I don't think there is any issue. It takes no CPU when it is not in use.

If your system uses a block data device (a solid state hard drive?) I suppose bioset would be used a lot.

peebee · #3 Post by **peebee** » Wed 13 Sep 2017, 12:28

No bioset's at all here that I can see - Kernel 4.13.1-lxpup64 in LxPupSc-17.09.22T......

OscarTalks · #4 Post by **OscarTalks** » Fri 15 Sep 2017, 22:02

Thanks for the responses so far.
I tried the kernel 4.9.13 from the Puppy repos in Slacko 6.9.9.9 and it also showed lots of [bioset] processes.
Continuing to test, I compiled 4.13.2 which is latest stable kernel and that one shows no biosets at all.
Not sure what to think about it.
Need to test if ndiswrapper will compile in 4.13 because I want to include it.
Change log says it supports up to 4.8
Might stick with 4.4.87 for now and see what happens with LTS at 4.13. or higher.

belham2 · #5 Post by **belham2** » Fri 15 Sep 2017, 22:34

Hi Oscar and all,

Here's Barry's EasyLinux4.0 with kernel 4.11.12. Bioset processes all over the place (my hard drive is an USB-attached Pata 133 IDE).

On this hard drive, I've got many different pups and my own woof-CE builds (using lots of different kernels) 'frugally' installed, from Xenails to tahrs to slackos to you name it, there's a good chance I have it in a 'frugal' folder. My grub4dos is so long it is pathetic.

But this past week I've been playing with Barry's Containers (in Easy4.0) trying to get my head around them. Anyhow, I'll have a look tomorrow at my recent xenial/tahrs/slacko woof-CE builds and see what they show with regards to biosets.

8Geee · #6 Post by **8Geee** » Fri 15 Sep 2017, 22:47

Block I/O not restricted to 512K page size. I presume this is needed for large file manipulations within the OS. I also see a need(?) for encryption, or the ability to encrypt such movements and/or such files.

BIO is the framework and seems to have appeared in my spins with migration to openssl1.0.2, the kernel (k3.4.82) is too old to have this natively (apparantly 4.4 +).

Regards
8Geee

Marv · #7 Post by **Marv** » Fri 15 Sep 2017, 22:59

No Biosets at all seen here in LxPup-Sc 17.09.21 - Linux 4.13.0-lxpup64 x86_64 running Grub4Dos frugal on a smallish SATA attached SSD.

LazY Puppy · #8 Post by **LazY Puppy** » Fri 15 Sep 2017, 23:32

Got two of them running in Tahr 6.0.2.

Limbomusic · #9 Post by **Limbomusic** » Sat 16 Sep 2017, 00:50

Same here Oscar. On 2 machines. Lots of -bioset processes- like 15 or something.
Old machine running tahr_6.0.6 - kernel 4.9.13
Newish laptop with ssd running tahr64_6.0.6 - kernel 4.9.30

belham2 · #10 Post by **belham2** » Sat 16 Sep 2017, 10:17

Hi Oscar and all,

Here's some pups from my stable, going in ascending order from kernel 2.6.### to peebee's latest 4.13.2.

Notice where this bioset thing started to show in the kernels as they progress:

belham2 · #11 Post by **belham2** » Sat 16 Sep 2017, 10:19

....continuing my post above due to forum rules about max 10 attachments per post......

LateAdopter · #12 Post by **LateAdopter** » Sat 16 Sep 2017, 21:20

OscarTalks wrote:Thanks for the responses so far.
I tried the kernel 4.9.13 from the Puppy repos in Slacko 6.9.9.9 and it also showed lots of [bioset] processes.
Continuing to test, I compiled 4.13.2 which is latest stable kernel and that one shows no biosets at all.
Not sure what to think about it.
Need to test if ndiswrapper will compile in 4.13 because I want to include it.
Change log says it supports up to 4.8
Might stick with 4.4.87 for now and see what happens with LTS at 4.13. or higher.

I have noticed that with kernel 4.13 /proc/cpuinfo is not working and there are no biosets. The explanation for /proc/cpuinfo is here: https://www.phoronix.com/scan.php?page= ... Management
I guess there may be a connection...
Kernel 4.12.9 /proc/cpuinfo is working and there are lots of biosets.

Limbomusic · #13 Post by **Limbomusic** » Fri 10 Nov 2017, 20:14

Hey Oscar

Would love an update on this - have u found out anything about these bio-processes? Are new kernels free of this - WAS it a problem?

Anyway. Hugs and kisses

OscarTalks · #14 Post by **OscarTalks** » Sat 11 Nov 2017, 01:30

I have not found an explanation for this, unless as earlier posts suggest it may be connected with the CPU info thing and they have decided to change something in 4.13 kernel because of this.

What I can tell you is that I am using 4.13.2 in my experimental Stretch remaster. This means that cpu frequency scaling does not work but I don't normally use that anyway and everything else seems fine. I believe it may be possible to fix the frequency scaling tool in Puppy to work with these kernels, but I need to look into the details of that when I get chance.

The kernels with lots of biosets seem to work fine for me, but a few people did report that things were running more slowly. If anyone has any further ideas I would be happy to hear them.

Limbomusic · #15 Post by **Limbomusic** » Sat 11 Nov 2017, 03:23

please know that your efforts are appreciated.

Only thing I have noticed is that browsers - especially chrome . just shuts down - if the page becomes too "heavy" - then u just get the "something happenden.. whatever dialog" - then I use opera - and that seems to work better.
tahrpup64

Marv · #16 Post by **Marv** » Sat 11 Nov 2017, 14:23

OscarTalks wrote: What I can tell you is that I am using 4.13.2 in my experimental Stretch remaster. This means that cpu frequency scaling does not work but I don't normally use that anyway and everything else seems fine. I believe it may be possible to fix the frequency scaling tool in Puppy to work with these kernels, but I need to look into the details of that when I get chance.

wcpufreq does set governors correctly (with the usual caveat about intel hardware and the intel_pstate governor) in the post 4.13 kernels, it is the frequency reporting that is goofed up. radky has fixed the issue in Pup-Sysinfo and there is a patched wcpufreq dealing with both those issues for testing and some discussion here: http://www.murga-linux.com/puppy/viewto ... 129#968664. Inxi and hardinfo do not report correctly at this time.

Update on 11/14/2017: The 4.14 kernel (for now

) has gone back to writing current processor speed to /proc/cpuinfo so frequency reporting should be ok again with Inxi and hardinfo. Both the old and modified wcpufreqs and radkys Pup-Sysinfo should be ok also.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Large numbers of "bioset" processes in recent kernels

Large numbers of "bioset" processes in recent kernels

me

continued post above due to forum max attch rules

hey

your