IPFire 2.21 (i586) r8169 driver crash

General questions.
Post Reply
francisS
Posts: 10
Joined: January 5th, 2019, 7:16 pm

IPFire 2.21 (i586) r8169 driver crash

Post by francisS » January 5th, 2019, 7:39 pm

Hello,

I have a thinkpad X40 with "IPFire 2.21 (i586) - core126" on an usb key and the network config

GREEN_DESCRIPTION='"pci: Intel Corporation 82541GI Gigabit Ethernet Controller"'
RED_DESCRIPTION='"usb: ASIX Electronics Corp. AX88178"'

I replaced the usb card by a pcmcia "Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)"

Now the red0 crash with the message:

Code: Select all

Jan  5 12:39:45 bill kernel: r8169 0000:03:00.0 red0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Jan  5 12:39:55 bill last message repeated 3 times
Jan  5 12:39:57 bill kernel: r8169 0000:03:00.0 red0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Jan  5 12:39:57 bill kernel: r8169 0000:03:00.0 red0: link up
Jan  5 12:40:01 bill kernel: r8169 0000:03:00.0 red0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Jan  5 12:40:05 bill last message repeated 4 times
Jan  5 12:40:07 bill kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Jan  5 12:40:07 bill kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.14.86-ipfire #1
Jan  5 12:40:07 bill kernel: Hardware name: IBM 2371Y29/2371Y29, BIOS 1UETD3WW (2.08 ) 12/21/2006
Jan  5 12:40:07 bill kernel: Call Trace:
Jan  5 12:40:07 bill kernel:  <IRQ>
Jan  5 12:40:07 bill kernel:  dump_stack+0x58/0x76
Jan  5 12:40:07 bill kernel:  __report_bad_irq+0x29/0xc0
Jan  5 12:40:07 bill kernel:  note_interrupt+0x21e/0x260
Jan  5 12:40:07 bill kernel:  ? unmask_irq.part.33+0x40/0x40
Jan  5 12:40:07 bill kernel:  handle_irq_event_percpu+0x4a/0x70
Jan  5 12:40:07 bill kernel:  handle_irq_event+0x27/0x40
Jan  5 12:40:07 bill kernel:  handle_fasteoi_irq+0x62/0x120
Jan  5 12:40:07 bill kernel:  handle_irq+0xb6/0xf0
Jan  5 12:40:07 bill kernel:  </IRQ>
Jan  5 12:40:07 bill kernel:  do_IRQ+0x44/0xd0
Jan  5 12:40:07 bill kernel:  common_interrupt+0x3b/0x40
Jan  5 12:40:07 bill kernel: EIP: cpuidle_enter_state+0x13e/0x360
Jan  5 12:40:07 bill kernel: EFLAGS: 00200246 CPU: 0
Jan  5 12:40:07 bill kernel: EAX: 00000000 EBX: 00000002 ECX: 436d5820 EDX: f73f3280
Jan  5 12:40:07 bill kernel: ESI: 436d5820 EDI: 00000ec5 EBP: c4215f20 ESP: c4215eec
Jan  5 12:40:07 bill kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan  5 12:40:07 bill kernel:  cpuidle_enter+0x14/0x20
Jan  5 12:40:07 bill kernel:  call_cpuidle+0x21/0x40
Jan  5 12:40:07 bill kernel:  do_idle+0x174/0x1d0
Jan  5 12:40:07 bill kernel:  cpu_startup_entry+0x65/0x70
Jan  5 12:40:07 bill kernel:  rest_init+0x91/0xa0
Jan  5 12:40:07 bill kernel:  start_kernel+0x4dd/0x506
Jan  5 12:40:07 bill kernel:  i386_start_kernel+0xd5/0xed
Jan  5 12:40:07 bill kernel:  startup_32_smp+0x164/0x170
Jan  5 12:40:07 bill kernel: handlers:
Jan  5 12:40:07 bill kernel: [<c3cc2cb0>] usb_hcd_irq
Jan  5 12:40:07 bill kernel: [<f7f02f90>] yenta_interrupt [yenta_socket]
Jan  5 12:40:07 bill kernel: [<f85cb640>] rtl8169_interrupt [r8169]
Jan  5 12:40:07 bill kernel: Disabling IRQ #16
Jan  5 12:40:09 bill kernel: r8169 0000:03:00.0 red0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Jan  5 12:40:09 bill kernel: r8169 0000:03:00.0 red0: link up
Jan  5 12:40:16 bill kernel: r8169 0000:03:00.0 red0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Jan  5 12:40:16 bill kernel: r8169 0000:03:00.0 red0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
The kernel suggested "irqpoll" option does not resolve the problem.

