| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <453BC0E7.1060308@mbligh.org> Date: Sun, 22 Oct 2006 12:05:11 -0700 From: "Martin J. Bligh" <mbligh@...igh.org> To: "Martin J. Bligh" <mbligh@...gle.com> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org Subject: Re: Strange errors from e1000 driver (2.6.18) Martin J. Bligh wrote: > I'm getting a lot of these type of errors if I run 2.6.18. If > I run the standard Ubuntu Dapper kernel, I don't get them. > What do they indicate? > > Oct 21 18:48:28 localhost kernel: buffer_info[next_to_clean] > Oct 21 18:48:28 localhost kernel: time_stamp <7b79d33> > Oct 21 18:48:28 localhost kernel: next_to_watch <3d> > Oct 21 18:48:28 localhost kernel: jiffies <7b7a0c1> > Oct 21 18:48:28 localhost kernel: next_to_watch.status <0> > Oct 21 18:48:30 localhost kernel: Tx Queue <0> > Oct 21 18:48:30 localhost kernel: TDH <3d> > Oct 21 18:48:30 localhost kernel: TDT <44> > Oct 21 18:48:30 localhost kernel: next_to_use <44> > Oct 21 18:48:30 localhost kernel: next_to_clean <39> > Oct 21 18:48:30 localhost kernel: buffer_info[next_to_clean] > Oct 21 18:48:30 localhost kernel: time_stamp <7b79d33> > Oct 21 18:48:30 localhost kernel: next_to_watch <3d> > Oct 21 18:48:30 localhost kernel: jiffies <7b7a2b5> > Oct 21 18:48:30 localhost kernel: next_to_watch.status <0> > Oct 21 18:48:32 localhost kernel: Tx Queue <0> > Oct 21 18:48:32 localhost kernel: TDH <3d> > Oct 21 18:48:32 localhost kernel: TDT <44> > Oct 21 18:48:32 localhost kernel: next_to_use <44> > Oct 21 18:48:32 localhost kernel: next_to_clean <39> > Oct 21 18:48:32 localhost kernel: buffer_info[next_to_clean] > Oct 21 18:48:32 localhost kernel: time_stamp <7b79d33> > Oct 21 18:48:32 localhost kernel: next_to_watch <3d> > Oct 21 18:48:32 localhost kernel: jiffies <7b7a4a9> > Oct 21 18:48:32 localhost kernel: next_to_watch.status <0> > Oct 21 18:48:34 localhost kernel: Tx Queue <0> > Oct 21 18:48:34 localhost kernel: TDH <3d> > Oct 21 18:48:34 localhost kernel: TDT <44> > Oct 21 18:48:34 localhost kernel: next_to_use <44> > Oct 21 18:48:34 localhost kernel: next_to_clean <39> > Oct 21 18:48:34 localhost kernel: buffer_info[next_to_clean] > Oct 21 18:48:34 localhost kernel: time_stamp <7b79d33> > Oct 21 18:48:34 localhost kernel: next_to_watch <3d> > Oct 21 18:48:34 localhost kernel: jiffies <7b7a69d> > Oct 21 18:48:34 localhost kernel: next_to_watch.status <0> > Oct 21 18:48:35 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out > Oct 21 18:48:36 localhost kernel: e1000: eth0: e1000_watchdog: NIC Link > is Up 100 Mbps Full Duplex Actually, maybe this set is more helpful: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Tx Queue <0> TDH <6> TDT <1f> next_to_use <1f> next_to_clean <2> buffer_info[next_to_clean] time_stamp <2de8b54> next_to_watch <6> jiffies <2de8db7> next_to_watch.status <0> e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Tx Queue <0> TDH <6> TDT <1f> next_to_use <1f> next_to_clean <2> buffer_info[next_to_clean] time_stamp <2de8b54> next_to_watch <6> jiffies <2de8fab> next_to_watch.status <0> e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Tx Queue <0> TDH <6> TDT <1f> next_to_use <1f> next_to_clean <2> buffer_info[next_to_clean] time_stamp <2de8b54> next_to_watch <6> jiffies <2de919f> next_to_watch.status <0> NETDEV WATCHDOG: eth0: transmit timed out e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists