Re: 5.3-RELEASE crashes during make buildworld (and other problems)
On Wednesday 12 January 2005 22:36, Rick Updegrove wrote: > Lowell Gilbert wrote: [ ... ] > > So, I am still trying to obtain a dump. > > Thanks to your reply, I did re-read #KERNEL-PANIC-TROUBLESHOOTING > more carefully and I did try the following. > > [EMAIL PROTECTED] nm -n /boot/kernel | grep c061c642 > nm: Warning: '/boot/kernel' is not an ordinary file /boot/kernel is a directory containing the kernel and loadable modules. Try to run nm on /boot/kernel/kernel. > > Any ideas on that? The reason I did not try that first was I > mistakenly thought I had to first capture the crash dump for some > reason. You can get much much more information about what went wrong from a crash dump, so try to capture one if you can. Oh, and build a debug kernel, if you didn't do it before. A crash dump can be pretty useless without one. [ ... ] > > > Rick cheers, m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3-RELEASE crashes during make buildworld (and other problems)
On Wed, 2005-Jan-12 13:36:04 -0800, Rick Updegrove wrote:
>Fatal trap 12: page fault while in kernel mode
>fault virtual address = 0x4d
>fault code = supervisor read, page not present
>instruction pointer= 0x8:0xc061c642
That's a NULL pointer dereference. It's not necessarily hardware.
>[EMAIL PROTECTED] nm -n /boot/kernel | grep c061c642
>nm: Warning: '/boot/kernel' is not an ordinary file
Two problems:
1) The kernel is /boot/kernel/kernel (sysctl kern.bootfile)
2) You're extremely unlikely to find a symbol at that address.
What you need to do is
$ nm -n `sysctl kern.bootfile` | less
and search for the symbol closest to but no greater than 0xc061c642
This still isn't enough information to reveal anything useful. As a
minimum, you need to enable DDB ("options DDB" and "options KDB") and
get a backtrace after the panic. If you don't already have one, a
serial console will make things much easier. A crashdump or gdb
session would be much better.
>> Hardware problems would be my first suspicion here.
>
>Me too... if it were not for the fact 5.3-RELEASE is the only OS that
>has problems on this hardware.
That doesn't totally rule out hardware. Pattern-sensitive memory
problems may not show up on different operating systems (or even
different kernels). That said, based on the trap information, I'd
look at a software cause first.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Extended Mail
Thank you for your response. Please don't reply to this message - it is an automated response and your reply will not be received. If you have a question for eBay Customer Support, please visit the following eBay Help page. This page will help you locate the answer to your question, or assist you in contacting us: http://pages.ebay.com/help/index.html If you would like to change your notification preferences, which determine what type of email you receive from eBay, please follow the steps below: 1. Click "My eBay" located at the top of all eBay pages. You may be asked to sign in. 2. Click the "eBay Preferences" link located under the "My Account" heading. 3. Click the "view/change" link to the right of "Notification Preferences." You may be asked to sign in once more. 4. On the "Change Your Notification Preferences" page, check the boxes to indicate the types of messages you'd like to receive from eBay. Then, uncheck the boxes to indicate the types of messages you don't want to receive from us. 5. Once you're done, be sure to click the "Save Changes" button at the top or bottom of the page. Again, thanks for writing eBay. -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: twa breakage on AMD64 with 9.1.5.2 3ware versionand2005-01-1103:00:49 UTC RELENG_5 commit
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Michael Meltzer > Sent: Wednesday, January 12, 2005 9:19 PM > To: freebsd stable > Subject: twa breakage on AMD64 with 9.1.5.2 3ware version > and2005-01-1103:00:49 UTC RELENG_5 commit > > > The new 3ware twa drive does not seem to work after the 2005-01-11 > 03:00:49 UTC RELENG_5 commit. Basically the device da is not > visible > to complete the boot and the system stopped asking for the > root path (if > their was an error message it scrolled to fast for me to see) > Backed off > to 5_3_0_RELEASE code to /usr/src/sys/dev/twa/* to get the system > backup. FWIW the 3ware support page does NOT list amd64 > freebsd support > for this driver( 9.1.5.2) and 3ware seem to define the downloadable > driver firmware feather in their makefile, the -D rule does > not seem to > have made it to the build. I tried to rebuild the code with > the correct > define but the firmware try to load but still had the problem. Took a > look at the CVS diffs but it a large/complex change set and someone > smarter than myself needs to take a look. -mjm > Could you see if the driver is getting loaded? The driver prints the message: "3ware device driver for 9000 series storage controllers...". Did the new firmware get flashed? You can download the firmware from the 3ware website and flash it on the card using a DOS floppy. Alternatively, you can add 'options TWA_FLASH_FIRMWARE' to your kernel configuration file and rebuild the kernel. This should build the kernel/driver with the firmware bundled, and the firmware should automatically get downloaded the next time you reboot. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
backporting tail from HEAD to RELENG_5
Hello, The command 'tail' has a very nice feature in HEAD. It can do 'tail -f' on multiple files. Is it possible that this gets backported to RELENG_5? I saw in cvsweb, that the committer was paul, but I don't know his e-mail address to ask him. Or should I file a PR? Greetings, Ronald. -- Ronald Klop, Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: backporting tail from HEAD to RELENG_5
On Thu, Jan 13, 2005 at 07:56:52PM +0100, Ronald Klop wrote: > Hello, > > The command 'tail' has a very nice feature in HEAD. > It can do 'tail -f' on multiple files. Is it possible that this gets > backported to RELENG_5? > Cool, I currently get this functionality from misc/xtail. xtail was on my short list of "must-have" ports. -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFLAGS=-O2 -pipe problems in RELENG_5 ?
On Wed, 12.01.2005 at 17:38:56 -0500, Mike Tancsa wrote: > I did a buildworld /buildkernel with a RELENG_5 box using the following > flags > > > CPUTYPE=i686 > KERNCONF=recycle > CFLAGS=-O2 -pipe > COPTFLAGS=-O2 -pipe > NO_MODULES=true# do not build modules with the kernel > MODULES_WITH_WORLD=true # do not build modules when building kernel I'm using -Os -pipe ever since installing 5.x after the gcc update. Haven't encountered any problem so far.. > cc -O2 -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c > /usr/src/games/fortune/strfile/strfile.c > /usr/src/games/fortune/strfile/strfile.c: In function `add_offset': > /usr/src/games/fortune/strfile/strfile.c:344: internal compiler error: Bus > error > Please submit a full bug report, > with preprocessed source if appropriate. > See http://gcc.gnu.org/bugs.html> for instructions. ICEs (internal compiler errors) usually point to serious hardware problems. Check that your RAM is OK and the CPU not overheating. Ulrich Spoerlein -- PGP Key ID: F0DB9F44 Encrypted mail welcome! Fingerprint: F1CE D062 0CA9 ADE3 349B 2FE8 980A C6B5 F0DB 9F44 Ok, which part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn." didn't you understand? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dual cpu and top in 5.3
Hi, I have a dual athlon mp system running FreeBSD 5.3-RELEASE-p2, I have wondered if both cpu's should show in top. Here is a snapshot of my top output. last pid: 15520; load averages: 0.28, 0.09, 0.03up 7+23:21:08 23:05:33 153 processes: 2 running, 151 sleeping CPU states: 0.2% user, 0.0% nice, 3.3% system, 2.5% interrupt, 94.0% idle Mem: 770M Active, 67M Inact, 115M Wired, 40M Cache, 112M Buf, 9804K Free Swap: 2048M Total, 920K Used, 2047M Free I compiled a SMP kernel of course, but I am not confident I have this setup right because of lack of evidence showing I am in SMP modein top, here is my dmesg boot log which does say 2 cpus detected. Copyright (c) 1992-2004 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.3-RELEASE-p2 #0: Tue Dec 28 17:24:11 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WEB1 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(TM) MP 2000+ (1666.74-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc048 real memory = 1073741824 (1024 MB) avail memory = 1045397504 (996 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: port 0xe800-0xe803 mem 0xfb80-0xfb800fff,0xfc00-0xfdff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd400-0xd47f mem 0xf800-0xf87f irq 16 at device 8.0 on pci0 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:e0:18:da:fa:c1 pcib2: at device 16.0 on pci0 pci2: on pcib2 cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: parallel port not found. sc0: 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 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) Timecounters tick every 1.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 50 packets/entry by default ad0: 39083MB [79408/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad0s1a Is it all looking dandy and I am ok or have I missed something, and should top show 2 cpu's or just 1? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Old patchset for net80211+atheros for 5.3 still available?
Just curious if anybody still has a copy of the last patchset for net80211+atheros for FreeBSD 5.3 still available. It came out after August 2004, and is no longer available through people.freebsd.org/~sam. The notable feature of this patchset was that it included a "doit" file that listed the steps needed to patch /usr/src. If you still have this available, could you post it online somewhere, or send me a copy? It enabled me to use WEP with my D-LINK DWL-G650 Rev. B and NetGEAR WG511T on FreeBSD 5.3-RELEASE, and there are a couple of others on bsdforums.org that would like to use this. I was hoping to write a How-To for this, except I only have the 20040824 patchset (the one before the one I need). Thanks. -- Freddie Cash, CCNT CCLPHelpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dual cpu and top in 5.3
Chris <[EMAIL PROTECTED]> wrote: > Hi, I have a dual athlon mp system running FreeBSD 5.3-RELEASE-p2, I > have wondered if both cpu's should show in top. > > Here is a snapshot of my top output. > > last pid: 15520; load averages: 0.28, 0.09, 0.03up 7+23:21:08 > 23:05:33 > 153 processes: 2 running, 151 sleeping > CPU states: 0.2% user, 0.0% nice, 3.3% system, 2.5% interrupt, 94.0% idle > Mem: 770M Active, 67M Inact, 115M Wired, 40M Cache, 112M Buf, 9804K Free > Swap: 2048M Total, 920K Used, 2047M Free > > I compiled a SMP kernel of course, but I am not confident I have this > setup right because of lack of evidence showing I am in SMP modein > top, here is my dmesg boot log which does say 2 cpus detected. On SMP machines, top should show a column titled "C" which contains the number of the processor on which the process was scheduled last (i.e. either "0" or "1" if you have two processors). > [...] > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > [...] > SMP: AP CPU #1 Launched! Looks OK. You can also query "sysctl hw.ncpu" to get the number of processors detected (and supported) by the kernel. > Is it all looking dandy and I am ok or have I missed something, and > should top show 2 cpu's or just 1? The "top" command doesn't display the number of processors directly, as far as I know. But it has the "C" column, as explained above. On an SMP machine of mine with two processors (it's a dual Celeron-466), the output looks like this: last pid: 55565; load averages: 0.01, 0.01, 0.00 up 295+04:59:09 00:40:23 76 processes: 1 running, 75 sleeping CPU states: 0.2% user, 0.0% nice, 0.2% system, 0.0% interrupt, 99.6% idle Mem: 72M Active, 7296K Inact, 35M Wired, 48K Cache, 25M Buf, 39M Free Swap: 320M Total, 29M Used, 291M Free, 8% Inuse PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 77 bind 2 0 12512K 9820K select 0 394:50 0.00% 0.00% named 22723 root 2 0 2200K 264K poll 0 190:52 0.00% 0.00% dovecot 111 root 2 0 3056K 936K select 1 94:35 0.00% 0.00% sendmail 79 root 2 0 1312K 364K select 1 35:56 0.00% 0.00% ntpd .. and so on. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFLAGS=-O2 -pipe problems in RELENG_5 ?
Ulrich Spoerlein wrote: CPUTYPE=i686 KERNCONF=recycle CFLAGS=-O2 -pipe COPTFLAGS=-O2 -pipe NO_MODULES=true# do not build modules with the kernel MODULES_WITH_WORLD=true # do not build modules when building kernel I'm using -Os -pipe ever since installing 5.x after the gcc update. Haven't encountered any problem so far.. I think the problem is more the CPUTYPE. I've trashed a 5.2 installation by rebuilding all with CPUTYPE=athlon, and when I build with i686 on a p4 system with 5.3-stable, netstat won't show Internet connections anymore (only Unix domain), and who knows what else fails. Seems like gcc is pretty buggy when you use non-default settings. mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFLAGS=-O2 -pipe problems in RELENG_5 ?
At 05:51 PM 13/01/2005, Ulrich Spoerlein wrote: On Wed, 12.01.2005 at 17:38:56 -0500, Mike Tancsa wrote: > I did a buildworld /buildkernel with a RELENG_5 box using the following > flags > > > CPUTYPE=i686 > KERNCONF=recycle > CFLAGS=-O2 -pipe > COPTFLAGS=-O2 -pipe > NO_MODULES=true# do not build modules with the kernel > MODULES_WITH_WORLD=true # do not build modules when building kernel I'm using -Os -pipe ever since installing 5.x after the gcc update. Haven't encountered any problem so far.. There are some differences between O2 and Os according to the man page. Are you using that on your kernel and for buildworld ? ICEs (internal compiler errors) usually point to serious hardware problems. Check that your RAM is OK and the CPU not overheating. heating is not an issue. I have changed the power supply and RAM just in case. Like I said, if I get rid of the O2 optimization and just use -O it works just fine. I have run into bad hardware where make buildworld exposes the problems, but I had never been able to "work around" it by changing to -O instead of O2. I let the box run over night building world 8 times with -j2 through -j5 and all worked just fine. Looking at /usr/src/UPDATING, it appears O2 does not work. However, that seems to contradict statements on the list that it works. 20040728: System compiler has been upgraded to GCC 3.4.2-pre. As with any major compiler upgrade, there are several issues to be aware of. GCC 3.4.x has broken C++ ABI compatibility with previous releases yet again and users will have to rebuild all their C++ programs with the new compiler. A new unit-at-a-time optimization mode, which is default in this compiler release, is more aggressive in removing unused static symbols. This is the likely cause of 'make buildworld' breakages with non-default CFLAGS where optimization level is set to -O2 or higher. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with devfs amd /dev/fd/
On Tue, 4 Jan 2005, Jose M Rodriguez wrote: > Hi, > > trying to import foomatic-rip, I found great changes under /dev/fd/ > going from RELENG_4 to RELENG_5. > > Seems that /dev/fd/3 is used by several pipe construct like foomatic-rip > to get a free backwards error channel. > > Digging a bit, I found that now, I need mount fdescfs to get this. I > think this is not well documented in release notes. Nothing in the FreeBSD base system depends on /dev/fd. foomatic-rip a third-party program. It would be appropriate for the port to print a message reminding the user to mount fdescfs if they plan to use this application, but not appropriate to enable it by default just for this one port. > Also, seems that support /dev/fd/3 in devfs may be a good idea. Add a > sysctl to control how many /dev/fd/n devfs create will be even better. fdesc is populated automatically based on the calling program. If the program has file descriptor 3 open then /dev/fd/3 will be available. Likewise, if it is closed, /dev/fd/3 will not exist. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sound Card Troubles
On Wed, 5 Jan 2005, Warren wrote: > Im having a bit of difficulty in getting sound to work, due to the fact i have > On-Board Sound as well as a Sound Card (PCI) .. im wanting to use both but > being a lil new im unsure of hwo to procedd, could someone please point me in > the right direction ? What FreeBSD version? What hardware? I've put a SB Live in a machine with onboard sound and both show up. on 5.x you can use a sysctl to define which device /dev/audio, /dev/dsp, etc. point to. Of couse /dev/dsp0.0, /dev/dsp1.0, etc., are created so you can access each card individually. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unstable 5.3 boxes
On Wed, 5 Jan 2005, Mitch Parks wrote: > It seems both my test and production boxes are not stable with 5.3-Release. > I'm hoping for some insight in how to make at least the production box > not crash. [...] > #7 0xe93a0018 in ?? () > #8 0xc0580010 in kvprintf (fmt=0xc7b04c60 "?6w?\v6t?\v6t?", func=0x59, > arg=0xe93ad9bc, radix=-1067875706, ap=0xc3839674 "\001") > at /usr/src/sys/kern/subr_prf.c:643 > #9 0xc058940a in selwakeuppri (sip=0x0, pri=0) > at /usr/src/sys/kern/sys_generic.c:1096 > #10 0xc0598286 in ttwakeup (tp=0xc05842e8) at /usr/src/sys/kern/tty.c:2366 Something weird is going on here. selwakeuppri() doesn't call any of the printf functions -- it calls doselwakeup() and thats it. I don't see anything in doselwakeup() that would call a printf function offhand. The null arguments in frame 9 are also odd and would certainly trip up doselwakeup() since it immediately dereferences sid. This was opening a serial device it looks like. Do you have syslog set to output to a serial terminal, or have getty enabled on ttyd*, or something plugged into any serial port, or something of that nature? The later call to ttwakeup() occurs in a block where carrier has been raised. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting 5.3R on second disk using NTLDR
On Sat, 8 Jan 2005, Aron Stansvik wrote: > I've been struggling with a dual boot setup for the best part of two > days here, and I'm not going to go outline the hazzles I've been > through. This is where I am now: Note that boot0 will happily coexist with XP, so you may want to use that option instead of dealing with NTLDR's limitations. boot0cfg -B -o packet ad0 boot0cfg -B -o packet ad1 Use F5 to toggle between disks. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GMIRROR can be destroyed by ordinary users
On Sat, 8 Jan 2005, Simon L. Nielsen wrote: > On 2005.01.08 19:39:42 +0100, Pawel Jakub Dawidek wrote: > > On Sat, Jan 08, 2005 at 04:33:14PM +0100, Simon L. Nielsen wrote: > > +> I'm not really sure it is expected that you can do that when being in > > +> the operator group. > > > > Yes. If you want to change it you should do: > > > > # chmod 600 /dev/geom.ctl > > Being in the operator group only gives read access to /dev/geom.ctl > (it's root:operator crw-r-) so I think it's somewhat counter > intuitive that one can stop the mirror without write permission there. > Wouldn't it be better to only allow stopping the mirror (and similar) > if the user has write access to geom.ctl? ioctls generally open the control device read-only so they will succeed if the user had read access to the device. ioctls themselves do not have read or write permission bits, so its all-or-nothing unless the driver or kernel code does suser() type checks. At least at a filesystem level. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MegaRAID 'Bad Slot' Kernel message and crash.
On Tue, 11 Jan 2005, Tony Byrne wrote: > Basically, after some amount of uptime the kernel will emit a "amr0: > Bad slot x completed" message and pretty soon after this the box goes into a > partially unresponsive state forcing us to reboot it. So far the only > thing triggering the problem is the nightly jobs, where the amount of > IO is higher than during the day. scottl has been able to reproduce this on a U320 controller he has. I only have U160 equipment and can't get the txn rate up high enough to reproduce the issue. The driver needs KTR instrumentation so we can see where the bad slot is popping up from. The "bad slot" message appears when the controller returns completion for a command that had already completed. The amr driver has several other issues and is in dire need of an overhaul. Unfortunately LSI has not been forthcoming with documentation, so Scott and I are pretty much scratching our heads without knowing where to go. This is in 5.X and HEAD, at least. I can't comment on 4.x. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: twa breakage on AMD64 with 9.1.5.2 3ware version and2005-01-1103:00:49 UTC RELENG_5 commit
On Thu, 13 Jan 2005, Michael Meltzer wrote: > The new 3ware twa drive does not seem to work after the 2005-01-11 > 03:00:49 UTC RELENG_5 commit. Basically the device da is not visible > to complete the boot and the system stopped asking for the root path (if > their was an error message it scrolled to fast for me to see) You can press scroll-lock and use the arrow or pageup/down keys to view the console buffer. Optionally you can set up a serial console and log all the output there. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dual cpu and top in 5.3
Ok thanks yes I have the C column (happy) PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 466 root80 229M 25168K nanslp 0 9:57 0.00% 0.00% java 797 root80 229M 25168K nanslp 0 1:45 0.00% 0.00% java 800 root80 229M 25168K nanslp 0 1:10 0.00% 0.00% java 657 root80 2580K 1028K nanslp 1 0:57 0.00% 0.00% da-popb4sm 480 root 960 3160K 1548K select 0 0:55 0.00% 0.00% ntpd 439 root 960 7964K 6808K select 0 0:47 0.00% 0.00% dccifd Chris On Fri, 14 Jan 2005 00:43:24 +0100 (CET), Oliver Fromme <[EMAIL PROTECTED]> wrote: > Chris <[EMAIL PROTECTED]> wrote: > > Hi, I have a dual athlon mp system running FreeBSD 5.3-RELEASE-p2, I > > have wondered if both cpu's should show in top. > > > > Here is a snapshot of my top output. > > > > last pid: 15520; load averages: 0.28, 0.09, 0.03up 7+23:21:08 > > 23:05:33 > > 153 processes: 2 running, 151 sleeping > > CPU states: 0.2% user, 0.0% nice, 3.3% system, 2.5% interrupt, 94.0% > > idle > > Mem: 770M Active, 67M Inact, 115M Wired, 40M Cache, 112M Buf, 9804K Free > > Swap: 2048M Total, 920K Used, 2047M Free > > > > I compiled a SMP kernel of course, but I am not confident I have this > > setup right because of lack of evidence showing I am in SMP modein > > top, here is my dmesg boot log which does say 2 cpus detected. > > On SMP machines, top should show a column titled "C" which > contains the number of the processor on which the process > was scheduled last (i.e. either "0" or "1" if you have two > processors). > > > [...] > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > [...] > > SMP: AP CPU #1 Launched! > > Looks OK. > > You can also query "sysctl hw.ncpu" to get the number of > processors detected (and supported) by the kernel. > > > Is it all looking dandy and I am ok or have I missed something, and > > should top show 2 cpu's or just 1? > > The "top" command doesn't display the number of processors > directly, as far as I know. But it has the "C" column, as > explained above. > > On an SMP machine of mine with two processors (it's a dual > Celeron-466), the output looks like this: > > last pid: 55565; load averages: 0.01, 0.01, 0.00 up 295+04:59:09 > 00:40:23 > 76 processes: 1 running, 75 sleeping > CPU states: 0.2% user, 0.0% nice, 0.2% system, 0.0% interrupt, 99.6% idle > Mem: 72M Active, 7296K Inact, 35M Wired, 48K Cache, 25M Buf, 39M Free > Swap: 320M Total, 29M Used, 291M Free, 8% Inuse > > PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND > 77 bind 2 0 12512K 9820K select 0 394:50 0.00% 0.00% named > 22723 root 2 0 2200K 264K poll 0 190:52 0.00% 0.00% dovecot > 111 root 2 0 3056K 936K select 1 94:35 0.00% 0.00% sendmail > 79 root 2 0 1312K 364K select 1 35:56 0.00% 0.00% ntpd > .. and so on. > > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "A language that doesn't have everything is actually easier > to program in than some that do." >-- Dennis M. Ritchie > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unstable 5.3 boxes
On Thu, 13 Jan 2005, Doug White wrote: #7 0xe93a0018 in ?? () #8 0xc0580010 in kvprintf (fmt=0xc7b04c60 "?6w?\v6t?\v6t?", func=0x59, arg=0xe93ad9bc, radix=-1067875706, ap=0xc3839674 "\001") at /usr/src/sys/kern/subr_prf.c:643 #9 0xc058940a in selwakeuppri (sip=0x0, pri=0) at /usr/src/sys/kern/sys_generic.c:1096 #10 0xc0598286 in ttwakeup (tp=0xc05842e8) at /usr/src/sys/kern/tty.c:2366 Something weird is going on here. selwakeuppri() doesn't call any of the printf functions -- it calls doselwakeup() and thats it. I don't see anything in doselwakeup() that would call a printf function offhand. The null arguments in frame 9 are also odd and would certainly trip up doselwakeup() since it immediately dereferences sid. This was opening a serial device it looks like. Do you have syslog set to output to a serial terminal, or have getty enabled on ttyd*, or something plugged into any serial port, or something of that nature? The later call to ttwakeup() occurs in a block where carrier has been raised. No serial devices, and ttyd* are "off". Syslog messages are going to the console, but nowhere special. Since my last post, I've cvsup'd to -p4 plus this patch: http://redirx.com/?guho but I had another reboot this week with nearly identical output: http://redirx.com/?go54 My -p4 kernel also removed NFS since I wasn't using it Since then, I've disabled HTT in the BIOS and ACPI during boot. Last crash took almost two weeks to happen, so for now, I guess I wait. | Mitch Parks * [EMAIL PROTECTED] | "I bring you love and deeper understanding." - Kate Bush ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