Code: Select all

Jan  5 16:27:12 bill kernel: r8169 0000:03:00.0 red0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Jan  5 16:27:22 bill last message repeated 3 times
Jan  5 16:27:26 bill kernel: NETDEV WATCHDOG: red0 (r8169): transmit queue 0 timed out
Jan  5 16:27:26 bill kernel: ------------[ cut here ]------------
Jan  5 16:27:26 bill kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:328 dev_watchdog+0x1c2/0x1d0
Jan  5 16:27:26 bill kernel: Modules linked in: xt_IMQ imq xt_length xt_DSCP xt_layer7 cls_fw sch_htb nfnetlink_queue nfnetlink_log ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_nat xt_mark xt_policy xt_TCPMSS nf_nat_irc nf_conntrack_irc nf_nat_tftp nf_conntrack_tftp nf_nat_ftp nf_conntrack_ftp nf_nat_h323 nf_conntrack_h323 xt_CT xt_helper nf_nat_sip nf_conntrack_sip xt_conntrack xt_comment ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit iptable_raw iptable_mangle iptable_nat nf_nat_ipv4 nf_nat iptable_filter sch_fq_codel iTCO_wdt iTCO_vendor_support psmouse pcspkr serio_raw snd_intel8x0m snd_intel8x0 thinkpad_acpi r8169 snd_ac97_codec i2c_i801 lpc_ich mii ac97_bus pcc_cpufreq snd_pcm e1000 snd_timer snd i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt acpi_cpufreq soundcore rfkill lp parport_pc
Jan  5 16:27:26 bill kernel:  parport video xfs pcmcia sdhci_pci sdhci mmc_core yenta_socket pcmcia_rsrc ata_generic pata_acpi pcmcia_core
Jan  5 16:27:26 bill kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.86-ipfire #1
Jan  5 16:27:26 bill kernel: Hardware name: IBM 2371Y29/2371Y29, BIOS 1UETD3WW (2.08 ) 12/21/2006
Jan  5 16:27:26 bill kernel: task: de6191c0 task.stack: de614000
Jan  5 16:27:26 bill kernel: EIP: dev_watchdog+0x1c2/0x1d0
Jan  5 16:27:26 bill kernel: EFLAGS: 00210246 CPU: 0
Jan  5 16:27:26 bill kernel: EAX: 00000039 EBX: ffc5bd88 ECX: 00000800 EDX: fffff000
Jan  5 16:27:26 bill kernel: ESI: fffffb36 EDI: f698f000 EBP: f6c79f5c ESP: f6c79f3c
Jan  5 16:27:26 bill kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan  5 16:27:26 bill kernel: CR0: 80050033 CR2: b6db4f0f CR3: 1e80c000 CR4: 000006d0
Jan  5 16:27:26 bill kernel: Call Trace:
Jan  5 16:27:26 bill kernel:  <SOFTIRQ>
Jan  5 16:27:26 bill kernel:  ? qdisc_rcu_free+0x40/0x40
Jan  5 16:27:26 bill kernel:  call_timer_fn+0x33/0x130
Jan  5 16:27:26 bill kernel:  ? qdisc_rcu_free+0x40/0x40
Jan  5 16:27:26 bill kernel:  ? qdisc_rcu_free+0x40/0x40
Jan  5 16:27:26 bill kernel:  run_timer_softirq+0x5c8/0x730
Jan  5 16:27:26 bill kernel:  ? __softirqentry_text_start+0x8/0x8
Jan  5 16:27:26 bill kernel:  __do_softirq+0xb6/0x275
Jan  5 16:27:26 bill kernel:  ? __softirqentry_text_start+0x8/0x8
Jan  5 16:27:26 bill kernel:  call_on_stack+0x45/0x50
Jan  5 16:27:26 bill kernel:  </SOFTIRQ>
Jan  5 16:27:26 bill kernel:  ? irq_exit+0xc5/0xd0
Jan  5 16:27:26 bill kernel:  ? do_IRQ+0x7c/0xd0
Jan  5 16:27:26 bill kernel:  ? common_interrupt+0x3b/0x40
Jan  5 16:27:26 bill kernel:  ? cpuidle_enter_state+0x13e/0x360
Jan  5 16:27:26 bill kernel:  ? cpuidle_enter+0x14/0x20
Jan  5 16:27:26 bill kernel:  ? call_cpuidle+0x21/0x40
Jan  5 16:27:26 bill kernel:  ? do_idle+0x174/0x1d0
Jan  5 16:27:26 bill kernel:  ? cpu_startup_entry+0x65/0x70
Jan  5 16:27:26 bill kernel:  ? rest_init+0x91/0xa0
Jan  5 16:27:26 bill kernel:  ? start_kernel+0x4dd/0x506
Jan  5 16:27:26 bill kernel:  ? i386_start_kernel+0xd5/0xed
Jan  5 16:27:26 bill kernel:  ? startup_32_smp+0x164/0x170
Jan  5 16:27:26 bill kernel: Code: f8 e8 23 ae 13 00 8b 97 d8 02 00 00 eb 9a 89 f8 c6 05 31 f1 6a de 01 e8 ad 86 fd ff ff 75 f0 50 57 68 d8 61 5b de e8 1b 70 ac ff <0f> 0b 83 c4 10 eb c4 8d b4 26 00 00 00 00 3e 8d 74 26 00 55 89
Jan  5 16:27:26 bill kernel: ---[ end trace e080f38406d16dd6 ]---
Jan  5 16:27:26 bill kernel: r8169 0000:03:00.0 red0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Jan  5 16:27:26 bill kernel: r8169 0000:03:00.0 red0: link up
Jan  5 16:27:27 bill kernel: r8169 0000:03:00.0 red0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Best regards.

