Ask Your Question

fedora 22 cinnamon dmesg memory problem

asked 2016-04-19 11:23:30 -0600

zug234zwang gravatar image

This query is probably more appropriately directed to a cinnamon or cinnamon-fedora forum, if any. However, I'll probably have better luck at this forum.

Boot disk recently died; decided to recover by re-installing everything, starting with Fedora 22 Live. kde proved problematic so switched to cinnamon. Several months ago, while using Fedora 22 with kde4, I researched how to make an external hard disk bootable. One of the steps was to find the device node assigned to the drive.

dmesg | tail
[ 4783.165535] sd 6:0:0:0: [sdc] Attached SCSI disk
device node = sdc

Today, I'm under fedora 22 64 bit with cinnamon 2.6.13, 16gb memory. I inserted a hard disk to my usb connected docking station (device sdd). Cinnamon automatically mounted it; I then unmounted the drive, leaving it still assigned to device sdd. Then:

[  474.183592] scsi 7:0:0:0: Direct-Access     WDC WD30 EZRX-00DC0B0          PQ: 0 ANSI: 5
[  474.185430] sd 7:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
[  474.185608] sd 7:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[  474.185861] sd 7:0:0:0: [sdd] Write Protect is off
[  474.185864] sd 7:0:0:0: [sdd] Mode Sense: 28 00 00 00
[  474.186112] sd 7:0:0:0: [sdd] No Caching mode page found
[  474.186115] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[  474.186293] sd 7:0:0:0: Attached scsi generic sg4 type 0
[  474.188831] sd 7:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
[  474.274863]  sdd: sdd1 sdd2
[  474.275939] sd 7:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
[  474.276534] sd 7:0:0:0: [sdd] Attached SCSI disk
[  840.116816] DMA-API: debugging out of memory - disabling
[  920.589012] kworker/dying (16) used greatest stack depth: 10848 bytes left
[ 1093.678988] kworker/dying (6) used greatest stack depth: 10672 bytes left
[ 1223.786129] usb 3-10: USB disconnect, device number 5

The heading lines from the top command (executed as the super user) are:

top - 08:38:49 up 26 min,  2 users,  load average: 0.00, 0.07, 0.17
Tasks: 224 total,   1 running, 223 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.8 us,  0.5 sy,  0.0 ni, 98.4 id,  0.2 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem : 16271316 total, 14042704 free,  1125872 used,  1102740 buff/cache
KiB Swap:  8191996 total,  8191996 free,        0 used. 14745112 avail Mem 


  1. (In linux-newbie terms) what does this message mean: "DMA-API: debugging out of memory - disabling"?

  2. Why is there no "device node = sdd" message in the dmesg output? Does it relate to the "debugging ... memory..." message?

  3. With 16gb memory, I installed from Fedora 22 Live without making any effort to tweak my memory settings. Do the memory lines from the top command indicate a ...

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2016-04-20 04:11:02 -0600

genodeftest gravatar image

This is just a vague answer, probably someone can give you a better one, but I don't want to leave it unanswered.

  1. Have a look into the source code or the documentation (just search for "DMA"). From what this file suggests, DMA-API debugging is used to help track down issues, but it is not essential. In your case it looks like something is doing _a lot_ DMA calls and the kernel doesn't want to eat your RAM with debugging information.

  2. I don't think so. I don't even see the "device node = …" message on my system – and I do have a disk installed ;)

  3. I don't think so – no problem, no fix.

You might want to run a SMART self-test on the disk, e.g. by using smartctl (command line, as root) or gnome-disks (GUI).

In general, I don't understand what could be wrong here. This might be because I didn't get your problem.

edit flag offensive delete link more


thanks for the response, genodeftest. I could be mistaken, but I thought that my fedora22-kde4(dmesg) output did contain the "device node =" string. With that string missing, and a "...debugging..." message occurring, I questioned it. Also, on a cold boot, just after the bios message, when the screen shows Fedora options to select, the TOP ONE IN THE LIST is "fedora ... debug ..." which I also think is strange. This might relate to previous problems I had installing Fedy (i.e. repo not exist).

No problems were reported re sudo smartctl -s on -t short /dev/sdb.

zug234zwang gravatar imagezug234zwang ( 2016-04-20 12:08:33 -0600 )edit

Question Tools

1 follower


Asked: 2016-04-19 11:23:30 -0600

Seen: 97 times

Last updated: Apr 20 '16