Mouse and Keyboard Unresponsive

[NeoGeo64]

What would cause my keyboard and mouse to become unresponsive after the computer goes to sleep or sometimes when it boots? By unresponsive I mean that it doesn't even seem to be getting power because the lights on the keyboard and mouse will not and are not illuminated.

[karlchen]

Hello, NeoGeo64.

Taking both threads, which you started within 5 minutes, this one and *Cinnamon* Unresponsive, together, I tend to conclude that you experience a serious problem. My bet will be a driver software problem. But I may be wrong.
The complete screen output of the terminal command

Code: Select all

inxi -Fxz

might be a good starting point.
Searching the logfile /var/log/syslog for error messages which occur around the time when you experience the hangs would be advisable, too.

Cheers,
Karl

[NeoGeo64]

Thanks for your reply but I do see this as a seperate issue from my Cinnamon thread. This only happens when the computer goes to sleep or when it's starting up... and it's random - it doesn't happen everytime. This is a much more serious issue than Cinnamon freezing because I can make it unfreeze. When my keyboard is unresponsive I can't even wake the PC up or anything. All I can is give it a hard shutdown... which probably isn't too good for my 1TB ext4 HDD... is it? It is not a SSD. Also, I'm going to go over my logfiles for a little while. Maybe something will show up there. I'm willing to put up with these issues because Mint is *that awesome*.

[NeoGeo64]

OK! I found the system logs and it is very telling. Some input device drivers crashed. I uploaded the log .txt file to the web because for some reason the message board here won't allow me to post that much text... it actually says I didn't post anything at all. This link will take you to WikiSend and the download button takes you directly to the log file. Please, Linux experts, look at my log file @ crashlog.txt and please tell me what you see.

[karlchen]

Hello, NeoGeo64.

I assume that this section attracted your attention starting at line 1156

Code: Select all

