NetBSD-Bugs archive

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

Re: kern/40945: system process locked at 100% CPU


I haven't pinpointed the actual cause, here's the full conf of the
working kernel setup:

include "arch/amd64/conf/std.amd64"
options         INCLUDE_CONFIG_FILE    
ident           "$Revision: 280409-1$"
maxusers        128           
options         CPURESET_DELAY=500
options         RTC_OFFSET=0   
options         NTP            
options         KTRACE         
options         SYSVMSG        
options         SYSVSEM        
options         SYSVSHM        
options         MODULAR        
options         USERCONF       
options         SYSCTL_INCLUDE_DESCR   
options         ENHANCED_SPEEDSTEP
options         BUFQ_PRIOCSCAN
makeoptions     COPTS="-O2 -fno-omit-frame-pointer"
options         COMPAT_NETBSD32
options         COMPAT_LINUX
options         COMPAT_LINUX32 
options         EXEC_ELF32
options         COMPAT_BSDPTY  
file-system     FFS            
file-system     LFS            
file-system     MFS            
file-system     NFS            
file-system     CD9660         
file-system     MSDOSFS        
file-system     FDESC          
file-system     KERNFS         
file-system     NULLFS         
file-system     OVERLAY        
file-system     PROCFS         
file-system     UMAPFS         
file-system     PTYFS          
file-system     TMPFS          
options         QUOTA          
options         WAPBL          
options         NFSSERVER      
options         GATEWAY        
options         INET           
options         INET6          
options         MROUTING       
options         PFIL_HOOKS     
options         IPFILTER_LOG   
options         IPFILTER_LOOKUP
options         RANDOM_IP_ID
options         SCSIVERBOSE    
options         WSEMUL_VT100           
options         WS_KERNEL_FG=WSCOL_GREEN
options         WSDISPLAY_COMPAT_PCVT          
options         WSDISPLAY_COMPAT_SYSCONS       
options         WSDISPLAY_COMPAT_USL           
options         WSDISPLAY_COMPAT_RAWKBD        
config          netbsd  root on ? type ?
ipmi0           at mainbus?
acpi0           at mainbus0
options         ACPI_SCANPCI           
options         MPBIOS                 
options         MPBIOS_SCANPCI         
options         VGA_POST               
hpet*           at acpi?               
pckbc*          at acpi?               
pci*    at mainbus? bus ?
pci*    at pchb? bus ?
pci*    at ppb? bus ?
pchb*   at pci? dev ? function ?       
pcib*   at pci? dev ? function ?       
ppb*    at pci? dev ? function ?       
ichlpcib* at pci? dev ? function ?     
agp*    at pchb?
isa0    at ichlpcib?
pckbd*          at pckbc?              
vga*            at pci? dev ? function ?
wsdisplay*      at vga? console ?
wsdisplay*      at wsemuldisplaydev?
wskbd*          at pckbd? console ?
com0    at isa? port 0x3f8 irq 4       
com1    at isa? port 0x2f8 irq 3
options         INTEL_CORETEMP
scsibus* at scsi?
sd*     at scsibus? target ? lun ?     
st*     at scsibus? target ? lun ?     
cd*     at scsibus? target ? lun ?     
ch*     at scsibus? target ? lun ?     
ses*    at scsibus? target ? lun ?     
uk*     at scsibus? target ? lun ?     
piixide* at pci? dev ? function ?      
atabus* at ata?
wd*     at atabus? drive ? flags 0x0000
atapibus* at atapi?
cd*     at atapibus? drive ? flags 0x0000      
sd*     at atapibus? drive ? flags 0x0000      
st*     at atapibus? drive ? flags 0x0000      
uk*     at atapibus? drive ? flags 0x0000      
re*     at pci? dev ? function ?       
rgephy* at mii? phy ?                  
ehci*   at pci? dev ? function ?       
uhci*   at pci? dev ? function ?       
usb*    at ehci?
usb*    at uhci?
uhub*   at usb?
uhub*   at uhub? port ?
uhidev* at uhub? port ? configuration ? interface ?
ukbd*   at uhidev? reportid ?
wskbd*  at ukbd? console ? mux 1
uhid*   at uhidev? reportid ?
umass*  at uhub? port ? configuration ? interface ?
cinclude "arch/amd64/conf/GENERIC.local"
pseudo-device   crypto                 
pseudo-device   swcrypto               
pseudo-device   bio                    
pseudo-device   ccd             4      
pseudo-device   cgd             4      
pseudo-device   raid            8      
options         RAID_AUTOCONFIG        
pseudo-device   fss             4      
pseudo-device   md              1      
options         MEMORY_DISK_HOOKS      
options         MEMORY_DISK_DYNAMIC    
pseudo-device   vnd                    
pseudo-device   bpfilter               
pseudo-device   ipfilter               
pseudo-device   loop                   
pseudo-device   ppp                    
pseudo-device   tun                    
pseudo-device   tap                    
pseudo-device   gre                    
pseudo-device   gif                    
pseudo-device   stf                    
pseudo-device   vlan                   
pseudo-device   bridge                 
pseudo-device   accf_data              
pseudo-device   accf_http              
pseudo-device   pty                    
pseudo-device   rnd                    
pseudo-device   clockctl               
pseudo-device   ksyms                  
pseudo-device   lockstat               
pseudo-device   wsmux                  
pseudo-device   wsfont
pseudo-device   drvctl
options         FILEASSOC              
pseudo-device   veriexec                1
options         PAX_MPROTECT=0         
options         PAX_ASLR=0

P.S. On a side note, I must admit I'm really amazed by the new
improvements within NetBSD 5 - I've only recently upgraded from version
2. Rock on.

David Holland a écrit :
> The following reply was made to PR kern/40945; it has been noted by GNATS.
> From: David Holland <>
> To:
> Cc: 
> Subject: Re: kern/40945: system process locked at 100% CPU
> Date: Wed, 6 May 2009 22:39:14 +0000
>  On Mon, May 04, 2009 at 03:30:05PM +0000, okay_awright wrote:
>   >  The bug is still present in the final 5.0 release.
>   >  The only workaround I was able to find (I'm no kernel hacker or ACPI
>   >  expert) is to disable every Intel sensor device within the kernel, then
>   >  the problem disappears and the system process remains idle. Something
>   >  may be broken or incomplete within the new envsys 2, for information the
>   >  problem did not appear in the previous (4.0) distribution.
>  Which drivers specifically do you need to disable? (And do you need to
>  disable all of them or is there just one that's really causing the
>  problem? I'd expect the latter.)
>  -- 
>  David A. Holland

Home | Main Index | Thread Index | Old Index