Bug 14164
Summary: | "Unknown boot option" warning message should not be printed for options which will be passed to kernel modules | ||
---|---|---|---|
Product: | Other | Reporter: | Adam Williamson (adamw) |
Component: | Other | Assignee: | Rusty Russell (rusty) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | alan, jcm, mishu, rdunlap, rusty |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | all | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Adam Williamson
2009-09-11 16:28:54 UTC
Is this because modern modprobe is scraping these options from /proc/cmdline? If so, yes, we should suppress those messages altogether. CC'd Jon, he'd know. I don't know how it's implemented, exactly, that may well be how it works. I just know that you can pass any module parameter as a kernel command line parameter in that format (modulename.moduleparameter=value) and it gets passed on somehow. ping? this still regularly causes confusion for users when we're trying to debug various issues, see https://bugzilla.redhat.com/show_bug.cgi?id=538840#c3 for a recent example: it's a 'cosmetic' bug but with unfortunate effects. Yea, exactly that's what happens. Modprobe pulls out those arguments and processes them. I don't know why I missed this bug, but that should be fixed now. I even have daily reminders setup and should get CC'd on every module issue from now on. |