Bug 42640
Summary: | Realtek RTS5116 card reader produces errors during boot | ||
---|---|---|---|
Product: | Drivers | Reporter: | Disabled Account (disabled_20190211) |
Component: | MMC/SD | Assignee: | drivers_mmc-sd |
Status: | NEW --- | ||
Severity: | normal | CC: | c3904a4a, chris, eric.donkersloot, gmiramir, szg00000 |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.2.1 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Disabled Account
2012-01-23 16:25:01 UTC
So is anyone going to look into this? I think there's lots of people just putting up with these errors, but it looks like ** fill out any nasty word here ** This isn't an SD/MMC driver, it's a SCSI driver: rts_pstor, in staging. Because it's a staging driver, it's not supported and it's not very surprising that you're seeing bugs in it. It looks like the primary author is "wwang <wei_wang@realsil.com.cn>" -- you could try getting in touch. I also have this "Bad target number" and my card reader doesn't work, so I've submitted an emaill to this wwang and I hope we can get this fixed in 3.2x kernels... After reading this from Patrick Volkerding of Slackware, I figured if it's good enough for Pat, that's good enough for me and reason enough I want to stay with 3.2x also, but I really want to see/need to see this fixed! Quote from Patrick Volkerding; After hearing that the 3.4.x kernel series will have long-term support, I tested 3.4.9 hoping that it would prove stable enough to use that as the release kernel, but there are problems with an oops in clocksource.c every few boots. Given that the 3.2.x series has been very stable, it seems prudent to stick with that for release, and 3.2.28 is going to be the release kernel. *** Bug 46681 has been marked as a duplicate of this bug. *** Please try this bug with latest kernel image. |