Dec 16 02:22:17 linux kernel: [   18.698923] ------------[ cut here ]------------
Dec 16 02:22:17 linux kernel: [   18.698946] WARNING: CPU: 4 PID: 0 at /build/buildd/linux-3.13.0/drivers/usb/host/xhci-ring.c:1579 handle_cmd_completion+0xe46/0xe50()
Dec 16 02:22:17 linux kernel: [   18.698956] Modules linked in: rfcomm bnep bluetooth binfmt_misc snd_hda_codec_hdmi dcdbas snd_hda_codec_realtek dm_multipath scsi_dh snd_hda_intel arc4 x86_pkg_temp_thermal snd_hda_codec intel_powerclamp coretemp kvm_intel snd_hwdep kvm ath9k snd_pcm crct10dif_pclmul ath9k_common crc32_pclmul ghash_clmulni_intel ath9k_hw aesni_intel aes_x86_64 lrw snd_page_alloc gf128mul glue_helper ath ablk_helper snd_seq_midi cryptd snd_seq_midi_event mac80211 snd_rawmidi snd_seq snd_seq_device snd_timer cfg80211 serio_raw snd mei_me lpc_ich mei soundcore mac_hid parport_pc ppdev lp parport dm_mirror dm_region_hash dm_log usb_storage hid_generic usbhid hid radeon i2c_algo_bit ttm drm_kms_helper ahci psmouse drm r8169 libahci mii video
Dec 16 02:22:17 linux kernel: [   18.699062] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 3.13.0-37-generic #64-Ubuntu
Dec 16 02:22:17 linux kernel: [   18.699066] Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A01 05/16/2013
Dec 16 02:22:17 linux kernel: [   18.699069]  0000000000000009 ffff88023ed03da8 ffffffff8171ed09 0000000000000000
Dec 16 02:22:17 linux kernel: [   18.699077]  ffff88023ed03de0 ffffffff8106773d ffff88022db516d0 ffff88022db511e0
Dec 16 02:22:17 linux kernel: [   18.699083]  0000000000000009 000000022db511e0 ffff88022d4a0000 ffff88023ed03df0
Dec 16 02:22:17 linux kernel: [   18.699090] Call Trace:
Dec 16 02:22:17 linux kernel: [   18.699093]  <IRQ>  [<ffffffff8171ed09>] dump_stack+0x45/0x56
Dec 16 02:22:17 linux kernel: [   18.699111]  [<ffffffff8106773d>] warn_slowpath_common+0x7d/0xa0
Dec 16 02:22:17 linux kernel: [   18.699119]  [<ffffffff8106781a>] warn_slowpath_null+0x1a/0x20
Dec 16 02:22:17 linux kernel: [   18.699127]  [<ffffffff8157be86>] handle_cmd_completion+0xe46/0xe50
Dec 16 02:22:17 linux kernel: [   18.699135]  [<ffffffff8157d893>] xhci_irq+0x333/0xa60
Dec 16 02:22:17 linux kernel: [   18.699142]  [<ffffffff8157dfd1>] xhci_msi_irq+0x11/0x20
Dec 16 02:22:17 linux kernel: [   18.699150]  [<ffffffff810bf8ae>] handle_irq_event_percpu+0x3e/0x1d0
Dec 16 02:22:17 linux kernel: [   18.699157]  [<ffffffff810bfa7d>] handle_irq_event+0x3d/0x60
Dec 16 02:22:17 linux kernel: [   18.699164]  [<ffffffff810c2507>] handle_edge_irq+0x77/0x130
Dec 16 02:22:17 linux kernel: [   18.699175]  [<ffffffff81015cde>] handle_irq+0x1e/0x30
Dec 16 02:22:17 linux kernel: [   18.699184]  [<ffffffff81731b4d>] do_IRQ+0x4d/0xc0
Dec 16 02:22:17 linux kernel: [   18.699192]  [<ffffffff8172722d>] common_interrupt+0x6d/0x6d
Dec 16 02:22:17 linux kernel: [   18.699195]  <EOI>  [<ffffffff815d1862>] ? cpuidle_enter_state+0x52/0xc0
Dec 16 02:22:17 linux kernel: [   18.699211]  [<ffffffff815d1989>] cpuidle_idle_call+0xb9/0x1f0
Dec 16 02:22:17 linux kernel: [   18.699220]  [<ffffffff8101d1de>] arch_cpu_idle+0xe/0x30
Dec 16 02:22:17 linux kernel: [   18.699227]  [<ffffffff810bed85>] cpu_startup_entry+0xc5/0x290
Dec 16 02:22:17 linux kernel: [   18.699237]  [<ffffffff8104131d>] start_secondary+0x21d/0x2d0
Dec 16 02:22:17 linux kernel: [   18.699242] ---[ end trace 87463e5a22eef008 ]---

Will have to do some googling and hope doing so will return some interpretation of what the trace details are trying to tell its reader ...

Cheers,
Karl
--
P.S.:
And I had started wondering whether the mouse and keyboard hangs might be related to this known problem:

If you're experiencing keyboard or mouse freezes, please check the following bug report: https://bugs.launchpad.net/ubuntu/+sour ... ug/1270445

Please, do net let yourself be confused because the quote has been taken from the Mint 17.1 KDE RC release notes. The same warning can be found in all Mint 17 and Mint 17.1 release notes, no matter which desktop environment: Mate, Cinnamon, KDE or xfce.

[karlchen]

Hello, NeoGeo64.

Found 2 ALSA related posts where the trace messages at the end of the posts look pretty much like yours:
http://www.alsa-project.org/db/?f=12bd4 ... 672039bac6
http://www.alsa-project.org/db/?f=d91a5 ... b76d8e9c25
No explanation given what they mean. No diagnostics given. No cure suggested. Hm ...

However, ALSA seems pretty unrelated to mouse nad keyboard freezes.

Karl

[gogolink]

I think I might have the same issue. The first time I turn my desktop on, its USB ports seem dead, and sometimes (?) the HDMI port as well; I'm at the log-in window, but can't log in. When I give it a cold Shutdown and power the system on right away again, usually (?) it comes back with everything responsive. Once I'm in, I have no problems.

Here's my system info:

