Bug 443855
| Summary: | kernel 2.6.24.4-64 breaks xsane device scanning | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gus Wirth <gwirth79> | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | low | Docs Contact: | |||||||||||
| Priority: | low | ||||||||||||
| Version: | 8 | CC: | nphilipp | ||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i386 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | 2.6.25.6-27.fc8 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2009-01-09 07:47:32 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: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Gus Wirth
2008-04-23 18:14:41 UTC
selinux is set to permissive mode. Running the xsane program as root has no effect. From your description I understand that it works if you boot into the old kernel. I'll change the component to kernel then. Mind that you should try to reproduce the problem without any proprietary kernel modules loaded (i.e. an untainted kernel). Yikes! Things have been working so well for so long that I forgot about that. I've gotten rid of the offending modules and retested with the same results. Snippet of /var/log/messages: Apr 30 20:34:34 falcon kernel: ppdev: user-space parallel port driver Apr 30 20:34:34 falcon xsane: io/hpmud/model.c 513: no HP_LaserJet_4ML attribute s found in /usr/share/hplip/data/models/models.dat Apr 30 20:34:34 falcon xsane: io/hpmud/model.c 524: no HP_LaserJet_4ML attribute s found in /usr/share/hplip/data/models/unreleased/unreleased.dat Apr 30 20:34:34 falcon xsane: io/hpmud/pp.c 1239: ignoring hp:/par/HP_LaserJet_4 ML?device=/dev/parport0 support=0 Apr 30 20:34:34 falcon kernel: sysctl table check failed: /dev/parport/parport0/ devices/ppdev0/timeslice Sysctl already exists Apr 30 20:34:34 falcon kernel: Pid: 2545, comm: xsane Not tainted 2.6.24.4-64.fc 8 #1 Apr 30 20:34:34 falcon kernel: [<c0442bef>] set_fail+0x3b/0x43 Apr 30 20:34:34 falcon kernel: [<c0443006>] sysctl_check_table+0x40f/0x460 Apr 30 20:34:34 falcon kernel: [<c04352d5>] sysctl_head_finish+0x18/0x22 Apr 30 20:34:34 falcon kernel: [<c044301a>] sysctl_check_table+0x423/0x460 Apr 30 20:34:34 falcon kernel: [<c04352d5>] sysctl_head_finish+0x18/0x22 Apr 30 20:34:34 falcon kernel: [<c044301a>] sysctl_check_table+0x423/0x460 Apr 30 20:34:34 falcon kernel: [<c04352d5>] sysctl_head_finish+0x18/0x22 Apr 30 20:34:34 falcon kernel: [<c044301a>] sysctl_check_table+0x423/0x460 Apr 30 20:34:34 falcon kernel: [<c04352d5>] sysctl_head_finish+0x18/0x22 Apr 30 20:34:34 falcon kernel: [<c044301a>] sysctl_check_table+0x423/0x460 Apr 30 20:34:34 falcon kernel: [<c04352d5>] sysctl_head_finish+0x18/0x22 Apr 30 20:34:34 falcon kernel: [<c044301a>] sysctl_check_table+0x423/0x460 Apr 30 20:34:34 falcon kernel: [<c043429d>] sysctl_set_parent+0x19/0x2a Apr 30 20:34:34 falcon kernel: [<c0435536>] register_sysctl_table+0x45/0x7e Apr 30 20:34:34 falcon kernel: [<f8a12294>] parport_device_proc_register+0xa2/0 xbc [parport] Apr 30 20:34:34 falcon kernel: [<f8a10b1b>] parport_register_device+0x1bb/0x20c [parport] Apr 30 20:34:34 falcon kernel: [<f89c66ff>] pp_ioctl+0x13b/0x700 [ppdev] Apr 30 20:34:34 falcon kernel: [<f89c61c6>] pp_irq+0x0/0x45 [ppdev] Apr 30 20:34:34 falcon kernel: [<c04930cc>] do_ioctl+0x4c/0x62 Apr 30 20:34:34 falcon kernel: [<c0493319>] vfs_ioctl+0x237/0x249 Apr 30 20:34:34 falcon kernel: [<c0493370>] sys_ioctl+0x45/0x5d Apr 30 20:34:34 falcon kernel: [<c04051da>] syscall_call+0x7/0xb Apr 30 20:34:34 falcon kernel: ======================= Can you run the 'dmesg' command after the program that's reading the scanner hangs and upload that? Also run this command while the program is hanging and upload what it writes to the syslog: echo "t" >/proc/sysrq-trigger Don't drop them in the comment box, create individual attachments and set the type to text/plain. Created attachment 304315 [details]
dmesg with xsane stuck
Created attachment 304316 [details]
messages resulting from echo "t" > /proc/sysrq-trigger
Created attachment 304318 [details]
dmesg with xsane stuck
I did a reboot to get a clean dmesg.
A simple work-around is to disconnect the printer before starting xsane. With the printer disconnected, xsane works as expected. Created attachment 304430 [details]
dmesg without printer attached
This is fixed with kernel-2.6.25.6-27.fc8 on Fedora 8. It might have been fixed sooner but I didn't test it till now. This broke again with kernel-2.6.26.5-28.fc8 and kernel-2.6.26.6-49.fc8 in exactly the same way. Should I file a new bug report or can this one be reopened? This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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 Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |