|
Bugzilla – Full Text Bug Listing |
| Summary: | unexpected fd0/floppy messages on tty[1-6] | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Felix Miata <mrmazda> |
| Component: | Basesystem | Assignee: | Jiri Kosina <jkosina> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | chcao, mpluskal, tiwai, tonyj |
| Version: | 13.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Tumbleweed y2logs from host gx760 | ||
The error message is due to the "fix" in 3.14 kernel,
7b7b68bba5ef23734c35ffb0d8d82079ed604d33
floppy: bail out in open() if drive is not responding to block0 read
So I suspect that the same access to the floppy device was done even on openSUSE 13.1, but the error wasn't reported.
But I don't know why /proc/partition behavior changed between oS 13.1 and 13.2 regarding floppy...
Jiri, any clue?
(In reply to Takashi Iwai from comment #1) > but the error wasn't reported. The reporters system has the console loglevel set to 7, he doesn't have rsyslog running (which normally lowers it to 1) or quiet on the command line (which normally lowers it to 4). It seems something has changed in the install process. This occurred on 64 bit TW 20150815 host g5eas running kernel 4.1.4 with systemd-logger installed. Installing rsyslog, which removed systemd-logger, removed the problem, though I do hear a floppy access attempt running fdisk -l. Not reproducible on comment 0 host gx760 running 42.3/4.4.92. Same messages appear in dmesg, but not on the ttys. /proc/partitions does have a line item for fd0 even though drive is empty. Same host gx760 booted to TW20171023/4.13.8 does almost same, but floppy error is 10 rather than -5. I do not hear a floppy access attempt running fdisk -l booted to either TW or 42.3, but fd0 error messages do then get logged. This version of openSUSE changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or consider the bug still valid, please feel free to reopen this bug against that version, or open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime |
Created attachment 622338 [details] Tumbleweed y2logs from host gx760 To reproduce: 1-log in on any of tty[1-6] on system with empty floppy drive 2a-fdisk -l; or 2b-hwinfo --[cdrom|disk|ide|partition|redasd|scsi] # pick any one Actual results: 1-expected command output; plus 2-(e.g.) [ 565.922030] blk_update_request: I/O error, dev fd0, sector 0 [ 565.922903] floppy: error -5 while reading block 0 [ 565.949031] blk_update_request: I/O error, dev fd0, sector 0 [ 565.949927] floppy: error -5 while reading block 0 Expected results: 1-expected command output # (only) Notes: 1-Happens with 3.16.7 on 13.2 and 3.18.3 and 3.19.rc7 on Tumbleweed 2-only happens on two (4 installations) of four (8 installations) real hardware multiboot hosts tested (gx760 w/ ICH10D SATA; fi965 w/ ICH8R SATA using mdraid ), not on hosts big41 (NM10/ICH7 SATA) or gx28c (ICH6 SATA) 3-sometimes litter precedes, sometimes follows, sometimes mixed among expected command output, depending on output expected 4-/proc/partitions on 13.2 and TW contain fd0. /proc/partitions on 13.1 using 3.11.10, and Rawhide using 3.19.rc7 do not contain fd0.