System: Host: gogo-Inspiron-3847 Kernel: 3.13.0-40-generic x86_64 (64 bit, gcc: 4.8.2)
Desktop: Gnome Distro: Linux Mint 17.1 Rebecca
Machine: System: Dell product: Inspiron 3847
Mobo: Dell model: 088DT1 version: A01 Bios: Dell version: A04 date: 04/03/2014
CPU: Quad core Intel Core i5-4460 CPU (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 25540.6
Clock Speeds: 1: 800.00 MHz 2: 3201.00 MHz 3: 800.00 MHz 4: 800.00 MHz
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
X.Org: 1.15.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1680x1050@60.0hz, 1680x1050@59.9hz
GLX Renderer: Mesa DRI Intel Haswell Desktop GLX Version: 3.0 Mesa 10.1.3 Direct Rendering: Yes
Audio: Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0
Card-2: Intel 8 Series/C220 Series Chipset High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture ver: k3.13.0-40-generic
Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k bus-ID: 03:00.0
IF: wlan0 state: down mac: <filter>
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 ver: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Card-3: Atheros usb-ID: 0cf3:0036
IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
Drives: HDD Total Size: 1000.2GB (1.7% used) 1: id: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID: / size: 19G used: 5.4G (32%) fs: ext4 ID: /home size: 811G used: 11G (2%) fs: ext4
ID: swap-1 size: 10.00GB used: 0.00GB (0%) fs: swap
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 177 Uptime: 29 min Memory: 1291.1/7902.5MB Runlevel: 2 Gcc sys: 4.8.2 Client: Shell inxi: 1.8.4

And here's a section of a syslog (from /var/log/syslog.1) that to me (but I don't know how to read it) looks similar to what NeoGeo64 posted:

Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154400] ------------[ cut here ]------------
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154405] WARNING: CPU: 2 PID: 43 at /build/buildd/linux-3.13.0/drivers/usb/host/xhci-ring.c:1582 handle_cmd_completion+0xe46/0xe50()
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154406] Modules linked in: rfcomm bnep binfmt_misc nls_iso8859_1 x86_pkg_temp_thermal intel_powerclamp arc4 ath9k coretemp ath9k_common ath9k_hw ath dcdbas kvm_intel kvm mac80211 snd_hda_codec_realtek crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi cfg80211 snd_hda_intel ghash_clmulni_intel aesni_intel snd_hda_codec ath3k btusb aes_x86_64 lpc_ich bluetooth lrw gf128mul snd_hwdep glue_helper mei_me snd_pcm snd_page_alloc ablk_helper snd_seq_midi cryptd snd_seq_midi_event snd_rawmidi snd_seq mei snd_seq_device snd_timer parport_pc ppdev dm_multipath lp serio_raw snd scsi_dh soundcore mac_hid parport dm_mirror dm_region_hash dm_log ums_realtek usb_storage hid_generic usbhid hid i915 psmouse i2c_algo_bit r8169 drm_kms_helper mii ahci drm libahci video
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154437] CPU: 2 PID: 43 Comm: khubd Not tainted 3.13.0-40-generic #69-Ubuntu
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154438] Hardware name: Dell Inc. Inspiron 3847/088DT1 , BIOS A04 04/03/2014
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154439] 0000000000000009 ffff88021fb03da8 ffffffff8171f226 0000000000000000
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154441] ffff88021fb03de0 ffffffff810677cd ffff88020eb6f630 ffff88020eb6f130
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154442] 0000000000000004 000000020eb6f130 ffff88020ea86000 ffff88021fb03df0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154444] Call Trace:
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154445] <IRQ> [<ffffffff8171f226>] dump_stack+0x45/0x56
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154450] [<ffffffff810677cd>] warn_slowpath_common+0x7d/0xa0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154452] [<ffffffff810678aa>] warn_slowpath_null+0x1a/0x20
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154453] [<ffffffff8157c406>] handle_cmd_completion+0xe46/0xe50
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154456] [<ffffffff810981b5>] ? check_preempt_curr+0x75/0xa0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154458] [<ffffffff8157dd43>] xhci_irq+0x333/0xa60
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154459] [<ffffffff8157e481>] xhci_msi_irq+0x11/0x20
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154461] [<ffffffff810bf97e>] handle_irq_event_percpu+0x3e/0x1d0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154463] [<ffffffff810bfb4d>] handle_irq_event+0x3d/0x60
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154464] [<ffffffff810c25d7>] handle_edge_irq+0x77/0x130
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154467] [<ffffffff81015dbe>] handle_irq+0x1e/0x30
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154470] [<ffffffff8173205d>] do_IRQ+0x4d/0xc0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154472] [<ffffffff8172772d>] common_interrupt+0x6d/0x6d
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154473] <EOI> [<ffffffff8149205e>] ? dev_printk_emit+0x3e/0x40
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154477] [<ffffffff815795b6>] ? xhci_cancel_cmd+0x86/0x270
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154479] [<ffffffff817270bb>] ? _raw_spin_unlock_irqrestore+0x1b/0x40
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154481] [<ffffffff81579589>] xhci_cancel_cmd+0x59/0x270
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154483] [<ffffffff815730b3>] xhci_address_device+0x413/0x620
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154485] [<ffffffff8153d504>] hub_port_init+0x1f4/0xb10
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154488] [<ffffffff814a31a9>] ? update_autosuspend+0x39/0x60
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154490] [<ffffffff814a3215>] ? pm_runtime_set_autosuspend_delay+0x45/0x90
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154491] [<ffffffff8153ec85>] hub_port_connect_change+0x185/0xb50
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154493] [<ffffffff81545ff4>] ? usb_control_msg+0xd4/0x110
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154495] [<ffffffff8153fb24>] hub_events+0x4d4/0xa30
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154497] [<ffffffff815400b5>] hub_thread+0x35/0x160
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154500] [<ffffffff810ab0a0>] ? prepare_to_wait_event+0x100/0x100
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154501] [<ffffffff81540080>] ? hub_events+0xa30/0xa30
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154504] [<ffffffff8108b562>] kthread+0xd2/0xf0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154505] [<ffffffff8108b490>] ? kthread_create_on_node+0x1c0/0x1c0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154507] [<ffffffff8172fc7c>] ret_from_fork+0x7c/0xb0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154508] [<ffffffff8108b490>] ? kthread_create_on_node+0x1c0/0x1c0
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.154509] ---[ end trace 3d29b2ec64a3a23e ]---

