kernel/4971: Kernel panic (apm)

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

kernel/4971: Kernel panic (apm)

Emilio Perea
>Number:         4971
>Category:       kernel
>Synopsis:       panic on -current kernel
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    bugs
>State:          open
>Quarter:        
>Keywords:      
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jan 13 20:10:02 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Emilio Perea
>Release:        3.8 -current
>Organization:
net
>Environment:
       
        System      : OpenBSD 3.8
        Architecture: OpenBSD.i386
        Machine     : i386
>Description:

This was a crash this morning, running -current kernel as of yesterday
morning.  It ran without problems for almost 24 hours before dropping to
ddb.  I have switched to the last snapshot kernel and will report any
further problem.
*----------------------------------------------------------------------*
panic: lockmgr: pid 3, not exclusive lock holder 3 unlocking
Stopped at    Debugger+0x4:   leave
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION
ddb> trace
Debugger(d0f3df89,e7d06f44,e7d06f6c,6,d0f3dfc0) at Debugger+0x4
panic(d0515fe0,3,3,0,800b) at panic+0x63
lockmgr(d0f3dfc0,6,0,0,d0f3df80) at lockmgr+0xbb
apm_thread(d0f3df80) at apm_thread+0x2c
Bad frame pointer: 0xd0708e98
ddb> ps
   PID   PPID   PGRP    UID  S       FLAGS  WAIT          COMMAND
  5530   9373   3651   7791  3       0x184  poll          tcpserver
 16910  16176  15763   1000  3      0x4086  piperd        tai64nlocal
 15763  16176  15763   1000  3      0x4086  pause         tail
 16176   2777  16176   1000  3      0x4086  pause         tcsh
  2777  20404  20404   1000  3       0x184  select        sshd
 20404  23158  20404      0  3      0x4184  netio         sshd
  1153   7950   7950     67  3       0x184  netcon        httpd
 23337   4028   3651   7794  3      0x4084  piperd        qmail-clean
  3004   4028   3651   7795  3      0x4084  select        qmail-rspawn
 32745   4028   3651      0  3      0x4084  select        qmail-lspawn
  9872  10844   3651  1697246030  3      0x4084  piperd        multilog
 26404  13632   3651      0  3      0x4084  netcon        tcpserver
  4390  14407   3651  1697246030  3      0x4084  piperd        multilog
 11337  26062   3651  1270288640  3      0x4184  poll          dnscache
 14734   9707   3651  1168820790  3      0x4184  netio         tinydns
  4510   3765   3651  1697246030  3      0x4084  piperd        multilog
  6814  26139   3651  1697246030  3      0x4084  piperd        multilog
 14292  17912   3651  1697246030  3      0x4084  piperd        multilog
 28739   2998   3651  1168820790  3      0x4184  netio         tinydns
  2027  19768   3651      0  3      0x4084  netcon        tcpserver
  4028  18539   3651   7796  3      0x4084  select        qmail-send
 14159  29745   3651      0  3      0x4084  netcon        tcpserver
 32058  12859   3651   7792  3      0x4084  piperd        multilog
 18599  19015   3651   7792  3      0x4084  piperd        multilog
  9373   1102   3651   7791  3      0x4184  netcon        tcpserver
 15995  16476   3651   7792  3      0x4084  piperd        multilog
 17912   7852   3651      0  3      0x4084  poll          supervise
 13632   7852   3651      0  3      0x4084  poll          supervise
 14407   7852   3651      0  3      0x4084  poll          supervise
  9797   7852   3651      0  3      0x4084  poll          supervise
  3765   7852   3651      0  3      0x4084  poll          supervise
  2998   7852   3651      0  3      0x4084  poll          supervise
 10844   7852   3651      0  3      0x4084  poll          supervise
 19768   7852   3651      0  3      0x4084  poll          supervise
 12598   7852   3651      0  3      0x4084  poll          supervise
 12859   7852   3651      0  3      0x4084  poll          supervise
 29745   7852   3651      0  3      0x4084  poll          supervise
 19015   7852   3651      0  3      0x4084  poll          supervise
  1102   7852   3651      0  3      0x4084  poll          supervise
 16476   7852   3651      0  3      0x4084  poll          supervise
 18539   7852   3651      0  3      0x4084  poll          supervise
 26139   7852   3651      0  3      0x4084  poll          supervise
 26062   7852   3651      0  3      0x4084  poll          supervise
 12335   3651   3651      0  3      0x4084  piperd        readproctitle
  7852   3651   3651      0  3      0x4084  nanosleep     svscan
 11452      1  11452      0  3      0x4086  ttyin         getty
 22680      1  22680      0  3      0x4086  ttyin         getty
 29497      1  29497      0  3      0x4086  ttyin         getty
 29049      1  29049      0  3      0x4086  ttyin         getty
 26134      1  26134      0  3      0x4086  ttyin         getty
 23139      1  23139      0  3        0x84  select        cron
  3651      1   3651      0  3      0x4086  pause         sh
 23158      1  23158      0  3        0x84  select        cron
 20525   7950   7950     67  3       0x184  netcon        httpd
 30792   7950   7950     67  3       0x184  netcon        httpd
 19331   7950   7950     67  3       0x184  netcon        httpd
 29156   7950   7950     67  3       0x184  netcon        httpd
 22876   7950   7950     67  3       0x184  netcon        httpd
 14472      1  14472      0  3       0x184  select        inetd
 28881      1  28881      0  3        0x84  poll          ftpd
  7950      1   7950     67  3       0x184  select        httpd
 19366      1  19366      0  3   0x40184  select        lpd
  1063  31040  31040     83  3       0x184  poll          ntpd
 31040      1  31040      0  3        0x84  poll          ntpd
 30370  17393  17393     73  3       0x184  poll          syslogd
 17393      1  17393      0  3        0x84  netio         syslogd
    14      0      0      0  3    0x100204  crypto_wa     crypto
    13      0      0      0  3    0x100204  aiodoned      aiodoned
    12      0      0      0  0    0x100204                update
    11      0      0      0  3    0x100204  cleaner       cleaner
    10      0      0      0  3    0x100204  reaper        reaper
     9      0      0      0  3    0x100204  pgdaemon      pagedaemon
     8      0      0      0  3    0x100204  pftm          pfpurge
     7      0      0      0  3    0x100204  timeout       sensors
     7      0      0      0  3    0x100204  usbevt        usb1
     5      0      0      0  3    0x100204  usbtsk        usbtaskd
     4      0      0      0  3    0x100204  usbevt        usb0
