[Bug 665720] New: /etc/sysconfig/keyboard is ignored in VTs
https://bugzilla.novell.com/show_bug.cgi?id=665720 https://bugzilla.novell.com/show_bug.cgi?id=665720#c0 Summary: /etc/sysconfig/keyboard is ignored in VTs Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mrmazda@earthlink.net QAContact: qa@suse.de Found By: --- Blocker: --- http://lists.opensuse.org/opensuse-factory/2011-01/msg00022.html is where I first posted this to mailing list two weeks ago, but that thread has generated no responses from anyone but me. At least two systems exhibiting this had fresh installs considerably before this started, updated via zypper dup numerous times either from a milestone iso or from online Factory repos. That which I know for sure is being ignored as of kernel-2.6.37-18-desktop: KBD_DELAY="250" KBD_RATE="20" KBD_NUMLOCK="yes" Delay doesn't seem too far off, but rate is considerably higher than 20, and NUM, which is on on POST via BIOS, stays off in all vts after the kernel has turned it off. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c3
--- Comment #3 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c4
--- Comment #4 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c
Philipp Thomas
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c5
--- Comment #5 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c6
--- Comment #6 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c7
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c8
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c9
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c10
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c11
--- Comment #11 from Felix Miata
When you run kbdrate -r 20 -d 250 on a system that it isn't working on, does it fix it? If not, can you provide the output of strace <kbdrate command>?
Likewise with setleds +num.
I finally remembered to try this on a M6 system (kt880) before duping to RC1. kbdrate & setleds from root prompt do what they're supposed to do. I did double check, and the problem is only exhibited on alternate boots, except if because on current boot it was ignored I've run kbdrate & setleds manually, in which case on subsequent boot it was ignored again, breaking the alternate boot pattern. All the above only applied if restart was via command 'init 6' (>6 successive boots). Then I switched to restart via command 'reboot' for the next several boots, in which keyboard file was always ignored, and after switching back to 'init 6' for three more boots; then since (>8 successive boots), the alternate boot pattern has been back. In all of this testing specifically for this bug I've only been booting into runlevel 3, via 3 on Grub cmdline, in part because of common loss of sync between NUM state and NUM led when switching back & forth between X & consoles. Then on an init 6 restart I removed the 3 from Grub's cmdline. KDM came up, I switched to tty2, found NUM lit with NUM state on and kbd repeat at 20, logged in root, ran an rpm query, logged out, went back to KDM, and selected restart. On restart I again removed 3 from Grub cmdline before proceeding, but this time I was left on tty1, with NUM led off to see "...runlevel 5 has been reached", and no access to X's tty7. I logged in root on tty2, then 'init 3; init 5' to reach KDM, switched back to tty2 to find NUM state off but NUM led on, and kbd rate maximized. I exited login, switched to KDM, selected reboot, removed 3 from Grub cmdline again, and found myself left on tty1 in runlevel 5 same as last restart. I repeated this 5/KDM restart process once more with same result. Tired of this, I changed repos to RC1 iso only, zypper ref; zypper al kernel-desktop; zypper dup, and repeated booting via command 'reboot'. /etc/sysconfig/keyboard was obeyed on 3-4 successive runlevel 3 boots, then not on the next. So, I 'zypper rl kernel-desktop', switched repo from RC1 iso to factory's OSS & non-OSS, 'zypper ref', 'zypper in kernel-desktop', and rebooted via command 'reboot'. That resulted in no boot, just GRUB. I fixed Grub using Knoppix CD, then booted RC1, and rebooted 4 times using 'init 6'. /etc/sysconfig/keyboard's NUM, delay and rate settings were disobeyed every time. Then I restarted using 'reboot', and they were obeyed. I did it again, and they were not, and again twice more, both not. Then I tried 'init 6' again, and they were obeyed, and again thrice, but next two not after turning NUM on manually each time, and next not after turn NUM on manually, then turning it back off before init 6. Next I left NUM off, but after init 6 again disobeyed 7 cycles before being obeyed again. Next disobeyed runlevel 3 boot, after login I did 'init 1', typed root password, 'init 3', and enjoyed normal runlevel 3 function. Next I booted via 'reboot' directly to runlevel 1, typed root password, 'init 3', and happiness again, at least 7 straight cycles.
From where I sit, this is seriously wierd, and very annoying, since network does not come up automatically on every normal (3) boot when keyboard settings are ignored.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c12
--- Comment #12 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c13
--- Comment #13 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c14
--- Comment #14 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c15
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c16
--- Comment #16 from Lars Müller
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c17
--- Comment #17 from Felix Miata
What makes you think this is a dup as you wrote in comment 15?
You mean besides the fact that sometimes services start and sometimes not, or that the services that start or not aren't always the same, or that sometimes init never finishes?
BTW 8 weeks ago nobody talked about RUN_PARALLEL of /etc/sysconfig/boot.
Which is an unfortunate result of the lack of attention to this bug or the Factory mailing list thread(s?) I started back then.
A comment like #2 in bug#680297 sounds rude.
That comment was an expression of frustration that so little attention was given to a bug that might have been fixed or a workaround provided in relnotes before 11.4 went GA. No such intent was meant, and I'm sorry you feel that way. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c18
Stephan Barth
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c19
--- Comment #19 from Lars Müller
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c20
--- Comment #20 from Mark Goldstein
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c21
--- Comment #21 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c22
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c23
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c24
--- Comment #24 from Felix Miata
Parallel boot isn't a kernel issue.
Per comment 1 vanilla kernel is alternate solution, so why couldn't it be a kernel issue? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c25
--- Comment #25 from Felix Miata
(In reply to comment #57)
My guess is more dbus and ConsoleKit. For a try please disable dbus for next boot
insserv -fr dbus
"Next" boot so as to attempt to do that completely hung at Starting D-Bus daemon. Any chance this is a kernel issue related to (enabled) HyperThreading CPU rather than a single core or multicore CPU? Most mounts md RAID?
... as this is not a solution we have to investigate this precisely.
Beside this with a working blogd you may have a look into /var/log/boot.msg you can compare the time stamps in the <notice> entries for the dbus service.
Attached -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c26
--- Comment #26 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c27
--- Comment #27 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c28
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c29
--- Comment #29 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c30
Dr. Werner Fink
You have to specify a comment when changing the status of a bug from RESOLVED to REOPENED.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c31
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c32
Felix Miata
Felix? Now what is going on? As blogd works now I'd like to ask what has caused the remaining problem on our system.
host big31 http://www.smolts.org/client/show_all/pub_f2e7a2ea-9a3d-4f4e-9ee5-4a2252755b... currently on kernel 2.6.37.4-1-default as indicated in comment 28 attachment, and unlike my other test systems runs on md RAID1, simply stops part way throught init on a random basis, that is, several or more boots proceed normally, but eventually boot simply won't finish. Since comment 31 I booted it 6 straight times successfully with parallel boot disabled, then saw in the boot.msg between EOF and tail of comment 28 attachment 14 lines, 5 of which were blank, all about acpid and cpufreq. Then I reenabled parallel boot, and booted it 4 straight times normally & successfully. #5 was very slow after: Master Resource Control: previous runlevel: N, switching to runlevel: ... 3 Master Resource Control: Running /etc/init.d/before.local ... done acpid: starting up with proc fs acpid: 2 rules loaded acpid: waiting for events: event logging is off Starting acpid ... done Starting D-Bus daemon ... done Loading CPUFreq modules - hardware support not available ... skipped Checking/updating CPU microcode ... done Starting syslog services ... done That's where it sat 10+ minutes after trying to boot. Then it sat several more minutes, as CAD failed to actually cause a reboot after "INIT: Switching to runlevel: 6; INIT: Sending processes the TERM signal; INIT: Sending processes the KILL signal". I hit the reset button, then chose 2.6.37-20-vanilla, which booted normally. I then replaced 2.6.37-20-vanilla with 2.6.37.6-4-vanilla and booted normally 4 straight times, which seemed to me to indicate this was indeed an openSUSE kernel bug, until boot #5 hung even earlier than with desktop kernel, at "Starting D-Bus daemon ... done", and CAD failed to reboot again. I did notice that shutdown/reboot from boot #4 had a noticeable pause. 11.2 on same system always boots completely. # zypper wp blogd .. No providers of 'blogd' found. # ??? Where does blogd come from??? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c33
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c34
--- Comment #34 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c35
--- Comment #35 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c36
--- Comment #36 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c37
--- Comment #37 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c38
Felix Miata
You may try as root
type -p blogd
OK
which should result in /sbin/blogd and with
rpm -qf /sbin/blogd
you should see at least sysvinit-tools.
OK
You may also debug your system by disabling script by script to identify the cause of this random hang (compare with comment #29)
Can you look at comment 37 attachment and suggest which to try or which order to try?
Beside this you may use /var/log/boot.omsg after a reboot to see the former boot/shutdown messages and /var/log/boot.msg to investigate the current boot messages.
Comment 35 attachment provided this, which seems to add little to comment 32.
Clearly you should use the blogd from the attachments of the bug #642289
Are you sure? I am already using that blogd now, but zypper lu shows sysvinit & sysvinit-tools installed are 2.88-37.40.1 while 2.88-37.43.1 are available? Should I install those plus available aaa_base, aaa_base-extras and other available updates before proceeding further? If my comment 25 question was answered, I'm missing it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c39
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c40
--- Comment #40 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c41
--- Comment #41 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c42
--- Comment #42 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c43
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c44
Felix Miata
Hmmm ... the mainboard from BIOSTAR could have a problem in Advanced Configuration and Power Interface (ACPI) or the Desktop Management Interface (DMI) ...
Questiion: Are there any updates for the BIOS of the mainboard available?
No BIOS update is available that addresses anything resembling issues described in this bug. http://www.biostar.com.tw/app/en/mb/bios.php?S_ID=355 11.0 and 11.2 always boot right up, and IIRC, so does Knoppix from CD and DVD v 5.3.1, 6.0 & 6.2. I've not yet seen explained how to disable DRM/GPU control, irqbindall, set_kthread_prio. I only know how to disable services that obviously exist in chkconfig --list output, plus nomodeset on cmdline. If there's some doc that explains, please name it. I'm also waiting for an answer to whether there's any point to trying disabling HyperThreading in the BIOS. Note too all my other systems for which blogd solved the parallel boot issues are both slower and older than big31, not running RAID, and not HyperThreading. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c45
Dr. Werner Fink
No BIOS update is available that addresses anything resembling issues described in this bug. http://www.biostar.com.tw/app/en/mb/bios.php?S_ID=355
The hwinfo you've attached shows: DMI: BIOSTAR Group G31-M7 TE/G31-M7 TE, BIOS 080014 05/19/2008 and maybe there have been some fixes in the meanwhile not mentioned.
11.0 and 11.2 always boot right up, and IIRC, so does Knoppix from CD and DVD v 5.3.1, 6.0 & 6.2.
The problem happens by using the kernel from 11.4 not from 11.0, nor 11.2, nor from Knoppix. This could be a bug of the kernel as well as a bug of the mainboard or a bug handling ACPI events of this mainboard or all of them.
I've not yet seen explained how to disable DRM/GPU control, irqbindall, set_kthread_prio. I only know how to disable services that obviously exist in chkconfig --list output, plus nomodeset on cmdline. If there's some doc that explains, please name it.
For drm use lsmod | grep drm and blacklist the module which uses drm_kms_helper in /etc/modprobe.d/99-local.conf, run mkinird afterwards to make this also available in the initrd. Also disable KMS by setting NO_KMS_IN_INITRD to "yes" in /etc/sysconfig/kernel
I'm also waiting for an answer to whether there's any point to trying disabling HyperThreading in the BIOS.
This is openSUSE not SLES
Note too all my other systems for which blogd solved the parallel boot issues are both slower and older than big31, not running RAID, and not HyperThreading.
/usr/src/linux/Documentation/kernel-parameters.txt parameter acpi= ... [...] acpi= [HW,ACPI,X86] Advanced Configuration and Power Interface Format: { force | off | strict | noirq | rsdt } force -- enable ACPI if default was off off -- disable ACPI if default was on noirq -- do not use ACPI for IRQ routing strict -- Be less tolerant of platforms that are not strictly ACPI specification compliant. rsdt -- prefer RSDT over (default) XSDT copy_dsdt -- copy DSDT to memory See also Documentation/power/pm.txt, pci=noacpi [...] Beside this HyperThreading seem to be disabled due hwinfo from attachment #422961 [...] CPU0: Hyper-Threading is disabled [...] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c46
--- Comment #46 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c47
--- Comment #47 from Felix Miata
Felix? do you have any news? That is do you have done some tests with the acpi= kernel parameter?
1-Over half of my machines share physical space, that is, most I use to test with have to be physically moved from storage to a single spot where connection to power, keyboard, trackball & display is possible. Big31 lost its right to that space due to the time lag between the comment 40, 41, 42 group and comment 43 so that I could follow up in timely fashion on bugs not exhibited on big31. 2-Before big31 can get its space back I have to finish with the machine now in shared space, and, must find out how to answer all your questions. I still don't know about how to disable every one of the items listed in comment 29, some of which I asked about again in later comment(s), such as irqbindall & set_kthread_prio. 3-I have my doubts about a BIOS update released more than 4 years after manufacture fixing anything to do with ACPI, particularly since older kernels don't have apparent ACPI trouble. So, no, not yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c48
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c49
--- Comment #49 from Ivan Ganev
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c50
--- Comment #50 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c51
--- Comment #51 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c52
--- Comment #52 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c53
--- Comment #53 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c54
--- Comment #54 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c55
--- Comment #55 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c56
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c57
--- Comment #57 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c58
--- Comment #58 from Dieter Jurzitza
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c59
--- Comment #59 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c60
Mario Guzman
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c61
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c62
--- Comment #62 from Jeff Mahoney
participants (1)
-
bugzilla_noreply@novell.com