Somebody claiming to be Dave Vandervies wrote:
> After upgrading to 7.4, my pine64-lts box failed to boot bsd.mp on
> two out of two tries, with an identical panic message both times:
> (see below for full (u-boot + kernel + ddb) boot log of the panic
> and dmesg from bsd.sp which doe
keys, 6 key codes
wskbd0 at ukbd0 mux 1
wskbd0: connecting to wsdisplay0
uhidev1 at uhub4 port 2 configuration 1 interface 1 "Unicomp Endura Pro
Keyboard" rev 1.10/43.34 addr 4
uhidev1: iclass 3/1, 3 report ids
ums0 at uhidev1 reportid 1: 3 buttons, Z dir
wsmouse0 at ums0 mux 0
ucc0 at uhidev1 reportid 2: 573 usages, 20 keys, array
wskbd1 at ucc0 mux 1
wskbd1: connecting to wsdisplay0
uhid0 at uhidev1 reportid 3: input=1, output=0, feature=0
uhidev2 at uhub4 port 3 configuration 1 interface 0 "Logitech USB Laser Mouse"
rev 2.00/56.01 addr 5
uhidev2: iclass 3/1
ums1 at uhidev2: 8 buttons, Z and W dir
wsmouse1 at ums1 mux 0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (823130ad660d9ca0.a) swap on sd0b dump on sd0b
--
Dave Vandervies
dj3va...@terse.ca
Plan your future! Make God laugh!
like apmd uses kqueue to get this information; that interface
doesn't appear in any documentation I've found.
Am I looking in the wrong places, or is the documentation wrong
here? Is the way apmd does it meant to be a supported interface?
Thanks,
dave
--
Dave Vandervies
dj3va...@terse.ca
Plan
'?')
> return (-1);
> if (len == 3)
> return (1);
> @@ -1218,6 +1221,10 @@ tty_keys_device_attributes(struct tty *t
> return (-1);
> tmp[i] = '\0';
> *size = 4 + i;
> +
> + /* Ignore DA response. */
> + if (buf[2] == '?')
> +
ptr++;
> if (*ptr == '>')
> ptr++;
> + if (*ptr == '\0')
> + break;
> }
>
> buf[len++] = *ptr;
>
--
Dave Vandervies
dj3va...@terse.ca
Plan your future! Make God laugh!
this by running with TERM=vt100, but on
-current that workaround no longer works.
dave
--
Dave Vandervies
dj3va...@terse.ca
Plan your future! Make God laugh!
Since upgrading to 6.7 I've occasionally seen the tmux server crash
when a client connects to a session.
(I can't say for sure that it never happened pre-6.7, since it's
occasional and my usage patterns have drifted over time.)
Today it annoyed me enough to track it down, and it looks like a
loop
job: http://www.tedunangst.com/flak/post/vmtimed
Port: http://terse.ca/vmtimed.tar.gz
--
Dave Vandervies
dj3va...@terse.ca / dj3va...@uwaterloo.ca
Plan your future! Make God laugh!
On an amd64 5.8-release system running under VMWare, with the virtual USB
controller configured as USB 2.0, I'm seeing a problem getting device
descriptor strings off of USB devices (or, at least, the one that I
care about).
With the virtual USB configured to support USB 3.0, the problem goes
/* sunos 4.1.x & osf/1 processes discard(flush) when ~icanon */
--
Dave Vandervies
dj3va...@terse.ca / dj3va...@uwaterloo.ca
Plan your future! Make God laugh!
10 matches
Mail list logo