Francis

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8031
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: IPFire 2.21 (i586) r8169 driver crash

Post by Arne.F » January 6th, 2019, 2:36 pm

I think the reason is not the r8169 driver because this is one of the most common Nics.

I use this in a bunch of systems PCI (RTL8169) and also PCIe (RTL8168, RTL811x)
all use the r8169 module.

But i have serious problems the the card slot of my Thinkpad X220 with linux. (Not only IPFire) After a while the card simply not answer anymore. (USB3 Cards and LAN Cards)

Also i have seen that your system is using the legacy kernel. Any Pentium should support PAE and should use the ipfire-pae kernel if i586 variant is installed.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

francisS
Posts: 10
Joined: January 5th, 2019, 7:16 pm

Re: IPFire 2.21 (i586) r8169 driver crash

Post by francisS » January 7th, 2019, 10:20 am

Thank Arne,

I have probably a problem with the r8169 driver and the thinkpad X40 pcmcia...

Do you know why I have the message "r8169 0000:03:00.0 red0: rtl_counters_cond == 1 (loop: 1000, delay: 10)." ?

My system have less than 4Go memory so why I need to use a PAE kernel ? PAE kernel is needed to access more than 4Go memory with a 32bits arch.

Best regards.

Francis

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8031
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: IPFire 2.21 (i586) r8169 driver crash

Post by Arne.F » January 7th, 2019, 5:45 pm

You should use the pae kernel if the cpu support it because many security features like NoeXecute and other memory protections need PAE. It also may be faster and have better interrupt handling because it can use the memory mapping features of the cpu and not software emulated.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

francisS
Posts: 10
Joined: January 5th, 2019, 7:16 pm

Re: IPFire 2.21 (i586) r8169 driver crash

Post by francisS » January 8th, 2019, 5:37 am

Hello Arne,

Thank for the information about PAE but I can not install linux-pae" I have the error message

pakfire linux-pae: no pae support found, aborted!

I have this cpu.

Code: Select all

# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 13
model name      : Intel(R) Pentium(R) M processor 1.40GHz
stepping        : 6
microcode       : 0x18
cpu MHz         : 1400.000
cache size      : 2048 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts cpuid est tm2
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips        : 2792.18
clflush size    : 64
cache_alignment : 64
address sizes   : 32 bits physical, 32 bits virtual
power management:
Best regards.

Francis

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8031
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: IPFire 2.21 (i586) r8169 driver crash

