|
Bugzilla – Full Text Bug Listing |
| Summary: | shpchp module loaded even on laptop | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Andreas Jaeger <aj> |
| Component: | Kernel | Assignee: | Greg Kroah-Hartman <gregkh> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Jaeger
2005-08-27 14:38:59 UTC
Because that's the way the driver shows it self "can accept any pci bridge device" I'd suggest just blacklisting it, or unloading it, it's harmless. Should we black list it in general - or is this something I should do just on my system? Well, 99% of the systems will not have this chip, but for that 1% that do, blacklisting it in general will cause those users to be upset. So, for your system, yes, you should blacklist it. For any laptop, yes. I don't know what the rules are for blacklisting stuff in general though. Hannes, any ideas? Can't we be a bit smarter here? Are there any information in the PCI config which could help us? In general, of course we could blacklist it; just add a line alias shpchp = off to /etc/modprobe.conf. Not very selective, though. The smarter way would be to have a hwcfg file for this slot, ie hwcfg-bus-pci-0000.00:13.0 with just the lines: STARTMODE='boot' MODULE='' in it. That would prevent the loading of any module for this specific slot. Of course, this would mean YaST has to write it. And knowing how stretched the YaST resources are I doubt we're getting this ... Greg, how does this driver know whether it can do anything sensible here? Does it even know that? Don't use alias shpchp = off but blacklist shpchp Then it won't just be loaded automatically but a hwcfg-* would make it loaded. The problem is that with udev_log=err (default) you won't see the message that this module is blacklisted. You only see it with udev_log=info. Does it do any harm if it is loaded? No, it doesn't do any harm if it is loaded. I'll see if I can change the driver to only let it load when needed, instead of for every pci bridge... Is not going to happen for SLES10 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 ;( |