update to OpenBSD 5.0-current (GENERIC) #109: Wed Nov 30 17:27:38 MST
2011 to include several diffs to ucom(4).
now instead of flooding the message buffer with ucomstart: null oxfer,
I got the concise message uvm_mapent_alloc: out of static map entries
and my program returns with i2c: open():
On 2011-11-30, Daniel Gracia lists.d...@electronicagracia.com wrote:
At the very least you're seeing some errors. In my case, the USB/serial
adapters -uticom, uftdi and uplcom- would fail without notice. Ports
would open, but with no TX/RX. Detaching/reattaching won't bring them
back to
At the very least you're seeing some errors. In my case, the USB/serial
adapters -uticom, uftdi and uplcom- would fail without notice. Ports
would open, but with no TX/RX. Detaching/reattaching won't bring them
back to live; only rebooting.
If your project has deadline, search for a PCI/ePCI
panic message:
uvm_fault(0xd0a2c8c0, 0x1000, 0, 1) - e
kernel: page fault trap, code=0
Stopped at usb_allocmem+0x14f: cmpl%ebx,0(%eax)
I also have a similar panic message. My solution is to disable ehci
from my GENERIC. stupid but it works on this NVIDIA USB controller.
jakemsr@
I managed to capture trace and ps output from ddb
Is this a worthy cause to investigate further or should I take the
advice of others and move on to real(tm) hardware. It would be a shame
given the distasteful argument well it works fine under
ddb trace
panic message:
uvm_fault(0xd0a2c8c0, 0x1000, 0, 1) - e
kernel: page fault trap, code=0
Stopped at usb_allocmem+0x14f: cmpl%ebx,0(%eax)
On Tuesday, November 29, 2011 7:14 PM, Byron Klippert
byronklipp...@ml1.net wrote:
I managed to capture trace and ps output from ddb
Is this a
I've nothing but trouble trying to work with _every_ USB/Serial adapter
on OpenBSD. Hacking on drivers didn't helped, so I tend to think our USB
stack is quite poor.
But I don't blame; USB is a toy, and USB devices are toys. Getting
real(tm) hardware you should solve your problems.
PS: This
On Mon, 28 Nov 2011 10:02:41 +0100
Daniel Gracia wrote:
When I unplug the device the system hangs or if
I run usbdevs the system hangs, once hung the watchdog kicks in and
reboots the machine.
Completely unsubstantiated and untested theory but out of interest does
it still hang if you whip
I wrote a C program to talk to a I2C usb master device. On the surface
this program seems to work consistently. It wasn't until I wrapped the C
program in shell code and looped it, when a problem was exposed
ultimately crashing the system. I do not know whether my program is
causing the crash or
9 matches
Mail list logo