Immediately after this, there are these lines -- I quote them here because they mention a USB device:

Dec 18 18:13:11 gogo-Inspiron-3847 mdm[1387]: WARNING: Plymouth is running, asking it to stop...
Dec 18 18:13:11 gogo-Inspiron-3847 mdm[1387]: WARNING: Plymouth stopped
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.239057] init: plymouth-upstart-bridge main process ended, respawning
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.241252] init: plymouth-upstart-bridge main process (1394) terminated with status 1
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.241258] init: plymouth-upstart-bridge main process ended, respawning
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.358620] usb 3-10: Device not responding to set address.
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.562787] usb 3-10: device not accepting address 5, error -71
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.674942] usb 3-10: new full-speed USB device number 6 using xhci_hcd
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.692404] usb 3-10: New USB device found, idVendor=0cf3, idProduct=0036
Dec 18 18:13:11 gogo-Inspiron-3847 kernel: [ 14.692414] usb 3-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0

Can anyone make sense of this?

[harlekein]

I just upgraded from 17 to 17.1. When I boot up my laptop the leds on the external USB keyboard and Mouse are on. As soon as I hit the login screen for Mint they turn off and become unresponsive.

Everything was working fine on 17. It is still fine on the boot menu and in Win8. It's explicitely 17.1 that's failing my USB devices. I think I'll be rolling back to 17, because this is very important to me.

Code: Select all

