Subject: -current oddities
To: None <port-alpha@netbsd.org>
From: Michael G. Schabert <mikeride@prez.org>
List: port-alpha
Date: 08/30/1999 18:48:28 
Hi all,
I noticed that my kernel (one yesterday & one today) doesn't shutdown
properly. It seems to stop doing anything after synching the disks. When I
shutdown (I've tried -h and -r, & the reboot command), it shows this:
*** FINAL System shutdown message from mikeride@prez.buf.servtech.com ***
System going down IMMEDIATELY


Aug 30 18:22:34 prez shutdown: halt by mikeride:
Aug 30 18:22:34 prez shutdown: halt by mikeride:
Aug 30 18:22:43 prez syslogd: exiting on signal 15
Aug 30 18:22:43 prez syslogd: exiting on signal 15
syncing disks... 11 11 11 8 6 done

and it stops on the next line. I never get the >>> that I used to. Even
when I hit the reset button, it jumps to
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.ed.ec.f4.eb.....ea.e9.e8.e7.e6.e5.
V6.1-2, built on May  8 1996 at 10:26:42

without showing me the >>> ??? I'm using serial console, is there any way
to try to force a debugger? I've tried just waiting & typing
<return>b<return>, as well as trying tr<return> to see if a trace might
come out, both to no avail.


Another peculiarity with -current is that PC cards are no longer
hot-swappable. It doesn't notice when I put one in, like t used to. My
guess is that that ability was temporarily backed out because some ports
were having trouble with that freezing the machine, although I'd been doing
it consistently on my Alpha for awhile. If that's an intentional
limitation, no probs, I just didn't know if it was or not.

Any info greatly appreciated.

Thank you,
Mike
Bikers don't *DO* taglines.
Do I need to enable something in my kernel config? I have a pretty pared-down system, which I arrived at by commenting out anything I saw in GENERIC that I didn't see in a grep of dmesg (as per the kernel how-to), but with some pcmcia lines added in that were in other included configs. On a similar note, since that card wasn't doing much for me, I threw in an el-cheapo SoundBlaster 16 card. When I first did this (a couple weeks ago) it was pretty much totally unsupported: Aug 23 20:21:29 prez /netbsd: isapnp0: read port 0x203 Aug 23 20:21:29 prez /netbsd: isapnp0: card 1 violates PnP spec; byte 0 Aug 23 20:21:29 prez /netbsd: isapnp0: Maximum tag size exceeded, card 1 Aug 23 20:21:29 prez /netbsd: isapnp0: No current device for tag, card 1 Aug 23 20:21:30 prez /netbsd: isapnp0: Maximum tag size exceeded, card 1 Aug 23 20:21:30 prez /netbsd: isapnp0: No current device for tag, card 1 which continued for awhile. I compiled a new kernel yesterday, & now see that it's recognised, but still not configured. Here's the current dmesg: isapnp0: read port 0x203 sb0 at isapnp0 port 0x220/16,0x300/2,0x388/4 irq 10 drq 1,5 sb0: sbmatch failed isapnp0: <Creative ViBRA16C PnP, CTL7001, PNPB02F, Game> port 0x200/8 not configured isapnp0: <SCM SwapBox Plug and Play, SCM0469, , > port 0x3e2/2 not configured Is that card on its way to being supported, by the fact that it's "getting closer" to being recognized properly? I'm certainly willing to be a guinnea pig if I'm SOL as far as the built-in card goes. Thanks for any insight, Mike Bikers don't *DO* taglines.