Bug 16890

Summary: Fatal trap 12: page fault while in kernel mode (panic: sbdrop)
Product: Base System Reporter: lew <lew>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.3-STABLE   
Hardware: Any   
OS: Any   

Description lew 2000-02-21 21:10:01 UTC 
Fatal trap 12: page fault while in kernel mode
fault virtual address: 0x5e455b3a
fault code: supervisor read, page not present
instruction pointer: 0x8:0x5e455b3a
stack pointer: 0x10: 0xd2d94f60
frame pointer: 0x10: 0xd2d94f78
code segment: base rx0, limit 0xfffff, type 0x1b
              DPL 0, pres 1, def32 1, gran 1
processor eflags: interrupt enabled, resume, IOPL=0
current process: 4452 (diablo)
interrupt mask: net
trap number: 12
panic: page fault
syncing disks... 213 212 151 77 65 65 65 65 65 (repeat 16 times)
giving up

---- also, another crash ----
panic: sbdrop
syncing disks... panic: sbdrop

Fatal trap 12: page fault while in kernel mode
fault virtual address: 0x3d385145
fault code: supervisor read, page not present
instruction pointer: 0x8:0x3d385145
stack pointer: 0x10: 0xc024cb80
frame pointer: 0x10: 0xc024cb98
code segment: base rx0, limit 0xfffff, type 0x1b
              DPL 0, pres 1, def32 1, gran 1
processor eflags: interrupt enabled, resume, IOPL=0
current process: Idle
interrupt mask: net
trap number: 12
panic: page fault

--- special victim's note ---
Spoke with Chris of cdrom.com, and learned about the "triple curse"
involving our Intel chipset, the built-in DE0 and NCR controller.
We've eliminated the DE0, and installed a TX0.  Problem persists.

--- our configuration ---
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California. All rights reserved.
FreeBSD 3.3-STABLE #10: Wed Dec 22 13:44:53 PST 1999
    lewis@feeder.via.net:/usr/src/sys/compile/DIABLO
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 498752036 Hz
CPU: Pentium III (498.75-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x672  Stepping = 2
  Features=0x387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM
OV,PAT,PSE36,<b18>,MMX,FXSR,<b25>>
real memory  = 536870912 (524288K bytes)
avail memory = 519589888 (507412K bytes)
Preloaded elf kernel "kernel" at 0xc02c1000.
Pentium Pro MTRR support enabled
Probing for devices on PCI bus 0:
chip0: <Intel 82443BX host to PCI bridge (AGP disabled)> rev 0x03 on pci0.0.0
ncr0: <ncr 53c875 fast20 wide scsi> rev 0x37 int a irq 11 on pci0.13.0
ncr1: <ncr 53c875 fast20 wide scsi> rev 0x37 int b irq 10 on pci0.13.1
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x05 int a irq 5 on pci0.15.
0
fxp0: Ethernet address 00:a0:c9:fc:45:7f
xl0: <3Com 3cSOHO100-TX OfficeConnect> rev 0x30 int a irq 7 on pci0.16.0
xl0: Ethernet address: 00:50:da:b4:65:e6
xl0: autoneg complete, link status good (half-duplex, 100Mbps)
chip1: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.18.0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.18.1
chip2: <Intel 82371AB Power management controller> rev 0x02 on pci0.18.3
vga0: <Cirrus Logic model 00bc VGA-compatible display device> rev 0x23 on pci0.2
0.0
Probing for PnP devices:
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 8250
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1 not found at 0x2f8
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa
wdc0: unit 0 (wd0): <WDC WD273BA>, LBA, DMA, 32-bit, multi-block-16
wd0: 26105MB (53464320 sectors), 3328 cyls, 255 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1): <WDC WD273BA>, LBA, DMA, 32-bit, multi-block-16
wd1: 26105MB (53464320 sectors), 3328 cyls, 255 heads, 63 S/T, 512 B/S
wdc1 not found at 0x170
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
ccd0-3: Concatenated disk drivers
Waiting 15 seconds for SCSI devices to settle
changing root device to da0s1a
da0 at ncr0 bus 0 target 0 lun 0
da0: <QUANTUM VIKING II 4.5WLS 4110> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled
da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C)
WARNING: / was not properly dismounted
xl0: selecting MII, 100Mbps, half duplex
xl0: selecting MII, 100Mbps, full duplex
xl0: transmission error: 90
xl0: tx underrun, increasing tx start threshold to 120 bytes

Fix: 

Run FreeBSD 2.2.8-REL, which has been rock-stable
compared to the past year's releases of FreeBSD.
Everyone seems to be aware of this problem, but
nobody seems to be committed to fixing it.  HELP!
How-To-Repeat: Run any version of FreeBSD above 2.2.8, and pound
away at the NIC card while doing heavy I/O.
Comment 1 lew 2000-02-22 20:25:48 UTC 
(old):
    --- special victim's note ---
    Spoke with Chris of cdrom.com, and learned about the "triple curse"
    involving our Intel chipset, the built-in DE0 and NCR controller.
    We've eliminated the DE0, and installed a TX0.  Problem persists.
(Correction):
    I meant to say "FXP0" instead of "DE0".
(Addition):
    Problem persists, even after recompiling the kernel with "fxp0"
    commented out (so the driver is completely removed).  Out of
    desperation, I tried that this morning.  Still crash city, and a lot

    of screwed up disk structures (using soft updates).
Comment 2 iedowse freebsd_committer freebsd_triage 2001-08-12 23:30:35 UTC 
State Changed
From-To: open->feedback


Does this still occur on more recent releases?
Comment 3 iedowse 2001-08-13 01:46:10 UTC 
In message <BHEIICGHBDLPJGKHLJKGAEMKCDAA.lew@persiankitty.com>, Lew Payne write
s:
>A year and a half after reporting the problem, I get a response?
>I'll tell you what -- I'm never going to help, much less give the
>freebsd team the time of day, again.

I'm sorry if you are unhappy with the lack of responses. This
problem sounds like an obscure hardware-specific issue that I don't
think was ever fully tracked down; you didn't get an answer because
nobody knew the answer.

May I take it that I can close this PR?

Ian
Comment 4 Alfred Perlstein freebsd_committer freebsd_triage 2001-08-13 01:46:56 UTC 
State Changed
From-To: feedback->closed

Submitter refuses to assist in solving the problem, which may not 
even exist any longer.