Re: [PATCH] - ports/144792 (untar.c, Makefile) ports/archivers/untar

2010-03-19 Thread Garrett Cooper
On Fri, Mar 19, 2010 at 2:56 PM, Adam PAPAI  wrote:
> Hi,
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144792
>
> To remove the compile warnings I've added the required header files. (and a
> small fix for the Makefile NOMAN -> NO_MAN warning)
>
> http://www.wooh.hu/freebsd/untar.c.patch.txt
> http://www.wooh.hu/freebsd/Makefile.patch.txt

1. This belongs on ports@ because it doesn't deal with the software in
the base FreeBSD system.
2. You can attach the files in the email and they'll be properly
uuencoded into GNATS.
HTH,
-Garrett
___
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"


[PATCH] - ports/144792 (untar.c, Makefile) ports/archivers/untar

2010-03-19 Thread Adam PAPAI

Hi,

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144792

To remove the compile warnings I've added the required header files. 
(and a small fix for the Makefile NOMAN -> NO_MAN warning)


http://www.wooh.hu/freebsd/untar.c.patch.txt
http://www.wooh.hu/freebsd/Makefile.patch.txt

--
Adam PAPAI

___
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: ldd leaves the machine unresponsive

2010-03-19 Thread Anton Shterenlikht
On Thu, Mar 18, 2010 at 11:29:36AM -0400, jhell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 
> 
> On Wed, 17 Mar 2010 12:32, Anton Shterenlikht wrote:
> In Message-Id: <20100317163230.gj87...@mech-cluster241.men.bris.ac.uk>
> 
> > Just updated to ia64 r205248
> >
> > If my problem is due to my mis-configuration,
> > I apologise in advance.
> >
> > I run this shell script after each upgrade
> > and 'make delete-old-libs' to check
> > if any shared objects need to be rebuilt:
> >
> > 
> >
> > #!/bin/sh
> >
> > for file in `find /bin /sbin /usr/bin /usr/sbin /usr/lib /usr/libexec 
> > /usr/local -name "*"`
> > do
> >echo $file
> >ldd $file >> /root/ldd_results 2> /dev/zero
> > done
> >
> > 
> >
> 
> This will probably do closer to what you actually would want to look for.
> 
> Writing to /dev/zero ... I don't know never tried it since /dev/null is 
> usually the standard place to throw trash.
> 
> #!/bin/sh
> for file in `find /*bin /usr/*bin /usr/lib* /usr/local/*bin -type f` do
>   echo $file
>   ldd $file >>/root/ldd_results 2>/dev/null
> done
> 
> The problem with your script is that it finds most files that it can not 
> or is not useful to run ldd on and leaves you junk in return.
> 
> It might be more useful if you searched for dynamically linked ELF 
> binaries to run ldd against like the following.
> 
> === Script starts here ===
> #!/bin/sh
> 
> SEARCHPATH="/*bin /usr/*bin /usr/lib* /usr/local/*bin"
> 
> trap 'exit 1' 2
> 
> check_libs() {
> for spath in $SEARCHPATH; do
>  for ifelf in `find $spath -type f`; do
>  ldd `file $ifelf | grep dynamically | cut -f1 -d:`
>  done
> done
> }
> 
> check_libs 2>/dev/null
> === Script ends here ===
> 
> The above will find all type ELF * that are dynamically linked within the 
> SEARCHPATH variable and run ldd on them and print the results to stdout.
> 
> Obviously since you are going to have thousands of files being questioned, 
> stdout is not going to be useful.
> 
> So with the about stated:
> save the script to: checklibs.sh
> run with: "sh checklibs.sh >/root/checklibs_output"
> or: "script /root/checklibs_output checklibs.sh"
> 
> > After the upgrade to r205248, the script
> > freezes at seemingly random points.
> >
> 
> Unneeded disk usage & execution.
> 
> > I can still ssh to the machine (using keys), i.e.
> > I see the welcome message, but cannot get to the console prompt.
> 
> Of course... to many open files or processes in wait. SSH already has the 
> information it needs loaded into memory, that's why you can get sort-of-in
> 
> ZFS file-system perhaps ?

I've no ZFS.

I'm seeing very similar behaviour now with csup:

