Re: events/0 eats 100% cpu on core duo laptop

From: Stephen Hemminger
Date: Tue May 16 2006 - 18:23:05 EST

On Wed, 17 May 2006 00:49:09 +0300 (EEST)
Dimitris Zilaskos <dzila@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> It seems that the issue occurs as soon as the nic is brought up:
> Pid: 6, comm: events/0
> EIP: 0060:[<c02e9e6f>] CPU: 0
> EIP is at __gm_phy_read+0x42/0x7b
> EFLAGS: 00000293 Not tainted ( #1)
> EAX: 000004e8 EBX: 00002884 ECX: 7a7cd340 EDX: e0030000
> ESI: 00000003 EDI: 00002880 EBP: c1617340 DS: 007b ES: 007b
> CR0: 8005003b CR2: b7fd6ccb CR3: 005b4000 CR4: 000006d0
> [<c02e9ed8>] gm_phy_read+0x30/0x5b
> [<c02ec704>] sky2_phy_task+0x31/0x129
> [<c012dffc>] run_workqueue+0x76/0xea
> [<c02ec6d3>] sky2_phy_task+0x0/0x129
> [<c012e1b2>] worker_thread+0x142/0x164
> [<c0118fe0>] default_wake_function+0x0/0x12
> [<c0118fe0>] default_wake_function+0x0/0x12
> [<c012e070>] worker_thread+0x0/0x164
> [<c01317b9>] kthread+0xb7/0xbd
> [<c0131702>] kthread+0x0/0xbd
> [<c01011a1>] kernel_thread_helper+0x5/0xb
> The nic was not working properly at bootup (it was unable to
> detect link,gain ip from dhcp) but I have discovered that adding an ifconfig
> eth0 up prior to launching dhcp worked:
> sky2 eth0: enabling interface
> sky2 eth0: Link is up at 100 Mbps, full duplex, flow control tx
> sky2 eth0: disabling interface
> sky2 eth0: phy read timeout
> sky2 eth0: enabling interface
> sky2 eth0: phy read timeout
> sky2 eth0: speed/duplex mismatch<6>sky2 eth0: Link is up at 100 Mbps, full
> duplex, flow control tx
> Also when I shutdown/reboot sky2 eth0: phy read timeout messages flood
> the console for a few seconds. The nic is detected as :
> sky2 v0.15 addr 0xf0000000 irq 19 Yukon-EC Ultra(0xb4) rev 2
> Best regards,

That's my driver. I put a lot of fixes in for 2.6.17, one of which changes
the setup of the chip type used in this machine. The driver is significantly
changed from 2.6.16 so best bet is to just take the 2.6.17 latest version
and compile it on 2.6.16 (or update to 2.6.17). I got reports from Fujitsu E610
user that it now works fine.

Unfortunately, I don't have the hardware (or full specs for the chip) used
in that machine. Maybe I need to get a MacBook.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at