Menu
▾
▴
Re: [E1000-devel] Lost Ticks and ICH8
|
From: Jason G. <jgu...@ob...> - 2006-10-29 04:19:59
|
On Sat, Oct 28, 2006 at 09:25:33PM -0600, Jason Gunthorpe wrote: > On Fri, Oct 20, 2006 at 02:26:43PM -0700, Brandeburg, Jesse wrote: > > > any luck? I am expecting at the very least the BIOS changed behavior. > Ok, I have upgraded to the latest BIOS (since I last posted yet > another one has been released..) dmidecode says the version is now > CO96510J.86A.5434.2006.1016.1710 Good news, I finally found out how to follow your last advice to turn off AMT. In this BIOS it is hidden under a password protected page called 'Intel Management Engine' and the default password is in the AMT documentation on the intel site. The BIOS instruction guide for this MB has no hint. Ir made me choose a new strong password (which I will defiantely loose) before I could turn it off. :< At least it will never get turned on again! [This BIOS seems to be a total joke, it looks like they randomly tossed together a bunch of modules and gave zippo thought to how they work together.] So, after doing that, and setting the management from AMT to OFF everything works fine: [ 302.645867] in e1000_update_stats 3179 [ 302.645894] e1000_update_stats 3255 [ 302.645902] e1000_update_stats 3308 [ 302.645904] e1000_update_stats 3321 [ 302.645906] media_type 0 link_speed 1000 [ 302.645954] in e1000_read_phy_reg 3363 [ 302.645956] in e1000_swfw_sync_acquire 3271 0x2 [ 302.645958] out e1000_swfw_sync_acquire 3275 [ 302.645962] in e1000_read_phy_reg_ex 3429 [ 302.646015] out e1000_read_phy_reg_ex 3492 [ 302.646018] out e1000_read_phy_reg 3416 [ 302.646020] e1000_update_stats 3336 [ 302.646022] out e1000_update_stats 3338 $ ethtool -i eth0 driver: e1000 version: 7.1.9-k4 firmware-version: 1.1-0 bus-info: 0000:00:19.0 # ethtool -e eth0 Offset Values ------ ------ 0x0000 00 16 76 c8 16 f7 00 08 ff ff 10 10 ff ff ff ff 0x0010 ff ff ff ff c7 10 01 00 86 80 4a 10 86 80 00 00 0x0020 01 0d 00 00 00 00 05 96 20 50 00 33 00 00 07 8d 0x0030 84 06 41 03 00 00 00 00 00 00 00 00 00 00 00 00 0x0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0060 00 01 00 40 2a 12 07 40 ff ff ff ff ff ff ff ff 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ed 5a 0x0080 20 61 1f 00 02 0e 12 00 40 2f 1f 00 18 90 1b 00 0x0090 00 00 12 00 a0 2f 1f 00 24 8b 11 00 f0 f8 12 00 0x00a0 00 20 1f 00 b0 10 10 00 00 00 11 00 c0 20 1f 00 0x00b0 9a 24 1d 00 d3 00 1e 00 a0 28 1f 00 ce 04 14 00 0x00c0 60 2f 1f 00 e4 29 10 00 00 00 1f 00 40 01 00 00 0x00d0 20 1f 1f 00 06 16 10 00 14 b8 11 00 2a 01 15 00 0x00e0 67 00 1e 00 40 1f 1f 00 65 00 14 00 2a 00 15 00 0x00f0 2a 00 16 00 60 1f 1f 00 b0 3f 12 00 ff c0 16 00 0x0100 ec 1d 17 00 ef f9 18 00 10 02 19 00 80 18 1f 00 0x0110 03 00 15 00 80 17 1f 00 08 00 16 00 80 17 1f 00 0x0120 08 d0 18 00 80 18 1f 00 18 d9 18 00 60 18 1f 00 0x0130 00 08 1a 00 00 00 1f 00 01 00 19 00 40 13 00 00 0x0140 51 60 1f 00 01 00 11 00 00 00 1f 00 ff ff ff ff 0x0150 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [snip] I don't know what you want to take away from this.. Is this just a BIOS bug or does the driver have to do something horrible to interface with AMT? In any case it would be nice to have a dmesg print that something is wrong :> I wonder if it also fixes my prior problem with flow control not working? Regards, Jason |
