You are not logged in.
I upgraded to the new kernel 3.13.4-1 the other day and everytime I'd try to log into Xwindows the system from GDM, it would hard freeze. So I went about problem solving and couldn't find what was going on. I then upgraded to the 3.13.5-1 kernel thinking that might fix it. It did not. So I went rooting around for a couple hours. Then I realized that it only occured when I went to touch my mouse. So I switched to my Wacom tablet to see if I was right. And yep, it worked perfectly with the tablet. No Freezes.
So for anyone else having problems with the XWindows freezing constantly try switching to another pointer device (unlikely I know). Or you can do what I did and downgrade the kernel from 3.13 to the last 3.12 version which involves downgrading the headers, nvidia driver, and nvidia-utils if you have them. I am using the same mouse in 3.12 with no problems.
I couldn't find a bug report anywhere about it and I don't know what actually causes the mouse to freeze the system while the tablet doesn't.
By the way I use the Nvidia Proprietary driver for XWindows so that might be causing it too since it had to be downgraded... not sure... I can't get any logs from the hard freezez at all.
The 3.13 kernel also randomly decides to lose sync with my main harddrive and then go in a kernel panic on boot sometimes. Clearly it has a few bugs to work out. I'm gonna stick with 3.12 for a while.
Here's the device info:
Bus 009 Device 006: ID 1532:0016 Razer USA, Ltd DeathAdder Mouse
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1532 Razer USA, Ltd
idProduct 0x0016 DeathAdder Mouse
bcdDevice 1.00
iManufacturer 1 Razer
iProduct 2 Razer DeathAdder
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 73
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1
Device Status: 0x0000
(Bus Powered)
goodluck all!
Last edited by classdark (2014-02-24 03:27:45)
Offline
Is the news on the front page apropos?
https://www.archlinux.org/news/linux-31 … w-modular/
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
No. I do use a PS/2 keyboard and I did try that solution but that did nothing to fix the problem. When I use the keyboard, it doesn't cause any hard crashes at all just the mouse. Also oddly enough the problem does not occur with my wacom tablet as I said just with my razer deathadder. I have no keyboard problems whatsoever just the mouse freezing problem as soon as you touch it in Xwindows. I tried GDM, KDM, etc all do the same exact thing as well as startx.
Reverting the kernel fixes it whatever is causing the hard crash. It's not a kernel panic. It's a system freeze. My numpad doesn't blink or anything like normal, the system just hard freezes and nothing moves or works including the numlock button.
Last edited by classdark (2014-02-24 04:04:40)
Offline
I just experienced a similar problem after upgrading to 3.13. At first I thought this was an Intel driver bug (I'm using Bumblebee with Intel + NVIDIA drivers), but nothing showed up in the logs, and it did seem to happen when moving the mouse. I'll try downgrading as well.
EDIT: mouse info
$ lsusb -vs 003:003
Bus 003 Device 003: ID 046d:c069 Logitech, Inc. M500 Laser Mouse
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d Logitech, Inc.
idProduct 0xc069 M500 Laser Mouse
bcdDevice 56.01
iManufacturer 1 Logitech
iProduct 2 USB Laser Mouse
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 U56.01_B0009
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 71
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0006 1x 6 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
Last edited by bchr (2014-02-24 13:08:13)
Offline
This may be related to this thread on the kernel ML: http://www.spinics.net/lists/linux-usb/msg102375.html
Offline
I made some more tests, I discarded Kernel 3.13 and USB problems (it also happened when back in 3.12.9 with no USB device plugged in). I downgraded xf86-video-intel back to 2.99.909-2 and things seem to be (more) stable. Since downgrading to kernel 3.12 fixes the issue for you, I guess we do not have the same problem after all.
Offline