|
List Info
Thread: Digital Server 5300
|
|
| Digital Server 5300 |
  Netherlands |
2007-06-15 05:01:29 |
|
| OpenBSD 4.2 adds support for AlphaServer 1200. I have a DigitalServer
5300 which is just a 1200 remarketed for Windows NT.
The system boots fine (see attachment boot.log). However:
panic: trap
Stopped at Debugger+0x4: ret zero,(ra)
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS
PANIC!
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb> trace
Debugger(4, fffffc00008486d0, 5, 8, 3, 8) at Debugger+0x4
panic(fffffc0000821f08, fffffe0002b83cf0, 108, 2, fffffe0002b83cf0,
166c7fd45f7
34742) at panic+0x100
trap(?, 1, 0, ?, ?, 166c7fd45f734742) at trap+0xc0
XentMM(?, 1, 0, ?, ?, 166c7fd45f734742) at XentMM+0x20
tulip_tx_intr(?, ?, ?, ?, a, 166c7fd45f734742) at tulip_tx_intr+0x17c
tulip_intr_handler(?, ?, ?, ?, a, 166c7fd45f734742) at
tulip_intr_handler+0x1d8
tulip_intr_handler(?, ?, ?, ?, a, 166c7fd45f734742) at
tulip_intr_handler+0x1d8
ddb> ps
PID PPID PGRP UID S FLAGS WAIT COMMAND
*12951 17427 17427 0 7 0x4002 ssh
17427 4819 17427 0 2 0x4002 cvs
4819 30121 4819 0 3 0x4082 pause ksh
30121 16194 30121 0 3 0x4080 select sshd
9118 1 9118 0 3 0x40180 select sendmail
2201 1 2201 0 3 0x80 select cron
16194 1 16194 0 3 0x80 select sshd
22164 1 22164 0 3 0x180 select inetd
13299 22313 22313 73 3 0x180 poll syslogd
22313 1 22313 0 3 0x88 netio syslogd
9 0 0 0 3 0x100200 crypto_wa crypto
8 0 0 0 3 0x100200 aiodoned aiodoned
7 0 0 0 3 0x100200 syncer update
6 0 0 0 3 0x100200 cleaner cleaner
5 0 0 0 3 0x100200 reaper reaper
4 0 0 0 3 0x100200 pgdaemon pagedaemon
3 0 0 0 3 0x100200 pftm pfpurge
2 0 0 0 3 0x100200 bored syswq
1 0 1 0 3 0x4080 wait init
0 -1 0 0 3 0x80200 scheduler swapper
ddb>
This is reproduceable with a simple (nmap) portscan or any intensive
Network usage.
Note that this is not a bug report. I don't need this machine running.
However, if somebody is interrested in helping out, I'd be glad to
report.
Cheers,
Pascal
|
Approximate file size 9980 bytes |
| Re: Digital Server 5300 |
  Austria |
2007-06-15 08:54:55 |
"Pascal S. de Kloe" <pascal quies.net> wrote:
> OpenBSD 4.2 adds support for AlphaServer 1200. I have a
DigitalServer
> 5300 which is just a 1200 remarketed for Windows NT.
>
> The system boots fine (see attachment boot.log).
However:
>
>
> panic: trap
> Stopped at Debugger+0x4: ret zero,(ra)
> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN
REPORTING THIS
> PANIC!
> DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING
THAT INFORMATION!
> ddb> trace
> Debugger(4, fffffc00008486d0, 5, 8, 3, 8) at
Debugger+0x4
> panic(fffffc0000821f08, fffffe0002b83cf0, 108, 2,
fffffe0002b83cf0,
> 166c7fd45f7
> 34742) at panic+0x100
> trap(?, 1, 0, ?, ?, 166c7fd45f734742) at trap+0xc0
> XentMM(?, 1, 0, ?, ?, 166c7fd45f734742) at XentMM+0x20
> tulip_tx_intr(?, ?, ?, ?, a, 166c7fd45f734742) at
tulip_tx_intr+0x17c
> tulip_intr_handler(?, ?, ?, ?, a, 166c7fd45f734742) at
> tulip_intr_handler+0x1d8
>
> tulip_intr_handler(?, ?, ?, ?, a, 166c7fd45f734742) at
> tulip_intr_handler+0x1d8
>
>
> ddb> ps
> PID PPID PGRP UID S FLAGS WAIT
COMMAND
> *12951 17427 17427 0 7 0x4002
ssh
> 17427 4819 17427 0 2 0x4002
cvs
> 4819 30121 4819 0 3 0x4082 pause
ksh
> 30121 16194 30121 0 3 0x4080 select
sshd
> 9118 1 9118 0 3 0x40180 select
sendmail
> 2201 1 2201 0 3 0x80 select
cron
> 16194 1 16194 0 3 0x80 select
sshd
> 22164 1 22164 0 3 0x180 select
inetd
> 13299 22313 22313 73 3 0x180 poll
syslogd
> 22313 1 22313 0 3 0x88 netio
syslogd
> 9 0 0 0 3 0x100200 crypto_wa
crypto
> 8 0 0 0 3 0x100200 aiodoned
aiodoned
> 7 0 0 0 3 0x100200 syncer
update
> 6 0 0 0 3 0x100200 cleaner
cleaner
> 5 0 0 0 3 0x100200 reaper
reaper
> 4 0 0 0 3 0x100200 pgdaemon
pagedaemon
> 3 0 0 0 3 0x100200 pftm
pfpurge
> 2 0 0 0 3 0x100200 bored
syswq
> 1 0 1 0 3 0x4080 wait
init
> 0 -1 0 0 3 0x80200 scheduler
swapper
> ddb>
>
>
> This is reproduceable with a simple (nmap) portscan or
any intensive
> Network usage.
>
> Note that this is not a bug report. I don't need this
machine running.
> However, if somebody is interrested in helping out, I'd
be glad to
> report.
A workaround would be disabling de(4) by booting 'boot -fl
c'. dc(4)
should run better.
|
|
[1-2]
|
|