Re: 5.4-p1 crash
Hi Mitch, Saturday, June 18, 2005, 12:23:19 AM, you typed the following: Below are details regarding another crash on a Dell 2600 SMP (HTT and USB disabled). It has been 9 days since the last crash. I didn't have the serial console in place for this last crash, but it is now. Text includes: 1. backtrace 2. dmesg 3. kernel conf Since Dell diagnostics and Memtest check out fine, I'm kind of between a rock and a hard place here. I have a similar 2600 running 4.9 that is working great. I'd welcome any advice. I think I'm experiencing this as well on my Dell gx280, however I don't have any backtrace. my dmesg: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-DanGerSEC #2: Fri May 27 23:16:31 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/daemon Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 1071144960 (1021 MB) avail memory = 1042702336 (994 MB) MPTable: DELL Opti GX280 ioapic0: Changing APIC ID to 8 ioapic0: Assuming intbase of 0 ioapic0 Version 2.0 irqs 0-23 on motherboard npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib0: unable to route slot 1 INTA pcib0: unable to route slot 2 INTA pcib0: unable to route slot 28 INTA pcib0: unable to route slot 28 INTB pcib1: MPTable PCI-PCI bridge irq 11 at device 1.0 on pci0 pci1: PCI bus on pcib1 pci0: display, VGA at device 2.0 (no driver attached) pci0: display at device 2.1 (no driver attached) pcib2: MPTable PCI-PCI bridge irq 11 at device 28.0 on pci0 pci2: PCI bus on pcib2 bge0: Broadcom BCM5751 Gigabit Ethernet, ASIC rev. 0x4001 mem 0xdfcf-0xdfcf irq 16 at device 0.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5750 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:11:43:b9:b2:ef pcib3: MPTable PCI-PCI bridge irq 10 at device 28.1 on pci0 pci3: PCI bus on pcib3 uhci0: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-A port 0xff80-0xff9f irq 21 at device 29.0 on pci0 usb0: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-B port 0xff60-0xff7f irq 22 at device 29.1 on pci0 usb1: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-C port 0xff40-0xff5f irq 18 at device 29.2 on pci0 usb2: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-D port 0xff20-0xff3f irq 23 at device 29.3 on pci0 usb3: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 29.7 (no driver attached) pcib4: MPTable PCI-PCI bridge at device 30.0 on pci0 pci4: PCI bus on pcib4 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xdc80-0xdcff mem 0xdf9fff80-0xdf9f irq 16 at device 0.0 on pci4 miibus1: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:14:be:1d isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH6 UDMA100 controller port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 16 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: Intel ICH6 SATA150 controller port 0xfea0-0xfeaf,0xfe30-0xfe33,0xfe20-0xfe27,0xfe10-0xfe13,0xfe00-0xfe07 irq 20 at device 31.2 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pci0: serial bus, SMBus at device 31.3 (no driver attached) orm0: ISA Option ROMs at iomem 0xcc800-0xc,0xcb000-0xcc7ff,0xca800-0xcafff,0xc-0xca7ff on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1:
Re: What is considered the best supported RAID controller for 5.x?
Hello! The subject says it all ... I'm looking a new server, and right now have built it around the SRCZCRX PCI-X 128MB, since I've had good luck with the Intel RAID controllers with 4.x, and I *really* like the storcon CLI utility ... but, with the move to 5.x, I'm wondering if there is something else I should be looking at, or is this still a good card to go with? IMHO it's the entire product line of ICP Vortex, now owned by Adaptec. These cards really rock. Battery backed up cache, RAID 1+0, driver maintained my company's engineers, yet in the stock FreeBSD kernel, curses based management utility to repair arrays without reboot, unattended rebuild if you exchange a broken disk with a brand new one, same interface to the host for _all_ products including SATA, ... Just works. Period. We use them for typo3.org, wetteronline.de uses them. I'm in no way affiliated with them, I just like the products. A lot ;-) HTH, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-p1 crash
Kris Kennaway a crit : On Fri, Jun 17, 2005 at 03:23:19PM -0700, Mitch Parks wrote: Below are details regarding another crash on a Dell 2600 SMP (HTT and USB disabled). It has been 9 days since the last crash. I didn't have the serial console in place for this last crash, but it is now. Text includes: 1. backtrace 2. dmesg 3. kernel conf Since Dell diagnostics and Memtest check out fine, I'm kind of between a rock and a hard place here. I have a similar 2600 running 4.9 that is working great. I'd welcome any advice. Unfortunately this is a known bug in FreeBSD; check the archives for more discussion. Doug White tried to look at fixing it before 5.4-RELEASE but I think he gave up. do you know if someone works on it ? I sent two mail in freebsd-stable about it without solution and this bug is really annoying : http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/015952.html and http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/015864.html there is a PR for it : kern/74319 Kris thanks -- Philippe PEGON ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
4.10-STABLE panic, twice
Not sure what triggered it, but it seems file system related. The second
core dump didn't save because I forgot to move the dumpdir to /usr, it
was something to do with ffs also though.
GNU gdb 4.18 (FreeBSD)
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...Deprecated bfd_read
called at
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c
line 2627 in elfstab_build_psymtabs
Deprecated bfd_read called at
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c
line 933 in fill_symbuf
IdlePTD at physical address 0x003ab000
initial pcb at physical address 0x00306580
panicstr: ffs_blkfree: freeing free block
panic messages:
---
panic: ffs_blkfree: freeing free block
syncing disks... 19 ad2: WRITE command timeout tag=0 serv=0 - resetting
ata1: resetting devices .. done
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
giving up on 1 buffers
Uptime: 25d22h35m26s
dumping to dev #ad/0x20001, offset 790656
dump ata0: resetting devices .. done
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 69.82:1045 81.178.74.143:4666 in via fxp1
ad2: WRITE command timeout tag=0 serv=0 - resetting
ata1: resetting devices .. done
---
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
487 if (dumping++) {
(kgdb) bt
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
#1 0xc015ed08 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316
#2 0xc015f13c in poweroff_wait (junk=0xc02c0620, howto=-1070856704)
at /usr/src/sys/kern/kern_shutdown.c:595
#3 0xc022cf47 in ffs_blkfree (ip=0xc89f1e0c, bno=46208, size=16384)
at /usr/src/sys/ufs/ffs/ffs_alloc.c:1450
#4 0xc023182e in handle_workitem_freeblocks (freeblks=0xc10dce80)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:2146
#5 0xc022fc1b in process_worklist_item (matchmnt=0x0, flags=0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:723
#6 0xc022faaa in softdep_process_worklist (matchmnt=0x0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:622
#7 0xc018e563 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1198
(kgdb)
FreeBSD bone.bone.servebeer.com 4.10-STABLE FreeBSD 4.10-STABLE #0: Mon
Oct 25 04:30:06 BST 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/BONE i386
This one happened while I was asleep. It failed to fsck ad2 afterwards,
so it was sat in single user mode. The second panic ALSO failed to fsck
ad2 and sat in single user mode until I ran it manually. ad2 is actually
a laptop drive. Perhaps this is a sign the disk is on it's way out? If
that was the case I thought it would have just gone to click of death
mode and the system would have locked up?
Any help much appreciated. I am currently trying to update to the latest
STABLE. In fact, the second panic happened during the first attempt at a
make buildworld... this time around it's still running though.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD MySQL still WAY slower than Linux
I've posted a longer reply, with a trimmed cc list on the -performance mailing list if anyone is still interested and I'll leave it off -stable as it's probably become somewhat off topic now. Sadly, I don't think simply having an async FS is going to solve our problem though. :( Ta, Steve Roome For refernce: On Fri, Jun 17, 2005 at 09:28:54AM -0400, David Sze wrote: At 05:15 PM 16/06/2005 +0100, Steve Roome wrote this to All: It turns out that the problem was the same thing everyone usually points the finger at, but no one actually mentioned this time: Linux mounts its partitions async by default. I don't have the exact numbers in front of me right now, but these were the ballpark figures (I'm not going to separate out results for all of the different threading libraries for FreeBSD because the deltas weren't huge): ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD MySQL still WAY slower than Linux
On Friday 17 June 2005 23:47, Javier Henderson wrote: Wilko Bulte wrote: On Fri, Jun 17, 2005 at 02:26:48PM -0700, Javier Henderson wrote.. Wilko Bulte wrote: On Fri, Jun 17, 2005 at 11:12:06PM +0200, Matthias Buelow wrote.. Wilko Bulte [EMAIL PROTECTED] writes: If you give me $5 per Unix system found there I can retire here and now. For financial transaction processing, and the customer's accounts? Yes. Go and visit the London City and check their computer rooms. You will be surprised about the number of UNIX boxes. You don't think IBM, HP, Sun etc sell their UNIX machines just to ISPs or..? But are those Unix servers actually processing bank transactions and holding customer accounts? Why not? As an aside: what do you think telecom operators run their main billing systems on? UNIX... I'm sure some do. Others run theirs on VMS. Any idea what downtime costs per hour on those systems? A lot. So how is this relevant for freebsd-stable@ ? ... Thanks! -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpRDPXg1ZiQO.pgp Description: PGP signature
Routes not deleted after link down
Hi, i discovered that routes are not deleted from routing table after link on interface goes down. For example: netstat -rnf inet | grep bge0 default10.1.14.1 UGS 0 135968 bge0 10.1/17link#1 UC 00 bge0 route -n monitor got message of size 96 on Sat Jun 18 15:10:38 2005 RTM_IFINFO: iface status change: len 96, if# 1, link: down, +flags:UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST netstat -rnf inet | grep bge0 default10.1.14.1 UGS 0 136011 bge0 10.1/17link#1 UC 00 bge0 Should't all routes via bge0 be deleted after link on bge0 goes down? thanks michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount floppy - Input/output error
On Fri, Jun 17, 2005 at 04:34:38PM +0400, wrote: Hi! Such problem! # uname -rs FreeBSD 5.4-RELEASE-p1 # mount -t msdosfs /dev/fd0 /mnt/flp msdosfs: /dev/fd0: Input/output error # fdformat -f 1440 /dev/fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing fdformat: ioctl(FD_FORM): Input/output error # fdcontrol -v /dev/fd0 /dev/fd0: 1.44M drive (3.5 high-density) #cat /etc/fstab |grep fd /dev/fd0/mnt/flpmsdos rw,noauto 0 0 # ls /dev |grep fd fd fd0 # cat /var/run/dmesg.boot |grep fd fdc0: floppy drive controller (FDE) port 0x3f7,0x3f0-0x3f5 irq 6 on acpi0 fdc0: cannot reserve DMA request line fd0: 1440-KB 3.5 drive on fdc0 drive 0 Help to solve a problem! thanks I have nearly the same problem. In my case it could be resolved by using non-ACPI kernel. -ip -- Never test for an error condition you don't know how to handle. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Routes not deleted after link down
Michal Vanco wrote: i discovered that routes are not deleted from routing table after link on interface goes down. For example: [ ... ] Should't all routes via bge0 be deleted after link on bge0 goes down? Maybe. If the system was not going to be reconnected to that network anytime soon, it would be a good idea. On the other hand, if the link down was due to a transient failure of a wireless connection, which will be back up in a second or two, it's much better not to drop the route and kill any open connections. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-p1 crash
On Fri, Jun 17, 2005 at 07:53:52PM -0400, Kris Kennaway wrote: On Fri, Jun 17, 2005 at 03:23:19PM -0700, Mitch Parks wrote: Below are details regarding another crash on a Dell 2600 SMP (HTT and USB disabled). It has been 9 days since the last crash. I didn't have the serial console in place for this last crash, but it is now. Text includes: 1. backtrace 2. dmesg 3. kernel conf Since Dell diagnostics and Memtest check out fine, I'm kind of between a rock and a hard place here. I have a similar 2600 running 4.9 that is working great. I'd welcome any advice. Unfortunately this is a known bug in FreeBSD; check the archives for more discussion. Doug White tried to look at fixing it before 5.4-RELEASE but I think he gave up. Just curious... What's the problem? Is there known steps that can trigger it quickly so we can grab the bug? Cheers, -- Xin LI delphij frontfree net http://www.delphij.net/ See complete headers for GPG key and other information. pgpS4QNzJhS3f.pgp Description: PGP signature
Re: 5.4-p1 crash
Xin LI a crit : On Fri, Jun 17, 2005 at 07:53:52PM -0400, Kris Kennaway wrote: On Fri, Jun 17, 2005 at 03:23:19PM -0700, Mitch Parks wrote: Below are details regarding another crash on a Dell 2600 SMP (HTT and USB disabled). It has been 9 days since the last crash. I didn't have the serial console in place for this last crash, but it is now. Text includes: 1. backtrace 2. dmesg 3. kernel conf Since Dell diagnostics and Memtest check out fine, I'm kind of between a rock and a hard place here. I have a similar 2600 running 4.9 that is working great. I'd welcome any advice. Unfortunately this is a known bug in FreeBSD; check the archives for more discussion. Doug White tried to look at fixing it before 5.4-RELEASE but I think he gave up. Just curious... What's the problem? Is there known steps that can trigger it quickly so we can grab the bug? for me, it seems that it is an expect program which connects to a lot of network equipement with spawn ssh ... for retrieving some informations. For the moment, I reduced the frequency and the server crash happens much less often. Cheers, -- Philippe PEGON ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Routes not deleted after link down
On Saturday 18 June 2005 20:48, Chuck Swiger wrote: Michal Vanco wrote: i discovered that routes are not deleted from routing table after link on interface goes down. For example: [ ... ] Should't all routes via bge0 be deleted after link on bge0 goes down? Maybe. If the system was not going to be reconnected to that network anytime soon, it would be a good idea. On the other hand, if the link down was due to a transient failure of a wireless connection, which will be back up in a second or two, it's much better not to drop the route and kill any open connections. hmm ... this approach is may be appropriate for deskop instalation. what about internet router? shouldn't fast convergence be better in this case? imagine two links connected to the same router with different metrics. if first of them goes down, the second never gets used in this case. michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Routes not deleted after link down
El Domingo, 19 de Junio de 2005 00:04, Michal Vanco escribi: On Saturday 18 June 2005 20:48, Chuck Swiger wrote: Michal Vanco wrote: i discovered that routes are not deleted from routing table after link on interface goes down. For example: [ ... ] Should't all routes via bge0 be deleted after link on bge0 goes down? Maybe. If the system was not going to be reconnected to that network anytime soon, it would be a good idea. On the other hand, if the link down was due to a transient failure of a wireless connection, which will be back up in a second or two, it's much better not to drop the route and kill any open connections. hmm ... this approach is may be appropriate for deskop instalation. what about internet router? shouldn't fast convergence be better in this case? imagine two links connected to the same router with different metrics. if first of them goes down, the second never gets used in this case. michal First, this is a thread for net, not stable. Second, you may need a route daemon for this. ospf is a well known canditate where convergence in case of lost link is a must. Also, you can monitor link status and do the switch from a daemon. Userland ppp have more or less this. -- josemi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Routes not deleted after link down
Michal Vanco wrote: On Saturday 18 June 2005 20:48, Chuck Swiger wrote: [ ... ] Maybe. If the system was not going to be reconnected to that network anytime soon, it would be a good idea. On the other hand, if the link down was due to a transient failure of a wireless connection, which will be back up in a second or two, it's much better not to drop the route and kill any open connections. hmm ... this approach is may be appropriate for deskop instalation. what about internet router? shouldn't fast convergence be better in this case? imagine two links connected to the same router with different metrics. if first of them goes down, the second never gets used in this case. You're right that a router should notice and quickly respond to an interface going down. Routing software like routed, gated, zebra, CARP, freevrrpd should register to receive interface change notifications and do the appropriate thing. In fact, that's pretty much what those programs actually do, although the details vary. Anyway, if you don't run such programs, FreeBSD generally is using static routes or a simple dynamic default route discovered via DHCP. The network stack has timeouts in place to close down open TCP connections and the like if no traffic can be sent for a long time. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Can't mount partitions with soft-updates enabled with async option
I am not sure if I do something wrong here or it is suppose to work that way but the async option doesn't seem to work for partitions that have soft-updates turned on. Can someone please clarify the difference and if the speed difference (if any) is significant when using the async option instead of the soft-updates for cases such as the /usr/obj or as a squid data storage? Is async preferred over soft-updates when data loss is not a big issue? Please CC Thank you, Lefteris Tsintjelis ASDA ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-p1 crash
On Sun, 19 Jun 2005, Xin LI wrote: On Fri, Jun 17, 2005 at 07:53:52PM -0400, Kris Kennaway wrote: On Fri, Jun 17, 2005 at 03:23:19PM -0700, Mitch Parks wrote: Below are details regarding another crash on a Dell 2600 SMP (HTT and USB disabled). It has been 9 days since the last crash. I didn't have the serial console in place for this last crash, but it is now. [snip] Since Dell diagnostics and Memtest check out fine, I'm kind of between a rock and a hard place here. I have a similar 2600 running 4.9 that is working great. I'd welcome any advice. Unfortunately this is a known bug in FreeBSD; check the archives for more discussion. Doug White tried to look at fixing it before 5.4-RELEASE but I think he gave up. Just curious... What's the problem? Is there known steps that can trigger it quickly so we can grab the bug? For my occurrence, I haven't found a predictable way to make it crash. Though I haven't *tried* to trigger it. Crashes have been at seemingly random times with no particular correlational activities that have been detected. If there are particular benchmark, performance or other tools I could use to try and trigger it, let me know if that will help. Mitch Parks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA_DMA errors
I am having ATA_DMA errors on 5.4R and 5 STABLE up to June 16 (haven't done a cvsup again). It doesn't happen on 5.3R or lower. The exact error message is below: It happens within a few hours of use. The laptop will then reboot, and fsck must be ran. After fsck the timeouts happen within a few seconds of booting. Is this a known issue? ERROR MSG --- ad0: timeout - READ_DMA retrying (2 retries left) LBA=24531835 ad0: warning - removed from configuration ata0-master: failure - READ_DMA timed out --- The laptop is a SONY VAIO PCG-Z1WA dmesg info ad0: 57231MB TOSHIBA MK6021GAS/GA024A [116280/16/63] at ata0-master UDMA100 fdisk info # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=116280 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=116280 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 117210177 (57231 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't mount partitions with soft-updates enabled with async option
Lefteris Tsintjelis [EMAIL PROTECTED] writes: I am not sure if I do something wrong here or it is suppose to work that way but the async option doesn't seem to work for partitions that have soft-updates turned on. Can someone please clarify the difference and if the speed difference (if any) is significant when using the async option instead of the soft-updates for cases such as the /usr/obj or as a squid data storage? Is async preferred over soft-updates when data loss is not a big issue? With softupdates, everything is asynchronous so the option doesn't make sense. For improving squid filesystem performance, have you mounted the partition with noatime? That might make some difference. mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-p1 crash
Xin LI a crit :
On Fri, Jun 17, 2005 at 07:53:52PM -0400, Kris Kennaway wrote:
On Fri, Jun 17, 2005 at 03:23:19PM -0700, Mitch Parks wrote:
Below are details regarding another crash on a Dell 2600 SMP (HTT and USB
disabled). It has been 9 days since the last crash. I didn't have the
serial console in place for this last crash, but it is now.
Text includes:
1. backtrace
2. dmesg
3. kernel conf
Since Dell diagnostics and Memtest check out fine, I'm kind of between a
rock and a hard place here. I have a similar 2600 running 4.9 that is
working great. I'd welcome any advice.
Unfortunately this is a known bug in FreeBSD; check the archives for
more discussion. Doug White tried to look at fixing it before
5.4-RELEASE but I think he gave up.
Just curious...
What's the problem? Is there known steps that can trigger it quickly so
we can grab the bug?
I just tested in one FreeBSD-5.4-p1 box (HP DL360 with two CPU) and it seems this simple expect
program which runs six times simultaneously crashs the box after approximately 2 hours :
#! /usr/local/bin/expect
set timeout 60
set host [lindex $argv 0]
set pass PASSWORD
spawn ssh [EMAIL PROTECTED]
expect {
continue*(yes/no) { send yes\r ; exp_continue }
assword: { send $pass\r }
}
expect *# {
send ls\r
}
expect *# {
send exit\r
}
puts Done.
Cheers,
if that can help
--
Philippe PEGON
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
re0 no carrier problem - Patches found in archives didn't work.
Hello. I am running a recent FreeBSD STABLE i386 [lack of nvidia-amd64 :( ] on
amd64 Acer Aspire 1525 machine. I have a RealTek 8169SB Single-chip Gigabit
Ethernet on rgephy RTL8169S/8110S media interface.
The card is properly detected by the pci/re driver and shows up in ifconfig,
but I'm expereiencing unpredictible problems with setting up link: Sometimes
re0 reports it status ''no carrier'', even when everything was working fine a
boot before.
A common scenario:
After boot, the status is active and media 'autoselect: 10baseT/UTP
hw-loopback), but when i try to do anything with the interface (ifconfig re0
up, dhclient re0) it changes to no carrier and mode to autoselect (none).
The diode on re0 card's port blinks with yellow light (compared to stable green
when working) about once a second. When the blink occures, it also happens on
the my switch's diodes where the cable is connected. [They occur in a rapid
sequence - the green 'Act' diode first, then 'Link' blinks for a fraction of
second after which both go dark]
Sometimes after waiting several minutes it changes to active again. Sometimes
not.
It was mentioned before, I have tried patches i could find,
the one from:
http://lists.freebsd.org/pipermail/freebsd-stable/2005-March/013107.html
seems to do what it's supposed to, ie.
--- from rgephy.c part:
+ if (bmcr RGEPHY_BMCR_ISO) {
this never happens.
+ mii-mii_media_active |= IFM_NONE;
+ mii-mii_media_status = 0;
+ return;
+ }
from if_re.c part:
+
+ for (phy = 0; phy 32; phy++) {
+ bmsr = re_miibus_readreg(dev, phy, MII_BMSR);
+ bmsr = re_miibus_readreg(dev, phy, MII_BMSR);
+ if (!bmsr) continue;
--- goes here with phy = 1
+
+ re_miibus_writereg(dev, phy, MII_BMCR, BMCR_RESET);
+ for (i = 0; i RL_TIMEOUT; i++) {
+ if (!(re_miibus_readreg(dev, phy, MII_BMCR)
+ BMCR_RESET)) break;
+ DELAY(100);
+ }
breaks with i = 0
+ re_miibus_writereg(dev, phy, MII_BMCR, BMCR_LOOP);
+
+ break;
+ }
Unfortunately this doesn't fix the problem.
I have also found some additional patches for if_re but i couldn't apply them
to stable - if_re.c changed and i wasn't sure how to merge it.
Please help, I spent a week searching for a fix :( I'm eager to check any patch
sent, spend the afternoon in ddb, etc. Just tell me what/where to search - my
knowledge on network drivers is close to nil.
--
m.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What is considered the best supported RAID controller for 5.x?
On Sat, 18 Jun 2005, Patrick M. Hausen wrote: Hello! The subject says it all ... I'm looking a new server, and right now have built it around the SRCZCRX PCI-X 128MB, since I've had good luck with the Intel RAID controllers with 4.x, and I *really* like the storcon CLI utility ... but, with the move to 5.x, I'm wondering if there is something else I should be looking at, or is this still a good card to go with? IMHO it's the entire product line of ICP Vortex, now owned by Adaptec. These cards really rock. Battery backed up cache, RAID 1+0, driver maintained my company's engineers, yet in the stock FreeBSD kernel, curses based management utility to repair arrays without reboot, unattended rebuild if you exchange a broken disk with a brand new one, same interface to the host for _all_ products including SATA, ... 'k, its the above that I've grown to love with the Intel cards ... do you have a URL for these? Checking Adaptec's site, they don't seem to explicitly list the ICP Vortex stuff ... Also, is there a particular card that I should avoid, in their line up, or are they all good? I'm looking to put this into an Intel SR1400 Server Platform ... the motherboard has onboard U320 SCSI, so I was figuring to go the 0 Channel route ... and the SR1400 is 3x drive bays, so would be going RAID5 for this ... thanks ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
