Bug 1198335
| Summary: | no response from server machine after attaching busid | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tomas Lestach <tlestach> | ||||
| Component: | usbip | Assignee: | Jonathan Dieter <jonathan> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 21 | CC: | jonathan, tkasparek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-18 14:25:11 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Tomas Lestach
2015-03-03 20:12:08 UTC
I suspect this is a kernel panic, because the system completely stops responding. Is there any way you can set up a serial console so we can get the kernel's error messages? I don't have a Pi 2, so I don't really have a way of testing this myself. If there's no way to do a serial connection, perhaps look into netconsole. I'm seeing conflicting information as to whether it's useful for kernel panics after the system has booted (it's definitely useless when trying to trace early kernel panics). I'll try to get a cable for the serial console. Created attachment 998537 [details]
captured output form the serial console
Here we go. I got the serial console and I'm attaching the captured output. Is that, what you need?
Yes, at least in that it shows that we're hitting a kernel bug rather than a userspace problem. It looks like the problem is when the USB/IP driver unlinks the usb device on the host so it can make it available, but to debug this further will require building a debug kernel for the RPi2. The real issue is that I'm most definitely not a kernel developer and we're rapidly reaching the point where I'm out of my depth. So we can go one of two ways. Either I can post this bug to linux-usb.org, or you can. If I do it, I'll be adding another layer between the bug reporter and the potential bug fixer, so I'd prefer to let you go there directly. On the other hand, if you'd rather I try to deal with it, I'm happy to do so. Either way, the first step is to build a debug kernel. I'd appreciate, if you could post it as I'm afraid I couldn't answer any of the possible kernel or usbip questions. But feel free to put me into CC, so I can get any additional information, when needed. Ok, that's fine. Can you please build a debug kernel, preferably with something like https://repos.fedorapeople.org/repos/thl/kernel-vanilla-mainline/fedora-21/SRPMS/kernel-4.0.0-0.rc2.git0.1.vanilla.mainline.knurd.1.fc21.src.rpm as its base, and upload the serial console output from that. Hello Jonathan,
even if I've built the debug kernel (the build process took almost 8 hours), I wasn't able to boot it, yet.
However I updated the kernel to raspberrypi-kernel-3.18.9-501.20150308git780e681.sc20.armv7hl and was able to attach and use the USB port over IP!
It works like expected, the issue must have been fixed in the mentioned kernel!
client:
# usbip port
Imported USB devices
====================
Port 01: <Port in Use> at High Speed(480Mbps)
unknown vendor : unknown product (04f9:0331)
9-2 -> usbip://192.168.88.239:3240/1-1.5
-> remote bus/dev 001/004
# lsusb
Bus 009 Device 028: ID 04f9:0331 Brother Industries, Ltd
...
# scanimage -L
device `brother4:bus1;dev1' is a Brother MFC-L2700DW USB scanner
...
Let me use and watch it for couple of days to make sure, it's stable.
I'm sorry you weren't able to run the debug kernel, but I'm glad the latest kernel seems to fix the problem. Let me know if you run into any more problems. Seeing as there don't seem to have been any problems in the last few months, I'm closing this. Please reopen if the problem has persisted. |