AW: AW: 5.3 and re driver problem? (Solved)
Just for the archives if somebody searches this: ifconfig reX inet IP netmask MASK media 100BaseTX medioopt full-duplex -rxcsum -txcsum in rc.conf solved the problem and the interfaces works again. thanks for help, karl > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im Auftrag von > Mikko Työläjärvi > Gesendet: Samstag, 08. Jänner 2005 06:37 > An: Karl M. Joch > Cc: [EMAIL PROTECTED] > Betreff: Re: AW: 5.3 and re driver problem? > > On Fri, 7 Jan 2005, Karl M. Joch wrote: > > > forgot to mention, this 3 cards are onboard because this i > a mini-pc. so no > > chance to replace them :-(. > > I had to turn off checksum offloading (add "-rxcsum -txcsum" to > ifconfig_re0 in /etc/rc.conf) in order to make my on-board interface > work. > > $.02, > /Mikko > > > > > thx. > > > >> -Ursprüngliche Nachricht- > >> Von: Pertti Kosunen [mailto:[EMAIL PROTECTED] > >> Gesendet: Freitag, 07. Jänner 2005 17:21 > >> An: [EMAIL PROTECTED] > >> Cc: Karl M. Joch > >> Betreff: Re: 5.3 and re driver problem? > >> > >> Karl M. Joch wrote: > >> > >>> Hello, > >>> > >>> on a box with 3 re interfaces i get a lot of watchdog timeouts and > >>> stopping/clow connections. only found 1 or 2 postings with > >> the same problem, > >>> but not much replys. the box worked great with 4.x. > >>> > >>> any suggestions would be very appreziated. > >>> > >> > >> I changed re nic to Intel gigE (em) and had no network > problems since. > >> > >> Disabling ACPI might help. > >> > >> > > > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
twa breakage on AMD64 with 9.1.5.2 3ware version and 2005-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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Support for Sis 755 AGP WAS: Fwd: Radeon DRI problems after system upgrade
On Tuesday 11 January 2005 20:55, Jonathan Fosburgh wrote: > On Tuesday 11 January 2005 16:42, Jung-uk Kim wrote: > > I think I screwed up the PCI ID. :-( > > > > Can you test the attached patch? It's for 6-CURRENT but you get the > > idea. > > It now probes correctly: > > agp0: mem 0xd800-0xdfff at device 0.0 > on pci0 > Things are pointing a little more towards AGP. I found a posting on x11@ by Jung-uk Kim about testing AGP before blaming DRI. I compiled the program and ran it, here is what I am getting: version: 0.0 bridge id: 0x7551039 agp_mode: 0x1f000217 aper_base: 0xe800 aper_size: 4 pg_total: 112640 pg_system: 112640 pg_used: 0 MTRR: e800/40 entry.key : 4 ioctl(AGPIOC_BIND): Invalid argument Apparently, the aperture is being incorrectly probed as 4M. I have it at the smallest setting which is 32M. Is there something I can do to force it to the correct amount of memory? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel build failure amd64
On Wed, Jan 12, 2005 at 05:19:14PM -0800, Ade Lovett wrote: Your src/ tree is not up to date, or has been otherwise mangled. The commit that added KB_CONF_NO_PROBE_TEST touched two files: Yes. My cvs repo got mangled. Either cvsup or the (not-FreeBSD) OS it's hosted on mangled something. Unfortunately cvsup didn't seem to pick that up, so I don't know if my cvsup or the mirror it's taken off is at issue. Now I need to hunt through my repo for other truncated files. :-( -- Christopher Vance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel build failure amd64
On Thu, Jan 13, 2005 at 11:51:24AM +1100, I wrote: Recent cvsup with cvs up. Removed /usr/obj/.../src/sys/GENERIC. (cd /usr/src; make kernel) dies with /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: `KB_CONF_NO_PROBE_TEST' undeclared (first use in this function) /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: (Each undeclared identifier is reported only once /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: for each function it appears in.) *** Error code 1 The only file mentioning KB_CONF_NO_PROBE_TEST in any version appears to be src/sys/dev/kbd/atkbd.c, with no definition anywhere. cvs repo was broken, so cvsup not working right, or something similar sorry to bother you -- Christopher Vance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel build failure amd64
Christopher Vance wrote: The only file mentioning KB_CONF_NO_PROBE_TEST in any version appears to be src/sys/dev/kbd/atkbd.c, with no definition anywhere. Your src/ tree is not up to date, or has been otherwise mangled. The commit that added KB_CONF_NO_PROBE_TEST touched two files: [EMAIL PROTECTED]:/sys/dev/kbd] 2% grep KB_CONF_NO_PROBE_TEST * atkbd.c:if (!(flags & KB_CONF_NO_PROBE_TEST)) atkbdreg.h:#define KB_CONF_NO_PROBE_TEST (1 << 3) /* don't test keyboard during probe */ -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kernel build failure amd64
Recent cvsup with cvs up. Removed /usr/obj/.../src/sys/GENERIC. (cd /usr/src; make kernel) dies with cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/d2/FreeBSD/root/5-stable/usr/src/sys -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/dev/acpica -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/altq -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/ipfilter -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/pf -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/dev/ath -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/dev/ath/freebsd -I/d2/FreeBSD/root/5-stable/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c: In function `probe_keyboard': /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: `KB_CONF_NO_PROBE_TEST' undeclared (first use in this function) /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: (Each undeclared identifier is reported only once /d2/FreeBSD/root/5-stable/usr/src/sys/dev/kbd/atkbd.c:1120: error: for each function it appears in.) *** Error code 1 The only file mentioning KB_CONF_NO_PROBE_TEST in any version appears to be src/sys/dev/kbd/atkbd.c, with no definition anywhere. -- Christopher Vance ___ 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.
Tony Byrne writes: | 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. | | Before deployment, we tested the box with 5.3-STABLE and managed to | trigger the problem twice. This forced us to try 4.10-STABLE which | was fine in testing and for a number of weeks after deployment. | However, just before new year we saw our first Bad Slot and crash under | 4.10. Since then it has happened 3 more times. We have upgraded the firmware to | the latest version available from Intel, and if anything this has made | the problem worse. | | The machine had 3 disks configured as a single RAID5 array. A fourth | disk is configured as a hot-standby. The card is equipped with 128Mb | of battery-backed cache. Write-back caching is enabled on the card. | Read-ahead caching is enabled in non-adaptive mode. | | Is anyone else using a SRCU42X RAID card and seeing similar | problems to ours? What about other cards supported by the amr driver? We run RAID 10 across 4 drives at work on Dell PE2850's which have amr RAID's and no-one has reported this problem to me (which they do). We run FreeBSD 4.10 & 5.3 on them. This is with and without our local mods. We have most experience with 4.10. Dell has their own firmware version (atleast to call it is a PERC controller). For now this is a "works for me". Doug A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nforce shipset
On Wed, 12 Jan 2005 16:09:36 -0700 Didier Caamano <[EMAIL PROTECTED]> wrote: > Greetings to all: > > I was wondering if FBSD has support for the nforce2 ship set, I will > > really love to have FBSD on my computer, but I need to know if it > support the ship set. The nforce2 chipset works nicely. The sound and ethernet support will very depending on what chipset was used, so you will need to look up what was used for it on that board. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nforce shipset
Greetings to all: I was wondering if FBSD has support for the nforce2 ship set, I will really love to have FBSD on my computer, but I need to know if it support the ship set. Thanks in advance, have a good day ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CFLAGS=-O2 -pipe problems in RELENG_5 ?
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 After rebooting and trying to repeat the process, I get the following [ns4-new]# rm -R /usr/obj/ [ns4-new]# make buildworld -- >>> Rebuilding the temporary build tree -- rm -rf /usr/obj/usr/src/i386 mkdir -p /usr/obj/usr/src/i386/legacy/usr/bin mkdir -p /usr/obj/usr/src/i386/legacy/usr/games mkdir -p /usr/obj/usr/src/i386/legacy/usr/include/c++/3.3 mkdir -p /usr/obj/usr/src/i386/legacy/usr/include/sys mkdir -p /usr/obj/usr/src/i386/legacy/usr/lib mkdir -p /usr/obj/usr/src/i386/legacy/usr/libexec mkdir -p /usr/obj/usr/src/i386/legacy/usr/sbin mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/dict mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devX100 mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devX100-12 mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devX75 mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devX75-12 mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devascii mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devcp1047 mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devdvi mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devhtml mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devkoi8-r mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devlatin1 mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devlbp mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devlj4 mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devps mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/groff_font/devutf8 mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/tmac/mdoc mkdir -p /usr/obj/usr/src/i386/legacy/usr/share/tmac/mm mkdir -p /usr/obj/usr/src/i386/lib mkdir -p /usr/obj/usr/src/i386/usr/bin mkdir -p /usr/obj/usr/src/i386/usr/include mkdir -p /usr/obj/usr/src/i386/usr/lib/compat/aout mkdir -p /usr/obj/usr/src/i386/usr/libdata/ldscripts mkdir -p /usr/obj/usr/src/i386/usr/libexec mkdir -p /usr/obj/usr/src/i386/usr/sbin mkdir -p /usr/obj/usr/src/i386/usr/share/misc mkdir -p /usr/obj/usr/src/i386/usr/share/snmp/defs mkdir -p /usr/obj/usr/src/i386/usr/share/snmp/mibs mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/obj/usr/src/i386/usr/include >/dev/null ln -sf /usr/src/sys /usr/obj/usr/src/i386 -- >>> stage 1.1: legacy release compatibility shims -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/i386 MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" make -f Makefile.inc1 DESTDIR= BOOTSTRAPPING=503101 -DNOHTML -DNOINFO -DNOLINT -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -DNO_CPU_CFLAGS -DNO_WARNS legacy ===> tools/build /usr/obj/usr/src/i386/usr/src/tools/build created for /usr/src/tools/build cd /usr/src/tools/build; make buildincludes; make installincludes rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include /usr/src/tools/build/dummy.c cc -O2 -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/tools/build/dummy.c building static egacy library ranlib libegacy.a sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libegacy.a /usr/obj/usr/src/i386/legacy/usr/lib -- >>> stage 1.2: bootstrap tools -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/i386 MAKEFLAGS="-m /usr/src/tools/build/mk -m /usr/src/share/mk" make -f Makefile.inc1 DESTDIR= BOOTSTRAPPING=503101 -DNOHTML -DNOINFO -DNOLINT -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -DNO_CPU_CFLAGS -DNO_WARNS bootstrap-tools ===> games/fortune/strfile /usr/obj/usr/src/i386/usr/src/games/fortune/strfile created for /usr/src/games/fortune/strfile rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include /usr/src/games/fortune/strfile/strfile.c echo strfile: /usr/lib/libc.a /usr/obj/usr/src/i386/legacy/usr/lib/libegacy.a >> .depend 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':
Re: 5.3-RELEASE crashes during make buildworld (and other problems)
Rick Updegrove wrote: PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 607 root 1310 136K36K RUN 51:14 98.97% 98.97% burnK7 *"end paste from top process" As you can see it went on for 51 minutes and my machine did not lock up and the heat alarm did not go off. Please note that I ran KDE and portupgrade during this test with no problems at all. Also note there is a 160 GIG drive in here that was undergoing a fsck -B which really slows down the system a lot. Thanks again for the reply, but I do not suspect hardware per se. The reason I believe this is as I mentioned this machine runs FreeBSD 4.11-STABLE and/or Win2K (all service packs) just fine. On windoze I just beat half-life 2 without ever crashing it. 98.87% for 51 minutes *should* have triggered any heat problems, so looks like the HW is not the problem (worth ruling out anyway). best wishes Mark ___ 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)
Lowell Gilbert wrote: > That should be "dumpdir", not "DUMPDIR". > The default would be /var/crash instead of /usr/crash. > Also, /dev/ad0s1b has to be bigger than your RAM size. Thank you very much for the reply Lowell, That DUMPDIR was silly of me, thank you for pointing it out. I have 1.5 GIGS of RAM and /var is 248 MEGS which is self-explanatory. > You can try to analyze the panic messages themselves. > There is some guidance for this in the FAQ. The guidence I read at in the developer's handbook suggests I obtain a crashdump and post to the list because the info found in a panic (example of one of mine below) is not enough. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4d fault code = supervisor read, page not present instruction pointer = 0x8:0xc061c642 stack pointer = 0x10:0xf00e1cc4 frame pointer = 0x10:0xf00e1cd0 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 = 1009 (kdeinit) trap number = 12 panic: page fault Uptime: 21m8s 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 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. > 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. > If you try it again, does it fail in the same place? No it does not fail in the same place every time but I still do not suspect hardware per se. For more details on why I believe that statement, please see: http://lists.freebsd.org/pipermail/freebsd-stable/2005-January/011034.html Thanks again for the reply it was helpful. Rick ___ 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)
Mark Kirkwood wrote: I am wondering if cpu overheating could be a factor. In 4.x you are building with gcc 2.95, whereas 5.3 uses 3.4 - the 3.x compiler takes longer and works harder, which may be generating more heat (i.e too much heat). You can test this by installing the cpuburn port and running it for 10-20 minutes. Thank you very much for the reply Mark. I installed cpuburn but ran out of time that night to test it. After some reading, I limited the RAM by adding the following to rc.conf hw.physmem="512M"# Limit physical memory. See loader(8) Then I rebooted. I did this because I do not want to wait for 1536M to be written to disk after the inevitable crash. Then I ran cpuburn (actually burnK7) and "top" and monitored them. *"start paste from top process" last pid: 56346; load averages: 1.00, 1.00, 1.13 up 0+01:28:13 19:59:17 31 processes: 2 running, 29 sleeping CPU states: 99.2% user, 0.0% nice, 0.4% system, 0.4% interrupt, 0.0% idle Mem: 48M Active, 160M Inact, 69M Wired, 1848K Cache, 60M Buf, 214M Free Swap: 3047M Total, 3047M Free PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 607 root 1310 136K36K RUN 51:14 98.97% 98.97% burnK7 *"end paste from top process" As you can see it went on for 51 minutes and my machine did not lock up and the heat alarm did not go off. Please note that I ran KDE and portupgrade during this test with no problems at all. Also note there is a 160 GIG drive in here that was undergoing a fsck -B which really slows down the system a lot. Thanks again for the reply, but I do not suspect hardware per se. The reason I believe this is as I mentioned this machine runs FreeBSD 4.11-STABLE and/or Win2K (all service packs) just fine. On windoze I just beat half-life 2 without ever crashing it. On FreeBSD 4.11 I run make buildworld every few days without ever crashing it. The only thing I can think to do differently is comment # hw.physmem="512M"# Limit physical memory. See loader(8) and try cpuburn again? Any other ideas? Rick P.S. After writing all this, I did manage to finally build 5.3-STABLE after a few more tries at make buildworld, from wherever it failed. Aside from one lockup in KDE (no crashdump yet sorry) last night it has been ok today. I will however continue to test make buildworld and try to get a crashdump to post to the list because I would really like to know what is really causing this instability. Thanks again! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Suspend problem on FreeBSD 5.3-STABLE
> At this time the cardbus driver reports: > > "cbb0: CardBus card activation failed" Ignore this message. It means "no driver attached," and has been removed from current (soon to be MFC'd). What are the lines before it? Without knowing that, it is impossible to say what went wrong. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: update for 4.11 Security Officer-supported branches
Barry Bouwsma wrote: [thread hijacked from freebsd-security@ and landed in stable@ ] On Mon, 10 Jan 2005 11:16:34 -0800, Julian Elischer wrote: While a 4.12 will PROBABLY not happen, I do plan on continued MFCs of important changes to RELENG_4 as I do not envision my custommers moving to 5.x until some time in 2006 at the earliest. (Including fixes from dragonfly, and possibly some new drivers and thing like USB fixes. Thanks, Julian, and I'd like to contemplate getting a few of my MFC hacks that I'm running on 4.x, added to releng, if possible. One of these things I've found very handy is the `mount' option introduced in 5.x that allows one to specify with -F an alternate to /etc/fstab to be used. we can probably MFC anything that doesn't break any existing ABI. This I use for conditional mounting of devices which may or may not be present, like external USB (to catch your interest, heh) drives with a complicated partition layout. I test if a known drive is present at a certain device, and if so, `mount -F /etc/fstab-da0' or `-da1' and so on, as part of my boot. In order to adopt this change, I had to add to libc in 4.x as well as butcher the `mount' code. Does such a change stand a chance of being added to 4.x, or are infrastructure changes required this way, like to libc, off-limits outside my own hive of personal hackery? libc is not usually a target in a legacy branch. Addign a new function to it may be ok in some cases but probably best to not do it. (What's missing, as far as I know, that could be handy, is a comparable option to `umount' when one wants to quickly detach a drive with ten mounted filesystems. I haven't looked at this idea) (freebsd-legacy@ , anyone, for those of us too stubborn to join the modern world, and get confused when the -stable list postings don't make clear what release is being discussed, or want a quiet place to mull over 2.2.x ?) I was considerring this.. when 4.11 dies, we may make such a list. thanks barry bouwsma ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Suspend problem on FreeBSD 5.3-STABLE
On Wed, Jan 12, 2005 at 07:29:48AM -0700, M. Warner Losh wrote: > : > FA411 16 bit PCMCIA card after a suspend/resume works as expected. I > : > will try to down the interface and kldunload the dc driver before > : > shutdown to see if that helps. > : > : That fits with my analysis as well. It seems that cardbus handles > : things fine but individual drivers may be lacking in suspend/resume support. > > Cardbus should be detaching and reattaching the device. So that's > clearly a bug in cardbus. Individual drivers have no choice in this > matter, since we can't know if the cards that are there after the > resume were the ones we suspended with. This doesn't matter too much > for NIC cards (but none of the drivers cope with MAC addresses > changing), but matters a great deal for things like flash cards. > > : That's a good testing approach, btw. If you find the dc(4) driver seems > : to be the culprit, the next step is to go through any datasheets and > : other OS drivers to see if you can find what we're doing differently. > > I don't think that it is a dc problem. > After my tests I'm not sure where it is. Here's what I did: o Compiled a kernel without dc support so I could # kldload if_dc o Loaded if_dc.ko as a module o Inserted the card At this time the card was properly probed. o Ran dhclient dc0 and observed the card get an ip address from my dhcp server. o Did some more network tests (hit http://www.ebay.com in firefox...) o Turned off the card nicely prior to detaching it: # ifconfig dc0 down delete o Unplugged the card and observed it detach from the cbb0 "slot". o Unloaded the if_dc driver: # kldunload if_dc o Suspend the laptop to standby mode: # sysctl hw.acpi.lid_switch_state="S3" Close the laptop's lid o Resume: Open the laptop's lid o Reload the driver (kldload if_dc...) o Pluggin the card At this time the cardbus driver reports: "cbb0: CardBus card activation failed" This leads me to believe that either the CardBus handler has a problem attaching an existing "used" dc driver to the card after a suspend/resume or the dc driver has left something in a state after it's detach where a re-attach will not work correctly. Has anyone got any other ideas? -- Chris -- -- Chris Hilton chilton-at-vindaloo-dot-com "All I was doing was trying to get home from work!" -- Rosa Parks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Data modified on freelist"?
Rich Wales <[EMAIL PROTECTED]> writes: > I'm running 4-STABLE / 4.11-PRERELEASE (CVS tag=RELENG_4), dated 2004- > 12-10, on an AMD Athlon system at home. > > Last night, I got the following message from the kernel: > > Data modified on freelist: word 14 of object 0xc2aff700 > size 256 previous type FFS node (0xdeadc09e != 0xdeadc0de) > > What does this mean? Is it a reason for me to worry? Any ideas on > what might have caused it or what I should do about it? That's a single bit flipped. Assuming you don't have error-correcting memory, it could be anything, including a stray cosmic ray... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"Data modified on freelist"?
I'm running 4-STABLE / 4.11-PRERELEASE (CVS tag=RELENG_4), dated 2004- 12-10, on an AMD Athlon system at home. Last night, I got the following message from the kernel: Data modified on freelist: word 14 of object 0xc2aff700 size 256 previous type FFS node (0xdeadc09e != 0xdeadc0de) What does this mean? Is it a reason for me to worry? Any ideas on what might have caused it or what I should do about it? Rich Wales[EMAIL PROTECTED]http://www.richw.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr too small
On Wed, Jan 12, 2005 at 09:22:19AM +0100, Marc Plumet wrote: > Dear all, > > my system : > kern.osreldate: 503001 > FreeBSD 5.3-RELEASE #0: Tue Nov 9 13:34:27 CET 2004 > > I am running Freebsd on a laptop (Compaq Evo N800c). > I have a winnt partition (8GB) > I have a ufs partition (11GB) > my problem is that /usr is getting full. ,snip> > I could scratch the winnt partition because I can do most of my work > now with FreeBSD, I still need java/openoffice though, but therfore I > need some free space first. > > Is there a way to use the free space from the "scratched-winnt" partition to > increase the /usr size ? You could look at disk contatation, see gconcat(8) or striping, see gstripe(8). I'm not sure if this works for disk partitions, or if you need a complete disk for that. But this would require a backup of /usr, newfs-ing the concatenated device followed by restoring the backup. Another option would be to copy a large part of /usr, say /usr/local to the reformatted former winnt partition and mount it at /usr/local. Other directories could be moveed to the new partition and symlinked to their previous places. Roland -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpVtRoPvnLei.pgp Description: PGP signature
Re: /usr too small
On Wed, Jan 12, 2005 at 09:22:19AM +0100, Marc Plumet wrote: > Dear all, > > my system : > kern.osreldate: 503001 > FreeBSD 5.3-RELEASE #0: Tue Nov 9 13:34:27 CET 2004 > > I am running Freebsd on a laptop (Compaq Evo N800c). > I have a winnt partition (8GB) > I have a ufs partition (11GB) > > I have *** Working on device /dev/ad0 *** > parameters extracted from in-core disklabel are: > cylinders=38760 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=38760 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 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) > start 63, size 16374897 (7995 Meg), flag 0 > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 15/ sector 63 > The data for partition 2 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 16374960, size 22695120 (11081 Meg), flag 80 (active) > beg: cyl 1023/ head 255/ sector 63; > end: cyl 1023/ head 15/ sector 63 > > my problem is that /usr is getting full. > Filesystem 1K-blocksUsed Avail Capacity Mounted on > /dev/ad0s2a507630 362568 10445278%/ > devfs 1 1 0 100%/dev > /dev/ad0s2f 3966294 2783584 86540876%/home > /dev/ad0s2e 4737646 4222964 13567297%/usr > /dev/ad0s2d 1012974 55104 876834 6%/var > > I could scratch the winnt partition because I can do most of my work now with > FreeBSD, I still need java/openoffice though, but therfore I need some free > space first. > > Is there a way to use the free space from the "scratched-winnt" partition to > increase the /usr size ? You're best bet is probably to make the winnt drive into /usr/local. That's there the biggest stuff goes. You may have to do some further juggling of space to get openoffice to build, but it will certaintly install. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpeSGN9LclBM.pgp Description: PGP signature
Re: trap 12
>>Dumping 1023 MB >> >>Dump failed writing data (1) >> >>Dump failed writing trailer (1) >> >>Dump complete >> >> any hints to finding out why i can not get a saved core on this >> machnine would be much appreciated. >> > Is your swap drive your dumping to > 1023M. If not you need to > specify a dump drive that is > 1023M. foo.edu:/# bsdlabel twed0s1 # /dev/twed0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 4194304 524288 swap c: 1452114720unused0 0 # "raw" part, don't edit d: 2097152 47185924.2BSD 2048 16384 28552 e: 2097152 68157444.2BSD 2048 16384 28552 f: 41943040 89128964.2BSD 2048 16384 28552 g: 94224384 508559364.2BSD 2048 16384 28552 h: 131152 1450803204.2BSD 2048 16384 8200 looks to be 2g for 1g o' ram randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: trap 12
On Wed, 12 Jan 2005 00:29:42 -0800, Randy Bush <[EMAIL PROTECTED]> wrote: > managed to catch a crash that seems to happen every few days. this > was on an old build, re-cvsupping now > > FreeBSD foo.edu 5.3-STABLE FreeBSD 5.3-STABLE #3: Fri Dec 17 19:01:18 GMT > 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FOO i386 > >Fatal trap 12: page fault while in kernel mode >cpuid = 0; apic id = 00 >fault virtual address = 0x41959c25 >fault code = supervisor write, page not present >instruction pointer = 0x8:0xc04e832a >stack pointer = 0x10:0xe75d5978 >frame pointer = 0x10:0xe75d5994 >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 = 27496 (sshd) >trap number = 12 >panic: page fault >cpuid = 0 >boot() called on cpu#0 >Uptime: 5d19h20m0s >Dumping 1023 MB > >Dump failed writing data (1) > >Dump failed writing trailer (1) > >Dump complete > > any hints to finding out why i can not get a saved core on this > machnine would be much appreciated. > Is your swap drive your dumping to > 1023M. If not you need to specify a dump drive that is > 1023M. Scot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: update for 4.11 Security Officer-supported branches
[thread hijacked from freebsd-security@ and landed in stable@ ] On Mon, 10 Jan 2005 11:16:34 -0800, Julian Elischer wrote: > While a 4.12 will PROBABLY not happen, I do plan on continued MFCs of > important > changes to RELENG_4 as I do not envision my custommers moving to 5.x > until some > time in 2006 at the earliest. (Including fixes from dragonfly, and > possibly some new drivers > and thing like USB fixes. Thanks, Julian, and I'd like to contemplate getting a few of my MFC hacks that I'm running on 4.x, added to releng, if possible. One of these things I've found very handy is the `mount' option introduced in 5.x that allows one to specify with -F an alternate to /etc/fstab to be used. This I use for conditional mounting of devices which may or may not be present, like external USB (to catch your interest, heh) drives with a complicated partition layout. I test if a known drive is present at a certain device, and if so, `mount -F /etc/fstab-da0' or `-da1' and so on, as part of my boot. In order to adopt this change, I had to add to libc in 4.x as well as butcher the `mount' code. Does such a change stand a chance of being added to 4.x, or are infrastructure changes required this way, like to libc, off-limits outside my own hive of personal hackery? (What's missing, as far as I know, that could be handy, is a comparable option to `umount' when one wants to quickly detach a drive with ten mounted filesystems. I haven't looked at this idea) (freebsd-legacy@ , anyone, for those of us too stubborn to join the modern world, and get confused when the -stable list postings don't make clear what release is being discussed, or want a quiet place to mull over 2.2.x ?) thanks barry bouwsma ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Suspend problem on FreeBSD 5.3-STABLE
In message: <[EMAIL PROTECTED]> Nate Lawson <[EMAIL PROTECTED]> writes: : Christopher Sean Hilton wrote: : > Nate Lawson wrote: : >> : >> My cardbus works fine after suspend/resume. The only current bug is : >> the extremely long time before resume methods run that was introduced : >> in the past couple weeks. : >> : > : > This afternoon I retested. Here's a better description of the problem. : > My Netgear FA511 Card is not reinitialized after a suspend/resume cycle. : > I had thought that the problem was a cardbus issue but it only affects : > this one card. Some interesting information about this card: It's a : > 32bit cardbus adapter served by the dc driver. Plugging in a Netgear : > FA411 16 bit PCMCIA card after a suspend/resume works as expected. I : > will try to down the interface and kldunload the dc driver before : > shutdown to see if that helps. : : That fits with my analysis as well. It seems that cardbus handles : things fine but individual drivers may be lacking in suspend/resume support. Cardbus should be detaching and reattaching the device. So that's clearly a bug in cardbus. Individual drivers have no choice in this matter, since we can't know if the cards that are there after the resume were the ones we suspended with. This doesn't matter too much for NIC cards (but none of the drivers cope with MAC addresses changing), but matters a great deal for things like flash cards. : That's a good testing approach, btw. If you find the dc(4) driver seems : to be the culprit, the next step is to go through any datasheets and : other OS drivers to see if you can find what we're doing differently. I don't think that it is a dc problem. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr too small
On Wed, Jan 12, 2005 at 09:22:19AM +0100, Marc Plumet wrote: > Dear all, > > my system : > kern.osreldate: 503001 > FreeBSD 5.3-RELEASE #0: Tue Nov 9 13:34:27 CET 2004 > > I am running Freebsd on a laptop (Compaq Evo N800c). > I have a winnt partition (8GB) > I have a ufs partition (11GB) > > I have *** Working on device /dev/ad0 *** > parameters extracted from in-core disklabel are: > cylinders=38760 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=38760 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 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) > start 63, size 16374897 (7995 Meg), flag 0 > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 15/ sector 63 > The data for partition 2 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 16374960, size 22695120 (11081 Meg), flag 80 (active) > beg: cyl 1023/ head 255/ sector 63; > end: cyl 1023/ head 15/ sector 63 > > my problem is that /usr is getting full. > Filesystem 1K-blocksUsed Avail Capacity Mounted on > /dev/ad0s2a507630 362568 10445278%/ > devfs 1 1 0 100%/dev > /dev/ad0s2f 3966294 2783584 86540876%/home > /dev/ad0s2e 4737646 4222964 13567297%/usr > /dev/ad0s2d 1012974 55104 876834 6%/var > > I could scratch the winnt partition because I can do most of my work now with > FreeBSD, I still need java/openoffice though, but therfore I need some free > space first. > > Is there a way to use the free space from the "scratched-winnt" partition to > increase the /usr size ? Perhaps someone can give you a better advice but the easiest thing to do is to: 1) remove winnt partition 2) create freebsd partition 3) find a directory that takes up most space in /usr 4) put the content of that directory onto the new partition 5) remove the old directory and mount the new partition there OR You could try something fancy like using growfs for growing the filesystem or unionfs for creating multiple filesystem layers. Hope this helps, Andrew pgpkhg5ASyvNS.pgp Description: PGP signature
trap 12
managed to catch a crash that seems to happen every few days. this was on an old build, re-cvsupping now FreeBSD foo.edu 5.3-STABLE FreeBSD 5.3-STABLE #3: Fri Dec 17 19:01:18 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FOO i386 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x41959c25 fault code = supervisor write, page not present instruction pointer = 0x8:0xc04e832a stack pointer = 0x10:0xe75d5978 frame pointer = 0x10:0xe75d5994 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 = 27496 (sshd) trap number = 12 panic: page fault cpuid = 0 boot() called on cpu#0 Uptime: 5d19h20m0s Dumping 1023 MB Dump failed writing data (1) Dump failed writing trailer (1) Dump complete any hints to finding out why i can not get a saved core on this machnine would be much appreciated. randy --- 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-STABLE #3: Fri Dec 17 19:01:18 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FOO Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2665.92-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1073217536 (1023 MB) avail memory = 1044910080 (996 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pci1: at device 28.0 (no driver attached) pcib2: at device 29.0 on pci1 pci2: on pcib2 twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x3080-0x308f mem 0xfc80-0xfcff irq 48 at device 1.0 on pci2 twe0: [GIANT-LOCKED] twe0: 4 ports, Firmware FE7S 1.05.00.065, BIOS BE7X 1.08.00.048 em0: port 0x3000-0x303f mem 0xfc20-0xfc21 irq 54 at device 3.0 on pci2 em0: Ethernet address: 00:30:48:29:37:54 em0: Speed:N/A Duplex:N/A em1: port 0x3040-0x307f mem 0xfc22-0xfc23 irq 55 at device 3.1 on pci2 em1: Ethernet address: 00:30:48:29:37:55 em1: Speed:N/A Duplex:N/A pci1: at device 30.0 (no driver attached) pcib3: at device 31.0 on pci1 pci3: on pcib3 pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pcib4: at device 30.0 on pci0 pci4: on pcib4 pci4: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x2060-0x206f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xe-0xe3fff,0xc9000-0xc9fff,0xc8000-0xc8fff,0xc-0xc7fff on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled acd0: CDROM at ata1-master UDMA33 twed0: on twe0 twed0: 70910MB (145224064 sectors) SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! Mounting root from ufs:/dev/twed0s1a WARNING: / was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 20 files 1 WARNING: /var/spool was not properly dismounted /var/spool: mount pending error: blocks 100 files 19 /var/spool: superblock summary recomputed WARNING: /usr was not properly dismounted /usr: mount pending error: blocks 4 files 1 /usr: superblock summary recomputed WARN
/usr too small
Dear all, my system : kern.osreldate: 503001 FreeBSD 5.3-RELEASE #0: Tue Nov 9 13:34:27 CET 2004 I am running Freebsd on a laptop (Compaq Evo N800c). I have a winnt partition (8GB) I have a ufs partition (11GB) I have *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=38760 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=38760 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 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) start 63, size 16374897 (7995 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 15/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 16374960, size 22695120 (11081 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 15/ sector 63 my problem is that /usr is getting full. Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/ad0s2a507630 362568 10445278%/ devfs 1 1 0 100%/dev /dev/ad0s2f 3966294 2783584 86540876%/home /dev/ad0s2e 4737646 4222964 13567297%/usr /dev/ad0s2d 1012974 55104 876834 6%/var I could scratch the winnt partition because I can do most of my work now with FreeBSD, I still need java/openoffice though, but therfore I need some free space first. Is there a way to use the free space from the "scratched-winnt" partition to increase the /usr size ? Kind regards, Marc Plumet. ___ 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
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 ? Many motherboard BIOSes turn off integrated audio device if there is PCI audio adapter installed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
