Re: Current port status

[Frank Wille <frank%phoenix.owl.de@localhost>]

Here is an update:

On Wed, 1 Feb 2012 11:14:52 +0100
Frank Wille <frank%phoenix.owl.de@localhost> wrote:

> - (since 5.99.61) Problems after some major changes in the
> uvm/kmem/malloc code. The worst problem had been resolved (matt) but
> it still cannot mount the root file system anymore (/dev/console not
> found) and crashes.

Probably solved with http://www.netbsd.org/~matt/uvm_km.txt.
Needs testing.


> - (since 5.99.60) genfb(4) has wrong colors. Now it display pink
> kernel messages on a black background, while it was green on white
> before. The normal output is probably black on black now, and
> unreadable. The config files had not been changed.
> 
> - (since 5.99.56) The disklabel on MBR partitioned disks is no longer
>   correctly recognized. This is probably my fault. Will be fixed as
> soon as possible.

This point was fixed yesterday, just in time!


> - (since ~5.99.55) Firefox has become unstable. It crashes frequently.
>   Tabs and the scrolling wheel stop working. Problem can also be
> observed on macppc. Caused by switching gcc to 4.5.3 last summer?
> 
> - (since ~5.99.52) Problems with XOrg's mouse pointer acceleration
> make the pointer jump to the left or right screen border, and the
> only way to get it away from there is by typing "xset m 0". Also on
> macppc.
> 
> - (since ~5.99.41) The kernel hangs when detecting an USB device on
> the port (corrupted usb fragments). There is a workaround for it by
> setting the option USB_FRAG_DMA_WORKAROUND.

Example: This is a typical panic without USB_FRAG_DMA_WORKAROUND, when
plugging in an USB device:
  trap: kernel read DSI trap @ 0xb6938101 by usb_allocmem+0xec: srr1=0x9032,
  r1=0xaa759cc0 cr=0x28000088 xer=0 ctr=0x4199ac dsisr=0x40000000
  save LR(0xfffffffd) is inavalid.


Two more, which I forgot:

- (since ~5.99.40 or earlier?) Random lock errors, when launching a kernel.
  With some kernel revisions this happens frequently, with others rarely.
  The workaround is to boot the kernel once again, until it works.
  Example (messages appear before the copyright):
  WARNING: add memory segment 10000000-20000000,
  WARNING: which was not recognized by the Firmware.
  Reader / writer lock error: rw_vector_enter: lock against myself
  lock address: 0x0000000000459744
  current cpu:                   0
  current int:  0x000000000043c740
  owner/count:  0x000000000043c740  Flags: 0x0000000000000004
  panic: lock error

- (5.99.59) vr0: device timeout. Problems with vr(4). Might be 5.99.59 only.
  Needs more testing.


-- 
Frank Wille