Mouse Wheel gone
by Christian Menzel
Since the latest xorg-X11 upgrade I receive the already mentioned XKB
error and the mouse wheel is not working anymore.
Has anybody seen this behavior?
Regards
Chris
4 years, 3 months
Re: NFS failure
by Fulko.Hew＠sita.aero
Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
wrote:
> On Wed, 7 Apr 2004, Jeff Elkins wrote:
>
> > I'm getting failure messages on my nfs mounts i.e. :
> >
> > mount to NFS server 'music.elkins' failed: server is down.
> >
> > nsfd appears to be running and I didn't see anything suspicious in the
logs.
> > The servers are up and running and have other clients connected.
>
> You didn't mention what steps you took to debug it:
>
> Can you ping the server?
> What is the output of rpcinfo -p servername?
> Does the server have access restrictions (firewall, TCP Wrappers, etc)?
I have the same symptoms...
rpcinfo says that nfs et.al. are running.
Something has changed in test 2, since the same PC running RH9
accesses that host just fine.
4 years, 3 months
Will ext4 be in FC7?
by Justin Conover
With experimental release of EXT4 in 2.6.19, is it possible it will be in
rawhide soon and in FC7 at release time?
Thanks,
13 years
Are My RPM/Yum Seg-Faults Due to the Kernel FIle Corruption?
by Paul Dickson
Is the file corruption problem currently being discussed on LKML related
to the RPM/Yum seg-faults I occasionally on my 300 MHz, PII, notebook
(with only 256 MB of RAM)?
I usually see the seg-faults while glibc-common is being updated during a
large update (within the first 2 or 3 files of 30+ file update). If I
update glibc* first, that, and the following updated of the remainder
always works. If glibc has a lot of dependency info, I can see the
/var/lib/rpm/__db.00* databases taking a hit and requiring manual
deletion to restart.
If this is true, this bug might have started before FC6 was released, but
only gets hit when memory runs low.
-Paul
13 years, 1 month
mirror list and debuginfo bad, Ok with direct URL
by Jim Cornette
I just had a crash with gnome-games and decided to install the debuginfo
package so the information provided in the reports would be more useful
to track down the problem with the bug buddy output. I had to use the
direct url instead of the mirrorlist to get to the debuginfo packages.
Should the default be for the single url since these packages are in
less demand than the other binary rpms?
Jim
--
People of privilege will always risk their complete destruction
rather than surrender any material part of their advantage.
-- John Kenneth Galbraith
13 years, 2 months
Quick problem with s-c-securitylevel
by Paul F. Johnson
Hi,
When I try to run s-c-securitylevel from the commane line, I get the
following throwback
File
"/usr/share/system-config-securitylevel/system-config-securitylevel.py",
line 11, in <module>
import securitylevel
File
"/usr/share/system-config-securitylevel/system-config-securitylevel.py",
line 33, in <module>
import selinuxPage
File
"/usr/share/system-config-securitylevel/system-config-securitylevel.py",
line 27, in <module>
from Conf import *
ImportError: No module named Conf
What do I need to install to fix this problem?
TTFN
Paul
--
"Mmmmmmmm....Shakira geschmiert mit schokolade" sagt Homer
13 years, 2 months
2.6.19-1.2891.fc7 -- INFO: soft-safe -> soft-unsafe lock order detected
by Miles Lane
[ INFO: soft-safe -> soft-unsafe lock order detected ]
2.6.19-1.2891.fc7 #1
------------------------------------------------------
cupsd/1884 [HC0[0]:SC0[1]:HE1:SE0] is trying to acquire:
(&ssec->nlbl_lock){--..}, at: [<c04cec37>]
selinux_netlbl_socket_setsid+0xbb/0x123
and this task is already holding:
(af_callback_keys + sk->sk_family#3){-.-+}, at: [<c05daa1c>]
inet_accept+0x70/0xb5
which would create a new lock dependency:
(af_callback_keys + sk->sk_family#3){-.-+} -> (&ssec->nlbl_lock){--..}
but this new dependency connects a soft-irq-safe lock:
(af_callback_keys + sk->sk_family#3){-.-+}
... which became soft-irq-safe at:
[<c043fff1>] __lock_acquire+0x37d/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbdb6>] _read_lock_bh+0x30/0x3d
[<c04c687e>] selinux_socket_sock_rcv_skb+0xbd/0x252
[<c05d0645>] tcp_v4_rcv+0x37a/0x909
[<c05b7593>] ip_local_deliver+0x185/0x22e
[<c05b73d6>] ip_rcv+0x418/0x450
[<c059ae9c>] netif_receive_skb+0x2db/0x35a
[<c059c85f>] process_backlog+0x95/0xf6
[<c059ca46>] net_rx_action+0xa1/0x1a8
[<c042bf5a>] __do_softirq+0x6f/0xe2
[<c04063a1>] do_softirq+0x61/0xc7
[<ffffffff>] 0xffffffff
to a soft-irq-unsafe lock:
(&ssec->nlbl_lock){--..}
... which became soft-irq-unsafe at:
... [<c044007d>] __lock_acquire+0x409/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbc89>] _spin_lock+0x2b/0x38
[<c04cec37>] selinux_netlbl_socket_setsid+0xbb/0x123
[<c04d0c92>] selinux_netlbl_socket_post_create+0x2d/0x2f
[<c04c807b>] selinux_socket_post_create+0x156/0x15c
[<c059213c>] __sock_create+0x179/0x1b2
[<c05921ae>] sock_create+0x1a/0x1f
[<c0592435>] sys_socket+0x1b/0x3c
[<c0592cba>] sys_socketcall+0x77/0x241
[<c0404050>] syscall_call+0x7/0xb
[<ffffffff>] 0xffffffff
other info that might help us debug this:
3 locks held by cupsd/1884:
#0: (sk_lock-AF_INET){--..}, at: [<c05da9dd>] inet_accept+0x31/0xb5
#1: (af_callback_keys + sk->sk_family#3){-.-+}, at: [<c05daa1c>]
inet_accept+0x70/0xb5
#2: (policy_rwlock){..-?}, at: [<c04cebd0>]
selinux_netlbl_socket_setsid+0x54/0x123
the soft-irq-safe lock's dependencies:
-> (af_callback_keys + sk->sk_family#3){-.-+} ops: 0 {
initial-use at:
[<c0440098>] __lock_acquire+0x424/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbd3b>] _write_lock_bh+0x30/0x3d
[<c05c1871>] tcp_close+0x24b/0x52b
[<c05da570>] inet_release+0x43/0x49
[<c0591f72>] sock_release+0x17/0x68
[<c05921e0>] sock_close+0x2d/0x33
[<c047959b>] __fput+0xbe/0x168
[<c047965c>] fput+0x17/0x19
[<c0476f5d>] filp_close+0x54/0x5c
[<c0477ee1>] sys_close+0x78/0xb0
[<c0404050>] syscall_call+0x7/0xb
[<ffffffff>] 0xffffffff
hardirq-on-W at:
[<c0440056>] __lock_acquire+0x3e2/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbd3b>] _write_lock_bh+0x30/0x3d
[<c05c1871>] tcp_close+0x24b/0x52b
[<c05da570>] inet_release+0x43/0x49
[<c0591f72>] sock_release+0x17/0x68
[<c05921e0>] sock_close+0x2d/0x33
[<c047959b>] __fput+0xbe/0x168
[<c047965c>] fput+0x17/0x19
[<c0476f5d>] filp_close+0x54/0x5c
[<c0477ee1>] sys_close+0x78/0xb0
[<c0404050>] syscall_call+0x7/0xb
[<ffffffff>] 0xffffffff
in-softirq-R at:
[<c043fff1>] __lock_acquire+0x37d/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbdb6>] _read_lock_bh+0x30/0x3d
[<c04c687e>] selinux_socket_sock_rcv_skb+0xbd/0x252
[<c05d0645>] tcp_v4_rcv+0x37a/0x909
[<c05b7593>] ip_local_deliver+0x185/0x22e
[<c05b73d6>] ip_rcv+0x418/0x450
[<c059ae9c>] netif_receive_skb+0x2db/0x35a
[<c059c85f>] process_backlog+0x95/0xf6
[<c059ca46>] net_rx_action+0xa1/0x1a8
[<c042bf5a>] __do_softirq+0x6f/0xe2
[<c04063a1>] do_softirq+0x61/0xc7
[<ffffffff>] 0xffffffff
hardirq-on-R at:
[<c044001f>] __lock_acquire+0x3ab/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbdb6>] _read_lock_bh+0x30/0x3d
[<c04c687e>] selinux_socket_sock_rcv_skb+0xbd/0x252
[<c05d0645>] tcp_v4_rcv+0x37a/0x909
[<c05b7593>] ip_local_deliver+0x185/0x22e
[<c05b73d6>] ip_rcv+0x418/0x450
[<c059ae9c>] netif_receive_skb+0x2db/0x35a
[<c059c85f>] process_backlog+0x95/0xf6
[<c059ca46>] net_rx_action+0xa1/0x1a8
[<c042bf5a>] __do_softirq+0x6f/0xe2
[<c04063a1>] do_softirq+0x61/0xc7
[<ffffffff>] 0xffffffff
}
... key at: [<c09f6770>] af_callback_keys+0x10/0x100
the soft-irq-unsafe lock's dependencies:
-> (&ssec->nlbl_lock){--..} ops: 0 {
initial-use at:
[<c0440098>] __lock_acquire+0x424/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbc89>] _spin_lock+0x2b/0x38
[<c04cec37>] selinux_netlbl_socket_setsid+0xbb/0x123
[<c04d0c92>] selinux_netlbl_socket_post_create+0x2d/0x2f
[<c04c807b>] selinux_socket_post_create+0x156/0x15c
[<c059213c>] __sock_create+0x179/0x1b2
[<c05921ae>] sock_create+0x1a/0x1f
[<c0592435>] sys_socket+0x1b/0x3c
[<c0592cba>] sys_socketcall+0x77/0x241
[<c0404050>] syscall_call+0x7/0xb
[<ffffffff>] 0xffffffff
softirq-on-W at:
[<c044007d>] __lock_acquire+0x409/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbc89>] _spin_lock+0x2b/0x38
[<c04cec37>] selinux_netlbl_socket_setsid+0xbb/0x123
[<c04d0c92>] selinux_netlbl_socket_post_create+0x2d/0x2f
[<c04c807b>] selinux_socket_post_create+0x156/0x15c
[<c059213c>] __sock_create+0x179/0x1b2
[<c05921ae>] sock_create+0x1a/0x1f
[<c0592435>] sys_socket+0x1b/0x3c
[<c0592cba>] sys_socketcall+0x77/0x241
[<c0404050>] syscall_call+0x7/0xb
[<ffffffff>] 0xffffffff
hardirq-on-W at:
[<c0440056>] __lock_acquire+0x3e2/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbc89>] _spin_lock+0x2b/0x38
[<c04cec37>] selinux_netlbl_socket_setsid+0xbb/0x123
[<c04d0c92>] selinux_netlbl_socket_post_create+0x2d/0x2f
[<c04c807b>] selinux_socket_post_create+0x156/0x15c
[<c059213c>] __sock_create+0x179/0x1b2
[<c05921ae>] sock_create+0x1a/0x1f
[<c0592435>] sys_socket+0x1b/0x3c
[<c0592cba>] sys_socketcall+0x77/0x241
[<c0404050>] syscall_call+0x7/0xb
[<ffffffff>] 0xffffffff
}
... key at: [<c09ebb20>] __key.27522+0x0/0x8
stack backtrace:
[<c04051c1>] show_trace_log_lvl+0x1a/0x2f
[<c0405766>] show_trace+0x12/0x14
[<c04057ea>] dump_stack+0x16/0x18
[<c043fbe0>] check_usage+0x242/0x24c
[<c04404f3>] __lock_acquire+0x87f/0x9f8
[<c044094d>] lock_acquire+0x56/0x6f
[<c05fbc89>] _spin_lock+0x2b/0x38
[<c04cec37>] selinux_netlbl_socket_setsid+0xbb/0x123
[<c04d0f40>] selinux_netlbl_sock_graft+0xc7/0xcf
[<c04c4b74>] selinux_sock_graft+0x32/0x36
[<c05daa3b>] inet_accept+0x8f/0xb5
[<c0592b93>] sys_accept+0xd0/0x180
[<c0592d13>] sys_socketcall+0xd0/0x241
[<c0404050>] syscall_call+0x7/0xb
13 years, 2 months
kernel error - I/O error - "fc7", dm-1, sda5, fd0
by Jim Cornette
Why is this error related to filesystem devices happening with the "fc7"
kernel?
Jim
--------------------- Kernel Begin ------------------------
WARNING: Kernel Errors Present
Buffer I/O error on device dm-1, ...: 20 Time(s)
Buffer I/O error on device sda5, ...: 120 Time(s)
end_request: I/O error, dev fd0, sector ...: 3 Time(s)
---------------------- Kernel End -------------------------
--
It's simply unbelievable how much energy and creativity people have
invested into creating contradictory, bogus and stupid licenses...
--- Sven Rudolph about licences in debian/non-free.
13 years, 2 months
