|
Bugzilla – Full Text Bug Listing |
| Summary: | error output during 2nd stage textmode installation | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Arvin Schnell <aschnell> |
| Component: | YaST2 | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aschnell, jeffm, jslaby, mc, mrmazda |
| Version: | Milestone 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
screenshot
YaST logs screenshot from console 1 screenshot from console 10 |
||
|
Description
Arvin Schnell
2010-04-09 16:39:34 UTC
Created attachment 353509 [details]
screenshot
Created attachment 353510 [details]
YaST logs
The error text is a kernel message. The message 'end_request: I/O error, dev fd0, sector 0' from the screenshot was also written to the file /tmp/tmp.UgEe17uujP/dmesg from attached YaST2 logs. Why is this a kernel error? This is a typical message that is dumped when something probes a floppy drive where the drive either isn't present or doesn't have any media. If the issue is that the messages are overwriting YaST, then that's an installation issue. It means that the messages weren't properly redirected to a different console. No redirect is missing. A simple cat /dev/fd0 with redirects triggers the output (see c1.png). The message is also logged on console 10 (see c10.png). Created attachment 356436 [details]
screenshot from console 1
Created attachment 356437 [details]
screenshot from console 10
This has been happening for more than a month after normal boots after installation while ordinary login is active on tty[1-6], either a simple shell prompt, or running ncurses yast or mc. Weird, nothing except KERN_EMERG messages should be printed to the current console. And fd errors are KERN_ERR. It is OK that it goes to tty10 though. What's the contents of your /proc/sys/kernel/printk? I don't understand why it is printed at all. The block request should probably be REQ_QUIET. Seems to be fixed by someone in 11.3 GM. |