Sorry, I just realized that in gmail `Default reply behaviour` was set to `Reply` not `Reply All`, so I skipped the list when I replied last(for I forgot to select Reply All as I did before). Oops. So now hopefully everyone else can see the quoted previous email below. On Mon, Aug 8, 2016 at 4:35 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Mon, 8 Aug 2016, ican realizeum wrote: > >> Roger that. Here's what I found out: >> if I try to sysrq+o (aka poweroff) manually from a file that systemd >> runs at shutdown such as manually created a+x file: >> /usr/lib/systemd/system-shutdown/debug.sh >> >> then I get no ohci errors, >> screenshot: https://i.imgur.com/VVeAyj7.jpg >> only the "PME# disabled" and "enabling bus mastering" are seen. >> But if I allow the kernel(and/or whatever else happens before that) to >> do it, then the errors are back just like in my original post. > > The difference isn't clear. > >> The stack is this: >> https://i.imgur.com/9wlbure.jpg >> but it looks like something else called that and I don't know >> what(looks forked?), unless it's something from the following stack >> from the point where "Stop disk" happens: >> https://i.imgur.com/z9uq4ez.jpg >> Maybe I'll find out something from there. > > The caller was hcd_resume_work(), which is part of a workqueue. This > routine runs when the OHCI driver calls usb_hcd_resume_root_hub(). > There are only 3 places in the driver where this happens (two in > ohci-hcd.c and one in ohci-hub.c), but as far as I can tell, none of > them should have occurred if power/control was set to "on". If you > want, you can add an ohci_info() before each of those calls; knowing > which one it was will probably tell us what happened. > > However, this doesn't answer the question of why the resume failed. > My best guess is that it failed because something it needed had already > been shut down. > > Alan Stern > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