( I do csup -L2 /root/ports-supfile, where

# cat /root/ports-supfile
*default host=cvsup.uk.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=. delete use-rel-suffix compress

ports-all
# )

top(1) shows:

last pid:  1160;  load averages:  0.00,  0.06,  0.07
   up 0+00:10:53  15:05:52
81 processes:  3 running, 61 sleeping, 17 waiting
CPU 0:  0.0% user,  0.0% nice,  0.2% system,  0.0% interrupt, 99.8% idle
CPU 1:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
Mem: 23M Active, 19M Inact, 75M Wired, 136K Cache, 34M Buf, 5900M Free
Swap: 2780M Total, 2780M Free

  PIDUIDTHR PRI NICE   SIZERES STATE   C   TIME   WCPU COMMAND
   10  0  2 171 ki31 0K64K RUN 0  20:18 198.00% idle
   11  0 17 -48- 0K   544K WAIT0   0:01  0.00% intr
 1118   1001  1  960 12800K  3920K CPU00   0:00  0.00% top
4  0  1  -8- 0K32K -   1   0:00  0.00% g_down
 1158  0  4  -80 43672K  6296K biowr   0   0:00  0.00% csup


which stays in biowr state indefinitely.

I can issue kill -9 or kill -HUP from top(1),
which makes csup change state to STOP, but
nothing else happens.

As before, I can't log in from other terminals
and have to do a cold reset. I've reinstalled
on another disk, so not sure what's going on.

I think rm(1) is also extremely slow, but
maybe I'm imagining things.

many thanks
anton

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
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"


bsdtar(1) line_reader.c interesting code part - partial patch

2010-03-19 Thread Adam PAPAI

Hi,

Bug report sais:

http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/144786

bsdtar(1) doesn't support multi line matching or it is broken.

This patch [1] should solve it but not sure about this line in the 
original code:


if (lr->nullSeparator) {
...
}

This is  constant '\n' so this code part was never reached. This is why 
the '\n' separated lines were handled as one long line.


The line_reader.c header comment sais:

 * Read lines from file and do something with each one.  If option_null
 * is set, lines are terminated with zero bytes; otherwise, they're
 * terminated with newlines.

But where is the switch to change between \n and zero bytes? :)

[1]: http://www.wooh.hu/freebsd/line_reader.c.patch.txt


--
Adam PAPAI
___
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: newfs_msdos and DVD-RAM

2010-03-19 Thread Paul B Mahol
On Fri, Mar 19, 2010 at 7:11 PM, Fabian Keil
 wrote:
> Paul B Mahol  wrote:
>
>> FreeBSD 9.0 CURRENT panics when mounting file system created via
>> newfs_msdos on DVD-RAM disc.
>> Something to do about divide by zero.
>
> I recently had a similar problem with a 16GB iPod. I still haven't
> managed to actually mount it, but the patch below at least works
> around the panic.
>
> Does it work for you, too?

Obviously it will fix panic, but will not allow to mount. Zero value
should be handled
already much before. It looks the real bug is in newfs_msdos.

For some reason I did not managed to format DVD-RAM disc with FAT32 on WinXP,
it trashed disc completely so I was forced to blank it with dvd+rw-tools.
___
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: newfs_msdos and DVD-RAM

2010-03-19 Thread Fabian Keil
Paul B Mahol  wrote:

> FreeBSD 9.0 CURRENT panics when mounting file system created via
> newfs_msdos on DVD-RAM disc.
> Something to do about divide by zero.

I recently had a similar problem with a 16GB iPod. I still haven't
managed to actually mount it, but the patch below at least works
around the panic.

Does it work for you, too?

From 682d827f591d703e049274f495bf90f41b27c15f Mon Sep 17 00:00:00 2001
From: Fabian Keil 
Date: Fri, 19 Mar 2010 18:59:49 +0100
Subject: [PATCH] Work around weird msdosfs crash on mount. How can SecPerClust 
be zero here?

---
 sys/fs/msdosfs/msdosfs_vfsops.c |6 ++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/sys/fs/msdosfs/msdosfs_vfsops.c b/sys/fs/msdosfs/msdosfs_vfsops.c
index f229e91..22913c2 100644
--- a/sys/fs/msdosfs/msdosfs_vfsops.c
+++ b/sys/fs/msdosfs/msdosfs_vfsops.c
@@ -606,6 +606,12 @@ mountmsdosfs(struct vnode *devvp, struct mount *mp)
pmp->pm_firstcluster = pmp->pm_rootdirblk + pmp->pm_rootdirsize;
}
 
