Subject: port-i386/36920: NetBSD 4.0_BETA2 'supervisor trap integer divide fault' panic
To: None <port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Hauke Fath <hf@spg.tu-darmstadt.de>
List: netbsd-bugs
Date: 09/05/2007 16:55:00
>Number:         36920
>Category:       port-i386
>Synopsis:       NetBSD 4.0_BETA2 'supervisor trap integer divide fault' panic
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 05 16:55:00 +0000 2007
>Originator:     Hauke Fath <hf@spg.tu-darmstadt.de>
>Release:        NetBSD 4.0_BETA2
>Organization:
-- 
     The ASCII Ribbon Campaign                    Hauke Fath
()     No HTML/RTF in email	        Institut für Nachrichtentechnik
/\     No Word docs in email                     TU Darmstadt
     Respect for open standards              Ruf +49-6151-16-3281
>Environment:
	
	
System: NetBSD Hochstuhl 4.0_BETA2 NetBSD 4.0_BETA2 (HOCHSTUHL) #0: Mon Aug 27 16:30:58 CEST 2007  hf@Hochstuhl:/var/obj/netbsd-builds/4/i386/sys/arch/i386/compile/HOCHSTUHL i386
Architecture: i386
Machine: i386
>Description:

	After installing wip/tsm (IBM Tivoli Storage Manager backup
	client, linux binary) I started the cli tool dsmc, and got

kernel: supervisor trap integer divide fault, code=0
Stopped in pid 24176.1 (dsmc) at        netbsd:__qdivrem+0x38:  divl    %ecx,%eax
db{1}> t
__qdivrem(0,0,0,0,0) at netbsd:__qdivrem+0x38
__udivdi3(0,0,0,0,0) at netbsd:__udivdi3+0x19
bsd_to_linux_statfs64(0,cc77468c,bfbfefb8,c021787a,c046cde0) at netbsd:bsd_to_linux_statfs64+0x8e
linux_sys_statfs64(cc7d778c,d69d5c48,d69d5c68,830a2e6,830a000) at netbsd:linux_sys_statfs64+0xed
linux_syscall_plain(d69d5c88,2b,2b,2b,2b) at netbsd:linux_syscall_plain+0xb6
db{1}> sync
syncing disks...

and then the box hung, so no coredump.

The machine is a
cpu0: AMD Dual-Core Opteron or Athlon 64 X2 (686-class), 1795.66 MHz, id 0x20f32
cpu0: "Dual Core AMD Opteron(tm) Processor 165"
running NetBSD/i386.

wip/tsm has been used in production on two netbsd-3 machines here for
quite a while, without any problems.

>How-To-Repeat:
	Install netbsd-4, then wip/tsm. Start dsmc, try to log in to TSM server.

>Fix:
	Don't use TSM?

>Unformatted: