On Tue, Oct 09, 2018 at 05:32:57PM +, m...@netbsd.org wrote:
> Invalid TSS (this might be the right one)
It's probably not! it's probably "invalid TSS" :-)
On Wed, Sep 26, 2018 at 11:33:49PM +0200, Riccardo Mottola wrote:
> T43 "new": does go to sleep, but does not resume (while stock 8 does).
Better strategy: since we you have a machine that worked at some point,
you should try to bisect it. it's a somewhat tedious process of testing
~13 different k
On Tue, Oct 09, 2018 at 01:12:31AM +0200, Riccardo Mottola wrote:
> yet on sleep it crashes. I was able to catch the error.
> I add that even if it says "flushing disk" at the next reboot, the
> filesystem is dirty.
>
That's expected: I think we write a bit to the filesystem at mount and
only
On Tue, Oct 09, 2018 at 01:12:31AM +0200, Riccardo Mottola wrote:
> acpi0: entering state S3
> flushing disk caches: 16 done
> fatal protection fault in supervisor mode
> trap type 4 code 0 eip 0xc0135ea3 cd 0x8 eflags 0x210046 cr2 0xdac2b0c4
> ilevel 0x8 esp 0xc1210c80
> curlwp 0xc36422c0 pid 658
I purchased a couple of USB-serial adapters. Unfortunately, given the lack
of detail in the descriptions, they turned out to be
uchcom0: QinHeng Electronics (0x1a86) USB2.0-Ser! (0x7523), rev 1.10/2.54
According to
https://nxr.netbsd.org/xref/src/sys/dev/usb/uchcom.c#40
this is "the worst U
