|
Bugzilla – Full Text Bug Listing |
| Summary: | oops during usb disconnect of external dvb-t device (dvb_usb_a800) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Dirk Mueller <dmueller> |
| Component: | Kernel | Assignee: | Greg Kroah-Hartman <gregkh> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 7 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | oops | ||
|
Description
Dirk Mueller
2006-03-13 15:48:17 UTC
Created attachment 72584 [details]
oops
Greg, can you help? The USB dvb code is fragile and breaks often :( Gerd, any thoughts? I don't have the hardware for this, and the dvb project is developed outside of the USB kernel project, so I have no familarity with the code... Hmm, the oops is in the dvb core code, not the driver. It's not instantly obvious where the oops comes from. I suspect the whole dvb subsystem needs a audit to make it survive such an event ... As no one here has experience with these devices, and they are marked unsupported, I really don't know what to do here. I'll mark this LATER if that's not a problem for you. well, I reported it against SL where "supported.conf" doesn't have any relevance anyway ;) I'm fine with it, but I wanted to notice that this used to work just fine. mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;( |