[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: kernel/3743: kernel panic: uvm_fault: ffs
- To: bugs_(_at_)_cvs_(_dot_)_openbsd_(_dot_)_org
- Subject: Re: kernel/3743: kernel panic: uvm_fault: ffs
- From: Marco Peereboom <slash_(_at_)_peereboom_(_dot_)_us>
- Date: Sun, 11 Apr 2004 22:35:02 -0600 (MDT)
- Cc:
- Reply-to: Marco Peereboom <slash_(_at_)_peereboom_(_dot_)_us>
The following reply was made to PR kernel/3743; it has been noted by GNATS.
From: Marco Peereboom <slash_(_at_)_peereboom_(_dot_)_us>
To: craig_(_at_)_copi_(_dot_)_org
Cc: gnats_(_at_)_openbsd_(_dot_)_org
Subject: Re: kernel/3743: kernel panic: uvm_fault: ffs
Date: Sun, 11 Apr 2004 23:18:36 -0500
Dude your drive is dead or dying (or maybe the cable sucks). Replace
the drive ASAP!
This is not a software issue.
On Apr 11, 2004, at 9:19 PM, craig_(_at_)_copi_(_dot_)_org wrote:
>> Number: 3743
>> Category: kernel
>> Synopsis: kernel panic: uvm_fault: ffs
>> Confidential: yes
>> Severity: serious
>> Priority: medium
>> Responsible: bugs
>> State: open
>> Quarter:
>> Keywords:
>> Date-Required:
>> Class: sw-bug
>> Submitter-Id: net
>> Arrival-Date: Mon Apr 12 04:10:02 GMT 2004
>> Closed-Date:
>> Last-Modified:
>> Originator: Craig J Copi
>> Release: OpenBSD 3.4-stable (GENERIC) #13: Tue Mar 9 14:12:13
>> EST 2004
>> Organization:
> net
>> Environment:
>
> System : OpenBSD 3.4
> Architecture: OpenBSD.i386
> Machine : i386
>> Description:
> Generic kernel with patches through patch 13 from CVS stable branch.
> Kernel panic ended in debugger. Disk could not be synced. This
> has happened 2 or 3 times now since January (after upgrade to
> 3.4). There are two drives in the machine (from dmegs)
> wd0 at pciide0 channel 0 drive 0: <WDC WD307AA-00BAA0>
> wd0: 16-sector PIO, LBA, 29333MB, 16383 cyl, 16 head, 63 sec, 60074784
> sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
> wd1 at pciide0 channel 1 drive 0: <WDC WD800JB-00CRA1>
> wd1: 16-sector PIO, LBA, 76319MB, 16383 cyl, 16 head, 63 sec,
> 156301488 sectors
> wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4
> During boot the following messages appear:
> /bsd: wd1a: aborted command, interface CRC error reading fsbn 176 of
> 176-287 (wd1 bn 239; cn 0 tn 3 sn 50), retrying
> /bsd: wd1: transfer error, downgrading to Ultra-DMA mode 3
> /bsd: wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 3
> /bsd: wd1a: aborted command, interface CRC error reading fsbn 176 of
> 176-287 (wd1 bn 239; cn 0 tn 3 sn 50), retrying
> /bsd: wd1: soft error (corrected)
> This time it happened when nothing unusual was going on. One
> other time when I think a similar error occured (no debugging
> info obtained) an rsync was in process to wd1.
>
> TRACE FROM DDB (copied by hand):
> uvm_fault(0xd0546a80, 0xdadb3000, 0, 1) -> e
> kernal: page fault trap, code=0
> Stopped at bufq_default_add+0x14: movb 0x112(%eax),%dl
> bufq_default_add(d08ee8bc,d397fa6c,d08efc00,0,d397fa6c,0,4,d0400a98,530
> 5,2000,dad72db4, ...) at bufq_default_add+0x14
> wdstrategy(d397fa6c,297,40,d08d3dc0,0) at wdstrategy+0xf2
> spec_strategy(dad72dfc,10,10,40,dad65500) at spec_strategy+0x40
> spec_vnoperate(dad72dfc,0,3,0,0) at spec_vnoperate+0x1b
> VOP_STRATEGY(d397fa6c,0,c338cfe8,3d7c1) at VOP_STRATEGY+0x2b
> bwrite(d397fa6c,dad896c4,1,d01e9487,dad72e6c) at bwrite+0xda
> vop_generic_bwrite(...) at ..+0x14
> spec_vnoperate(...) at ..+0x1b
> VOP_BWRITE(..) at ..+0x2b
> bawrite(..) at ..+0x1a
> ffs_fsync(...) at ..+0x15b
> VOP_FSYNC(...) at ..0x3b
> sched_sync(...) at ..+0xac
> start_update(dad65500) at start_update+0x14
> Bad frame pointer: 0xd0670e88
>
> PS FROM DDB:
> copied by hand so most things left off. There were "normal" processes
> running, httpd, cyrus imapd, postfix, named. There is also an nfs
> mounted directory using automount. Nothing special was happening with
> the nfs mounted directory.
> 6 0 0 0 3 0x100204 aiodoned aiodoned
> * 5 0 0 0 2 0x100204 update
> 4 0 0 0 3 0x100204 cleaner cleaner
> 3 0 0 0 3 0x100204 reaper reaper
> 2 0 0 0 3 0x100204 pgdaemon pgdaemon
> 1 0 1 0 3 0x4080 wait init
> 0 -1 0 0 3 0x80204 scheduler swapper
>
> SHOW REGISTERS FROM DDB:
> es 0x10
> ds 0x10
> edi 0xd397fa6c end+0x337075c
> esi 0xd08ee800 end+0x2df4f0
> ebp 0xdad72d54 end+0xa763a44
> ebx 0xd397fa6c end+0x337075c
> edx 0x280
> ecx 0xd08ee8bc end+0x2df5ac
> eax 0xdadb3164 end+0xa7a3e54
> eip 0xd01c2904 bufq_default_add+0x14
> cs 0x8
> eflags 0x10282
> esp 0xdad72d3c end+0xa763a2c
> ss 0xdad72d3c end+0xa760d00
> bufq_default_add+0x14: movb 0x112(%eax),%dl
>
> BOOT DUMP ATTEMPT IN DDB:
> syncing disks... uvm_fault(0xd0546a80, 0dadb3000, 0, 1) -> e
> kernel: page fault trap, code=0
> Faulted in DDB; continuing...
>
> FULL DMESG:
> OpenBSD 3.4-stable (GENERIC) #13: Tue Mar 9 14:12:13 EST 2004
> root_(_at_)_styx:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: AMD Athlon Model 2 ("AuthenticAMD" 686-class) 649 MHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,
> FXSR
> real mem = 133738496 (130604K)
> avail mem = 118059008 (115292K)
> using 1658 buffers containing 6791168 bytes (6632K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(00) BIOS, date 06/28/00, BIOS32 rev. 0
> @ 0xfdae0
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> pcibios0 at bios0: rev. 2.1 @ 0xf0000/0x10000
> pcibios0: PCI IRQ Routing Table rev. 1.0 @ 0xf8220/144 (7 entries)
> pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C586 PCI-ISA"
> rev 0x00)
> pcibios0: PCI bus #1 is the last bus
> bios0: ROM list: 0xc0000/0x8000
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "AMD 751 System Controller" rev 0x25
> ppb0 at pci0 dev 1 function 0 "AMD 751 PCI-PCI" rev 0x01
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 5 function 0 "Matrox MGA Millennium II 2164WA-B
> AGP" rev 0x00
> wsdisplay0 at vga1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> pcib0 at pci0 dev 7 function 0 "VIA VT82C686 PCI-ISA" rev 0x1b
> pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06:
> ATA66, channel 0 configured to compatibility, channel 1 configured to
> compatibility
> wd0 at pciide0 channel 0 drive 0: <WDC WD307AA-00BAA0>
> wd0: 16-sector PIO, LBA, 29333MB, 16383 cyl, 16 head, 63 sec,
> 60074784 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
> wd1 at pciide0 channel 1 drive 0: <WDC WD800JB-00CRA1>
> wd1: 16-sector PIO, LBA, 76319MB, 16383 cyl, 16 head, 63 sec,
> 156301488 sectors
> wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4
> uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x0e: irq 10
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x20:
> disabled
> rl0 at pci0 dev 9 function 0 "Realtek 8139" rev 0x10: irq 11
> address 00:50:ba:8f:2c:05
> rlphy0 at rl0 phy 0: RTL internal phy
> isa0 at pcib0
> 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>
> sysbeep0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> npx0 at isa0 port 0xf0/16: using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> biomask c440 netmask cc40 ttymask ccc2
> pctr: user-level cycle counter enabled
> mtrr: Pentium Pro MTRR support
> dkcsum: wd0 matched BIOS disk 80
> dkcsum: wd1 matched BIOS disk 81
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
> WARNING: / was not properly unmounted
> wd1a: aborted command, interface CRC error reading fsbn 176 of
> 176-287 (wd1 bn
> 239; cn 0 tn 3 sn 50), retrying
> wd1: transfer error, downgrading to Ultra-DMA mode 3
> wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 3
> wd1a: aborted command, interface CRC error reading fsbn 176 of
> 176-287 (wd1 bn
> 239; cn 0 tn 3 sn 50), retrying
> wd1: soft error (corrected)
>
>> How-To-Repeat:
> Unknown. The machine had been rebooted a couple of days
> before the latest crash.
>
>> Fix:
> Unknown.
>
>
>> Release-Note:
>> Audit-Trail:
>> Unformatted:
Visit your host, monkey.org