+   if (SecPerClust == 0) {
+   printf("SecPerClust is 0? When did this happen?\n");
+   error = EINVAL;
+   goto error_exit;
+   }
+
pmp->pm_maxcluster = (pmp->pm_HugeSectors - pmp->pm_firstcluster) /
SecPerClust + 1;
pmp->pm_fatsize = pmp->pm_FATsecs * DEV_BSIZE;  /* XXX not used? */
-- 
1.6.6.2

Fabian


signature.asc
Description: PGP signature


newfs_msdos and DVD-RAM

2010-03-19 Thread Paul B Mahol
Hi,

FreeBSD 9.0 CURRENT panics when mounting file system created via
newfs_msdos on DVD-RAM disc.
Something to do about divide by zero.
___
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 [HOSTAP] run(4) ralink usb wireless

2010-03-19 Thread Ganbold
PseudoCylon wrote:
> Can you show me output of followings? (I have only intel chips.)
>
> #kldstat | grep if_run (after loading the driver. no need to run it)
> #objdump -h /boot/kernel/if_run.ko | grep text
> #objdump --source /boot/kernel/if_run.ko | grep \>:
>   

Here it is:

rspro# uname -an
FreeBSD rspro.micom.mng.net 9.0-CURRENT FreeBSD 9.0-CURRENT #15
r205084M: Thu Mar 18 21:23:45 ULAT 2010
ts...@beastie.micom.mng.net:/usr/obj/mips/usr/mysrc/sys/RSPRO_AR71XX  mips
rspro# kldstat | grep if_run
 31 0xc7e9c000 d338 if_run.ko
rspro# objdump -h /boot/kernel/if_run.ko | grep text
  1 .text a0b0      0050  2**4
rspro# objdump --source /boot/kernel/if_run.ko | grep \>:
 :
0008 :
0010 :
00c0 :
01d8 :
0398 :
0460 :
0a40 :
0f94 :
107c :
10ac :
1160 :
11c4 :
12d0 :
1330 :
13dc :
144c :
14d4 :
179c :
183c :
1894 :
1914 :
1998 :
1a18 :
1b24 :
1bb8 :
1c84 :
1d10 :
1e08 :
1ecc :
207c :
215c :
2190 :
2264 :
239c :
2470 :
25a8 :
2844 :
2924 :
3980 :
3a10 :
3ba8 :
51b8 :
51e8 :
5488 :
55b4 :
59e0 :
5ac4 :
5d38 :
5e5c :
64a0 :
6a00 :
6a24 :
6a48 :
6a6c :
6a90 :
6ab4 :
6ad8 :
725c :
7540 :
7888 :
78f8 :
7a28 :
7c00 :
80dc :
960c :
96c0 :
9850 :
997c :
9a08 :
9bf4 :
rspro#


Ganbold


>
>
> AK
>
>   
>> Same.
>> 
>
>   
>> rspro# ifconfig wlan0 up
>>
>> rspro# Trap cause = 5 (address error (store) - kernel mode)
>> [ thread pid 0 tid 100047 ]
>> Stopped at  ieee80211_radiotap_vdetach+0x70:sh  v1,0(a0)
>> db> bt
>> Tracing pid 0 tid 100047 td 0xc0f1f260
>> db_trace_thread+30 (?,?,?,?) ra 80071160 sp c7ec9948 sz 24
>> 80071044+11c (0,?,,?) ra 80070b54 sp c7ec9960 sz 32
>> 800707c0+394 (?,?,?,?) ra 80070ce4 sp c7ec9980 sz 168
>> db_command_loop+78 (?,?,?,?) ra 800733b8 sp c7ec9a28 sz 24
>> 800732b0+108 (?,?,?,?) ra 801d8b1c sp c7ec9a40 sz 424
>> kdb_trap+10c (?,?,?,?) ra 803c2690 sp c7ec9be8 sz 32
>> trap+134c (?,?,?,?) ra 803b97c8 sp c7ec9c08 sz 176
>> MipsKernGenException+10c (c0f6a637,c0f721c8,c7ea7c04,e51) ra 802c95b8 sp
>> c7ec9cb8 sz 200
>> 802c95a8+10 (?,?,?,?) ra 0 sp c7ec9d80 sz 0
>> pid 0
>> db>
>> 
>
>   
>> Ganbold
>> 
>
>
>   __
> Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your 
> favourite sites. Download it now
> http://ca.toolbar.yahoo.com.
> ___
> 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"
>
>
>
>   


