+Freed UMA keg was not empty. Lost # pages of memory.

[spyrule]

Hello,

I just setup FreeNAS 8.2.0-Release (I was running FreeNAS 8.0.4 previously for testing) on the following hardware :

FreeNAS-8.2.0-RELEASE-x64 (r11944)
AMD A8-3870 APU with Radeon(tm) HD Graphics (via Asus F1A75-M motherboard)
H80 Corsair HSF, in a Lian-Li PC-v354v case
8122MB (DDR3 1600)
600W PSU
on board video
1 x ZFS RAIDZ
6 x 1TB WD Black HDD (7200 rpm)
1 x 90GB SSD (running as cache)

So I setup FreeNAS 8.2 yesterday , and everything is working as expected, as well as I setup Email.

This morning I got my first email from the NAS, and the security run output shows the following issue :

freenas.***xx.net kernel log messages:
+++ /tmp/security.ILou5qpG 2012-08-13 03:01:00.000000000 -0400
+re0: promiscuous mode disabled
+epair0a: promiscuous mode disabled
+re0: link state changed to DOWN
+epair0a: link state changed to DOWN
+epair0b: link state changed to DOWN
+Freed UMA keg was not empty (336 items). Lost 2 pages of memory.
+Freed UMA keg was not empty (33 items). Lost 3 pages of memory.
+Freed UMA keg was not empty (8 items). Lost 2 pages of memory.
+Freed UMA keg was not empty (22 items). Lost 2 pages of memory.
+re0: link state changed to UP
+bridge0: Ethernet address: 92:2d:e1:29:e3:5e
+epair0a: Ethernet address: 02:d5:00:00:04:0a
+epair0b: Ethernet address: 02:d5:00:00:05:0b
+epair0a: link state changed to UP
+epair0b: link state changed to UP
+epair0a: promiscuous mode enabled
+re0: promiscuous mode enabled
+re0: link state changed to DOWN
+re0: link state changed to UP
+pid 25406 (minidlna), uid 40001: exited on signal 3
+pid 25581 (minidlna), uid 40001: exited on signal 3
+re0: promiscuous mode disabled
+epair0a: promiscuous mode disabled
+re0: link state changed to DOWN
+epair0a: link state changed to DOWN
+epair0b: link state changed to DOWN
+re0: link state changed to UP
+Freed UMA keg was not empty (504 items). Lost 3 pages of memory.
+Freed UMA keg was not empty (44 items). Lost 4 pages of memory.
+Freed UMA keg was not empty (250 items). Lost 5 pages of memory.
+Freed UMA keg was not empty (56 items). Lost 14 pages of memory.
+Freed UMA keg was not empty (110 items). Lost 10 pages of memory.
+bridge0: Ethernet address: a2:c4:69:8f:e7:8a
+epair0a: Ethernet address: 02:9a:27:00:04:0a
+epair0b: Ethernet address: 02:9a:27:00:05:0b
+epair0a: link state changed to UP
+epair0b: link state changed to UP
+epair0a: promiscuous mode enabled
+re0: link state changed to DOWN
+re0: promiscuous mode enabled
+re0: link state changed to UP

I've tried googling the Freed UMA keg, but I'm not finding anything useful or even indicative as to what this issue is (or if it even IS a real issue).

I've run the CPU through a 2 week burn-in with no issues found, I've run the memory through memory testing for a full week and no issues found.

The only piece of hardware that I know has an issue is the SSD drive, which is an older SSD that reads 40 sectors as bad (its now a 3 year old cheap ssd, so I'm not surprised).

The thing that's got me, is that I wasn't seeing this error on 8.0.4, but I am with 8.2. I know a lot was changed between the two, but I'm not sure where this issue is coming from.


Any help/suggestions are welcome,

Thanks,

Spyrule.

 

[cyberjock]

I've had the same thing on occasion. In particular, I think it is somehow related to the Jail. I don't know what it means though.

 

[deed02392]

I can second I believe this is something to do with the jail. These errors appeared within a few minutes after restarting the jail from the GUI.

 

[XeR]

Hello,

I just setup FreeNAS 8.2.0-Release (I was running FreeNAS 8.0.4 previously for testing) on the following hardware :

FreeNAS-8.2.0-RELEASE-x64 (r11944)
AMD A8-3870 APU with Radeon(tm) HD Graphics (via Asus F1A75-M motherboard)
H80 Corsair HSF, in a Lian-Li PC-v354v case
8122MB (DDR3 1600)
600W PSU
on board video
1 x ZFS RAIDZ
6 x 1TB WD Black HDD (7200 rpm)
1 x 90GB SSD (running as cache)

So I setup FreeNAS 8.2 yesterday , and everything is working as expected, as well as I setup Email.

This morning I got my first email from the NAS, and the security run output shows the following issue :



I've tried googling the Freed UMA keg, but I'm not finding anything useful or even indicative as to what this issue is (or if it even IS a real issue).

I've run the CPU through a 2 week burn-in with no issues found, I've run the memory through memory testing for a full week and no issues found.

The only piece of hardware that I know has an issue is the SSD drive, which is an older SSD that reads 40 sectors as bad (its now a 3 year old cheap ssd, so I'm not surprised).

The thing that's got me, is that I wasn't seeing this error on 8.0.4, but I am with 8.2. I know a lot was changed between the two, but I'm not sure where this issue is coming from.


Any help/suggestions are welcome,

Thanks,

Spyrule.

In my opinion , if you "force" close the jail ( turn "services-> core - > plugins" off ) , and this error may happen to you.

 

[Randall Flores]

I am testing 9.2.1

I installed owncloud and after awhile i lost the gui to owncloud. I couldnt hit it at all. I turned off the jail and when i was starting it back up I lost all connectivity to the box. When I got home the machine was still running and was displaying the "freed UMA key was not empty" etc etc. Messages. I tend to agree this pertains the the jails and since this is killing my box, i would say it is an issue, but thats me. Now i have to reboot it and hope nothing is hurt too badly.

 

[spyrule]

Well, it was because of this instability, that I said screw it, left FreeNAS and went to Xpenology. Been rock solid ever since. too bad, because other than this, I did like it.