Errors in Syslog on startup

[apgood]

HI,

 

Getting the below errors in my syslog on startup is there anything I can do to fix it?  (please let me know if full syslog is needed)

 

Version 4.7 on asus E35M1-M motherboard.  I did try 5 b14 but too many stabilty issues with nic and irq conflicts when up in addin nic card....

 

Jan 11 07:38:51 Tower kernel: DMI 2.6 present.

Jan 11 07:38:51 Tower kernel: AMI BIOS detected: BIOS may corrupt low RAM, working around it.

Jan 11 07:38:51 Tower kernel: e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)

Jan 11 07:38:51 Tower kernel: last_pfn = 0x11f000 max_arch_pfn = 0x1000000

Jan 11 07:38:51 Tower kernel: MTRR default type: uncachable

Jan 11 07:38:51 Tower kernel: MTRR fixed ranges enabled:

Jan 11 07:38:51 Tower kernel:  00000-9FFFF write-back

Jan 11 07:38:51 Tower kernel:  A0000-BFFFF write-through

Jan 11 07:38:51 Tower kernel:  C0000-D3FFF write-protect

Jan 11 07:38:51 Tower kernel:  D4000-E7FFF uncachable

Jan 11 07:38:51 Tower kernel:  E8000-FFFFF write-protect

Jan 11 07:38:51 Tower kernel: MTRR variable ranges enabled:

Jan 11 07:38:51 Tower kernel:  0 base 000000000 mask F00000000 write-back

Jan 11 07:38:51 Tower kernel:  1 base 0DBF00000 mask FFFF00000 uncachable

Jan 11 07:38:51 Tower kernel:  2 base 0DC000000 mask FFC000000 uncachable

Jan 11 07:38:51 Tower kernel:  3 base 0E0000000 mask FE0000000 uncachable

Jan 11 07:38:51 Tower kernel:  4 disabled

Jan 11 07:38:51 Tower kernel:  5 disabled

Jan 11 07:38:51 Tower kernel:  6 disabled

Jan 11 07:38:51 Tower kernel:  7 disabled

Jan 11 07:38:51 Tower kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106

Jan 11 07:38:51 Tower kernel: e820 update range: 00000000dbf00000 - 000000011f000000 (usable) ==> (reserved)

Jan 11 07:38:51 Tower kernel: WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 495MB of RAM. (Minor Issues)

Jan 11 07:38:51 Tower kernel: ------------[ cut here ]------------

Jan 11 07:38:51 Tower kernel: WARNING: at arch/x86/kernel/cpu/mtrr/cleanup.c:1092 mtrr_trim_uncached_memory+0x499/0x4ba() (Minor Issues)

Jan 11 07:38:51 Tower kernel: Hardware name: System Product Name

Jan 11 07:38:51 Tower kernel: Modules linked in:

Jan 11 07:38:51 Tower kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9-unRAID #8 (Errors)

Jan 11 07:38:51 Tower kernel: Call Trace: (Errors)

Jan 11 07:38:51 Tower kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors)

Jan 11 07:38:51 Tower kernel:  [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors)

Jan 11 07:38:51 Tower kernel:  [<c13fbbad>] mtrr_trim_uncached_memory+0x499/0x4ba (Errors)

Jan 11 07:38:51 Tower kernel:  [<c13f7432>] setup_arch+0x440/0x805 (Errors)

Jan 11 07:38:51 Tower kernel:  [<c13f9b30>] ? __reserve_early+0xc4/0xcc (Errors)

Jan 11 07:38:51 Tower kernel:  [<c13f9cf8>] ? reserve_early_overlap_ok+0x2d/0x37 (Errors)

Jan 11 07:38:51 Tower kernel:  [<c1024fc0>] ? printk+0x15/0x17 (Errors)

Jan 11 07:38:51 Tower kernel:  [<c13f55f4>] start_kernel+0x63/0x280 (Errors)

Jan 11 07:38:51 Tower kernel:  [<c13f5091>] i386_start_kernel+0x91/0x96 (Errors)

Jan 11 07:38:51 Tower kernel: ---[ end trace 4eaa2a86a8e2da22 ]---

Jan 11 07:38:51 Tower kernel: update e820 for mtrr

Jan 11 07:38:51 Tower kernel: modified physical RAM map:

[prostuff1]

Your using an AMD Fusion based board and if you are running 4.7 you are running a version of unRAID that is probably "to old" and does not recognize all the hardware of that board.  One of the betas (12/13/14) would probably be a better choice for on that board.

[apgood]

