LaurentHU

Members
  • Posts

    34
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

LaurentHU's Achievements

Noob

Noob (1/14)

0

Reputation

  1. The new BIOS solved my issue with my SIL card Now I will maybe try to remove the DLink NIC and use the onboard to see if that works better, but not right now - I want to enjoy bug-free server for a while
  2. Problem with the Sil 3114 seems to be definitely solved with the new BIOS Now do I try to reuse the onboard network card?
  3. I found the same 1002 BIOS for the non-Pro card and just updated. No change for me in the IRQ distribution, eth0 with USB, and my Sil 3114 together with AHCI... Time will tell if it solves the rest!
  4. Sequel to this oh-so-interesting story : found the 1002 BIOS on an ASUS FTP Server, updated to it now, will see if I have improvement. So far IRQ mapping is exactly the same, and I still can't redistribute IRQs manually in the BIOS.
  5. Yep, I've seen this, unfortunately I was too cheap to pay for the Pro version, and the non-Pro didn't get the same BIOS update. Damn!!! On the current BIOS version my Sil 3114 is back at square 1, giving me still the same errors as reported above. How frustrating...
  6. Just as an update : * Booting with irqpoll option works, just the performances are then abysmal... Not a solution! * I flashed the Sil 3114 card with the latest "IDE" (=non RAID) BIOS, flashing worked OK but on the UNRAID server it doesn't boot anymore!! * I flashed the card with the latest Raid BIOS, and now it is running smoothly with it since more than 12 hours. Let's see if it stays like this!
  7. Thanks for the reply... Understand what you say, indeed it's a mistake in hindsight. I have now booted with irqpoll option and it looks better, I'll just have to assess the impact on perfs. I think it's the Sil 3114 card that is causing the issue, plus the fact the BIOS doesn't allow you to remap the IRQs...
  8. Sorry, so Sata controller is on the same irq than the onboard SATA as far as I can see : root@NAS:/proc# more interrupts CPU0 CPU1 0: 6504 142202 IO-APIC-edge timer 1: 0 2 IO-APIC-edge i8042 9: 0 0 IO-APIC-fasteoi acpi 12: 0 3 IO-APIC-edge i8042 17: 136 11235 IO-APIC-fasteoi ehci_hcd:usb1, ehci_hcd:usb2, ehci_hcd:usb3 18: 7028 959268 IO-APIC-fasteoi ohci_hcd:usb4, ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7, eth0 19: 2265 80198 IO-APIC-fasteoi ahci, sata_sil NMI: 0 0 Non-maskable interrupts LOC: 142490 6746 Local timer interrupts SPU: 0 0 Spurious interrupts PMI: 0 0 Performance monitoring interrupts PND: 0 0 Performance pending work RES: 156778 89635 Rescheduling interrupts CAL: 23 55 Function call interrupts TLB: 3595 8214 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts MCE: 0 0 Machine check exceptions MCP: 5 5 Machine check polls ERR: 0 MIS: 0
  9. Here is the complete logfile... I have AHCI selected in the BIOS for the mainboard SATA controller, but also have a Sil 3114 PCI controller that can't be setup on AHCI if I understood it well, and that sits on the same IRQ that my NIC. Bad, and can't be setup in BIOS again - ASUS E35 MB.
  10. Hello, I've recently upgraded to a Zacate (E35M1-M) system with 4.7, both at the same time, and since then I see frequent partial crashes. First thing : I had the issue with the onboard Realtek NIC, I changed it for a D-Link DGE-528T, works perfectly. BUT, now I get this frequently : May 19 00:51:10 NAS kernel: irq 19: nobody cared (try booting with the "irqpoll" option) May 19 00:51:10 NAS kernel: Pid: 0, comm: swapper Tainted: G W 2.6.32.9-unRAID #8 May 19 00:51:10 NAS kernel: Call Trace: May 19 00:51:10 NAS kernel: [] __report_bad_irq+0x2e/0x6f May 19 00:51:10 NAS kernel: [] note_interrupt+0xf5/0x13c May 19 00:51:10 NAS kernel: [] handle_fasteoi_irq+0x5f/0x9d May 19 00:51:10 NAS kernel: [] handle_irq+0x1a/0x24 May 19 00:51:10 NAS kernel: [] do_IRQ+0x40/0x96 May 19 00:51:10 NAS kernel: [] common_interrupt+0x29/0x30 May 19 00:51:10 NAS kernel: [] ? acpi_idle_enter_simple+0xfe/0x12a May 19 00:51:10 NAS kernel: [] cpuidle_idle_call+0x63/0x9b May 19 00:51:10 NAS kernel: [] cpu_idle+0x3a/0x4e May 19 00:51:10 NAS kernel: [] start_secondary+0x195/0x19a May 19 00:51:10 NAS kernel: handlers: May 19 00:51:10 NAS kernel: [] (ahci_interrupt+0x0/0x3df [ahci]) May 19 00:51:10 NAS kernel: [] (sil_interrupt+0x0/0x26d [sata_sil]) May 19 00:51:10 NAS kernel: Disabling IRQ #19 Always the same, never the same time, and after that for some reason the system never really recovers, load that was <1 goes to >5, and everything is way slow... Any idea?
  11. I can confirm I had the NIC issue, has to buy a separate one. For the RAM, I indeed see only 3.5 G or RAM out of the 4, knowing that some is reserved for the VGA but I should see a bit more maybe - can't care less though, because 4G is already 4 times too much for normal Unraid functionning. Sleep / Resume I'm not using so can't help.
  12. Up on this one - it seems it's not only happening in a few MBs but rather wider on Realtek NICs... Did we find a real 4.7 bug?
  13. Cyrnel do you mean that it crashed when the NIC was pushed with your new NIC?