search for: x9drd

...s. >>> Thanks to everyone that provided tips and suggestions along the way. >>> >> >> Do you mind sharing what hardware have you been running the 4.9 kernel on other than "Supermicro X9DRT, Dual Xeon E5-2650, 2x I350, 2x 82571EB" and >> "Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB" if any? Are you using any SATA/SAS controllers? > > We have no expansion cards installed except for the dual-port gigabit > NICs. We're using the onboard SATA controller for only the local Dom0 > OS, and iSCSI and NFS for managin...

...ny further updates unless something breaks. > Thanks to everyone that provided tips and suggestions along the way. > Do you mind sharing what hardware have you been running the 4.9 kernel on other than "Supermicro X9DRT, Dual Xeon E5-2650, 2x I350, 2x 82571EB" and "Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB" if any? Are you using any SATA/SAS controllers? Thanks, Sarah

...b 0000:04:00.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0401(Receiver ID) igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.1: [ 0] Receiver Error (First) This spams to the console continuously until hard booting. - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB igb 0000:82:00.0: Detected Tx Unit Hang Tx Queue <1> TDH <43> TDT <50> next_to_use <50> next_to_clean <43> buffer_info[next_to_clean] time_stamp...

...ess something breaks. >> Thanks to everyone that provided tips and suggestions along the way. >> > > Do you mind sharing what hardware have you been running the 4.9 kernel on other than "Supermicro X9DRT, Dual Xeon E5-2650, 2x I350, 2x 82571EB" and > "Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB" if any? Are you using any SATA/SAS controllers? We have no expansion cards installed except for the dual-port gigabit NICs. We're using the onboard SATA controller for only the local Dom0 OS, and iSCSI and NFS for managing storage for VMs an...

...b 0000:04:00.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0401(Receiver ID) igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.1: [ 0] Receiver Error (First) This spams to the console continuously until hard booting. - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB igb 0000:82:00.0: Detected Tx Unit Hang Tx Queue <1> TDH <43> TDT <50> next_to_use <50> next_to_clean <43> buffer_info[next_to_clean] time_stamp...

...erity=Corrected, type=Physical > Layer, id=0401(Receiver ID) > igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 > igb 0000:04:00.1: [ 0] Receiver Error (First) > > This spams to the console continuously until hard booting. > > - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB > > igb 0000:82:00.0: Detected Tx Unit Hang > Tx Queue <1> > TDH <43> > TDT <50> > next_to_use <50> > next_to_clean <43> > buffer_i...

On 02/21/2017 05:32 PM, Kevin Stange wrote: > On 02/21/2017 11:50 AM, Johnny Hughes wrote: >> On 02/21/2017 11:47 AM, Johnny Hughes wrote: >>> >>> >>> Kevin, >>> >>> Please try the 4.9.11-22 kernel that I just released for CentOS-6 (along >>> with the newer linux-firmare packages and xfsprogs). >>> >>> If you enable

...ical >> Layer, id=0401(Receiver ID) >> igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 >> igb 0000:04:00.1: [ 0] Receiver Error (First) >> >> This spams to the console continuously until hard booting. >> >> - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB >> >> igb 0000:82:00.0: Detected Tx Unit Hang >> Tx Queue <1> >> TDH <43> >> TDT <50> >> next_to_use <50> >> next_to_clean...

Howdy, I hit a snag trying to install Xen4CentOS on a Supermicro based system (X9DRD-7LN4F with the Broadcom/LSI 2308 chipset). I spent a few hours on this today, I'm posting this here in case it helps anyone else and saves them the frustration I dealt with. On this system I did a fresh install of CentOS 7, updated it, rebooted it, then installed Xen. The system was booting...

...erity=Corrected, type=Physical Layer, > id=0401(Receiver ID) > igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 > igb 0000:04:00.1: [ 0] Receiver Error (First) > > This spams to the console continuously until hard booting. > > - Supermicro X9DRD-iF/LF, Dual Xeon E5-2630, 2x I350, 2x 82575EB > > igb 0000:82:00.0: Detected Tx Unit Hang > Tx Queue <1> > TDH <43> > TDT <50> > next_to_use <50> > next_to_clean <43> > buffer_i...

Good news/bad news testing the new kernel on CentOS7 with my now notoriously finicky machines: Good news: 4.9.23-26.el7 (grabbed today via yum update) isn't any worse than 4.9.13-22 was on my xen hosts (as far as I can tell so far at least) Bad news: It isn't any better than 4.9.13 was for me either, if I don't set vcpu limit in the grub/xen config, it still panics like so: [