Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Crash on port-amd64



On Sun, 20 Apr 2008, Andrew Doran wrote:

On Fri, Apr 18, 2008 at 04:33:25PM -0700, Paul Goyette wrote:

This is with a up-to-date kernel (sources updated via CVS about 8 hours
ago).

While I had a './build.sh release' running, I got the following console
output:

kernel: page fault trap, code=0
Stopped in pid 11487.1 (cc1) at netbsd:kauth_authorize_action + 0x0a:
call *0(%rbx)

It could be bad hardware. However, others have reported severe memory
corruption on recent -current/amd64 with heavy network activity. I am
investigating that.

Simply to exclude the possibility, were you doing anything to kauth at
the time?

I don't touch kauth - I don't understand it well enough to touch it! :)
This is a "stock" 4.99.60 kernel plus the recent jumbo-frame fix for if_nfe. Sources were CVS-updated on 2008-04-18 at 23:51:17 UTC.

Seriously, there was nothing special going on, just a 'build.sh release'. My /usr/src and /usr/obj are NFS-exported, but the build.sh was running on the NFS server, not on a client. There _might_ have been a low level of NFS activity from one of my other machines, such as caused by a 'ls /usr/src', but nothing significant - ie I wasn't running 'find /usr/src/...') And I've since been successful at re-running the same 'build.sh release' without any problems.

----------------------------------------------------------------------
|   Paul Goyette   | PGP DSS Key fingerprint: |  E-mail addresses:   |
| Customer Service | FA29 0E3B 35AF E8AE 6651 |  paul%whooppee.com@localhost   |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette%juniper.net@localhost |
----------------------------------------------------------------------


Home | Main Index | Thread Index | Old Index