Hi

I was having huge problems with PHYO using 100%CPU when I had Ubuntu 10 loaded, now I have down graded back to 9.10. the problem was rectified, but it has returned, never had this problem before with earlier versions.

Even when the pc is idle phyo is using all of the cpu at 100%, not as damaging as the last version of ubuntu but still occurs.

A display from terminal with the problem using all cpu resources when hardly anything is running.

top - 09:02:20 up 29 min, 2 users, load average: 0.41, 0.48, 0.38
Tasks: 138 total, 2 running, 136 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.3%us, 80.7%sy, 0.0%ni, 18.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 2061508k total, 518880k used, 1542628k free, 49328k buffers
Swap: 3229024k total, 0k used, 3229024k free, 242520k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1049 root 15 -5 0 0 0 R 80.2 0.0 1:35.13 phy0
2001 sgu 20 0 199m 50m 22m S 0.7 2.5 0:24.42 firefox
1261 root 20 0 630m 25m 7664 S 0.3 1.3 0:52.63 Xorg
2045 sgu 20 0 2472 1172 880 R 0.3 0.1 0:00.14 top
1 root 20 0 2636 1548 1144 S 0.0 0.1 0:01.10 init
2 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/0
4 root 15 -5 0 0 0 S 0.0 0.0 0:00.06 ksoftirqd/0
5 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
6 root 15 -5 0 0 0 S 0.0 0.0 0:00.06 events/0
7 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 cpuset
8 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 khelper
9 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 netns
10 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 async/mgr
11 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kintegrityd/0
12 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kblockd/0
13 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kacpid


Thanks EAI

What is PHYO?

0 members found this post helpful.

PHO I do not know, just appears for no reason on terminal taking 100%cpu resources when I have nothing opened.

EAI

Ok, it's phy0 not PHYO. That zero is important.

It's related to your ethernet port. Try updating your kernel. Try switching to a different NIC.

1 members found this post helpful.

I pulled out the wireless card and put in a new lan card, so far it looks like that has solved the problem.

Just for interest sake I have not had these problems with earlier versions of ubuntu.

This is a duplicate post.

The OP solved the problem by removing his "wireless NIC".

So it sounds like it was probably an Atheros NIC, and probably the same as the issues cited here:
Also, for future reference, it's extremely likely there might be a solution (a viable athXX kernel driver update) here:

1 members found this post helpful.