headers
NetBSD source update | 1 Apr 2012 05:07
Picon

daily CVS update output


Updating src tree:
P src/sys/arch/hpcarm/conf/INSTALL_WZERO3
P src/sys/arch/hpcarm/conf/NETBOOKPRO
P src/sys/arch/hpcarm/conf/WZERO3
P src/sys/arch/hpcarm/conf/files.hpcarm
P src/sys/arch/hpcarm/conf/files.pxa2x0
P src/sys/arch/hpcarm/hpcarm/hpc_machdep.c
U src/sys/arch/hpcarm/hpcarm/kloader_machdep.c
U src/sys/arch/hpcarm/hpcarm/kloader_pxa2x0.S
P src/sys/arch/hpcarm/hpcarm/locore.S
P src/sys/arch/hpcarm/hpcarm/pxa2x0_hpc_machdep.c
P src/sys/arch/hpcarm/hpcarm/sa11x0_hpc_machdep.c
U src/sys/arch/hpcarm/include/kloader.h
P src/sys/arch/landisk/landisk/bus_dma.c
P src/sys/fs/v7fs/v7fs_vnops.c
P src/tests/lib/libc/sys/t_nanosleep.c
P src/usr.bin/make/make.1
cvs update: src/usr.sbin/tcpdump/Makefile is no longer in the repository

Updating xsrc tree:

Killing core files:

Running the SUP scanner:
SUP Scan for current starting at Sun Apr  1 03:02:58 2012
SUP Scan for current completed at Sun Apr  1 03:03:15 2012
SUP Scan for mirror starting at Sun Apr  1 03:03:15 2012
SUP Scan for mirror completed at Sun Apr  1 03:05:17 2012
(Continue reading)

Permalink | Reply | 0 comments |
headers
Manuel Bouyer | 1 Apr 2012 15:33

Re: powernow(4) not configured

On Tue, Mar 27, 2012 at 09:39:09PM +0300, Jukka Ruohonen wrote:
> On Tue, Mar 27, 2012 at 09:21:03PM +0300, Jukka Ruohonen wrote:
> > If you have time, you could add some of this information to the quirk table
> > in acpi_cpu.c (should be clear enough; but see pmf_get_platform(9)). Funnily
> > enough, the vendor(s) also put some copy-paste information to the "system"
> > fields in the DMI/SMBIOS, so you'd probably use the board or bios -fields.
> 
> Or can you try -current kernel?

Sorry but I won't be able to try in the next 2 weeks ...

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--
Permalink | Reply | 0 comments |
headers
NetBSD source update | 2 Apr 2012 05:27
Picon

daily CVS update output


Updating src tree:
P src/doc/3RDPARTY
P src/lib/libnpf/npf.c
P src/lib/libnpf/npf.h
P src/sys/kern/subr_kmem.c

Updating xsrc tree:

Killing core files:

Running the SUP scanner:
SUP Scan for current starting at Mon Apr  2 03:10:43 2012
SUP Scan for current completed at Mon Apr  2 03:11:20 2012
SUP Scan for mirror starting at Mon Apr  2 03:11:20 2012
SUP Scan for mirror completed at Mon Apr  2 03:12:52 2012

Updating release-4-0 src tree (netbsd-4-0):

Running the SUP scanner:
SUP Scan for release-4-0 starting at Mon Apr  2 03:15:50 2012
SUP Scan for release-4-0 completed at Mon Apr  2 03:15:57 2012

Updating release-5-0 src tree (netbsd-5-0):

Updating release-5-0 xsrc tree (netbsd-5-0):

Running the SUP scanner:
SUP Scan for release-5-0 starting at Mon Apr  2 03:22:37 2012
SUP Scan for release-5-0 completed at Mon Apr  2 03:22:46 2012
(Continue reading)

Permalink | Reply | 0 comments |
headers
Patrick Welche | 2 Apr 2012 14:50
Picon
Picon
Favicon

Re: gdb + sigtraps

On Mon, Mar 26, 2012 at 12:33:13PM -0400, Christos Zoulas wrote:
> On Mar 26,  5:11pm, prlw1 <at> cam.ac.uk (Patrick Welche) wrote:
> -- Subject: Re: gdb + sigtraps
> 
> | I do - I did a update build with head - maybe I need to clear obj out...
> | 
> | quark: {1} gdb /usr/bin/dig
> | GNU gdb (GDB) 7.3.1
> | ...
> | Reading symbols from /usr/bin/dig...(no debugging symbols found)...done.
> | (gdb) break main
> | Breakpoint 1 at 0x408b59
> | (gdb) run
> | Starting program: /usr/bin/dig 
> | 
> | Breakpoint 1, 0x0000000000408b59 in main ()
> | (gdb) c
> | Continuing.
> | 
> | Program received signal SIGTRAP, Trace/breakpoint trap.
> | 0x00007f7ff58390ba in _sys___kevent50 () from /usr/lib/libc.so.12
> | (gdb) 
> 
> Ok, I do too now. Good. Let me see what's wrong now. Hopefully I have
> my printf filled files still around.

I just compared an MP amd64 of 31st March with an MP i386 of 2nd April, using
the same gdb /usr/bin/dig example.

On run, they both receive a SIGTRAP
(Continue reading)

Permalink | Reply | 4 comments |
headers
Nicolas Joly | 2 Apr 2012 20:03
Picon
Picon
Favicon

ipmi(4) and negative temperatures


Hi,

I finally got some some to look into the envsys framework and ipmi
driver searching for the reason why it doesn't handle negative
temperatures.

