Please fix ucom + uplcom on -stable
Hello, My stable box panics daily with: panic: uhci_abort_xfer : not in process context I read that it's been fixed in -current. Will the fix be coming to -stable anytime soon? Dennis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
usb causing 5.3 release/stable crash?
Hello, I connect to the office machine via serial modem after office hours and encountered no problems until I tried using one of those USB to Serial adapters - I could connect alright but for less than 24 hours. It's okay during the weekdays but the office machine would hang over the weekend. Had to press the reset button. Unfortunately, it wouldn't boot anymore. Reinstalled 5.3-release today. And it's down after 4 hours remote dialin access. I used 5.3-stable from sometime December 2004 which worked well until I started using an ATEN UC-232 USB - Serial adapter, serial modem and mgetty. I read somewhere that /dev/ucom# would be replaced by /dev/cuaU# - might that be the solution to my problem? Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb causing 5.3 release/stable crash?
Okay, another case of replying to self Got a proper panic message this morning: panic: uchi_abort_xfer : not in process context Anybody seen one of these before? Possible solutions? David On Tue, 1 Feb 2005 22:23:43 +0800, david uy [EMAIL PROTECTED] wrote: Hello, I connect to the office machine via serial modem after office hours and encountered no problems until I tried using one of those USB to Serial adapters - I could connect alright but for less than 24 hours. It's okay during the weekdays but the office machine would hang over the weekend. Had to press the reset button. Unfortunately, it wouldn't boot anymore. Reinstalled 5.3-release today. And it's down after 4 hours remote dialin access. I used 5.3-stable from sometime December 2004 which worked well until I started using an ATEN UC-232 USB - Serial adapter, serial modem and mgetty. I read somewhere that /dev/ucom# would be replaced by /dev/cuaU# - might that be the solution to my problem? Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb causing 5.3 release/stable crash?
Yet another reply to self! Got some info from the current mailing list - seems they have a patch for this but don't know how to apply it. Patch maybe? Has this patch been included in the latest -stable? Building world as I write this. Will attempt to apply the patch, too! *fingers crossed* David On Wed, 2 Feb 2005 08:54:18 +0800, david uy [EMAIL PROTECTED] wrote: Okay, another case of replying to self Got a proper panic message this morning: panic: uchi_abort_xfer : not in process context Anybody seen one of these before? Possible solutions? David On Tue, 1 Feb 2005 22:23:43 +0800, david uy [EMAIL PROTECTED] wrote: Hello, I connect to the office machine via serial modem after office hours and encountered no problems until I tried using one of those USB to Serial adapters - I could connect alright but for less than 24 hours. It's okay during the weekdays but the office machine would hang over the weekend. Had to press the reset button. Unfortunately, it wouldn't boot anymore. Reinstalled 5.3-release today. And it's down after 4 hours remote dialin access. I used 5.3-stable from sometime December 2004 which worked well until I started using an ATEN UC-232 USB - Serial adapter, serial modem and mgetty. I read somewhere that /dev/ucom# would be replaced by /dev/cuaU# - might that be the solution to my problem? Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]