Date: Wed, 15 Sep 2004 13:06:10 +0900 From: Pyun YongHyeon <yongari@kt-is.co.kr> To: Doug Haigh <cd_freebsd@gatorzone.com> Cc: sparc64@freebsd.org Subject: Re: sparc64/71729: printf in kernel thread causes panic on SPARC Message-ID: <20040915040610.GB8052@kt-is.co.kr> In-Reply-To: <200409141548.i8EFm998087028@www.freebsd.org> References: <200409141548.i8EFm998087028@www.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 14, 2004 at 03:48:09PM +0000, Doug Haigh wrote: > > >Number: 71729 > >Category: sparc64 > >Synopsis: printf in kernel thread causes panic on SPARC > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-sparc64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Sep 14 15:50:17 GMT 2004 > >Closed-Date: > >Last-Modified: > >Originator: Doug Haigh > >Release: SPARC 5.2.1 > >Organization: > >Environment: > FreeBSD stesthost 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #12: Mon Sep 13 10:35:08 EDT 2004 cd@stesthost:/usr/src/sys/sparc64/compile/DBGKERNEL sparc64 > > THis is an Ultra-60 dual proc machine > >Description: > I create a kernel thread in my driver using kthread_create. When the thread routine executes, it tries to print out a debug message using 'printf'. When this executes, I trap in a panic with the following trace: > I'm currently experimenting fdc(4) on sparc64. In fdc(4) it creates a kernel thread with kthread_create(9). So I added a printf(9) in the thread handler to see whether it panics. But it never paniced the system and the message was displayed correctly. This is AXe UP machine(6.0-CURRENT). Myabe format(args. used in printf) dependent? > panic() at panic+0x174 > trap() at trap+0x3b4 > -- fast data access mmu miss tar=0 %o7=0xf000d784 > _end() at 0xf0008fd0 > openfirmware() at openfirmware+0x18 > OF_write() at OF_write+0x14 > ofw_cons_putc() at ofw_cons_putc+0x3c > cnputc() at cnputc+0x7c > putchar() at putchar+0x5c > kvprintf() at kvprintf+0x648 > printf() at printf+0x4C > > Same code works fine on i386 machines. > > >How-To-Repeat: > Create a driver that creates a thread and do a printf in the thread routine. > >Fix: > > >Release-Note: > >Audit-Trail: > >Unformatted: > _______________________________________________ > freebsd-sparc64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 > To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org" Regards, Pyun YongHyeon -- Pyun YongHyeon <http://www.kr.freebsd.org/~yongari>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040915040610.GB8052>