| Summary: | error message pops up after set nouveau.modeset=0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | wayneh <wayneh> |
| Component: | kernel | Assignee: | Neil Horman <nhorman> |
| Status: | CLOSED NOTABUG | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2 | CC: | kzhang, rpecorella, syeghiay |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-12-06 15:44:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 756082 | ||
|
Description
wayneh
2011-11-16 11:01:51 UTC
Hi, has anyone had a chance to look at this. Is there a workaround or errata on this problem? Thanks, Richard I don't believe this is related to video at all, seems to be networking from the message. Certainly not nouveau, as with "modeset=0" it's prevented from doing anything. Reassigning so someone may be able to help! Hi Sir, Would you kindly help to check who is able to help me to check this issue? Thanks. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Looks like an error message from the libfcoe stack. Reassigning This isn't a bug at all, its a informational message. and one thats only displayed when the console is in text mode (likely why it only shows up with nouveau.modeset=0), and when libfcoe debugging is enabled. I imagine the customer has libfcoe.libfcoe_debug_logging set on the command line or in one of the modprobe config files. remove that and this will go away, not that it hurts anything anyway. |