{"action":"created","issue":{"url":"https://api.github.com/repos/openbmc/openbmc/issues/191","repository_url":"https://api.github.com/repos/openbmc/openbmc","labels_url":"https://api.github.com/repos/openbmc/openbmc/issues/191/labels{/name}","comments_url":"https://api.github.com/repos/openbmc/openbmc/issues/191/comments","events_url":"https://api.github.com/repos/openbmc/openbmc/issues/191/events","html_url":"https://github.com/openbmc/openbmc/issues/191","id":136482176,"number":191,"title":"OCC errors on host shutoff","user":{"login":"KennethWilke","id":2534692,"avatar_url":"https://avatars.githubusercontent.com/u/2534692?v=3","gravatar_id":"","url":"https://api.github.com/users/KennethWilke","html_url":"https://github.com/KennethWilke","followers_url":"https://api.github.com/users/KennethWilke/followers","following_url":"https://api.github.com/users/KennethWilke/following{/other_user}","gists_url":"https://api.github.com/users/KennethWilke/gists{/gist_id}","starred_url":"https://api.github.com/users/KennethWilke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KennethWilke/subscriptions","organizations_url":"https://api.github.com/users/KennethWilke/orgs","repos_url":"https://api.github.com/users/KennethWilke/repos","events_url":"https://api.github.com/users/KennethWilke/events{/privacy}","received_events_url":"https://api.github.com/users/KennethWilke/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-25T19:13:02Z","updated_at":"2016-02-25T20:12:42Z","closed_at":null,"body":"Howdy OpenBMC folks,\r\n\r\nWe've noticed that sometimes we'll get a bunch of OCC related errors after a shutoff, and wanted to see if this is expected behavior.\r\n\r\n```\r\nroot@barreleye:~# obmcutil poweroff\r\nocc-i2c 3-0051: ERROR: sensor type FREQ not supported\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -1\r\n = None\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nroot@barreleye:~# occ-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\nocc-i2c 3-0051: ERROR: OCC data length is zero\r\nocc-i2c 3-0051: ERROR: cannot get occ sensor data: -22\r\n```"},"comment":{"url":"https://api.github.com/repos/openbmc/openbmc/issues/comments/188959695","html_url":"https://github.com/openbmc/openbmc/issues/191#issuecomment-188959695","issue_url":"https://api.github.com/repos/openbmc/openbmc/issues/191","id":188959695,"user":{"login":"nkskjames","id":2212755,"avatar_url":"https://avatars.githubusercontent.com/u/2212755?v=3","gravatar_id":"","url":"https://api.github.com/users/nkskjames","html_url":"https://github.com/nkskjames","followers_url":"https://api.github.com/users/nkskjames/followers","following_url":"https://api.github.com/users/nkskjames/following{/other_user}","gists_url":"https://api.github.com/users/nkskjames/gists{/gist_id}","starred_url":"https://api.github.com/users/nkskjames/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nkskjames/subscriptions","organizations_url":"https://api.github.com/users/nkskjames/orgs","repos_url":"https://api.github.com/users/nkskjames/repos","events_url":"https://api.github.com/users/nkskjames/events{/privacy}","received_events_url":"https://api.github.com/users/nkskjames/received_events","type":"User","site_admin":false},"created_at":"2016-02-25T20:12:42Z","updated_at":"2016-02-25T20:12:42Z","body":"This is known behavior.  Basically we disable the OCC driver after we get a host powered off message.  There is a window between when host is powered off and this disabling of the driver when it still tries to read the OCC, but it can't because host is powered off.  It won't hurt anything and one day it will be cleaned up."}}