*    3      0      0      0  3    0x100204                apm0
     2      0      0      0  3    0x100204  kmalloc       kmthread
     1      0      1      0  3      0x4084  wait          init
     0     -1      0      0  3     0x80204  scheduler     swapper
ddb>
*----------------------------------------------------------------------*
dmesg
OpenBSD 3.8-current (GENERIC) #562: Thu Jan 12 09:10:00 CST 2006
    [hidden email]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(tm) XP 2200+ ("AuthenticAMD" 686-class, 256KB L2 cache) 1.81 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
cpu0: AMD Powernow: TS
real mem  = 519614464 (507436K)
avail mem = 467091456 (456144K)
using 4278 buffers containing 26083328 bytes (25472K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(46) BIOS, date 09/02/02, BIOS32 rev. 0 @ 0xfb690
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 70102 dobusy 1 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf0000/0xdad4
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfda50/128 (6 entries)
pcibios0: PCI Exclusive IRQs: 5 11 12
pcibios0: PCI Interrupt Router at 000:17:0 ("VIA VT8233A ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc0000/0xc000 0xcc000/0x5800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT8375 PCI" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8633 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "S3 ProSavage DDR" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ahc0 at pci0 dev 8 function 0 "Adaptec AHA-2940U2 U2" rev 0x00: irq 11
scsibus0 at ahc0: 16 targets
sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST39102LW, 0005> SCSI2 0/direct fixed
sd0: 8683MB, 6962 cyl, 12 head, 212 sec, 512 bytes/sec, 17783240 sec total
sd1 at scsibus0 targ 1 lun 0: <SEAGATE, ST39102LW, 0005> SCSI2 0/direct fixed
sd1: 8683MB, 6962 cyl, 12 head, 212 sec, 512 bytes/sec, 17783240 sec total
sd2 at scsibus0 targ 2 lun 0: <WDIGTL, WDE18300 ULTRA2, 1.30> SCSI2 0/direct fixed
sd2: 17461MB, 9942 cyl, 12 head, 299 sec, 512 bytes/sec, 35761710 sec total
sd3 at scsibus0 targ 3 lun 0: <iomega, jaz 1GB, J.86> SCSI2 0/direct removable
sd3: 1021MB, 1021 cyl, 64 head, 32 sec, 512 bytes/sec, 2091050 sec total
cd0 at scsibus0 targ 4 lun 0: <HP, CD-Writer 6020, 1.07> SCSI2 5/cdrom removable
fxp0 at pci0 dev 9 function 0 "Intel 8255x" rev 0x05, i82558: irq 12, address 00:90:27:86:21:db
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 0
re0 at pci0 dev 10 function 0 "Realtek 8169" rev 0x10: irq 5, address 00:0f:b5:f6:8a:56
rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 0
rl0 at pci0 dev 14 function 0 "Realtek 8139" rev 0x10: irq 5, address 00:30:1b:0f:e1:aa
rlphy0 at rl0 phy 0: RTL internal phy
viapm0 at pci0 dev 17 function 0 "VIA VT8233A ISA" rev 0x00
iic0 at viapm0
pciide0 at pci0 dev 17 function 1 "VIA VT82C571 IDE" rev 0x06: ATA133, channel 0 configured to compatibility, channel 1 configured to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
uhci0 at pci0 dev 17 function 2 "VIA VT83C572 USB" rev 0x23: irq 11
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 17 function 3 "VIA VT83C572 USB" rev 0x23: irq 11
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
auvia0 at pci0 dev 17 function 5 "VIA VT8233 AC97" rev 0x40: irq 5
ac97: codec id 0x414c4710 (Avance Logic ALC200)
ac97: codec features headphone, 18 bit DAC, 18 bit ADC, Realtek 3D
audio0 at auvia0
isa0 at mainbus0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
spkr0 at pcppi0
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
it0 at isa0 port 0x290/8: IT87
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask ef45 netmask ff65 ttymask ffe7
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
ahc0: target 0 using 16bit transfers
ahc0: target 0 synchronous at 40.0MHz, offset = 0xf
dkcsum: sd0 matches BIOS drive 0x80
ahc0: target 1 using 16bit transfers
ahc0: target 1 synchronous at 40.0MHz, offset = 0xf
dkcsum: sd1 matches BIOS drive 0x81
ahc0: target 2 using 16bit transfers
ahc0: target 2 synchronous at 40.0MHz, offset = 0x1f
dkcsum: sd2 matches BIOS drive 0x82
ahc0: target 3 synchronous at 10.0MHz, offset = 0xf
dkcsum: sd3 matches BIOS drive 0x83
root on sd0a
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02
*----------------------------------------------------------------------*
>How-To-Repeat:
        unknown
>Fix:
        unknown


>Release-Note:
>Audit-Trail:
>Unformatted:

Reply | Threaded
Open this post in threaded view
|

Re: kernel/4971: Kernel panic (apm)

Emilio Perea
My recent reply to Pedro's message bounced, so I'm re-sending it here:

----- Forwarded message from Emilio Perea <[hidden email]> -----

Date: Thu, 19 Jan 2006 15:47:53 -0600
From: Emilio Perea <[hidden email]>
To: Pedro Martelletto <[hidden email]>
Subject: Re: kernel/4971: Kernel panic (apm)
In-Reply-To: <[hidden email]>
User-Agent: Mutt/1.5.11

On Fri, Jan 13, 2006 at 07:02:32PM -0200, Pedro Martelletto wrote:

> On Fri, Jan 13, 2006 at 02:58:54PM -0600, Emilio Perea wrote:
> > It has running -current for quite a while.  Yesterday's was only an
> > upgrade from the day before's.
>
> Thanks for the info.
>
> That panic is certainly scary.
>
> Basically, what it is saying is that 3 != 3.
>
> Anyway, I'm on it. Let me know if there's anything else I can do to help
> you. I will let you know if I find something in the code.

Pedro, I assume you didn't find the cause of that panic.  It has not
happened again, so it may have been due to a corrupted source file.
Today I got a couple of these messages:

*----------------------------------------------------------------------*
sd2(ahc0:2:0): Check Condition (error 0x70) on opcode 0x28
    SENSE KEY: Hardware Error
 COMMAND INFO: 0xffffffff
     ASC/ASCQ: ASC 0x44 ASCQ 0xb2
*----------------------------------------------------------------------*

One of the partitions on sd2 is where I have the OpenBSD repository
mirrored by CVSup, so it's possible that a similar hardware problem
caused a file to be corrupted, with "undefined" results.  I feel very
bad about having you follow a false alarm if this turns out to be the
case.  Unless it happens again or you have found something, I would not
pursue this further.

I apologize for the (probable) false alarm!

Emilio

----- End forwarded message -----

Reply | Threaded
Open this post in threaded view
|

Re: kernel/4971: Kernel panic (apm)

Emilio Perea
In reply to this post by Emilio Perea
The following reply was made to PR kernel/4971; it has been noted by GNATS.

From: Emilio Perea <[hidden email]>
To: [hidden email], [hidden email]
Cc:  
Subject: Re: kernel/4971: Kernel panic (apm)
Date: Thu, 19 Jan 2006 16:11:40 -0600

 My recent reply to Pedro's message bounced, so I'm re-sending it here:
 
 ----- Forwarded message from Emilio Perea <[hidden email]> -----
 
 Date: Thu, 19 Jan 2006 15:47:53 -0600
 From: Emilio Perea <[hidden email]>
 To: Pedro Martelletto <[hidden email]>
 Subject: Re: kernel/4971: Kernel panic (apm)
 In-Reply-To: <[hidden email]>
 User-Agent: Mutt/1.5.11
 
 On Fri, Jan 13, 2006 at 07:02:32PM -0200, Pedro Martelletto wrote:
 > On Fri, Jan 13, 2006 at 02:58:54PM -0600, Emilio Perea wrote:
 > > It has running -current for quite a while.  Yesterday's was only an
 > > upgrade from the day before's.
 >
 > Thanks for the info.
 >
 > That panic is certainly scary.
 >
 > Basically, what it is saying is that 3 != 3.
 >
 > Anyway, I'm on it. Let me know if there's anything else I can do to help
 > you. I will let you know if I find something in the code.
 
 Pedro, I assume you didn't find the cause of that panic.  It has not
 happened again, so it may have been due to a corrupted source file.
 Today I got a couple of these messages:
 
 *----------------------------------------------------------------------*
 sd2(ahc0:2:0): Check Condition (error 0x70) on opcode 0x28
     SENSE KEY: Hardware Error
  COMMAND INFO: 0xffffffff
      ASC/ASCQ: ASC 0x44 ASCQ 0xb2
 *----------------------------------------------------------------------*
 
 One of the partitions on sd2 is where I have the OpenBSD repository
 mirrored by CVSup, so it's possible that a similar hardware problem
 caused a file to be corrupted, with "undefined" results.  I feel very
 bad about having you follow a false alarm if this turns out to be the
 case.  Unless it happens again or you have found something, I would not
 pursue this further.
 
 I apologize for the (probable) false alarm!
 
 Emilio
 
 ----- End forwarded message -----

Reply | Threaded
Open this post in threaded view
|

Re: kernel/4971: Kernel panic (apm)

Marco Peereboom
Those messages tell you that the device is broken.  The ASC/ASCQ are vendor
specific.

Toss it.

On Thu, Jan 19, 2006 at 04:25:02PM -0700, Emilio Perea wrote:

> The following reply was made to PR kernel/4971; it has been noted by GNATS.
>
> From: Emilio Perea <[hidden email]>
> To: [hidden email], [hidden email]
> Cc:  
> Subject: Re: kernel/4971: Kernel panic (apm)
> Date: Thu, 19 Jan 2006 16:11:40 -0600
>
>  My recent reply to Pedro's message bounced, so I'm re-sending it here:
>  
>  ----- Forwarded message from Emilio Perea <[hidden email]> -----
>  
>  Date: Thu, 19 Jan 2006 15:47:53 -0600
>  From: Emilio Perea <[hidden email]>
>  To: Pedro Martelletto <[hidden email]>
>  Subject: Re: kernel/4971: Kernel panic (apm)
>  In-Reply-To: <[hidden email]>
>  User-Agent: Mutt/1.5.11
>  
>  On Fri, Jan 13, 2006 at 07:02:32PM -0200, Pedro Martelletto wrote:
>  > On Fri, Jan 13, 2006 at 02:58:54PM -0600, Emilio Perea wrote:
>  > > It has running -current for quite a while.  Yesterday's was only an
>  > > upgrade from the day before's.
>  >
>  > Thanks for the info.
>  >
>  > That panic is certainly scary.
>  >
>  > Basically, what it is saying is that 3 != 3.
>  >
>  > Anyway, I'm on it. Let me know if there's anything else I can do to help
>  > you. I will let you know if I find something in the code.
>  
>  Pedro, I assume you didn't find the cause of that panic.  It has not
>  happened again, so it may have been due to a corrupted source file.
>  Today I got a couple of these messages:
>  
>  *----------------------------------------------------------------------*
>  sd2(ahc0:2:0): Check Condition (error 0x70) on opcode 0x28
>      SENSE KEY: Hardware Error
>   COMMAND INFO: 0xffffffff
>       ASC/ASCQ: ASC 0x44 ASCQ 0xb2
>  *----------------------------------------------------------------------*
>  
>  One of the partitions on sd2 is where I have the OpenBSD repository
>  mirrored by CVSup, so it's possible that a similar hardware problem
>  caused a file to be corrupted, with "undefined" results.  I feel very
>  bad about having you follow a false alarm if this turns out to be the
>  case.  Unless it happens again or you have found something, I would not
>  pursue this further.
>  
>  I apologize for the (probable) false alarm!
>  
>  Emilio
>  
>  ----- End forwarded message -----

Reply | Threaded
Open this post in threaded view
|

Re: kernel/4971: Kernel panic (apm)

Pedro Martelletto
In reply to this post by Emilio Perea
On Thu, Jan 19, 2006 at 04:11:40PM -0600, Emilio Perea wrote:
> My recent reply to Pedro's message bounced, so I'm re-sending it here:

Sorry about that.

I'm closing the PR. If the problem shows up again, please let me know.

-p.