Post by Arne.F » January 8th, 2019, 7:56 am

Strange. This cpu support sse2 but no pae, there is something wrong...

Update: Pentium M and Celeron M based on banias core has a CPUID bug that not report PAE correctly.

So at the moment there is no easy way to install the pae kernel even it should work. (Ubuntu has a special option to force the pae kernel installation...)
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

francisS
Posts: 10
Joined: January 5th, 2019, 7:16 pm

Re: IPFire 2.21 (i586) r8169 driver crash

Post by francisS » January 8th, 2019, 9:30 am

Hello Arne,

After lot of search I find this about my processor, this is a Dothan (cpu family 6 model 13) Pentium M LV 738, but I do not find if it support PAE ! :(

I find this about Intel processor and PAE:

PAE is provided by Intel Pentium Pro (and above) CPUs - including all later Pentium-series processors except the 400 MHz bus versions of the Pentium M, as well as by other processors such as the AMD Athlon and later AMD processor models with similar or more advanced versions of the same architecture.

My processor is 400MHz fsb but form Intel this processor support NX and form Internet for NX PAE is needed...

Not clear :(

From ubuntu I have this "https://help.ubuntu.com/community/PAE".

When I have access to the system I'll try to use the "forcepae" kernel option (not sure that work with ipfire kernel) or to use this bypass.

# cat /proc/cpuinfo | sed 's/flags\t*:/& pae/' > /tmp/cpuinfo_pae
# mount -o bind /tmp/cpuinfo_pae /proc/cpuinfo
# mount -o remount,ro,bind /proc/cpuinfo

Best regards

Francis

francisS
Posts: 10
Joined: January 5th, 2019, 7:16 pm

Re: IPFire 2.21 (i586) r8169 driver crash

Post by francisS » January 9th, 2019, 6:00 am

Hello,

With these command I can install the PAE kernel, but I have to do that each time I update the kernel... no time to test "forcepae" options (I have to reinstall ipfire).

# cat /proc/cpuinfo | sed 's/flags\t*:/& pae/' > /tmp/cpuinfo_pae
# mount -o bind /tmp/cpuinfo_pae /proc/cpuinfo
# mount -o remount,ro,bind /proc/cpuinfo

Now I have a 36 bits physical address size, I use PAE or this a kernel message ?

Code: Select all

# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 13
model name      : Intel(R) Pentium(R) M processor 1.40GHz
stepping        : 6
microcode       : 0x18
cpu MHz         : 1400.000
cache size      : 2048 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts cpuid est tm2
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips        : 2792.38
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 32 bits virtual
power management:

francisS
Posts: 10
Joined: January 5th, 2019, 7:16 pm

Re: IPFire 2.21 (i586) r8169 driver crash

Post by francisS » January 9th, 2019, 8:41 am

Hello,

I had to reinstall ipfire because I suppose there is a mkfs.xfs/grub incompatibility...

When I tried to installed the PAE kernel I have a "/boot" disk full, the filesystem size is 64M, "du" say 24M used and "df" more than 50M... No way to retrieve de "lost" space so I do this from "IPFire 2.21 core126".

- remove kernel PAE (disk full initramfs not complete and no install problem)
- backup /boot
- mkfs.xfs -f /dev/sdxxx
- restore /boot
- install kernel PAE
- reboot

At the boot gurb enter in rescue mode because an "unknown filesystem".

Booting form an USB "IPFire 2.19" key, the "/boot" filesystem is xfs, but it can not be mounted because an unknown xfs feature.

Grub need to be update or the boot sector (come from "IPFire 2.19") or ... ?

When I have time I will test the r8169 driver with the PAE kernel.

Best regards.

Francis

francisS
Posts: 10
Joined: January 5th, 2019, 7:16 pm

Re: IPFire 2.21 (i586) r8169 driver crash

Post by francisS » January 16th, 2019, 7:00 am

Hello,

Same problem with the PAE kernel.

Code: Select all

Jan 14 18:23:33 bill kernel: r8169 0000:03:00.0 red0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Jan 14 18:23:33 bill kernel: r8169 0000:03:00.0 red0: link up
Jan 14 18:23:39 bill kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Jan 14 18:23:39 bill kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.14.86-ipfire-pae #1
Jan 14 18:23:39 bill kernel: Hardware name: IBM 2371Y29/2371Y29, BIOS 1UETD3WW (2.08 ) 12/21/2006
Jan 14 18:23:39 bill kernel: Call Trace:
Jan 14 18:23:39 bill kernel:  <IRQ>
Jan 14 18:23:39 bill kernel:  dump_stack+0x58/0x76
Jan 14 18:23:39 bill kernel:  __report_bad_irq+0x29/0xc0
Jan 14 18:23:39 bill kernel:  note_interrupt+0x221/0x260
Jan 14 18:23:39 bill kernel:  ? unmask_irq.part.33+0x40/0x40
Jan 14 18:23:39 bill kernel:  handle_irq_event_percpu+0x3d/0x50
Jan 14 18:23:39 bill kernel:  handle_irq_event+0x27/0x40
Jan 14 18:23:39 bill kernel:  handle_fasteoi_irq+0x62/0x120
Jan 14 18:23:39 bill kernel:  handle_irq+0xb6/0xf0
Jan 14 18:23:39 bill kernel:  </IRQ>
Jan 14 18:23:39 bill kernel:  do_IRQ+0x44/0xd0
Jan 14 18:23:39 bill kernel:  common_interrupt+0x3b/0x40
Jan 14 18:23:39 bill kernel: EIP: cpuidle_enter_state+0x152/0x370
Jan 14 18:23:39 bill kernel: EFLAGS: 00000246 CPU: 0
Jan 14 18:23:39 bill kernel: EAX: 00000000 EBX: 00000002 ECX: be7c2261 EDX: f6602d00
Jan 14 18:23:39 bill kernel: ESI: be7c2261 EDI: 0001aebc EBP: d0e17f28 ESP: d0e17ef4
Jan 14 18:23:39 bill kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan 14 18:23:39 bill kernel:  ? finish_task_switch+0xeb/0x200
Jan 14 18:23:39 bill kernel:  cpuidle_enter+0x14/0x20
Jan 14 18:23:39 bill kernel:  call_cpuidle+0x21/0x40
Jan 14 18:23:39 bill kernel:  do_idle+0x174/0x1d0
Jan 14 18:23:39 bill kernel:  cpu_startup_entry+0x55/0x60
Jan 14 18:23:39 bill kernel:  rest_init+0x91/0xa0
Jan 14 18:23:39 bill kernel:  start_kernel+0x4bb/0x4d3
Jan 14 18:23:39 bill kernel:  i386_start_kernel+0xcb/0xe4
Jan 14 18:23:39 bill kernel:  startup_32_smp+0x164/0x168
Jan 14 18:23:39 bill kernel: handlers:
Jan 14 18:23:39 bill kernel: [<d08d01b0>] usb_hcd_irq
Jan 14 18:23:39 bill kernel: [<f7b07f00>] yenta_interrupt [yenta_socket]
Jan 14 18:23:39 bill kernel: [<f9749650>] rtl8169_interrupt [r8169]
Jan 14 18:23:39 bill kernel: Disabling IRQ #16
Jan 14 18:23:45 bill kernel: r8169 0000:03:00.0 red0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Jan 14 18:23:45 bill kernel: r8169 0000:03:00.0 red0: link up
Jan 14 18:23:53 bill kernel: r8169 0000:03:00.0 red0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Jan 14 18:23:57 bill kernel: r8169 0000:03:00.0 red0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Jan 14 18:23:57 bill kernel: r8169 0000:03:00.0 red0: link up
Jan 14 18:24:09 bill kernel: r8169 0000:03:00.0 red0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Also I have this problem with the e1000 (only one time and the driver do not crash, interface is restarted).

Code: Select all

Jan 13 09:09:55 bill kernel: e1000 0000:02:01.0 green0: Detected Tx Unit Hang
Jan 13 09:09:55 bill kernel:   Tx Queue             <0>
Jan 13 09:09:55 bill kernel:   TDH                  <4f>
Jan 13 09:09:55 bill kernel:   TDT                  <65>
Jan 13 09:09:55 bill kernel:   next_to_use          <65>
Jan 13 09:09:55 bill kernel:   next_to_clean        <4d>
Jan 13 09:09:55 bill kernel: buffer_info[next_to_clean]
Jan 13 09:09:55 bill kernel:   time_stamp           <652ff9c>
Jan 13 09:09:55 bill kernel:   next_to_watch        <51>
Jan 13 09:09:55 bill kernel:   jiffies              <6530100>
Jan 13 09:09:55 bill kernel:   next_to_watch.status <0>
Jan 13 09:09:57 bill kernel: e1000 0000:02:01.0 green0: Detected Tx Unit Hang
Jan 13 09:09:57 bill kernel:   Tx Queue             <0>
Jan 13 09:09:57 bill kernel:   TDH                  <4f>
Jan 13 09:09:57 bill kernel:   TDT                  <65>
Jan 13 09:09:57 bill kernel:   next_to_use          <65>
Jan 13 09:09:57 bill kernel:   next_to_clean        <4d>
Jan 13 09:09:57 bill kernel: buffer_info[next_to_clean]
Jan 13 09:09:57 bill kernel:   time_stamp           <652ff9c>
Jan 13 09:09:57 bill kernel:   next_to_watch        <51>
Jan 13 09:09:57 bill kernel:   jiffies              <6530380>
Jan 13 09:09:57 bill kernel:   next_to_watch.status <0>
Jan 13 09:09:59 bill kernel: e1000 0000:02:01.0 green0: Detected Tx Unit Hang
Jan 13 09:09:59 bill kernel:   Tx Queue             <0>
Jan 13 09:09:59 bill kernel:   TDH                  <4f>
Jan 13 09:09:59 bill kernel:   TDT                  <65>
Jan 13 09:09:59 bill kernel:   next_to_use          <65>
Jan 13 09:09:59 bill kernel:   next_to_clean        <4d>
Jan 13 09:09:59 bill kernel: buffer_info[next_to_clean]
Jan 13 09:09:59 bill kernel:   time_stamp           <652ff9c>
Jan 13 09:09:59 bill kernel:   next_to_watch        <51>
Jan 13 09:09:59 bill kernel:   jiffies              <6530600>
Jan 13 09:09:59 bill kernel:   next_to_watch.status <0>
Jan 13 09:10:01 bill kernel: e1000 0000:02:01.0 green0: Detected Tx Unit Hang
Jan 13 09:10:01 bill kernel:   Tx Queue             <0>
Jan 13 09:10:01 bill kernel:   TDH                  <4f>
Jan 13 09:10:01 bill kernel:   TDT                  <65>
Jan 13 09:10:01 bill kernel:   next_to_use          <65>
Jan 13 09:10:01 bill kernel:   next_to_clean        <4d>
Jan 13 09:10:01 bill kernel: buffer_info[next_to_clean]
Jan 13 09:10:01 bill kernel:   time_stamp           <652ff9c>
Jan 13 09:10:01 bill kernel:   next_to_watch        <51>
Jan 13 09:10:01 bill kernel:   jiffies              <6530880>
Jan 13 09:10:01 bill kernel:   next_to_watch.status <0>
Jan 13 09:10:03 bill kernel: NETDEV WATCHDOG: green0 (e1000): transmit queue 0 timed out
Jan 13 09:10:03 bill kernel: ------------[ cut here ]------------
Jan 13 09:10:03 bill kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:328 dev_watchdog+0x1c2/0x1d0
Jan 13 09:10:03 bill kernel: Modules linked in: r8169 xt_hashlimit i2c_dev ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_nat xt_mark xt_policy xt_TCPMSS nf_nat_irc nf_conntrack_irc nf_nat_tftp nf_conntrack_tftp nf_nat_ftp nf_conntrack_ftp nf_nat_h323 nf_conntrack_h323 xt_CT xt_helper nf_nat_sip nf_conntrack_sip xt_conntrack xt_comment ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit iptable_raw iptable_mangle iptable_nat nf_nat_ipv4 nf_nat iptable_filter sch_fq_codel iTCO_wdt iTCO_vendor_support psmouse snd_intel8x0 pcspkr snd_intel8x0m serio_raw snd_ac97_codec ac97_bus snd_pcm thinkpad_acpi asix snd_timer lpc_ich mfd_core usbnet snd mii i2c_i801 i2c_algo_bit e1000 fb_sys_fops syscopyarea sysfillrect sysimgblt i2c_core soundcore rfkill pcc_cpufreq acpi_cpufreq lp parport_pc parport video xfs pcmcia
Jan 13 09:10:03 bill kernel:  sdhci_pci sdhci mmc_core yenta_socket pcmcia_rsrc ata_generic pata_acpi pcmcia_core
Jan 13 09:10:03 bill kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.86-ipfire-pae #1
Jan 13 09:10:03 bill kernel: Hardware name: IBM 2371Y29/2371Y29, BIOS 1UETD3WW (2.08 ) 12/21/2006
Jan 13 09:10:03 bill kernel: task: d0e1c1c0 task.stack: d0e16000
Jan 13 09:10:03 bill kernel: EIP: dev_watchdog+0x1c2/0x1d0
Jan 13 09:10:03 bill kernel: EFLAGS: 00210246 CPU: 0
Jan 13 09:10:03 bill kernel: EAX: 0000003b EBX: f9acfc5c ECX: 000408f6 EDX: fffff000
Jan 13 09:10:03 bill kernel: ESI: fffffd53 EDI: f6213000 EBP: f507bf60 ESP: f507bf40
Jan 13 09:10:03 bill kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan 13 09:10:03 bill kernel: CR0: 80050033 CR2: b7e44044 CR3: 1101c000 CR4: 000006f0
Jan 13 09:10:03 bill kernel: Call Trace:
Jan 13 09:10:03 bill kernel:  <SOFTIRQ>
Jan 13 09:10:03 bill kernel:  ? qdisc_rcu_free+0x40/0x40
Jan 13 09:10:03 bill kernel:  call_timer_fn+0x33/0x130
Jan 13 09:10:03 bill kernel:  ? qdisc_rcu_free+0x40/0x40
Jan 13 09:10:03 bill kernel:  ? qdisc_rcu_free+0x40/0x40
Jan 13 09:10:03 bill kernel:  run_timer_softirq+0x5a8/0x700
Jan 13 09:10:03 bill kernel:  ? __softirqentry_text_start+0x8/0x8
Jan 13 09:10:03 bill kernel:  __do_softirq+0xb6/0x275
Jan 13 09:10:03 bill kernel:  ? __softirqentry_text_start+0x8/0x8
Jan 13 09:10:03 bill kernel:  call_on_stack+0x45/0x50
Jan 13 09:10:03 bill kernel:  </SOFTIRQ>
Jan 13 09:10:03 bill kernel:  ? irq_exit+0xc5/0xd0
Jan 13 09:10:03 bill kernel:  ? do_IRQ+0x7c/0xd0
Jan 13 09:10:03 bill kernel:  ? common_interrupt+0x3b/0x40
Jan 13 09:10:03 bill kernel:  ? finish_task_switch+0xeb/0x200
Jan 13 09:10:03 bill kernel:  ? cpuidle_enter_state+0x152/0x370
Jan 13 09:10:03 bill kernel:  ? cpuidle_enter+0x14/0x20
Jan 13 09:10:03 bill kernel:  ? call_cpuidle+0x21/0x40
Jan 13 09:10:03 bill kernel:  ? do_idle+0x174/0x1d0
Jan 13 09:10:03 bill kernel:  ? cpu_startup_entry+0x55/0x60
Jan 13 09:10:03 bill kernel:  ? rest_init+0x91/0xa0
Jan 13 09:10:03 bill kernel:  ? start_kernel+0x4bb/0x4d3
Jan 13 09:10:03 bill kernel:  ? i386_start_kernel+0xcb/0xe4
Jan 13 09:10:03 bill kernel:  ? startup_32_smp+0x164/0x168
Jan 13 09:10:03 bill kernel: Code: f8 e8 33 5e 13 00 8b 97 d8 02 00 00 eb 9a 89 f8 c6 05 31 3a eb d0 01 e8 5d 98 fd ff ff 75 f0 50 57 68 78 7b db d0 e8 1b 51 ad ff <0f> 0b 83 c4 10 eb c4 8d b4 26 00 00 00 00 3e 8d 74 26 00 55 89
Jan 13 09:10:03 bill kernel: ---[ end trace 17f02b30761a1aa5 ]---
Jan 13 09:10:03 bill kernel: e1000 0000:02:01.0 green0: Reset adapter
Jan 13 09:10:07 bill kernel: e1000: green0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
IPFire is installed on an USB key.

Best regards.

Francis

Post Reply