CONFIG_BOOT_PRINTK_DELAY is not set
Bug #733191 reported by
Tim Gardner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Tim Gardner | ||
| Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
| Maverick |
Fix Released
|
Undecided
|
Tim Gardner | ||
| Natty |
Fix Released
|
Undecided
|
Tim Gardner | ||
Bug Description
CONFIG_
| Changed in linux (Ubuntu Maverick): | |
| assignee: | nobody → Tim Gardner (timg-tpi) |
| status: | New → In Progress |
| Changed in linux (Ubuntu Natty): | |
| assignee: | nobody → Tim Gardner (timg-tpi) |
| status: | New → In Progress |
| tags: | added: verification-needed-maverick |
To post a comment you must log in.

SRU Justification
Impact: Kernel oops are difficult to read after scrolling past. This parameter inserts a print delay that is used to slow the output to the console.
Patch Description: Enable CONFIG_ BOOT_PRINTK_ DELAY. This has no run time impact unless the kernel command line parameter boot_delay is set.