Bug 99418
| Summary: | kernel upgrading to 2.6.0-0 test | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Andy_M <verttigo> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 9 | CC: | alan.cramer, eric, riel |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-01-28 08:57:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I saw a very simular event after installing the new 2.6.0-0 test kernel. I also noticed named complaining when the service started up: process `named' is using obsolete setsockopt SO_BSDCOMPAT process `named' is using obsolete setsockopt SO_BSDCOMPAT process `named' is using obsolete setsockopt SO_BSDCOMPAT process `named' is using obsolete setsockopt SO_BSDCOMPAT process `named' is using obsolete setsockopt SO_BSDCOMPAT process `named' is using obsolete setsockopt SO_BSDCOMPAT the named error messages are a problem with bind, "setsockopt SO_BSDCOMPAT" has been obsolete since kernel version 2.2 or so and does nothing (I think Linux sockets are already BSD compatible); the 2.6 kernel simply prints an error message to catch those last few applications using this interface (which has been obsolete for more than 6 years) Andy_M's problem does look genuine, though... Should I open a new bug regarding the named problem then? I am using the standard bind packages from RH 9. yes please do a separate bug for named. the usb issue can be that the usb modules got renamed between 2.4 and 2.6; we're working on making modutils autoconvert but it currently doesn't. the new name is uhci-hcd.ko while modutils probably tries to load uchi.ko renaming or making a symlink should show if this assumption of "different module name" is correct or not. mine tends to tell me that usb-ochi module could not be found. would this be linked to modules.conf or rc.sysinit? tried again with kernel-2.6.0-0.test1.1.26 and got the same error above (couldn't find usb_ochi.ko ) and i also got told this time that mousedev was already in the kernel. no usb mouse and same problem with usb-ochi in kernel-2.6.0-0.test2.1.28. is there something i am not doing that i should be? Upgraded to kernel-2.6.0-0.test2.1.29 Upon booting, it complains about usb-ochi as usual. This time however instead of complaining about mousedev and keybdev already being in the kernel, it now says that it couldn't be found. once i got into X, i switched to a new console via Ctrl+Alt+F1, logged in as root and invoked modprobe ochi-hcd and it worked for the first time, and now the mouse is working. Just need to fix it during boot somehow. If someone can point me to the right place, I should be able to fix it myself. I also can not view the RPM database, or install any RPM when booted into the 2.6.0 kernel. I get the following: [root@badboy root]# rpm -qa | grep kernel rpmdb: unable to join the environment error: db4 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages index using db3 - Resource temporarily unavailable (11) error: cannot open Packages database in /var/lib/rpm [root@badboy root]# --------- Rebooting into the 2.4.20-13.9 allows RPM to work normally the later is an RPM bug.... known. The usb stuff should be more or less all taken care of with current kernels + modutils. Please file other bugs separately, thanks! |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425 Description of problem: not usb keyboard and mouse could be used after upgrading from 2.4.20 to 2.6.0 kernel version. Version-Release number of selected component (if applicable): kernel upgrading to 2.6.0-0 test How reproducible: Always Steps to Reproduce: 1.n/a 2. 3. Additional info: