Date: Wed, 24 Jan 2001 06:28:24 -0800 (PST) From: myleal@spliceip.com.br To: freebsd-gnats-submit@FreeBSD.org Subject: kern/24608: FreeBSD 4.2 Panics in Realtek rl driver Message-ID: <200101241428.f0OESO551048@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 24608
>Category: kern
>Synopsis: FreeBSD 4.2 Panics in Realtek rl driver
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jan 24 06:30:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Marcus Yuri Maranhao Leal
>Release: 4.2-RELEASE
>Organization:
Splice IP
>Environment:
FreeBSD pajeus.spliceip.com.br 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Wed Dec 6 12:05:51 BRST 2000 root@piranhas.spliceip.com.br:/usr/src/sys/compile/PIRANHAS i386
>Description:
The machine is configurated as a firewall, with 4 Realtek RealTek 8139 10/100BaseTX network interfaces. The machine panics eventually. The following is the log of kernel debug:
bash-2.04# pwd
/var/crash
bash-2.04# ls -l
total 829274
-rw-r--r-- 1 root wheel 2 Jan 23 09:37 bounds
-rw-r--r-- 1 root wheel 1779263 Jan 23 09:25 kernel.0
-rw-r--r-- 1 root wheel 1779263 Jan 23 09:38 kernel.3
-rw-r--r-- 1 root wheel 5 Nov 20 10:03 minfree
-rw------- 1 root wheel 268423168 Jan 23 09:25 vmcore.0
-rw------- 1 root wheel 174063616 Jan 23 09:29 vmcore.1
-rw------- 1 root wheel 134217728 Jan 23 09:33 vmcore.2
-rw------- 1 root wheel 268423168 Jan 23 09:38 vmcore.3
bash-2.04# gdb -k kernel.0 vmcore.0
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
IdlePTD 3031040
initial pcb at 263c80
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xa4c07000
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01a8968
stack pointer = 0x10:0xc0242368
frame pointer = 0x10:0xc0242374
code segment = base 0x0, 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 tty
trap number = 12
panic: page fault
syncing disks... 5
done
Uptime: 10d21h4m25s
dumping to dev #ad/0x20001, offset 533096
dump ata0: resetting devices .. done
255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
---
#0 0xc013cef6 in dumpsys ()
(kgdb) where
#0 0xc013cef6 in dumpsys ()
#1 0xc013cd17 in boot ()
#2 0xc013d094 in poweroff_wait ()
#3 0xc0203561 in trap_fatal ()
#4 0xc0203239 in trap_pfault ()
#5 0xc0202e1f in trap ()
#6 0xc01a8968 in rl_encap ()
#7 0xc01a8b37 in rl_start ()
#8 0xc017655c in ether_output_frame ()
#9 0xc01764ca in ether_output ()
#10 0xc0190b5f in ip_output ()
#11 0xc018fd99 in ip_forward ()
#12 0xc018ee16 in ip_input ()
#13 0xc018f183 in ipintr ()
------------
The other core (vmcore.3) has the same trace, so, I think that the problem is in RealTek rl driver. We have another FreeBSD 4.2 Firewall, with 4 NICs, with the same configuration (except the NICs, they are 3COM 10/100 FastEtherlink XL), that does not panics.
The realtek NIC are:
bash-2.04$ dmesg | grep -i realtek
rl0: <RealTek 8139 10/100BaseTX> port 0xa400-0xa4ff mem 0xdb800000-0xdb8000ff irq 11 at device 9.0 on pci0
rlphy0: <RealTek internal media interface> on miibus0
rl1: <RealTek 8139 10/100BaseTX> port 0xa000-0xa0ff mem 0xdb000000-0xdb0000ff irq 9 at device 10.0 on pci0
rlphy1: <RealTek internal media interface> on miibus1
rl2: <RealTek 8139 10/100BaseTX> port 0x9800-0x98ff mem 0xda800000-0xda8000ff irq 5 at device 11.0 on pci0
rlphy2: <RealTek internal media interface> on miibus2
rl3: <RealTek 8139 10/100BaseTX> port 0x9400-0x94ff mem 0xda000000-0xda0000ff irq 11 at device 12.0 on pci0
rlphy3: <RealTek internal media interface> on miibus3
---------------------------------------------------------
>How-To-Repeat:
Try to install 4 Realtek NICs in FreeBSD 4.2, and let it runs as a firewall.
>Fix:
Does not known. Maybe a rl driver fix?
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101241428.f0OESO551048>