ec 20 16:16:09 P25Wv2 kernel: [   18.169219] usb 3-10: device not accepting address 6, error -108
Dec 20 16:16:10 P25Wv2 ntpdate[1935]: adjust time server 91.189.89.199 offset 0.088186 sec
Dec 20 16:16:12 P25Wv2 kernel: [   20.409593] init: Failed to spawn nvidia-persistenced main process: unable to execute: No such file or directory
Dec 20 16:16:13 P25Wv2 NetworkManager[938]: <warn> error monitoring device for netlink events: error processing netlink message: Object busy
Dec 20 16:16:14 P25Wv2 kernel: [   23.173338] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
Dec 20 16:16:14 P25Wv2 kernel: [   23.173348] xhci_hcd 0000:00:14.0: Abort the command ring, but the xHCI is dead.
Dec 20 16:16:19 P25Wv2 NetworkManager[938]: <info> (eth0): IP6 addrconf timed out or failed.
Dec 20 16:16:19 P25Wv2 NetworkManager[938]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Dec 20 16:16:19 P25Wv2 NetworkManager[938]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Dec 20 16:16:19 P25Wv2 NetworkManager[938]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Dec 20 16:16:19 P25Wv2 wpa_supplicant[1062]: wlan0: CTRL-EVENT-SCAN-STARTED 
Dec 20 16:16:19 P25Wv2 kernel: [   28.176820] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
Dec 20 16:16:19 P25Wv2 kernel: [   28.176830] xhci_hcd 0000:00:14.0: Abort the command ring, but the xHCI is dead.
Dec 20 16:16:19 P25Wv2 kernel: [   28.176884] usb 3-1: USB disconnect, device number 2
Dec 20 16:16:20 P25Wv2 acpid: input device has been disconnected, fd 17
Dec 20 16:16:20 P25Wv2 kernel: [   28.221792] usb 3-5: USB disconnect, device number 3
Dec 20 16:16:20 P25Wv2 kernel: [   28.222199] usb 3-9: USB disconnect, device number 4
Dec 20 16:16:20 P25Wv2 acpid: input device has been disconnected, fd 18
Dec 20 16:16:20 P25Wv2 acpid: input device has been disconnected, fd 19

Update: I was about to recover my CloneZilla backup when I noticed at the boot of my laptop it stayed on the initial screen for longer than usual as well as the fans blowing at max. I decided to completely power off my laptop instead of just rebooting. That issues resolved and when I booted back into Mint both my keyboard and mouse were still alive during and after login.

[NeoGeo64]

Just wondering if anyone has deciphered the logfiles or anything else that would explain what's going on.

[gogolink]

I had a couple of boots without any problems, but just now the same thing that harlekin described happened again: mouse, keyboard working during the boot-up process until log-in screen, then they're off; in this case, the HDMI port was off as well. Shut down by power button, turned back on -- same thing, though HDMI is working. But not the USB ports. Tried again, power button off, on again: and yes, this time everything's working.

This thing is annoying.

I already upgraded the kernel from 3.13.0-37 to 3.13.0-40. Will now upgrade to 3.16.0-28. If anything interesting happens, I'll report back.

[msandefur03]

I have an inspiron 3847 also, with similar problems. I dual boot LM17 (not 17.1) with Win7. I have no mouse problems on the windows side, but about 50% of the time the mouse will power off just as I get to the Mint login screen. Very frustrating. I have also found the HDMI port to be unreliable. Perhaps there is an incompatibility with this particular hardware? Suggestions appreciated!

[gogolink]

Since I upgraded the kernel from the 3.13 series to the 3.16 series (3.16.0-28, to be precise), I have not had any problem with the USB ports. That's admittedly on only six boot-ups so far -- enough to be optimistic, not enough to be certain that the problem is solved.

I have sometimes still had the HDMI port unresponsive during log-in; since I have a dual monitor set-up, and the other monitor runs on VGA, this hasn't been a problem for me. Once I log in, HDMI becomes fully functional again.

[nadia14]

I have tried to install Mint 17.1 mate on a friend pc (inspiron 3847 with i3). Booted fine from dvd, installed ok.

Same problem.

And upgrading to 3.16 doesn't fix the problem . Atm he is using lubuntu 14.04 that _seems_ to work ok. Hope the problem will be fixed, the pc is an interesting machine at a not too expensive price (fortunatly i haven't bought it too!)

[gogolink]

Well, I can now say that for me, the problem has disappeared since the upgrade to the 3.16-series kernel. I have had more than 30 boot-ups since then, and no more unresponsive mouse or keyboard on USB port. I have had a couple of times (three or so) when the monitor on the HMDI port didn't come on, but since I have a two-monitor set-up and the monitor on the VGA connector was always there, that hasn't been a problem.