At first I thought this was a scanner problem, but I’ve found that if I’m using the mouse while I’m scanning or sometimes just flipping back and forth with my usb kvm the keyboard and mouse become useless. If I’m scanning while I use the mouse, the system locks up. Here is what I’m seeing in /var/log/messages.
After executing xsane:
Feb 12 11:10:41 bnmlinux xsane: io/hpmud/musb.c 1987: invalid usb_open: Permission deniedFeb 12 11:10:41 bnmlinux xsane: io/hpmud/musb.c 1987: invalid usb_open: Permission deniedFeb 12 11:10:41 bnmlinux xsane: io/hpmud/musb.c 1987: invalid usb_open: Permissi
on deniedFeb 12 11:10:41 bnmlinux xsane: io/hpmud/musb.c 1987: invalid usb_open: Permissi
on denied
Feb 12 11:10:41 bnmlinux xsane: io/hpmud/musb.c 1987: invalid usb_open: Permission denied
Feb 12 11:10:41 bnmlinux xsane: io/hpmud/musb.c 1987: invalid usb_open: Permission denied
Feb 12 11:10:41 bnmlinux xsane: io/hpmud/musb.c 1987: invalid usb_open: Permission denied
Feb 12 11:10:41 bnmlinux xsane: io/hpmud/musb.c 1987: invalid usb_open: Permission denied
Then while the scanner is scanning:
Feb 12 11:19:26 bnmlinux kernel: 5264.843405] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Feb 12 11:19:26 bnmlinux kernel: 5264.843429] ata5.00: irq_stat 0x40000001
Feb 12 11:19:26 bnmlinux kernel: 5264.843455] ata5.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 12 11:19:26 bnmlinux kernel: 5264.843457] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Feb 12 11:19:26 bnmlinux kernel: 5264.843460] res 00/00:03:00:12:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Feb 12 11:19:26 bnmlinux kernel: 5264.843498] ata5: hard resetting link
Feb 12 11:19:26 bnmlinux kernel: 5265.301023] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 12 11:19:26 bnmlinux kernel: 5265.309481] ata5.00: configured for UDMA/100
Feb 12 11:19:26 bnmlinux kernel: 5265.314444] ata5: EH complete
Feb 12 11:19:41 bnmlinux kernel: 5280.582058] INFO: task xsane:5305 blocked for more than 120 seconds.
Feb 12 11:19:41 bnmlinux kernel: 5280.582086] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
Feb 12 11:19:41 bnmlinux kernel: 5280.582105] xsane D 00000000 0 5305 5277 0x00000000
Feb 12 11:19:41 bnmlinux kernel: 5280.582142] f3127dc0 00200082 f20b80c0 00000000 c09f2080 f29865fc c09f2080 c09f2080
Feb 12 11:19:41 bnmlinux kernel: 5280.582182] 25dac861 00000499 c09f2080 c09f2080 f29865fc 25da383b 00000499 c09f2080
Feb 12 11:19:41 bnmlinux kernel: 5280.582220] f1a89740 f2986370 35cf091c f20b80c0 f3127dc8 f28657d0 f3127de8 c0521ba5
Feb 12 11:19:41 bnmlinux kernel: 5280.582255] Call Trace:
Feb 12 11:19:41 bnmlinux kernel: 5280.582285] <c0521ba5>] usb_kill_urb+0x85/0xb0
Feb 12 11:19:41 bnmlinux kernel: 5280.582305] <c052e671>] usbdev_ioctl+0x5a1/0xb20
Feb 12 11:19:41 bnmlinux kernel: 5280.582325] <c0325742>] vfs_ioctl+0x82/0xa0
Feb 12 11:19:41 bnmlinux kernel: 5280.582342] <c03259e9>] do_vfs_ioctl+0x79/0x310
Feb 12 11:19:41 bnmlinux kernel: 5280.582361] <c0325cff>] sys_ioctl+0x7f/0xa0
Feb 12 11:19:41 bnmlinux kernel: 5280.582369] <c0204073>] sysenter_do_call+0x12/0x28
Feb 12 11:19:41 bnmlinux kernel: 5280.582394] <ffffe424>] 0xffffe424
Feb 12 11:21:41 bnmlinux kernel: 5400.582062] INFO: task xsane:5305 blocked for more than 120 seconds.
Feb 12 11:21:41 bnmlinux kernel: 5400.582086] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
Feb 12 11:21:41 bnmlinux kernel: 5400.582106] xsane D 00000000 0 5305 5277 0x00000000
Feb 12 11:21:41 bnmlinux kernel: 5400.582142] f3127dc0 00200082 f20b80c0 00000000 c09f2080 f29865fc c09f2080 c09f2080
Feb 12 11:21:41 bnmlinux kernel: 5400.582181] 25dac861 00000499 c09f2080 c09f2080 f29865fc 25da383b 00000499 c09f2080
Feb 12 11:21:41 bnmlinux kernel: 5400.582218] f1a89740 f2986370 35cf091c f20b80c0 f3127dc8 f28657d0 f3127de8 c0521ba5
Feb 12 11:21:41 bnmlinux kernel: 5400.582254] Call Trace:
Feb 12 11:21:41 bnmlinux kernel: 5400.582282] <c0521ba5>] usb_kill_urb+0x85/0xb0
Feb 12 11:21:41 bnmlinux kernel: 5400.582303] <c052e671>] usbdev_ioctl+0x5a1/0xb20
Feb 12 11:21:41 bnmlinux kernel: 5400.582322] <c0325742>] vfs_ioctl+0x82/0xa0
Feb 12 11:21:41 bnmlinux kernel: 5400.582340] <c03259e9>] do_vfs_ioctl+0x79/0x310
Feb 12 11:21:41 bnmlinux kernel: 5400.582356] <c0325cff>] sys_ioctl+0x7f/0xa0
Feb 12 11:21:41 bnmlinux kernel: 5400.582373] <c0204073>] sysenter_do_call+0x12/0x28
Feb 12 11:21:41 bnmlinux kernel: 5400.582404] <ffffe424>] 0xffffe424
As always, any and all assistance is greatly appreciated.
Having received no replies to this thread and as a long time SuSE user, understand that it is a best effort/community-based support, I would like to seek clarification on something. If I purchase the boxed version of 11.2 when it releases in North America, will this type of problem be handled under the support mechanism that is offered with the boxed version? I am referring to the support statement:
For openSUSE users, the supported version of openSUSE may be the best choice—you’ll get complete end-user manual, installable media for x86 and x86 64-bit systems, plus 90 days of end-user installation support via email or phone.
and I remembered seeing an option to turn off APIC in the BIOS of my new system. While the poster in the thread above disabled apic with an option in the grub menu.lst file, I was able to achieve the same result by disabling APIC in my system’s BIOS.
So the list of all of the mods I did are as follows:
Modify /lib/udev/rules.d/50-udev-default.rules to comment out the line with MODE=“0664” and make it MODE=“0666” for the libusb section. This suppresses the messages that looked like this when I ran xsane:
libusb couldn’t open USB device /dev/bus/usb/001/001: Permission denied.
libusb requires write access to USB device nodes.
Made my user a member of the lp group. Even with the fix in step 1, the permissions on the scanner port always were still set to 664. The ownership of the /dev/bus/usb/002/002 object was root.lp so adding myself to the lp group resolved the last of the “libusb couldn’t open usb device” messages.
Disabling APIC in the BIOS resolved the system freeze problem.
Just wanted to share this in case anyone else had a similar problem. I’ve tested this with two long scan jobs (before with APIC enabled it wouldn’t get through one pass of a high res scan) and no problems. To quote the late Freddie Prinze, Sr “Lookin’ good”.
It looks to me like you don’t have suffiecent permissions for your scanner. Check the permissions of your dev and post back here, it should be something like /dev/usb/scanner0.
I agree, you will probably get faster support if you were to purchase the box set, other wise you just have to wait for someone to see your post. There are many of us that are more than willing to help out anytime we can.
Thanks for the reply. As you can see from my prior post, that was part of my problem. There were other issues but I think I’ve got them worked out. But I do thank you for the assistance.
OpenSuse 11.2 64bit
The above information was helpful to me. Thanks for your research. I had to spend a lot of time googling and testing before I got my printer back.
I had been getting error messages similar to the above but my HP C6380 continued to work. Then the scanner started playing up, refusing to scan a full page. It stopped part way through a scan and then it would time out. While trying to remedy this I lost printing as well. I tried to update to a more recent hplip, but found no change in behaviour. I downgraded to hplip 3.9.3-3.4.1 During this time Kwrite was freezing any time I tried to print. I think it still does. But all of my test pages are printing and OpenOffice is printing ok. A test print from Firefox worked as well. I no longer get hpmud permission denied logs.
In the file /etc/udev/55-hpmud.rules we find this.
Novell/Suse changed:
OWNER=“lp” to OWNER=“root”
because OWNER=“lp” is insecure because print job are processed by the user lp
so that a malicious print job might be able to change owner and permissions
of the device nodes and also a user who is allowed to set up a print queue
can set up a special queue with his selfmade driver which changes the
owner and permissions for all device nodes where in contrast OWNER=“root”
is more secure because then only root itself can change owner and permissions.
This change is not distro specific and therefore there is a upstream bug report
I’m glad my research helped but I have to tell you that a couple of months ago I switched to Mandriva after being a SuSE user for 7-8 years. I really hate to say this but I found Mandriva to be much more robust and easier from a hardware support perspective. It was all the things SuSE used to be. This is based on my hardware configuration and will vary based on others. But with Mandriva I didn’t have to edit config files by hand and there were consistent, easy to implement steps for ATI graphics driver support. I hope you enjoy OpenSuSE. I enjoyed it until I had all of these issues.