-- 
Her locks an ancient lady gave Her loving husband's life to save; And
men -- they honored so the dame -- Upon some stars bestowed her name.
But to our modern married fair, Who'd give their lords to save their
hair, No stellar recognition's given. There are not stars enough in heaven.
___
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: Panic @r205276 (Fatal trap 12: page fault while in kernel mode)

2010-03-19 Thread David Wolfskill
On Fri, Mar 19, 2010 at 01:09:11PM +, Rui Paulo wrote:
> ...
> > Do you all have either out-of-tree modules or modules that you did not
> > re-build when re-compiling your kernel?
> 
> I have in-tree modules, but I tried a clean build.

I corresponded with kmacy@ a bit yesterday.

Pending resolution, he's committed r205298 to "turn 205266 in to a no-op
until the problem can be properly diagnosed."

Peace,
david  (just built & booted FreeBSD 9.0-CURRENT #105 r205314 successfully)
-- 
David H. Wolfskill  da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpcVpQaMmorC.pgp
Description: PGP signature


Re: Panic @r205276 (Fatal trap 12: page fault while in kernel mode)

2010-03-19 Thread Rui Paulo

On 18 Mar 2010, at 22:15, K. Macy wrote:

> On Thu, Mar 18, 2010 at 1:38 PM, K. Macy  wrote:
 
 I have the same panic. I'll try to revert 205266.
>>> 
>>> Yes, 205266 is the culprit.
>> 
>> Try updating. I've made the change a no-op until I can track the problem 
>> down.
> 
> Do you all have either out-of-tree modules or modules that you did not
> re-build when re-compiling your kernel?

I have in-tree modules, but I tried a clean build.

--
Rui Paulo

___
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: recovery from terminated make installworld?

2010-03-19 Thread jhell


On Fri, 19 Mar 2010 02:28, Garrett Cooper wrote:
In Message-Id: <7d6fde3d1003182328w63c84053r2bbc3e05f4ec6...@mail.gmail.com>


On Thu, Mar 18, 2010 at 4:08 PM, krad  wrote:

On 18 March 2010 20:41, Freddie Cash  wrote:


On Thu, Mar 18, 2010 at 1:07 PM, Justin Hibbits 
wrote:



On Thu, Mar 18, 2010 at 4:03 PM, Anton Shterenlikht 
wrote:



I was in the single user mode doing 'make installworld'
when the system froze and I had to cold reboot.
Now in single user mode I get to:

Enter full pathname of shell or RETURN for /bin/sh:
/libexec/ld-elf.so.1: /lib/libc.so.7: invalid file format
/libexec/ld-elf.so.1: /lib/libc.so.7: invalid file format
Enter full pathname of shell or RETURN for /bin/sh:

Is there a way to recover?
Or do I have to reinstall from scratch?


Try /rescue/sh (or tcsh).  It's all statically linked, so you should be
able
to recover from there.

And if that doesn't work, try a LiveFS CD.


And, if all else fails, you can do a minimal install overtop.  You'll lose
all your /etc settings, but will get a bootable system again.

--
Freddie Cash
fjwc...@gmail.com
___
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"




easier and less risky to boot in on some form of live cd, mount all the fs
up under /mnt, set the DESTDIR=/mnt and continue the installworld


Yes, this is the easiest way to do things:

1. Boot live CD, USB, w/e.
2. mount all of your filesystems.
3. make -C $DESTDIR/usr/src installworld DESTDIR=$DESTDIR

No loss of data. But given that you've already done the reinstall, I
suppose there's no way to go back now :/...



make(1) and friends come on the live CD or USB stick images ?

AFAIR they didn't and it required a chroot(1) into the newly mounted 
environment and then running make(1) after invoking /rescue/sh to continue 
the install from a previously built world.


If so then the above would become:

chroot /mnt /rescue/sh
cd /usr/src
mergemaster -p
make installworld
mergemaster
sync ;sync ;reboot
--- continue whatever other steps from here...

The above assumes you have already installed your new kernel. If not then 
it should be obvious of the steps you have to take to get that done.


Regards,

--

 jhell

___
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"