search for: x9sri

Hello, Is it a Plan to correct the Broken mdadm and or driver for Intel Chipset C602, my Server SuperMicro Board X9SRi-F have a Problem with the new C8 or RH8 ? With C7 I can install Centos with no Problem? Have any a workaround or is it planed a Update for this Problem Thanks for a answer, -- mit freundlichen Gr?ssen / best regards, G?nther J. Niederwimmer

...s <billings at negate.org> wrote: > >> On Oct 2, 2019, at 15:14, G?nther J. Niederwimmer <gjn at gjn.priv.at> wrote: >> >> Hello, >> >> Is it a Plan to correct the Broken mdadm and or driver for Intel Chipset C602, >> my Server SuperMicro Board X9SRi-F have a Problem with the new C8 or RH8 ? > > Is there a bug filed on https://bugzilla.redhat.com/ yet? Also, please consider looking at this list of hardware no longer supported in rhel8. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/considerations_in_a...

On 10/2/19 9:27 PM, Jonathan Billings wrote: > On Oct 2, 2019, at 15:14, G?nther J. Niederwimmer <gjn at gjn.priv.at> wrote: >> >> Hello, >> >> Is it a Plan to correct the Broken mdadm and or driver for Intel Chipset C602, >> my Server SuperMicro Board X9SRi-F have a Problem with the new C8 or RH8 ? > > Is there a bug filed on https://bugzilla.redhat.com/ yet? Have you submitted the errors you encountered anywhere? Richard on CentOS-devel mailing list has similar problem but suggests it might be issue only with CentOS, he says he had to add t...

On Oct 2, 2019, at 15:14, G?nther J. Niederwimmer <gjn at gjn.priv.at> wrote: > > Hello, > > Is it a Plan to correct the Broken mdadm and or driver for Intel Chipset C602, > my Server SuperMicro Board X9SRi-F have a Problem with the new C8 or RH8 ? Is there a bug filed on https://bugzilla.redhat.com/ yet? Have you submitted the errors you encountered anywhere? -- Jonathan Billings

...e: > >> On Oct 2, 2019, at 15:14, G?nther J. Niederwimmer <gjn at gjn.priv.at> > >> wrote: > >> > >> Hello, > >> > >> Is it a Plan to correct the Broken mdadm and or driver for Intel Chipset > >> C602, my Server SuperMicro Board X9SRi-F have a Problem with the new C8 > >> or RH8 ?> > > Is there a bug filed on https://bugzilla.redhat.com/ yet? OK, I can't say I have a account ? > Also, please consider looking at this list of hardware no longer supported > in rhel8. > > > https://access.re...

After running ceph on XFS for some time, I decided to try btrfs again. Performance with the current "for-linux-min" branch and big metadata is much better. The only problem (?) I''m still seeing is a warning that seems to occur from time to time: [87703.784552] ------------[ cut here ]------------ [87703.789759] WARNING: at fs/btrfs/inode.c:2103

We''ve been hitting the following issue on a variety of hosts and recent Xen/dom0 version combinations. Here''s an excerpt from our latest: Xen: 4.1.4 (xenbits @ 23432) Dom0: 3.7.1-x86_64 BUG: unable to handle kernel NULL pointer dereference at 000000000000001c IP: [<ffffffff8141a301>] evtchn_from_irq+0x11/0x40 PGD 0 Oops: 0000 [#1] SMP Modules linked in: ebt_comment

...am or send it to lkml? Regarding the hardware: the RAM was checked with memtest86+ and no errors found and the CPU has been replaced by a new one (same model). Still, the VM crash is reproducible. The hardware on the crashing system is: CPU: Intel Xeon E5-2609v2/4x2,5GHz Motherboard: Supermicro X9SRI-F For information, the hardware on non-crashing system is: CPU: Intel XEON L5639/6x2,13 GHz Motherboard: Supermicro X8STi > It seems like the crashes are related to a RT process, even though no > sched_fifo/rr processes are started on this system intentionally. Also, > the > CPU usag...

...rdware: the RAM was checked with memtest86+ and no > errors > found and the CPU has been replaced by a new one (same model). Still, > the > VM crash is reproducible. > > The hardware on the crashing system is: > CPU: Intel Xeon E5-2609v2/4x2,5GHz > Motherboard: Supermicro X9SRI-F > > For information, the hardware on non-crashing system is: > CPU: Intel XEON L5639/6x2,13 GHz > Motherboard: Supermicro X8STi > >> It seems like the crashes are related to a RT process, even though no >> sched_fifo/rr processes are started on this system intentional...