{"action":"created","issue":{"url":"https://api.github.com/repos/Algodev-github/bfq-mq/issues/1","repository_url":"https://api.github.com/repos/Algodev-github/bfq-mq","labels_url":"https://api.github.com/repos/Algodev-github/bfq-mq/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/Algodev-github/bfq-mq/issues/1/comments","events_url":"https://api.github.com/repos/Algodev-github/bfq-mq/issues/1/events","html_url":"https://github.com/Algodev-github/bfq-mq/issues/1","id":244334307,"number":1,"title":"Hard lock-ups with bfq and bfq-mq","user":{"login":"monotykamary","id":1130103,"avatar_url":"https://avatars0.githubusercontent.com/u/1130103?v=4","gravatar_id":"","url":"https://api.github.com/users/monotykamary","html_url":"https://github.com/monotykamary","followers_url":"https://api.github.com/users/monotykamary/followers","following_url":"https://api.github.com/users/monotykamary/following{/other_user}","gists_url":"https://api.github.com/users/monotykamary/gists{/gist_id}","starred_url":"https://api.github.com/users/monotykamary/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/monotykamary/subscriptions","organizations_url":"https://api.github.com/users/monotykamary/orgs","repos_url":"https://api.github.com/users/monotykamary/repos","events_url":"https://api.github.com/users/monotykamary/events{/privacy}","received_events_url":"https://api.github.com/users/monotykamary/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-07-20T11:47:36Z","updated_at":"2017-07-20T12:27:27Z","closed_at":null,"body":"I wasn't too sure where to post this issue, but I'll post it here since the patches I format are directly from this repository. I've have formatted [patch snapshots of bfq-mq](https://gitlab.com/tom81094/custom-patches/tree/master/bfq-mq) and tested them with the ck-patchset and the stock kernel.\r\n\r\nIn testing 4.11-ck1 and 4.11-ck2 with `bfq-mq`, hard lockups occurred when the disk was idle or very close to idle. I have not tested for latency, but system ran as expected (with no problems) only if I am running multiple `make` threads or an application with moderate I/O load.\r\n\r\nMy workload at the time mainly consisted of testing patches and compiling kernels. With the ck-patchset and `bfq-mq`, as soon as a compile job was done and after a random amount of time, the system locks up. I assumed that this was a scheduler issue related with my CPU, so I left it as is.\r\n\r\nHowever, I saw similar cases when testing the stock kernel with the patch from 4.11.1 onwards, but it happened somewhat rarely so I didn't pay much attention to it. I experienced the same issue recently with the stock Arch Linux kernel 4.12.1 onwards when enabling `bfq`, and once more on kernel 4.12.2 + patch to the current commit (+ patch to include block merge for 4.13) when enabling `bfq` and `bfq-mq`. It is to the point where it locks up before I finish starting up my usual applications. `mq-deadline` and `kyber` work with no problems along with all the single-queue I/O schedulers so it doesn't seem like a hardware issue regarding my HDD. Out of source `bfq` has worked flawlessly.\r\n\r\nI don't think I've made any issues in formatting the patch since it applies very cleanly on git and on build, although I could be very wrong. The hard lockups will not respond to sysrq keys and there are no journal logs. I'm a bit troubled as to what to do to get more information on this.\r\n\r\n```\r\nMachine:   Device: portable System: Dell product: Inspiron 3421\r\n           Mobo: Dell model: Inspiron 3421 v: A01 BIOS: Dell v: A01 date: 11/05/2012\r\nCPU:       Dual core Intel Core i5-3317U (-HT-MCP-) cache: 3072 KB\r\n           clock speeds: max: 2600 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz\r\nGraphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller\r\n           Card-2: NVIDIA GK107M [GeForce GT 640M]\r\n           Display Server: X.Org 1.19.3 drivers: nvidia,intel Resolution: 1366x768@59.97hz\r\n           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile version: 4.2 Mesa 17.1.5\r\nAudio:     Card Intel 7 Series/C216 Family High Definition Audio Controller driver: snd_hda_intel\r\n           Sound: Advanced Linux Sound Architecture v: k4.12.2-1-ARCH\r\nNetwork:   Card-1: Broadcom Limited BCM43142 802.11b/g/n driver: bcma-pci-bridge\r\n           IF: N/A state: N/A mac: N/A\r\n           Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169\r\n           IF: enp9s0 state: down mac: e0:db:55:8d:dc:af\r\n           Card-3: Qualcomm Atheros AR9271 802.11n driver: ath9k_htc\r\n           IF: wlp0s29u1u2 state: N/A mac: N/A\r\nDrives:    HDD Total Size: 1000.2GB (34.4% used)\r\n           ID-1: /dev/sda model: TOSHIBA_MQ01ABD1 size: 1000.2GB\r\nPartition: ID-1: / size: 904G used: 310G (37%) fs: ext4 dev: /dev/sda4\r\n           ID-2: swap-1 size: 12.88GB used: 0.00GB (0%) fs: swap dev: /dev/sda3\r\nSensors:   System Temperatures: cpu: 48.0C mobo: N/A\r\n           Fan Speeds (in rpm): cpu: N/A\r\n```"},"comment":{"url":"https://api.github.com/repos/Algodev-github/bfq-mq/issues/comments/316687629","html_url":"https://github.com/Algodev-github/bfq-mq/issues/1#issuecomment-316687629","issue_url":"https://api.github.com/repos/Algodev-github/bfq-mq/issues/1","id":316687629,"user":{"login":"paolo-github","id":11974534,"avatar_url":"https://avatars3.githubusercontent.com/u/11974534?v=4","gravatar_id":"","url":"https://api.github.com/users/paolo-github","html_url":"https://github.com/paolo-github","followers_url":"https://api.github.com/users/paolo-github/followers","following_url":"https://api.github.com/users/paolo-github/following{/other_user}","gists_url":"https://api.github.com/users/paolo-github/gists{/gist_id}","starred_url":"https://api.github.com/users/paolo-github/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paolo-github/subscriptions","organizations_url":"https://api.github.com/users/paolo-github/orgs","repos_url":"https://api.github.com/users/paolo-github/repos","events_url":"https://api.github.com/users/paolo-github/events{/privacy}","received_events_url":"https://api.github.com/users/paolo-github/received_events","type":"User","site_admin":false},"created_at":"2017-07-20T12:27:27Z","updated_at":"2017-07-20T12:27:27Z","body":"\n> Il giorno 20 lug 2017, alle ore 13:47, monotykamary <notifications@github.com> ha scritto:\n> \n> I wasn't too sure where to post this issue, but I'll post it here since the patches I format are directly from this repository. I've have formatted patch snapshots of bfq-mq and tested them with the ck-patchset and the stock kernel.\n> \n> In testing 4.11-ck1 and 4.11-ck2 with bfq-mq, hard lockups occurred when the disk was idle or very close to idle. I have not tested for latency, but system ran as expected (with no problems) only if I am running multiple make threads or an application with moderate I/O load.\n> \n\nHi,\nthanks for reporting these issues.  Unfortunately, bfq-mq is just a\ndev branch, used to support the development of bfq for blk-mq.\nCurrently it is based against 4.13-rc1, and, to avoid a maintenance\nburden that I cannot afford, I have not made any bfq-mq-v4.11 branch :(\n\nSo, I can only guess the likely cause of these failures: bugs in the\nthe middle bfq-mq version that you happened to use to make upper\npatches.\n\n> My workload at the time mainly consisted of testing patches and compiling kernels. With the ck-patchset and bfq-mq, as soon as a compile job was done and after a random amount of time, the system locks up. I assumed that this was a scheduler issue related with my CPU, so I left it as is.\n> \n> However, I saw similar cases when testing the stock kernel with the patch from 4.11.1 onwards, but it happened somewhat rarely so I didn't pay much attention to it. I experienced the same issue recently with the stock Arch Linux kernel 4.12.1 onwards when enabling bfq, and once more on kernel 4.12.2 + patch to the current commit (+ patch to include block merge for 4.13). It is to the point where it locks up before I finish starting up my usual applications.\n\nSo, you are sure you have ALL the commits in 4.13-rc1?  I'm asking\nbecause 4.13-rc1 contains important fixes for bfq that didn't make it\nto 4.12 (because it was too late when they were ready).\n\n>  mq-deadline and kyber work with no problems along with all the single-queue I/O schedulers so it doesn't seem like a hardware issue regarding my HDD. Out of source bfq has worked flawlessly.\n> \n> I don't think I've made any issues in formatting the patch\nWhat patches exactly?  Aren't you talking about bfq in mainline now\n(and not any out-of-tree bfq)?\n\n\n> since it applies very cleanly on git and on build, although I could be very wrong. The hard lockups will not respond to sysrq keys and there are no journal logs. I'm a bit troubled as to what to do to get more information on this.\n> \n\nIf you are sure that you do have all 4.13-rc1commits in your kernel,\nthen the only solution for you, according to what your report, is to\nuse netconsole.  This would of course help all the community too.  If\nyou are willing to proceed, then please continue our discussion on the\nofficial bfq group:\nhttps://groups.google.com/forum/#!forum/bfq-iosched\n\nThanks,\nPaolo\n\n> Machine:   Device: portable System: Dell product: Inspiron 3421\n>            Mobo: Dell model: Inspiron 3421 v: A01 BIOS: Dell v: A01 date: 11/05/2012\n> CPU:       Dual core Intel Core i5-3317U (-HT-MCP-) cache: 3072 KB\n>            clock speeds: max: 2600 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz\n> Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller\n>            Card-2: NVIDIA GK107M [GeForce GT 640M]\n>            Display Server: X.Org 1.19.3 drivers: nvidia,intel Resolution: 1366x768@59.97hz\n>            OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile version: 4.2 Mesa 17.1.5\n> Audio:     Card Intel 7 Series/C216 Family High Definition Audio Controller driver: snd_hda_intel\n>            Sound: Advanced Linux Sound Architecture v: k4.12.2-1-ARCH\n> Network:   Card-1: Broadcom Limited BCM43142 802.11b/g/n driver: bcma-pci-bridge\n>            IF: N/A state: N/A mac: N/A\n>            Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169\n>            IF: enp9s0 state: down mac: e0:db:55:8d:dc:af\n>            Card-3: Qualcomm Atheros AR9271 802.11n driver: ath9k_htc\n>            IF: wlp0s29u1u2 state: N/A mac: N/A\n> Drives:    HDD Total Size: 1000.2GB (34.4% used)\n>            ID-1: /dev/sda model: TOSHIBA_MQ01ABD1 size: 1000.2GB\n> Partition: ID-1: / size: 904G used: 310G (37%) fs: ext4 dev: /dev/sda4\n>            ID-2: swap-1 size: 12.88GB used: 0.00GB (0%) fs: swap dev: /dev/sda3\n> Sensors:   System Temperatures: cpu: 48.0C mobo: N/A\n>            Fan Speeds (in rpm): cpu: N/A\n> \n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly, view it on GitHub, or mute the thread.\n> \n\n"}}
{"actor":{"display_login":"paolo-github"}}