To summarize, my new amd64 developpement workstation show bogus
warnmin and critmin limits for system temp (triggering a wrong event).

                      Current  CritMax  WarnMax  WarnMin  CritMin  Unit
       System Temp:    32.137   77.330   75.321  252.074  250.066 degC

At the same time, ipmitool report the corresponding values as negative
ones (-5.000 and -7.000), which make sense IMO.

System Temp      | 32.000     | degrees C  | ok    | -9.000    | -7.000    | -5.000    | 75.000    | 77.000    | 79.000

After a few debugging, i noted that ipmi(4) does not take into account
that sensors can use signed values and always use an unsigned 8bit for
calculations ...

With the attached patch, the system temp min limits looks ok, and all
other ones remains unchanged.

                      Current  CritMax  WarnMax  WarnMin  CritMin  Unit
       System Temp:    32.137   77.330   75.321   -5.021   -7.030 degC

Does this looks ok ?
Thanks.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Paul Goyette | 2 Apr 2012 20:17

Re: ipmi(4) and negative temperatures

Looks good to me...

On Mon, 2 Apr 2012, Nicolas Joly wrote:

>
> Hi,
>
> I finally got some some to look into the envsys framework and ipmi
> driver searching for the reason why it doesn't handle negative
> temperatures.
>
> To summarize, my new amd64 developpement workstation show bogus
> warnmin and critmin limits for system temp (triggering a wrong event).
>
>                      Current  CritMax  WarnMax  WarnMin  CritMin  Unit
>       System Temp:    32.137   77.330   75.321  252.074  250.066 degC
>
> At the same time, ipmitool report the corresponding values as negative
> ones (-5.000 and -7.000), which make sense IMO.
>
> System Temp      | 32.000     | degrees C  | ok    | -9.000    | -7.000    | -5.000    | 75.000    | 77.000    | 79.000
>
> After a few debugging, i noted that ipmi(4) does not take into account
> that sensors can use signed values and always use an unsigned 8bit for
> calculations ...
>
> With the attached patch, the system temp min limits looks ok, and all
> other ones remains unchanged.
>
>                      Current  CritMax  WarnMax  WarnMin  CritMin  Unit
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthias Drochner | 2 Apr 2012 20:55
Picon
Picon
Favicon

Re: ipmi(4) and negative temperatures


On Mon, 2 Apr 2012 20:03:14 +0200
Nicolas Joly <njoly <at> pasteur.fr> wrote:
> +     vs = (sign == 0x1 || sign == 0x2) ? (int8_t)v : v;

Shouldn't the 1's complement case be considered? Just a small
error, but for sake of accuracy:
if ((vs < 0) && (sign == 0x1))
        vs++;

best regards
Matthias

------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Kennen Sie schon unsere app? http://www.fz-juelich.de/app
Permalink | Reply | 3 comments |
headers
Joerg Sonnenberger | 3 Apr 2012 03:21
Picon

Re: ipmi(4) and negative temperatures

On Mon, Apr 02, 2012 at 08:55:10PM +0200, Matthias Drochner wrote:
> 
> On Mon, 2 Apr 2012 20:03:14 +0200
> Nicolas Joly <njoly <at> pasteur.fr> wrote:
> > +     vs = (sign == 0x1 || sign == 0x2) ? (int8_t)v : v;
> 
> Shouldn't the 1's complement case be considered? Just a small
> error, but for sake of accuracy:
> if ((vs < 0) && (sign == 0x1))
>         vs++;

Who is using one-complement?

Joerg
Permalink | Reply | 1 comment |
headers
NetBSD source update | 3 Apr 2012 05:06
Picon

daily CVS update output


Updating src tree:
P src/lib/libc/sys/sigtimedwait.2
P src/sbin/mount_nfs/mount_nfs.8
P src/sbin/mount_ptyfs/mount_ptyfs.c
P src/share/man/man9/pmf.9
P src/sys/arch/hppa/hppa/db_machdep.c
P src/sys/fs/msdosfs/msdosfs_vnops.c
P src/sys/sys/bootblock.h
P src/usr.sbin/isibootd/isibootd.c
P src/usr.sbin/makefs/cd9660/cd9660_eltorito.c

Updating xsrc tree:

Killing core files:

Running the SUP scanner:
SUP Scan for current starting at Tue Apr  3 03:02:33 2012
SUP Scan for current completed at Tue Apr  3 03:03:03 2012
SUP Scan for mirror starting at Tue Apr  3 03:03:03 2012
SUP Scan for mirror completed at Tue Apr  3 03:04:49 2012

Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  34397908 Apr  3 03:06 ls-lRA.gz
Permalink | Reply | 0 comments |
headers
Nicolas Joly | 3 Apr 2012 09:17
Picon
Picon
Favicon

Re: ipmi(4) and negative temperatures

On Mon, Apr 02, 2012 at 08:55:10PM +0200, Matthias Drochner wrote:
> 
> On Mon, 2 Apr 2012 20:03:14 +0200
> Nicolas Joly <njoly <at> pasteur.fr> wrote:
> > +     vs = (sign == 0x1 || sign == 0x2) ? (int8_t)v : v;
> 
> Shouldn't the 1's complement case be considered? Just a small
> error, but for sake of accuracy:
> if ((vs < 0) && (sign == 0x1))
>         vs++;

Yep. Will add, thanks.

--

-- 
Nicolas Joly

Projects and Developments in Bioinformatics
Institut Pasteur, Paris.
Permalink | Reply | 0 comments |

Gmane