Re: fsck unable to read disk sectors
It wouldn't be the BSD way to try to stop the user shooting themselves in the foot. And I agree too as it wouldn't be right for glabel to try to keep track of all possible uses for a volume and know whether each is present. That would be a typical Linux type solution. However, would it be too much for glabel to just know about UFS and tell the user to use tunefs instead if there appears to be a UFS filesystem present ? On 17 May 2010 23:32, Bernd Walter ti...@cicely7.cicely.de wrote: On Mon, May 17, 2010 at 10:54:17PM +0930, Matt Thyer wrote: On 12 May 2010 11:16, Bernd Walter ti...@cicely7.cicely.de wrote: On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote: i've posted a log here which is pretty self explanatory: http://pastebin.com/tn3NiDDW [snip] One of the typical problems users have is that they forget that adding a label takes one sector, so the labeled device is smaller. This is no problem if you create the filesystem on the labeled drive, but often enough people add the label after creating the filesystem. FreeBSD's utilities should be able to detect this situation and either correct the filesystem size or refuse to apply the label. How can this work? glabel doesn't know anything about volume contents - it just writes a label-sector and offers the remaning storage as a new volume. Result: Refusing is impossible. Changing UFS filesystem size isn't an easy task and the last sector is already lost when filesystem comes into game. Result: Too late. I think the only reasonable thing to be done is that fsck can speak up by checking the volume size with the filesystems size _after_ glabel has overwritten the last sector. -- B.Walter be...@bwct.de http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ffs_copyonwrite panics
On Tue, 18 May 2010, Roman Bogorodskiy wrote: Hi, I've been using -CURRENT last update in February for quite a long time and few weeks ago decided to finally update it. The update was quite unfortunate as system became very unstable: it just hangs few times a day and panics sometimes. Some things can be reproduced, some cannot. Reproducible ones: 1. background fsck always makes system hang 2. system crashes on operations with nullfs mounts (disabled that for now) The most annoying one is ffs_copyonwrite panic which I cannot reproduce. The thing is that if I will run 'startx' on it with some X apps it will panic just in few minutes. When I leave the box with nearly no stress (just use it as internet gateway for my laptop) it behaves a little better but will eventually crash in few hours anyway. This may have been my fault. Can you please update and let me know if it is resolved? There was both a deadlock and a copyonwrite panic as a result of the softupdates journaling import. I just fixed the deadlock today. Thanks, Jeff The even more annoying thing is that when I cannot save the dump, because when the system boots and runs 'savecore' it leads to fss_copyonwrite panic as well. The panic happens when about 90% complete (as seem via ctrl-t). Any ideas how to debug and get rid of this issue? System arch is amd64. I don't know what other details could be useful. Roman Bogorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
clangBSD build error
building clangBSD revision URL: http://svn.freebsd.org/base/projects/clangbsd Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 208300 Node Kind: directory Schedule: normal Last Changed Author: rdivacky Last Changed Rev: 208260 Last Changed Date: 2010-05-18 18:21:49 +0800 (Tue, 18 May 2010) with llvm-devel(r103179) on freebsd 8 stable amd64 according to clangBSD wiki failed with following message: make -j4 buildworld - ... /usr/src.svn/src/lib/libc/stdlib/malloc.c:1098:38: error: 'tls_model' attribute ignored static __thread arena_t *arenas_map TLS_MODEL; ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: # define TLS_MODEL __attribute__((tls_model(initial-exec))) ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:1103:38: error: 'tls_model' attribute ignored static __thread tcache_t *tcache_tls TLS_MODEL; ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: # define TLS_MODEL __attribute__((tls_model(initial-exec))) ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:1122:37: error: 'tls_model' attribute ignored static __thread bool mmap_unaligned TLS_MODEL; ^ /usr/src.svn/src/lib/libc/stdlib/malloc.c:240:37: note: instantiated from: # define TLS_MODEL __attribute__((tls_model(initial-exec))) -- it seems that clang does NOT support tls_model attribute, I'm not sure. Does anyone meet similar error ? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
I have gotten access to a system this morning, I booted and installed 8.0 RELEASE on it, it had no problems installing or afterwords booting the SMP kernel. So, is it possible there's a regression/issue in HEAD, or perhaps you have something in the PCIE expansion slots that cause it, the system I'm using has nothing. Otherwise its possible there is a hardware revision difference. Have you tried 8 REL ? I'm up and rebuilding a kernel on it right now. Jack On Tue, May 18, 2010 at 4:40 PM, Ryan Stone ryst...@gmail.com wrote: amd64 exhibits the same problem, except that it's not even polite and panics without even asking. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEAD can't bring up APs on Intel LC5528(Jasper Forest)
I've also tried a 6.1-derived kernel. I doubt that it was fixed for 8.0-RELEASE and then broken again on HEAD, but I'll check and be sure. My guess is that the problem is with the BIOS. We loaned our reference board to our BIOS vendor for development purposes and the BIOS they left on it is also unable to start APs. I think that my best bet to track this down is to see how the original Intel BIOS and the bad BIOS is configuring the hardware differently. I'm not very familiar with this stuff so I'm not sure what I should be looking at. MTRRs, I guess. What else? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Attilio Rao wrote: I have another problem where the bwn is fully recognized and wlan0 is created but the interface doesn't scan at all: # netstat -nil Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll bwn0 2290 Link#1 00:26:5e:64:be:750 0 0 0 0 0 # ifconfig wlan0 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:26:5e:64:be:75 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid channel 1 (2412 MHz 11b) country US authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 wme bintval 0 # kldstat Id Refs AddressSize Name 14 0x8010 90b9a8 kernel 21 0x80c22000 28a9abwn_v4_ucode.ko doing ifconfig wlan0 list scan ends up immediately without further output. The dmesg is here: http://www.freebsd.org/~attilio/dmesg-bwn0.diff I had a similar problem w/ a 4309. If you haven't solved this already, please check that the radio is actually enabled. some laptops have a button. some have a key sequence. many also have a BIOS setting. mine looked pretty much the same as yours to FreeBSD but just endlessly scanned the channels for a signal until i noticed that the radio was disabled in BIOS. tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
