I recently got a D-Link DWA-140 and first used the staging driver which worked, except that it throws an error at me when shutting down my system and keeps the system from shutting down. I don't actually know if this thread is also about the rt2800usb driver for rt2870 USB chips. pObj->RTUSBCmdThr_pid = THREAD_PID_INIT_VALUE wait_for_completion (&pAd->CmdQComplete) pAd->net_dev->name, GET_PID_NUMBER(pObj->RTUSBCmdThr_pid), ret) printk(KERN_WARNING "%s: unable to RTUSBCmd thread, pid=%d, ret=%d!\n",
ret = KILL_THREAD_PID(pObj->RTUSBCmdThr_pid, SIGTERM, 1) PAd->CmdQ.CmdQState = RT2870_THREAD_STOPED + pid_nr(task_pid(pObj->RTUSBCmdThr_task))) + printk(KERN_DEBUG "Terminate the RTUSBCmdThr pid=%d!\n", printk("Terminate the RTUSBCmdThr_pid=%d!\n", GET_PID_NUMBER(pObj->RTUSBCmdThr_pid)) +ĜHECK_PID_LEGALITY(task_pid(pObj->RTUSBCmdThr_task)) ĜHECK_PID_LEGALITY(pObj->RTUSBCmdThr_pid) pObj->MLMEThr_pid = THREAD_PID_INIT_VALUE wait_for_completion (&pAd->mlmeComplete) pAd->net_dev->name, GET_PID_NUMBER(pObj->MLMEThr_pid), ret) printk (KERN_WARNING "%s: unable to Mlme thread, pid=%d, ret=%d!\n", ret = KILL_THREAD_PID(pObj->MLMEThr_pid, SIGTERM, 1) + printk(KERN_DEBUG "Terminate the MLMEThr pid=%d!\n", printk("Terminate the MLMEThr_pid=%d!\n", GET_PID_NUMBER(pObj->MLMEThr_pid)) +ĜHECK_PID_LEGALITY(task_pid(pObj->MLMEThr_task)) pObj->TimerQThr_pid = THREAD_PID_INIT_VALUE wait_for_completion(&pAd->TimerQComplete) pAd->net_dev->name, GET_PID_NUMBER(pObj->TimerQThr_pid), ret) printk(KERN_WARNING "%s: unable to stop TimerQThread, pid=%d, ret=%d!\n", ret = KILL_THREAD_PID(pObj->TimerQThr_pid, SIGTERM, 1) + pid_nr(task_pid(pObj->TimerQThr_task))) + printk(KERN_DEBUG "Terminate the TimerQThr pid=%d!\n", printk("Terminate the TimerQThr_pid=%d!\n", GET_PID_NUMBER(pObj->TimerQThr_pid)) POS_COOKIE pObj = (POS_COOKIE)pAd->OS_Cookie +ĜHECK_PID_LEGALITY(task_pid(pObj->TimerQThr_task)) Switching to other ttys works and they are responsive until executing "ifconfig".įrom the log, my _guess_ is that this is caused by this part of the patch: Typing on the keyboard shows up on the screen, but Ctrl-C does nothing. I was returned to a responsive prompt, but executing "ifconfig" again killed tty1. This was triggered by executing "ifconfig ra0 down" on kernel 2.6.31-rc4, which returned with a kernel bug. The whole system basically goes down the drain." I can't even shutdown anymore if I don't use the -n option. The reason fot this is that many networking applications "cylce" the interface once before using it to clear left-over configurations. Wicd stalls, the process can't be shut down any more.
Everything using PAM begins to fail, if I run sudo in a VT, i lose it (this might be related to your mounting problem). Examples: I lose the VT where I ran this. The command doesn't complete, produces no output and causes many other prolems.
0 kommentar(er)
