On Fri, Oct 17, 2003 at 01:31:08AM +0900, NISHIO Yasuhiro wrote:
> Bouyer san.
> Thank you for your reply.
> 
> > Sigh, we may have to block interrupts for the reset. Please try the
> > attached patch.
> 
> I try it. And got loops on intr again.
> But there are little bit changes.
> 
> - normal boot
> 	-> I got ``bogus intr'' messages.
> 		messages displayed more than 20 minuts,
> 		disk access LED is off.
> 
> - boot with ddb
> 	-> wdcebug_mask = 0x7f 
> 	   	I found LED blinking.
> 		And kernel found the wd0, wd1 and booting the system
> 		
>   ==========		
>   $ egrep -v '^(wdc|__wd)' BOOT-LOG-FILE | tail
>   system is cleanwdcstart from wdc_exec_xfer, flags 0x0
>   ; not checking
>   /dev/rwd0m: filewdc_exec_xfer 0xc1343034 channel 0 drive 0
>   system is cleanwdcstart from wdc_exec_xfer, flags 0x0
>   ; not checking
>   /dev/rwd0n: filewdc_exec_xfer 0xc1343034 channel 0 drive 0
>    system is cleanwdcstart from wdc_exec_xfer, flags 0x0
>   ; not checking
>   Setting tty flagwdc_exec_xfer 0xc1343034 channel 0 drive 0
>   s.
>   ==========  
> I use Serial console that speed is 9600 baud. I think there is a difference
> the interrupt timing.

Probably.

> 
> If you are interested in this result, Would you please check the full log at
> 
>      http://www.hh.iij4u.or.jp/~nishio/netbsd/1016/
> 	normal-boot.log			 5.3kB(boot netbsd.p2)	
> 	ddb-wdcdebug_mask=0x7f.log	99.5kB(boot netbsd.p2 -d,
> 						    wdcdebug_mask=0x7f)

These returns "file not found" for me

However, it seems even when the box doesn't loop on intr you
still get "bogus intr".
I just tried on my promise U100, I get them too. My U66 or U133 don't have
this problem, it seems to be a quirk or the U100.

I'll try to look more at this this week-end, but I don't have any idea of
where these spurious interrupts comes from yet.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--