NetBSD-Bugs archive

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

Re: port-amd64/53155: OS wedges after <12h uptime when >2 bnx network interfaces in use

> On Thu, Apr 05, 2018 at 07:25:00AM +0000, Havard Eidnes wrote:
>>  --- interrupt ---
>>  Bad frame pointer: 0xffff800000000000
>>  202:
>>  db{0}: machine cpu 1
>>  using CPU 1
>>  db{0}: tra
>>  x86_pause() at netbsd:x86_pause+0x2
>>  cdev_open() at netbsd:cdev_open+0xaf
>>  spec_open() at netbsd:spec_open+0x260
>>  VOP_OPEN() at netbsd:VOP_OPEN+0x33
>>  vn_open() at netbsd:vn_open+0x28b
>>  do_open() at netbsd:do_open+0x112
>>  do_sys_openat() at netbsd:do_sys_openat+0x68
>>  sys_open() at netbsd:sys_open+0x24
>>  syscall() at netbsd:syscall+0x1ed
> Any chance to find out what device this is? I wonder due to the kernel
> lock instances on the other cores...

For one, the machine is no longer sitting in DDB, it is a
semi-normal production machine so needs to be up most of the

Secondly, how would I go about finding out?

I don't even know how to identify which process this is, perhaps
other than doing a backtrace of each and every process on the
system at the time of the wedge.

However, if I were going to give a guess, I would guess at one of
the expect processes, which typically want to open a pty pair,
which should match the cdev_open() use.


- Håvard

Home | Main Index | Thread Index | Old Index