Thanks I did try using 5 beta 14, but is was just too unstable.  The onboard Realtek r111E was just causing too many stability issues and then when I tried a intel pci nic i got irq conflicts with the sata card that were even worse, while with an r8169 pci-e I was getting irq conflicts with usb controller which wasn't much better, so i went back to 4.7.

 

On 4.7 everything seems to be running fine, but network speed and windows copies are half the speed i would expect, so going to try to drop in the intel nic agin and see what happens. if no good theni think i'll put the atom board back in unless someone has some suggestion how i can fix the issues on 4.7 or the irq conflicts on 5b14, thought hoping the new version with the 3.2 kernel comes out soon and that will help with the 5 betas....

 

 

[prostuff1]

Try updating to the latest BIOS on the motherboard to fix IRQ issues.

 

The other thing you can try is adding irqpoll to the syslinux.cfg file.  Do a search on the forum to find an example I posted.

[apgood]

Hi Prostuff1,

Thanks for your help and pointers.  I checked the BIOS and it's the latest for that board (1002).  I also tried dropping in the Intel Pro100 pci card (causes irq conflicts on 18\19 with sata card).

I did a bit of digging in the forums and tried the irqpoll and irqfixup options in syslinux.cfg that you mentioned to others, but no luck still ends up complaining after it's been running for about half an hour.

I actually copied your irqfixup string as it looked from one of your posts like it was very similar to the irq conflict I am having, but it didn't work (atleast on 4.7 anyway).  I think I'm either going to put the atom d510 board back in and live the slower write performance (due needing a sata port multipler because only one pci slot on board) or buy a Celeron G530 and a motherboard that's on the compatible hardware list...  pity as the E350 board seems to be a good balance between power consumption and performance....

 

Update:  From looking at some posts by others about this motherboard it seems that a BIOS update is needed to fix the issues, so it's a matter of waiting until the updated BIOS is released.

[Golfonauta]

Hello,

 

me and my brother also have this motherboard.

 

Last BIOS I tried is 1502 with beta 14 and I have a lot of issues, it does not start the raid, but I can't see why, because it cuts the network comunication and after restarting, you also know there's nothing in the log.

 

My brother is on 5.06 he says without errors but I don't know how far he has gone with it.

 

I started with 5 beta 12 and was having issues of hangup if I sent a big folder to copy to it, then I tried with a little folder with some pictures, i made some tests and some pictures were corrupted, so the system isn't working fine.

 

I have run the memory test and it says it's ok.

 

I have paid for the license and it's horrible the feeling I have about it.

 

 

From ASUS:

 

E35M1-M-PRO BIOS 1502 - 2011.12.09

E35M1-M PRO 1402 BIOS - 2011.11.04

E35M1-M PRO 1002 BIOS - 2011.07.20

 

Thanks,

Ruben

syslog_1.txt

[mbryanr]

Not running 5b so you will probably get a better response from someone else or in the beta thread, but I noticed a few questionable items:

 

1.  Feb  9 13:19:17 Tower kernel: r8169 0000:04:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168e-2.fw (-2)

Causing the ethernet issues?

 

2.  Feb  9 13:19:17 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA5882289 (hda) 1953514584

Feb  9 13:19:17 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WCAZA8431017 (hdb) 1953514584

 

Not likely causing an error, but this value seems low...

Feb  9 13:19:17 Tower kernel: xor: using function: pIII_sse (3173.200 MB/sec)

 

Two drives identified as ide, bios setting?

[Golfonauta]

Hello mbryanr,

 

I think you are talking about the drives in my syslog, I don't know why 2 are seen as IDE, but the board has 4 native ports, 2 raid ports and I have also an adaptec 1430sa with 2 drives attached to it.

 

From my experience I use now all the times teracopy utility to avoid network problems. (it's free and incredible)

 

The motherboard is a little bastard, I tryed with a PCIE network card but it gives errors, for example is you say to the BIOS that the mainVGA is the onboard it does not try to power up the PCIEx16 and then the raid controller doesn't start. The PCIE board I purchased is an Intel Gigabit so nice, but never working in unraid.

[mbryanr]

A bios setting will change the drive type from ide to ahci. Likely those last two ports are identified as "ide" in the bios. I know my Asus board was setup similarly.

 

And in the RC2 release thread there was discussion on this error:

1.  Feb  9 13:19:17 Tower kernel: r8169 0000:04:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168e-2.fw (-2)

 

Tom found where some firmwares were not stored with the kernel, but he found the source and was planning to add it to unRAID.

.......

Here it is:

http://lime-technology.com/forum/index.php?topic=19954.msg178000#msg178000