Re: ata + vinum problems
On Mar 15, Mathew Kanner wrote: On Mar 15, Greg Lehey wrote: attention yet, but I do see that your problem relates to soft updates. It's not clear that the soft updates themselves are a cause of the problem, or just a facilitator, but it would be interesting to I did try it couple of days back with and without softupdates. Softupdates only made the problems appear more quickly but I've lost track of all the combinations that's I've tried so I should try one more time without. After some more time spent with the system. It turns out it is softupdates. I can complete the script (which copies /usr/ports to a newfs'ed system) without softupdates but with, it will stall and then crash. An interesting note, with softupdates, during a stall I did a sysctl vfs.hidirtbuffers=500 and it completed, howver, if I do this before running the script, it crashes as well (but doesn't take nearly as long to do so). Included is a traceback of when it crashed witht he hibuffers at 500. --Mat Script started on Thu Mar 23 15:23:03 2000 bash-2.03# gdb -k 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". (kgdb) core[Kexec-file kernel2. kernel2.: No such file or directory. (kgdb) ecxxec-file kernel.2 (kgdb) coresuymbol-file /usr/src/sys/compile/KZAZE/kernel.debug Reading symbols from /usr/src/sys/compile/KAZE/kernel.debug...done. (kgdb) core-file vmcore.2 IdlePTD 4165632 initial pcb at 364ea0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc026745a stack pointer = 0x10:0xc03218e4 frame pointer = 0x10:0xc03218f0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc025e10c stack pointer = 0x10:0xc032171c frame pointer = 0x10:0xc0321720 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault Uptime: 6m53s dumping to dev #ad/0x20001, offset 3047552 dump ata0: resetting devices .. done 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 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
Re: ata + vinum problems
Ok, this is NOT a softupdates *or* a vinum problem. This is a buffer cache problem. The problem is due to the large block size you are using when newfs'ing the filesystem coupled with problems in geteblk() which causes severe buffer cache KVM fragmentation. Softupdates exasperates the geteblk() problem. I thought I had fixed this problem but apparently not. Try applying my buf-cleanup-3.diff patch from: http://www.backplane.com/FreeBSD4/ Then go back to the configuration that was producing the problem before and see if it still occurs. Even with the above patch there is still a significant KVM fragmentation issue with large-block filesystems. You can guarentee 100% success by hacking the BKVASIZE define in sys/sys/param.h (AFTER applying the patch) from 16384 to 32768, but I wouldn't raise it much beyond that. This patch is only a partial fix to the problem. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata + vinum problems
Oh, addendum... I didn't see this email regarding an actual panic. There are two problems here, one of which (the nbufkv lockup) should be solved by my previous email. The second problem is this panic you are reporting, and I have no idea what is causing it so this issue remains open. It could be softupdates, it could be vinum, or it could be the ATA driver. What you need to do to help solve the panic is to gdb a debug version of the kernel image rather then the non debug version so the stack backtrace contains source line numbers and such. -Matt Matthew Dillon [EMAIL PROTECTED] : After some more time spent with the system. It turns out it :is softupdates. I can complete the script (which copies /usr/ports to :a newfs'ed system) without softupdates but with, it will stall and :then crash. An interesting note, with softupdates, during a stall I :did a sysctl vfs.hidirtbuffers=500 and it completed, howver, if I do :this before running the script, it crashes as well (but doesn't take :nearly as long to do so). : Included is a traceback of when it crashed witht he hibuffers :at 500. : : --Mat : :Script started on Thu Mar 23 15:23:03 2000 :bash-2.03# gdb -k :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". :(kgdb) core[Kexec-file kernel2. :kernel2.: No such file or directory. :(kgdb) ecxxec-file kernel.2 :(kgdb) coresuymbol-file /usr/src/sys/compile/KZAZE/kernel.debug :Reading symbols from /usr/src/sys/compile/KAZE/kernel.debug...done. :(kgdb) core-file vmcore.2 :IdlePTD 4165632 :initial pcb at 364ea0 :panicstr: page fault :panic messages: :--- :Fatal trap 12: page fault while in kernel mode :fault virtual address = 0x0 :fault code = supervisor read, page not present :instruction pointer= 0x8:0xc026745a :stack pointer = 0x10:0xc03218e4 :frame pointer = 0x10:0xc03218f0 :code segment = base 0x0, limit 0xf, type 0x1b : = DPL 0, pres 1, def32 1, gran 1 :processor eflags = interrupt enabled, resume, IOPL = 0 :current process= Idle :interrupt mask = bio :trap number= 12 :panic: page fault : :syncing disks... : :Fatal trap 12: page fault while in kernel mode :fault virtual address = 0x30 :fault code = supervisor read, page not present :instruction pointer= 0x8:0xc025e10c :stack pointer = 0x10:0xc032171c :frame pointer = 0x10:0xc0321720 :code segment = base 0x0, limit 0xf, type 0x1b : = DPL 0, pres 1, def32 1, gran 1 :processor eflags = interrupt enabled, resume, IOPL = 0 :current process= Idle :interrupt mask = bio :trap number= 12 :panic: page fault :Uptime: 6m53s : :dumping to dev #ad/0x20001, offset 3047552 :dump ata0: resetting devices .. done :511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 :494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 :477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 :460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 :443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 :426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 :409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 :392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 :375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 :358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 :341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 :324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 :307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 :290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 :273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 :256 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
Re: ata + vinum problems
On Mar 23, Matthew Dillon wrote: Oh, addendum... I didn't see this email regarding an actual panic. There are two problems here, one of which (the nbufkv lockup) should be solved by my previous email. The second problem is this panic you are reporting, and I have no idea what is causing it so this issue remains open. It could be softupdates, it could be vinum, or it could be the ATA driver. What you need to do to help solve the panic is to gdb a debug version of the kernel image rather then the non debug version so the stack backtrace contains source line numbers and such. -Matt Matthew Dillon [EMAIL PROTECTED] Included is a better backtrace. This does not include the patch that you suggested, I will do that tommorow. Thanks, --Mat Script started on Thu Mar 23 17:07:47 2000 bash-2.03# gdk b -k 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". (kgdb) exec-file v kernel.3 (kgdb) c symbol-file /usr/sr/ c/sys/compile/KAZE/kernel.debug Reading symbols from /usr/src/sys/compile/KAZE/kernel.debug...done. (kgdb) core-file vmcore.3 IdlePTD 4157440 initial pcb at 364ec0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc0175f96 stack pointer = 0x10:0xc0321948 frame pointer = 0x10:0xc0321948 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc025e120 stack pointer = 0x10:0xc0321780 frame pointer = 0x10:0xc0321784 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault Uptime: 5m27s dumping to dev #ad/0x20001, offset 3047552 dump ata0: resetting devices .. done 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 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 boot (howto=260) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:304
Re: ata + vinum problems
On Wednesday, 15 March 2000 at 16:29:03 -0500, Mathew Kanner wrote: On Mar 15, Mathew Kanner wrote: On Mar 15, Soren Schmidt wrote: Btw are you running the latest 4.0 or -current code ? there was a time when we had problems with the HPT and Promise controllers ? The kernel in question was cvsup'ed right at the change. I'm going to try 4.0 today. Replying to myself. By now this is probably the wrong list. I'm not sure what to do anymore. I've tried to set the bios settings back to what I've had when it worked it it doesn't seem to want to go. I've set the drives for ata/66 and ata/33. I've moved IRQ's around and even tried forcing them. Here are sets of dmesg and backtraces. This also happens with a kernel and modules compiled on sunday. The part that really bothers me is that I have a nearly identical machine, except for an extra drive in it that originally had the same problems but when I disabled the extra periphs, the problem went away. I'm a bit behind in my mail, and I don't have time to give this proper attention yet, but I do see that your problem relates to soft updates. It's not clear that the soft updates themselves are a cause of the problem, or just a facilitator, but it would be interesting to see what happens if you turn them off. Note also that there are some bogons in your config, to judge by the vinum startup messages. I'll analyse this in a day or two when I (hopefully) have more time. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata + vinum problems
On Mar 15, Soren Schmidt wrote: It seems Mathew Kanner wrote: disks on Promise controllers. I believe that the problems lies with multiple cards on the same interupt but what do I know -- execpt that the problem goes away when I disable most devices in the BIOS. The motherboard is a abit BE6-II, I've enabled most BIOS periphs such as serial ports, printer ports, usb, vga ints but not APM. Hmm, I've seen references on the net to the BE6 having trouble with ATA PCI controllers in one of the slots if the internal controller is enabled, I dont know which slot that is unfortunately, so moving things around is my best guess. I did get hit by that, in this case it's the 5th pci slot. When there a controller in there, the system just locks completly. Btw are you running the latest 4.0 or -current code ? there was a time when we had problems with the HPT and Promise controllers ? The kernel in question was cvsup'ed right at the change. I'm going to try 4.0 today. --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata + vinum problems
It seems Mathew Kanner wrote: Hi All, I wanted to document my difficuties with Vinum and multiple disks on Promise controllers. I believe that the problems lies with multiple cards on the same interupt but what do I know -- execpt that the problem goes away when I disable most devices in the BIOS. The motherboard is a abit BE6-II, I've enabled most BIOS periphs such as serial ports, printer ports, usb, vga ints but not APM. Hmm, I've seen references on the net to the BE6 having trouble with ATA PCI controllers in one of the slots if the internal controller is enabled, I dont know which slot that is unfortunately, so moving things around is my best guess. Btw are you running the latest 4.0 or -current code ? there was a time when we had problems with the HPT and Promise controllers ? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata + vinum problems
On Mar 15, Mathew Kanner wrote: On Mar 15, Soren Schmidt wrote: Btw are you running the latest 4.0 or -current code ? there was a time when we had problems with the HPT and Promise controllers ? The kernel in question was cvsup'ed right at the change. I'm going to try 4.0 today. Replying to myself. By now this is probably the wrong list. I'm not sure what to do anymore. I've tried to set the bios settings back to what I've had when it worked it it doesn't seem to want to go. I've set the drives for ata/66 and ata/33. I've moved IRQ's around and even tried forcing them. Here are sets of dmesg and backtraces. This also happens with a kernel and modules compiled on sunday. The part that really bothers me is that I have a nearly identical machine, except for an extra drive in it that originally had the same problems but when I disabled the extra periphs, the problem went away. Any suggestions? --Mat Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #5: Tue Mar 14 22:07:49 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/KAZE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (551.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,XMM real memory = 536870912 (524288K bytes) avail memory = 516157440 (504060K bytes) Preloaded elf kernel "kernel" at 0xc03e3000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: Matrox MGA G400 AGP graphics accelerator at 0.0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller at 7.2 chip1: Intel 82371AB Power management controller port 0x5000-0x500f at device 7.3 on pci0 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xa400-0xa47f mem 0xe606-0xe606007f irq 7 at device 11.0 on pci0 xl0: Ethernet address: 00:50:da:d6:6a:d0 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: supplying EUI64: 00:50:da:ff:fe:d6:6a:d0 atapci1: Promise ATA66 controller port 0xb800-0xb83f,0xb400-0xb403,0xb000-0xb007,0xac00-0xac03,0xa800-0xa807 mem 0xe600-0xe601 irq 5 at device 13.0 on pci0 ata2: at 0xa800 on atapci1 ata3: at 0xb000 on atapci1 atapci2: Promise ATA66 controller port 0xcc00-0xcc3f,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc07 mem 0xe604-0xe605 irq 10 at device 15.0 on pci0 ata4: at 0xbc00 on atapci2 ata5: at 0xc400 on atapci2 atapci3: Promise ATA66 controller port 0xe000-0xe03f,0xdc00-0xdc03,0xd800-0xd807,0xd400-0xd403,0xd000-0xd007 mem 0xe602-0xe603 irq 11 at device 17.0 on pci0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: parallel port not found. ad0: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata0-master using UDMA33 ad4: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata2-master using UDMA66 ad6: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata3-master using UDMA66 ad8: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata4-master using UDMA66 ad10: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata5-master using UDMA66 acd0: CD-RW MATSHITA CD-RW CW-7585 at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted vinum: loaded vinum: reading configuration from /dev/ad6s1e vinum: updating configuration from /dev/ad8s1e vinum: updating configuration from /dev/ad10s1e vinum: updating configuration from /dev/ad4s1e xl0: starting DAD for fe80:0001::0250:daff:fed6:6ad0 xl0: DAD complete for fe80:0001::0250:daff:fed6:6ad0 - no duplicates found --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:304 #1 0xc017f12c in poweroff_wait (junk=0xc03167af, howto=0) at ../../kern/kern_shutdown.c:554 #2 0xc02ba019 in trap_fatal (frame=0xc031fe64, eva=48) at
Re: ata + vinum problems
On Mar 15, Greg Lehey wrote: Replying to myself. By now this is probably the wrong list. I'm not sure what to do anymore. I've tried to set the bios settings back to what I've had when it worked it it doesn't seem to want to go. I've set the drives for ata/66 and ata/33. I've moved IRQ's around and even tried forcing them. Here are sets of dmesg and backtraces. This also happens with a kernel and modules compiled on sunday. The part that really bothers me is that I have a nearly identical machine, except for an extra drive in it that originally had the same problems but when I disabled the extra periphs, the problem went away. I'm a bit behind in my mail, and I don't have time to give this proper attention yet, but I do see that your problem relates to soft updates. It's not clear that the soft updates themselves are a cause of the problem, or just a facilitator, but it would be interesting to see what happens if you turn them off. Note also that there are some bogons in your config, to judge by the vinum startup messages. I'll analyse this in a day or two when I (hopefully) have more time. The bogons me were messing me around with Vinum before I figured out that the crash had messed up one of the disklabels. This occurs occasionally after a crash. I did try it couple of days back with and without softupdates. Softupdates only made the problems appear more quickly but I've lost track of all the combinations that's I've tried so I should try one more time without. Thanks, --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ata + vinum problems
Hi All,
I wanted to document my difficuties with Vinum and multiple
disks on Promise controllers. I believe that the problems lies with
multiple cards on the same interupt but what do I know -- execpt that
the problem goes away when I disable most devices in the BIOS.
The motherboard is a abit BE6-II, I've enabled most BIOS
periphs such as serial ports, printer ports, usb, vga ints but not APM.
I've included the script that causes the crash, a back-trace
and dmesg output right before the crash and the kernel config. The
raid devices where made via the vinum simplified commands (which are
*very nice*).
It should be noted that I had to control the 'tar' part of the
script because it was stuck in a "nbufkv" and disk activity ceases.
The crash happened upto 10 seconds after I get a shell prompt back.
The "nbufkv" was the sure sign that something had gone wrong in my
previous 'uncontrolled' tests.
--Mat
#!/bin/sh -x
BLOCK_SIZE=`expr 32 \* 1024`
FRAG_SIZE=`expr 8 \* 1024`
ISIZE=`expr 6 \* ${FRAG_SIZE}`
#CYL=635
CYL=200
FAKE=""
DEV="/dev/vinum/raid5"
MOUNT="/mnt1"
newfs ${FAKE} -v -b ${BLOCK_SIZE} -f ${FRAG_SIZE} -i ${ISIZE} -c ${CYL} ${DEV}
tunefs -n enable ${DEV}
mount ${DEV} ${MOUNT}
tar cf - -C /usr/ ports | tar xf - -C ${MOUNT}
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #4: Mon Mar 13 17:54:22 GMT 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/KAZE
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon (551.25-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x673 Stepping = 3
Features=0x387f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,XMM
real memory = 536870912 (524288K bytes)
avail memory = 516128768 (504032K bytes)
Preloaded elf kernel "kernel" at 0xc03e9000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: Matrox MGA G400 AGP graphics accelerator at 0.0 irq 10
isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: Intel 82371AB/EB (PIIX4) USB controller at 7.2 irq 9
chip1: Intel 82371AB Power management controller port 0x5000-0x500f at device 7.3 on
pci0
xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x9400-0x947f mem 0xe706-0xe706007f
irq 9 at device 11.0 on pci0
xl0: Ethernet address: 00:50:da:d6:6a:d0
miibus0: MII bus on xl0
xlphy0: 3Com internal media interface on miibus0
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: supplying EUI64: 00:50:da:ff:fe:d6:6a:d0
atapci1: Promise ATA66 controller port
0xa800-0xa83f,0xa400-0xa403,0xa000-0xa007,0x9c00-0x9c03,0x9800-0x9807 mem
0xe704-0xe705 irq 11 at device 13.0 on pci0
ata2: at 0x9800 on atapci1
ata3: at 0xa000 on atapci1
atapci2: Promise ATA66 controller port
0xbc00-0xbc3f,0xb800-0xb803,0xb400-0xb407,0xb000-0xb003,0xac00-0xac07 mem
0xe702-0xe703 irq 5 at device 15.0 on pci0
ata4: at 0xac00 on atapci2
ata5: at 0xb400 on atapci2
atapci3: Promise ATA66 controller port
0xd000-0xd03f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 mem
0xe700-0xe701 irq 10 at device 17.0 on pci0
atapci4: HighPoint HPT366 ATA66 controller port
0xdc00-0xdcff,0xd800-0xd803,0xd400-0xd407 irq 11 at device 19.0 on pci0
atapci5: HighPoint HPT366 ATA66 controller port
0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007 irq 11 at device 19.1 on pci0
fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5" drive on fdc0 drive 0
atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: cannot reserve I/O port range
ad0: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata0-master using UDMA33
ad4: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata2-master using UDMA66
ad6: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata3-master using UDMA66
ad8: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata4-master using UDMA66
ad10: 26063MB FUJITSU MPE3273AT [52953/16/63] at ata5-master using UDMA66
acd0: CD-RW MATSHITA CD-RW CW-7585 at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a
