Re: can not wake on lan after halt -p (or shutdown -p now) on releng_7 and releng_7_0

[Pyun YongHyeon]

On Sat, Oct 11, 2008 at 10:53:39AM +0800, David Adam wrote:
 > On Fri, 10 Oct 2008, Pyun YongHyeon wrote:
 > > On Fri, Oct 10, 2008 at 11:41:59AM +0800, David Adam wrote:
 > >  > On Mon, 6 Oct 2008, Georgi Iovchev wrote:
 > >  > > I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R
 > >  > > motherboard. Integrated network card is Realtek 8111B.
 > >  > > I can not wake the computer after I shutdown it from FreeBSD.
 > >  > > It is a dualboot system - windows xp and freebsd. If I shutdown the
 > >  > > computer from windows - later I can wake it up with magic packet. Even
 > >  > > if i shutdown the machine on the boot menu with the power button - 
 > > than
 > >  > > later I can wake on lan. The only situation where I CANNOT wake it is
 > >  > > when I shutdown the machine from freebsd (halt -p).
 > >  > > 
 > >  > > First I tested with 7.0-RELEASE-p5 amd64 (RELENG_7_0) and than I
 > >  > > upgraded to 7.1 PRERELASE amd64 (RELENG_7). I also tested with two
 > >  > > network cards - the integrated one Realtek 8111B and another one Intel
 > >  > > PRO1000PT PCI-E with WOL enabled.
 > >  > > 
 > >  > > With both nics and both freebsd versions the situation is the same -
 > >  > > after shutdown from bsd the computer is not able to wake on lan. The
 > >  > > indication on the switch port says that after shut down there is
 > >  > > active link.
 > >  > 
 > >  > I have a similar problem with an Intel SR1200 Pentium 3-class system, 
 > >  > using fxp(4) cards, although I haven't yet tried the `halt -p` command.
 > >  > 
 > > 
 > > fxp(4) should be taught to support WOL. Also note, not all fxp(4)
 > > hardwares support WOL.
 > 
 > Both of the fxp(4) interfaces on my development system certainly support 
 > WOL, so although I'm no kernel programmer I'd be more than happy to test 
 > patches or provide developer access.
 >  

I have a bunch of fxp cards donated by andre@ so I guess I'm one of
the best one that can experiment WOL capability on fxp(4). Before
that expeimentation I guess I have to read documentation of E100 to
write a WOL patch.
These days I'm somewaht overloaded for paid work and other network
drivers so I can't promise but I'll try if I manage to find spare
time.

-- 
Regards,
Pyun YongHyeon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: aclocal broken

[Jeremy Chadwick]

On Tue, Oct 14, 2008 at 12:49:35AM -0600, RYAN vAN GINNEKEN wrote:
> - Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> > On Mon, Oct 13, 2008 at 09:20:34PM -0600, RYAN vAN GINNEKEN wrote:
> > > Trying to install zoneminder port but getting this error 
> > > Using this version on Freebsd
> > > 
> > > FreeBSD pcbsd 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #42: Thu Sep 11 
> > > 09:07:25 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PCBSD  i386
> > > 
> > > cd . && /bin/sh 
> > > /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3/missing --run 
> > > autoheader
> > 
> > I have no such port on my system, and the FreeBSD web site agrees:
> > 
> > # cd /usr/ports/multimedia/zoneminder
> > /usr/ports/multimedia/zoneminder: No such file or directory.
> > # grep -i zoneminder /usr/ports/INDEX-7
> > #
> > 
> You are correct this is not a native FreeBSD port i downloaded this port from 
> here 
> http://www.zoneminder.com/forums/viewtopic.php?t=11965&postdays=0&postorder=asc&start=0

Which means you should ask the author of the port on that forum to
fix this problem.  :-)

> > This indicates whoever made the port Makefile is making use of the wrong
> > version of autoconf.  The following line should be added or changed in
> > the port Makefile:
> > 
> > USE_AUTOTOOLS=  autoconf:261:env
> I tried adding this to the Makefile but get this error instead
> USE_AUTOTOOLS=autoconf:261:env
> 
> make
> ===>  zoneminder-1.23.3,1 cannot install: unknown AUTOCONF version: 261.
> *** Error code 1

Ah, right -- we have no autoconf 2.61 port.  I believe ade@ could
comment on why that is.  You could try removing the USE_AUTOTOOLS line
altogether.

> So i tried to find out which version i was using and got this
> 
> autoconf --version

There are wrappers and other things for auto-tools on FreeBSD, so this
isn't a very good test.

I would recommend you talk to the author of this port and ask him to
update his suite/software to use autoconf 2.62.  Either way, this port
is not something in the FreeBSD ports tree; you'll need to talk to the
author.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: aclocal broken

[RYAN vAN GINNEKEN]

- Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 13, 2008 at 09:20:34PM -0600, RYAN vAN GINNEKEN wrote:
> > Trying to install zoneminder port but getting this error 
> > Using this version on Freebsd
> > 
> > FreeBSD pcbsd 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #42: Thu Sep 11 
> > 09:07:25 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PCBSD  i386
> > 
> > cd . && /bin/sh 
> > /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3/missing --run 
> > autoheader
> 
> I have no such port on my system, and the FreeBSD web site agrees:
> 
> # cd /usr/ports/multimedia/zoneminder
> /usr/ports/multimedia/zoneminder: No such file or directory.
> # grep -i zoneminder /usr/ports/INDEX-7
> #
> 
You are correct this is not a native FreeBSD port i downloaded this port from 
here 
http://www.zoneminder.com/forums/viewtopic.php?t=11965&postdays=0&postorder=asc&start=0

> http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/zoneminder
> 
> I'm not sure how much support you'll get here for that.
> 
> > aclocal.m4:14: error: this file was generated for autoconf 2.61.
> >   
> > You have another version of autoconf.  If you want to use that, 
> >   
> > you should regenerate the build system entirely.
> >   
> > aclocal.m4:14: the top level
> >   
> > autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 63   
> >   
> > autoheader-2.62: '/usr/local/bin/autom4te-2.62' failed with exit status: 63 
> >   
> 
> This indicates whoever made the port Makefile is making use of the wrong
> version of autoconf.  The following line should be added or changed in
> the port Makefile:
> 
> USE_AUTOTOOLS=autoconf:261:env
I tried adding this to the Makefile but get this error instead
USE_AUTOTOOLS=  autoconf:261:env

make
===>  zoneminder-1.23.3,1 cannot install: unknown AUTOCONF version: 261.
*** Error code 1

Stop in /usr/ports/multimedia/zoneminder.

So i tried to find out which version i was using and got this

autoconf --version
autoconf (GNU Autoconf) 2.62
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.


Next i tried changeing the line below and it was back to the exact same error 
above
USE_AUTOTOOLS=  autoconf:262:env


> 
> -- 
> | Jeremy Chadwickjdc at parodius.com |
> | Parodius Networking   http://www.parodius.com/ |
> | UNIX Systems Administrator  Mountain View, CA, USA |
> | Making life hard for others since 1977.  PGP: 4BD6C0CB |
> 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: can not wake on lan after halt -p (or shutdown -p now) on releng_7 and releng_7_0

[Pyun YongHyeon]

On Fri, Oct 10, 2008 at 11:43:26AM +0300, Georgi Iovchev wrote:
 > 
 > 
 > --
 > Friday, October 10, 2008, 4:20:58 AM:
 > 
 > > On Mon, Oct 06, 2008 at 06:13:34PM +0300, Georgi Iovchev wrote:
 >  >> Hello list
 >  >> 
 >  >> I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R
 >  >> motherboard. Integrated network card is Realtek 8111B.
 >  >> I can not wake the computer after I shutdown it from FreeBSD.
 >  >> It is a dualboot system - windows xp and freebsd. If I shutdown the
 >  >> computer from windows - later I can wake it up with magic packet. Even
 >  >> if i shutdown the machine on the boot menu with the power button - than
 >  >> later I can wake on lan. The only situation where I CANNOT wake it is
 >  >> when I shutdown the machine from freebsd (halt -p).
 >  >> 
 >  >> First I tested with 7.0-RELEASE-p5 amd64 (RELENG_7_0) and than I
 >  >> upgraded to 7.1 PRERELASE amd64 (RELENG_7). I also tested with two
 >  >> network cards - the integrated one Realtek 8111B and another one Intel
 >  >> PRO1000PT PCI-E with WOL enabled.
 >  >> 
 > 
 > > Don't know WOL issue of em(4) but re(4) should respond to WOL.
 > > 7.0-RELEASE had no support for WOL so RELENG_7 or 7.1-PRERELEASE
 > > should be used to experiment WOL.
 > Now I am using 7.1-prerelase
 > 
 >  >> With both nics and both freebsd versions the situation is the same -
 >  >> after shutdown from bsd the computer is not able to wake on lan. The
 > 
 > > Because you can wake up your sytem from Windows shutdown I think
 > > your BIOS is already configured to allow wakeup from WOL. Would
 > > you compare ethernet address of re(4) to Winwods? Have you tried to
 > > send Magic packets to FreeBSD box?
 > I have tried sending magic packets from another bsd machine. I am
 > using net/wol. I also tried to send magic packets from windows machine
 > using 3 different programs.
 > 
 > > You may also try suspend your box with acpiconf and resume from WOL.
 > I cant.
 > 
 > [EMAIL PROTECTED] ~]# acpiconf -s 5
 > acpiconf: invalid sleep type (5)
 > 
 > Actually I cant enter in any sleep state
 > [EMAIL PROTECTED] ~]# acpiconf -s 4
 > acpiconf: request sleep type (4) failed: Operation not supported
 > [EMAIL PROTECTED] ~]# acpiconf -s 3
 > acpiconf: request sleep type (3) failed: Operation not supported
 > [EMAIL PROTECTED] ~]# acpiconf -s 2
 > acpiconf: request sleep type (2) failed: Operation not supported
 > [EMAIL PROTECTED] ~]# acpiconf -s 1
 > acpiconf: request sleep type (1) failed: Operation not supported
 > 
 > I am using generic kernel with little modifications, (generally i have
 > commented many unused drivers - raid, if_) Acpi is in generic
 > kernel now.
 > 
 > I even tried to wake the machine with magic packet after shutdown -h.
 > But still no luck.
 > 
 > 
 >  >> indication on the switch port says that after shut down there is
 >  >> active link.
 >  >> 
 > 
 > > That indicates the controller is alive so it shall respond to WOL
 > > if it was correctly configured to receive WOL packets. Have you
 > > tried to send Magic packets to FreeBSD box?
 > 
 >  >> Here is some information after last update:
 >  >> 
 >  >> [EMAIL PROTECTED] ~]# uname -a
 >  >> FreeBSD backup.pulsar.bg 7.1-PRERELEASE FreeBSD
 >  >> 7.1-PRERELEASE #1: Mon Oct  6 17:01:26 EEST 2008
 >  >> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYCONF  amd64
 >  >> 
 >  >> [EMAIL PROTECTED] ~]# pciconf -lv
 >  >> ...
 >  >> [EMAIL PROTECTED]:3:0:0: class=0x02 card=0xe0001458
 >  >> chip=0x816810ec rev=0x01 hdr=0x00
 >  >> vendor = 'Realtek Semiconductor'
 >  >> device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
 >  >> class  = network
 >  >> subclass   = ethernet
 >  >> ...
 > 
 > > Show me dmesg output pertinent to re(4).
 > 
 > re0:  Ethernet> port 0xd000-0xd0ff mem 0xf200-0xf2000fff irq 17 at device 0.0 
 > on pci3
 > re0: turning off MSI enable bit.
 > re0: Chip rev. 0x3800
 > re0: MAC rev. 0x
 > miibus0:  on re0
 > rgephy0:  PHY 1 on miibus0
 > rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 > 1000baseT-FDX, auto
 > re0: Ethernet address: 00:1f:d0:24:19:e9
 > re0: [FILTER]
 > 

It looks like your chip is RTL8168B and I don't see any errors in
WOL related code of re(4). :-(
Can you check the resolved link speed/duplex of FreeBSD box after
shutdown?(You can enter to your switch menu and see the port
status.)
How about sending WOL packets over direct-connected UTP cable
without using switch?

-- 
Regards,
Pyun YongHyeon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: aclocal broken

[Jeremy Chadwick]

On Mon, Oct 13, 2008 at 09:20:34PM -0600, RYAN vAN GINNEKEN wrote:
> Trying to install zoneminder port but getting this error 
> Using this version on Freebsd
> 
> FreeBSD pcbsd 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #42: Thu Sep 11 09:07:25 
> EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PCBSD  i386
> 
> cd . && /bin/sh 
> /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3/missing --run 
> autoheader

I have no such port on my system, and the FreeBSD web site agrees:

# cd /usr/ports/multimedia/zoneminder
/usr/ports/multimedia/zoneminder: No such file or directory.
# grep -i zoneminder /usr/ports/INDEX-7
#

http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/zoneminder

I'm not sure how much support you'll get here for that.

> aclocal.m4:14: error: this file was generated for autoconf 2.61.  
> You have another version of autoconf.  If you want to use that,   
> you should regenerate the build system entirely.  
> aclocal.m4:14: the top level  
> autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 63 
> autoheader-2.62: '/usr/local/bin/autom4te-2.62' failed with exit status: 63   

This indicates whoever made the port Makefile is making use of the wrong
version of autoconf.  The following line should be added or changed in
the port Makefile:

USE_AUTOTOOLS=  autoconf:261:env

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

aclocal broken

[RYAN vAN GINNEKEN]

Trying to install zoneminder port but getting this error 
Using this version on Freebsd

FreeBSD pcbsd 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #42: Thu Sep 11 09:07:25 
EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PCBSD  i386

cd . && /bin/sh /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3/missing 
--run autoheader
aclocal.m4:14: error: this file was generated for autoconf 2.61.  
You have another version of autoconf.  If you want to use that,   
you should regenerate the build system entirely.  
aclocal.m4:14: the top level  
autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 63 
autoheader-2.62: '/usr/local/bin/autom4te-2.62' failed with exit status: 63   
*** Error code 1  

Stop in /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3.
*** Error code 1

Stop in /usr/ports/multimedia/zoneminder.

PLEASE HELP

Computer King & CaN Mail  -  Sales Service Hosting Backup

http://www.computerking.ca http://www.canmail.org

NEW!!! Custom Service Packages
Secure IMAP Email - Automated Remote Backups - Photo Blogs - Online Accounting 
Packages
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: can't see non-root writes to /dev/console

[Edwin Groothuis]

On Mon, Oct 13, 2008 at 06:23:01PM -0300, Carlos A. M. dos Santos wrote:
> The OpenBSD folks solved the permission issue along time ago(*) by
> means of a privilege separation feature. Take a look at
> 
>  http://www.openbsd.org/cgi-bin/cvsweb/xenocara/app/xconsole/
> 
> I will see if is possible to update the xconsole port in order to do
> the same. Is there any standard privilege separation framework on
> FreeBSD?

I haven't heard of it, but is it a framework on OpenBSD or is it
an approach?

Edwin

-- 
Edwin Groothuis Website: http://www.mavetju.org/
[EMAIL PROTECTED]   Weblog:  http://www.mavetju.org/weblog/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: can't see non-root writes to /dev/console

[Carlos A. M. dos Santos]

On Mon, Oct 13, 2008 at 6:05 PM, Edwin Groothuis <[EMAIL PROTECTED]> wrote:
> On Sun, Oct 12, 2008 at 10:23:53PM -0700, Jeremy Chadwick wrote:
>> > The ioctl call fails (EPERM) because only superuser can use TIOCCONS,
>> > regardless the ownership of the device. Using xterm with the "-C"
>> > argument works because xterm is installed with the setuid flag bit on.
>> > So the solution is "chmod +us  xconsole".
>>
>> Can someone security audit this program before blindly setuid-root'ing
>> it?
>
> Isn't xconsole not just the same values as /var/log/messages ?
>
> So information-leaking-wise it isn't a huge deal. Only the program
> itself is now the unknown.
>
> Edwin
> --
> Edwin Groothuis Website: http://www.mavetju.org/
> [EMAIL PROTECTED]   Weblog:  http://www.mavetju.org/weblog/

The OpenBSD folks solved the permission issue along time ago(*) by
means of a privilege separation feature. Take a look at

 http://www.openbsd.org/cgi-bin/cvsweb/xenocara/app/xconsole/

I will see if is possible to update the xconsole port in order to do
the same. Is there any standard privilege separation framework on
FreeBSD?

(*) http://openbsd.monkey.org/tech/200302/msg00064.html

-- 
cd /usr/ports/sysutils/life
make clean
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: can't see non-root writes to /dev/console

[Edwin Groothuis]

On Sun, Oct 12, 2008 at 10:23:53PM -0700, Jeremy Chadwick wrote:
> > The ioctl call fails (EPERM) because only superuser can use TIOCCONS,
> > regardless the ownership of the device. Using xterm with the "-C"
> > argument works because xterm is installed with the setuid flag bit on.
> > So the solution is "chmod +us  xconsole".
> 
> Can someone security audit this program before blindly setuid-root'ing
> it?

Isn't xconsole not just the same values as /var/log/messages ?

So information-leaking-wise it isn't a huge deal. Only the program
itself is now the unknown.

Edwin
-- 
Edwin Groothuis Website: http://www.mavetju.org/
[EMAIL PROTECTED]   Weblog:  http://www.mavetju.org/weblog/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Regression 7.0R -> 7-stable?

[John Baldwin]

On Monday 13 October 2008 03:09:46 am Gerrit Kühn wrote:
> On Fri, 10 Oct 2008 11:22:15 -0400 John Baldwin <[EMAIL PROTECTED]> wrote
> about Re: Regression 7.0R -> 7-stable?:
> 
> JB> Ok, can you run gdb on your kernel.debug and do
> JB> 'l *0x804608c0'
> 
> 0x804608c0 is in scheduler (/usr/src/sys/vm/vm_glue.c:670).
> 
> [...lines 665-674...]
> 
> 
> Hope this helps,
>   Gerrit

I was afraid of that, it basically means that it finished the entire boot 
process.  The next step is that init (pid 1) should be scheduled and try to 
execute.  You can maybe add some printf's to the code to start up init to see 
how far it gets.  The routine in question is 'start_init()' in 
sys/kern/init_main.c.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[Fabian Wenk]

Hello Jeremy

On 13.10.08 16:24, Jeremy Chadwick wrote:


Two items which are missed (sort of implied though): motherboard BIOS
version, and SCSI card BIOS version.


Ok, for my system this would be:

BIOS Information
Vendor: Phoenix Technologies Ltd.
Version: V1.06
Release Date: 08/01/2006


Adaptec SCSI BIOS v3.10.0


bye
Fabian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[Jeremy Chadwick]

On Mon, Oct 13, 2008 at 04:10:31PM +0200, Fabian Wenk wrote:
> Hello João
>
> On 13.10.08 13:43, JoaoBR wrote:
>> On Sunday 12 October 2008 06:57:11 Gary Jennejohn wrote:
>>> On Sat, 11 Oct 2008 23:51:18 +0200
>>>
>>> Fabian Wenk <[EMAIL PROTECTED]> wrote:
>
>>> > I do have a system with FreeBSD/amd64 6.3-RELEASE with 4 GB RAM
>>> > and an Adaptec 29160 Ultra160 SCSI adapter (ahc) with only a tape
>>> > drive connected. The disks are on an Areca RAID controller. Access
>>> > to the disks and the tape drive does work just fine without any
>>> > crashes.
>>>
>>> This is interesting because the 29160 is exactly the controller with
>>> which I had all my problems, but I was running it with disks only.
>
>> I guess his MB is not an AM2 socket 
>
> Right, my system board is a Tyan Thunder i7520 (S5360) server board (with 
> only one Xeon single core CPU). The Adaptec SCSI is a PCI and the Areca 
> RAID a PCIe controller.
>
> I guess some more facts are needed to track this down. Does it make 
> troubles with more then one CPU core and also more then 3.5 GB RAM 
> running on FreeBSD/amd64?
>
> If yes, then I'm not surprised that only a few people see this behavior.
>
> I think the following informations would be needed to narrow down the 
> affected environment:
>
> - FreeBSD version 6.x, 7.x or 8-CURRENT and i368 or amd64
> - make and model of system board
> - make and model of SCSI controller and which driver
> - on board SCSI controller or PCI / PCI-X / PCIe
> - device types connected to the SCSI, eg. disk, tape
> - number of cpu cores
> - amount of memory

Two items which are missed (sort of implied though): motherboard BIOS
version, and SCSI card BIOS version.

Let's try to make an effort to get some hardware and software stats from
other folks so we can determine what the commonality in all of this is.
I can keep track of this stuff if need be.

We know for sure at this point that some of the reported systems
experiencing this problem work fine on Linux (all memory seen, and no
data corruption), so that "sort of" clears the hardware of being bad or
buggy.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[Fabian Wenk]

Hello João

On 13.10.08 13:43, JoaoBR wrote:

On Sunday 12 October 2008 06:57:11 Gary Jennejohn wrote:

On Sat, 11 Oct 2008 23:51:18 +0200

Fabian Wenk <[EMAIL PROTECTED]> wrote:



> I do have a system with FreeBSD/amd64 6.3-RELEASE with 4 GB RAM
> and an Adaptec 29160 Ultra160 SCSI adapter (ahc) with only a tape
> drive connected. The disks are on an Areca RAID controller. Access
> to the disks and the tape drive does work just fine without any
> crashes.

This is interesting because the 29160 is exactly the controller with
which I had all my problems, but I was running it with disks only.


I guess his MB is not an AM2 socket 


Right, my system board is a Tyan Thunder i7520 (S5360) server 
board (with only one Xeon single core CPU). The Adaptec SCSI is a 
PCI and the Areca RAID a PCIe controller.


I guess some more facts are needed to track this down. Does it 
make troubles with more then one CPU core and also more then 3.5 
GB RAM running on FreeBSD/amd64?


If yes, then I'm not surprised that only a few people see this 
behavior.


I think the following informations would be needed to narrow down 
the affected environment:


- FreeBSD version 6.x, 7.x or 8-CURRENT and i368 or amd64
- make and model of system board
- make and model of SCSI controller and which driver
- on board SCSI controller or PCI / PCI-X / PCIe
- device types connected to the SCSI, eg. disk, tape
- number of cpu cores
- amount of memory

So for my system which works fine, this would be:

- FreeBSD/amd64 6.3-RELEASE
- Tyan Thunder i7520 (S5360)
- Adaptec 29160 Ultra160 SCSI adapter (ahc)
- PCI
- tape drive (DLT-8000)
- 1 cpu core
- 4 GB RAM


bye
Fabian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: very early kernel panic on system with 4GB mem

[Jeremy Chadwick]

On Mon, Oct 13, 2008 at 02:10:34PM +0100, Gianni Tedesco wrote:
> On Mon, 2008-10-13 at 13:20 +0100, Gianni Tedesco wrote:
> > Hi,
> > 
> > Tried booting FREEBSD7.0 Release #1 on a a dell poweredge SC1425. I get
> > an error 12: page fault in kernel mode (on write). Backtrace shows
> > garbage, a few calls in section _end... The fault is very early on,
> > literally copyright message, a message about memory above 4GB ignored
> > then crash. Incidentally this is a non-PAE build. Config attached below.
> > 
> > Couldn't find any other similar reports. I have remote gdb access to
> > machine so if you need further information let me know.
> > 
> > Thanks!
> > 
> > # #
> > # Kernel Configuration Files:
> > #
> > #
> > http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
> > #
> > # The handbook is also available locally in /usr/share/doc/handbook
> > # if you've installed the doc distribution, otherwise always see the
> > # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
> > # latest information.
> > #
> > # An exhaustive list of options and more detailed explanations of the
> > # device lines is also present in the ../../conf/NOTES and NOTES files.
> > # If you are in doubt as to the purpose or necessity of a line, check first
> > # in NOTES.
> > #
> > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.410 2004/08/01 19:37:34 markm Exp 
> > $
> > 
> > 
> > machine i386
> > #cpuI486_CPU
> > #cpuI586_CPU
> > cpu I686_CPU
> > ident   MANAGER
> > 
> > makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols
> > options KDB
> > options DDB
> > #makeoptionsCOPTFLAGS=-O0
> > makeoptions COPTFLAGS="-pipe"
> > #makeoptionsCOPTFLAGS="-pipe"
> > 
> > options MD_ROOT_SIZE=32000
> > 
> > hints "GENERIC.hints"
> > 
> > options PREEMPTION  # Enable kernel thread 
> > preemption
> > options UNIONFS
> > 
> > options SCHED_4BSD  # BSD scheduler
> > options INET# InterNETworking
> > #optionsINET6   # IPv6 communications protocols
> > options FFS # Berkeley Fast Filesystem
> > options SOFTUPDATES # Enable FFS soft updates support
> > #optionsUFS_ACL # Support for access control lists
> > #optionsUFS_DIRHASH # Improve performance on big directories
> > options MD_ROOT # MD is a potential root device
> > #optionsNFSCLIENT   # Network Filesystem Client
> > #optionsNFSSERVER   # Network Filesystem Server
> > #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT
> > #optionsMSDOSFS # MSDOS Filesystem
> > options CD9660  # ISO 9660 Filesystem
> > options PROCFS  # Process filesystem (requires PSEUDOFS)
> > options PSEUDOFS# Pseudo-filesystem framework
> > #optionsGEOM_GPT# GUID Partition Tables.
> > #optionsCOMPAT_43   # Compatible with BSD 4.3 [KEEP THIS!]
> > #optionsCOMPAT_FREEBSD4 # Compatible with FreeBSD4
> > options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
> > options KTRACE  # ktrace(1) support
> > options SYSVSHM # SYSV-style shared memory
> > options SYSVMSG # SYSV-style message queues
> > options SYSVSEM # SYSV-style semaphores
> > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time 
> > extensions
> > options KBD_INSTALL_CDEV# install a CDEV entry in /dev
> > options ADAPTIVE_GIANT  # Giant mutex is adaptive.
> > #optionsAHC_REG_PRETTY_PRINT# Print register bitfields in debug
> > # output.  Adds ~128k to driver.
> > #optionsAHD_REG_PRETTY_PRINT# Print register bitfields in debug
> > # output.  Adds ~215k to driver.
> > #optionsPREEMPTION
> > #optionsTCP_DROP_SYNFIN
> > #optionsPAE # Big RAM (>4Gb) extention
> > 
> > # To make an SMP kernel, the next two are needed
> > options SMP # Symmetric MultiProcessor Kernel
> > #optionsNETGRAPH
> > device  apic# I/O APIC
> > 
> > #optionsDEVICE_POLLING
> > #optionsHZ=2000
> > 
> > #
> > # Certain applications can grow to be larger than the 512M limit that
> > # FreeBSD initially imposes.  Below are some options to allow that
> > # limit to grow.  MAXDSIZ is the maximum that the limit can be set to,
> > # and the DFLDSIZ is the default value for the limit.  MAXSSIZ is the
> > # maximum that the stack limit can be set to.  You might want to set
> > # the default lower than the max, and explicitly set the maximum

Re: am2 MBs - 4g + SCSI wipes out root partition

[Jeremy Chadwick]

On Mon, Oct 13, 2008 at 07:39:44AM -0600, Scott Long wrote:
> JoaoBR wrote:
>> On Sunday 12 October 2008 14:10:36 Scott Long wrote:
>>
> I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS
> controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac
> driver) with a 5th generation RAID card with 8G of ram, both have no
> such corruption problems.  Providing this as a counter-example just to
> document some evidence of which products seem to work fine.
 Is your LSI SAS controller driven by mpt(4) or mfi(4)?
>>> I can personal vouch for MPT and MFI drivers working just fine with >4GB.
>>>
>>
>>
>> let narrow this a little bit, are you talking about AM2 sockets? 
>>
>> because on AM2 the MPT drv is faulty as AHC, AHD and AACD with => 4Gigs
>>
>>
>>
>
> Sounds to me like this is a problem either with AM2 systems, or an  
> infrastructure problem in the OS that is triggered by these AM2 systems.
> Either way, it's not a SCSI driver problem.

Fully acknowledged.  I'll add an entry to my Wiki describing this
compatibility problem, but it *will not* fall under the SCSI subsection.

It sounds as if there's an implementation/design problem either in
FreeBSD's hardware compatibility support for AM2 (probably something
very low-level) systems, or there is a bug with these Gigabyte boards;
it could be either, or possibly both.  It might work in Linux because,
for all we know, Linux may have workarounds in place for whatever the
problem may be.  We simply do not know at this point.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[Scott Long]

JoaoBR wrote:

On Sunday 12 October 2008 14:10:36 Scott Long wrote:


I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS
controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac
driver) with a 5th generation RAID card with 8G of ram, both have no
such corruption problems.  Providing this as a counter-example just to
document some evidence of which products seem to work fine.

Is your LSI SAS controller driven by mpt(4) or mfi(4)?

I can personal vouch for MPT and MFI drivers working just fine with >4GB.




let narrow this a little bit, are you talking about AM2 sockets? 


because on AM2 the MPT drv is faulty as AHC, AHD and AACD with => 4Gigs





Sounds to me like this is a problem either with AM2 systems, or an 
infrastructure problem in the OS that is triggered by these AM2 systems.

Either way, it's not a SCSI driver problem.

Scott

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: very early kernel panic on system with 4GB mem

[Gianni Tedesco]

On Mon, 2008-10-13 at 13:20 +0100, Gianni Tedesco wrote:
> Hi,
> 
> Tried booting FREEBSD7.0 Release #1 on a a dell poweredge SC1425. I get
> an error 12: page fault in kernel mode (on write). Backtrace shows
> garbage, a few calls in section _end... The fault is very early on,
> literally copyright message, a message about memory above 4GB ignored
> then crash. Incidentally this is a non-PAE build. Config attached below.
> 
> Couldn't find any other similar reports. I have remote gdb access to
> machine so if you need further information let me know.
> 
> Thanks!
> 
> # #
> # Kernel Configuration Files:
> #
> #
> http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
> #
> # The handbook is also available locally in /usr/share/doc/handbook
> # if you've installed the doc distribution, otherwise always see the
> # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
> # latest information.
> #
> # An exhaustive list of options and more detailed explanations of the
> # device lines is also present in the ../../conf/NOTES and NOTES files.
> # If you are in doubt as to the purpose or necessity of a line, check first
> # in NOTES.
> #
> # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.410 2004/08/01 19:37:34 markm Exp $
> 
> 
> machine   i386
> #cpu  I486_CPU
> #cpu  I586_CPU
> cpu   I686_CPU
> ident MANAGER
> 
> makeoptions   DEBUG=-g# Build kernel with gdb(1) debug symbols
> options   KDB
> options   DDB
> #makeoptions  COPTFLAGS=-O0
> makeoptions   COPTFLAGS="-pipe"
> #makeoptions  COPTFLAGS="-pipe"
> 
> options MD_ROOT_SIZE=32000
> 
> hints "GENERIC.hints"
> 
> options   PREEMPTION  # Enable kernel thread 
> preemption
> options   UNIONFS
> 
> options   SCHED_4BSD  # BSD scheduler
> options   INET# InterNETworking
> #options  INET6   # IPv6 communications protocols
> options   FFS # Berkeley Fast Filesystem
> options   SOFTUPDATES # Enable FFS soft updates support
> #options  UFS_ACL # Support for access control lists
> #options  UFS_DIRHASH # Improve performance on big directories
> options   MD_ROOT # MD is a potential root device
> #options  NFSCLIENT   # Network Filesystem Client
> #options  NFSSERVER   # Network Filesystem Server
> #options  NFS_ROOT# NFS usable as /, requires NFSCLIENT
> #options  MSDOSFS # MSDOS Filesystem
> options   CD9660  # ISO 9660 Filesystem
> options   PROCFS  # Process filesystem (requires PSEUDOFS)
> options   PSEUDOFS# Pseudo-filesystem framework
> #options  GEOM_GPT# GUID Partition Tables.
> #options  COMPAT_43   # Compatible with BSD 4.3 [KEEP THIS!]
> #options  COMPAT_FREEBSD4 # Compatible with FreeBSD4
> options   SCSI_DELAY=5000 # Delay (in ms) before probing SCSI
> options   KTRACE  # ktrace(1) support
> options   SYSVSHM # SYSV-style shared memory
> options   SYSVMSG # SYSV-style message queues
> options   SYSVSEM # SYSV-style semaphores
> options   _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time 
> extensions
> options   KBD_INSTALL_CDEV# install a CDEV entry in /dev
> options   ADAPTIVE_GIANT  # Giant mutex is adaptive.
> #options  AHC_REG_PRETTY_PRINT# Print register bitfields in debug
>   # output.  Adds ~128k to driver.
> #options  AHD_REG_PRETTY_PRINT# Print register bitfields in debug
>   # output.  Adds ~215k to driver.
> #options  PREEMPTION
> #options  TCP_DROP_SYNFIN
> #options  PAE # Big RAM (>4Gb) extention
> 
> # To make an SMP kernel, the next two are needed
> options   SMP # Symmetric MultiProcessor Kernel
> #options  NETGRAPH
> deviceapic# I/O APIC
> 
> #options  DEVICE_POLLING
> #options  HZ=2000
> 
> #
> # Certain applications can grow to be larger than the 512M limit that
> # FreeBSD initially imposes.  Below are some options to allow that
> # limit to grow.  MAXDSIZ is the maximum that the limit can be set to,
> # and the DFLDSIZ is the default value for the limit.  MAXSSIZ is the
> # maximum that the stack limit can be set to.  You might want to set
> # the default lower than the max, and explicitly set the maximum with
> # a shell command for processes that regularly exceed the limit like
> # INND.
> #
> options MAXSSIZ=(128UL*1024*1024)
> options MAXDSIZ=(2048UL*1024*1024)
> options DFLDSIZ=(1024UL*1024*1024)
> 

Re: am2 MBs - 4g + SCSI wipes out root partition

[JoaoBR]

On Monday 13 October 2008 10:50:54 Gary Jennejohn wrote:
> On Mon, 13 Oct 2008 09:35:10 -0200
>
> JoaoBR <[EMAIL PROTECTED]> wrote:
> > On Saturday 11 October 2008 07:13:16 Jeremy Chadwick wrote:
> > > It's a driver problem.  If you want to use SCSI then you'll have to
> > > limit memory to 3.5 GB.
>
> I probably should have written - it seems to be a problem with ahc.  In
> general SCSI seems to work, as Scott has recently documented.  But see
> below.
>
> > well indeed with less then 4G installed it works flawless, so the
> > difference I see is that former athln64 MBs had memory hole remap options
> > or when 4Gig installed they only gave 3.something to the OS even under
> > amd64 - this is NOT the case with the AM2 MBs which should support up to
> > 8/16Mb onboard but wth this amount freebsd amd64 does not even boot when
> > a scsi adaptor is installed
>
> I'm beginning to believe that it's motherboard/BIOS related and not a
> general problem with ahc or any other SCSI driver.  I can say that
> at least with my Gigabyte GA-M61P-S3 I observed data corruption with
> 4GB of memory installed and with the BIOS mapping a part of memory
> above 4GB.
>
> Forcing the kernel to use only 3.5GB solved the problem.
>

exactly, I have the same MB and Gigabytes support changed Ideas with me, even 
released a newer bios version but at the end they insisted that it is an OS 
issue since this problem does not appear with windows and fedora




-- 

João







A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[Tom Evans]

On Mon, 2008-10-13 at 09:37 -0200, JoaoBR wrote:
> On Saturday 11 October 2008 13:26:29 Adam McDougall wrote:
> > Jeremy Chadwick wrote:
> > > On Sat, Oct 11, 2008 at 04:45:29PM +0200, Gary Jennejohn wrote:
> > >> On Sat, 11 Oct 2008 03:13:16 -0700
> > >>
> > >> Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> > >>> On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote:
> >  On Fri, 10 Oct 2008 14:29:37 -0300
> > 
> >  JoaoBR <[EMAIL PROTECTED]> wrote:
> > > I tried MBs as Asus, Abit and Gigabyte all same result
> > >
> > > Same hardware with SATA works perfect
> > >
> > > Same hardware with scsi up to 3.5Gigs installed works perfect
> > >
> > > what calls my attention that all this MBs do not have the memroy hole
> > > remapping feature so the complete 4gigs are available what normally
> > > was not the case with amd64 Mbs for the Athlon 64 CPUs
> > >
> > > some has an opinion if this is a freebsd issue or MB falure or scsi
> > > drv problem?
> > 
> >  It's a driver problem.  If you want to use SCSI then you'll have to
> >  limit memory to 3.5 GB.
> > >>>
> > >>> What you're saying is that Adaptec and LSI Logic SCSI controllers
> > >>> behave badly (and can cause data loss) on amd64 systems which contain
> > >>> more than 3.5GB of RAM.  This is a very big claim.
> > >>>
> > >>> Have you talked to Scott Long about this?
> > >>>
> > >>> Please expand on this, and provide evidence or references.  I need to
> > >>> document this in my Wiki if it is indeed true.
> > >>
> > >> See the freebsd-scsi thread with Subject "data corruption with ahc
> > >> driver and 4GB of memory using a FBSD-8 64-bit installation?" from Wed,
> > >> 30 Jan 2008.
> > >>
> > >> This was for ahc, but the bit-rot which Scott mentions in his reply
> > >> might also apply to the LSI Logic controllers.
> > >>
> > >> Basically the driver doesn't correctly handle DMA above 4GB.  Since the
> > >> PCI hole gets mapped above 4GB it causes problems.  the (S)ATA drivers
> > >> don't seem to have this problem.
> > >
> > > Thank you -- this is the exact information I was looking for.
> > >
> > > I will update my Wiki page to reflect this quite major problem.
> >
> > I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS
> > controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac
> > driver) with a 5th generation RAID card with 8G of ram, both have no
> > such corruption problems.  Providing this as a counter-example just to
> > document some evidence of which products seem to work fine.
> > ___
> 
> 
> well this for sure is NOT a AM2 MB but any server MB which indeed run fine as 
> Tyans, SMs and others I guess
> 

It sounds like your issue is specific to certain motherboards and BIOS,
which would be non driver specific. Unless this is something that can be
worked around, I think the 'solution' is that with this hardware, you
are limited to 3.5 GB RAM. 

Perhaps different SoHo boards would provide different behaviour...

Cheers

Tom


signature.asc
Description: This is a digitally signed message part

Re: am2 MBs - 4g + SCSI wipes out root partition

[Gary Jennejohn]

On Mon, 13 Oct 2008 09:35:10 -0200
JoaoBR <[EMAIL PROTECTED]> wrote:

> On Saturday 11 October 2008 07:13:16 Jeremy Chadwick wrote:
> > It's a driver problem.  If you want to use SCSI then you'll have to limit
> > memory to 3.5 GB.
> 

I probably should have written - it seems to be a problem with ahc.  In
general SCSI seems to work, as Scott has recently documented.  But see
below.

> 
> well indeed with less then 4G installed it works flawless, so the difference 
> I 
> see is that former athln64 MBs had memory hole remap options or when 4Gig 
> installed they only gave 3.something to the OS even under amd64 - this is NOT 
> the case with the AM2 MBs which should support up to 8/16Mb onboard but wth 
> this amount freebsd amd64 does not even boot when a scsi adaptor is installed
> 

I'm beginning to believe that it's motherboard/BIOS related and not a
general problem with ahc or any other SCSI driver.  I can say that
at least with my Gigabyte GA-M61P-S3 I observed data corruption with
4GB of memory installed and with the BIOS mapping a part of memory
above 4GB.

Forcing the kernel to use only 3.5GB solved the problem.

---
Gary Jennejohn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[JoaoBR]

On Sunday 12 October 2008 14:10:36 Scott Long wrote:

> >> I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS
> >> controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac
> >> driver) with a 5th generation RAID card with 8G of ram, both have no
> >> such corruption problems.  Providing this as a counter-example just to
> >> document some evidence of which products seem to work fine.
> >
> > Is your LSI SAS controller driven by mpt(4) or mfi(4)?
>
> I can personal vouch for MPT and MFI drivers working just fine with >4GB.
>


let narrow this a little bit, are you talking about AM2 sockets? 

because on AM2 the MPT drv is faulty as AHC, AHD and AACD with => 4Gigs



-- 

João







A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[JoaoBR]

On Sunday 12 October 2008 06:57:11 Gary Jennejohn wrote:
> On Sat, 11 Oct 2008 23:51:18 +0200
>
> Fabian Wenk <[EMAIL PROTECTED]> wrote:
> > Hello Jeremy
> >
> > On 11.10.08 18:52, Jeremy Chadwick wrote:
> > > Could the problem be specific to certain firmware revisions on the
> > > cards?
> >
> > Some other idea, which versions of FreeBSD/amd64 are affected?
> > Only 8-CURRENT, or also 6.x- and/or 7.x-RELEASE?
> >
> > As far as I have seen from the reports, it does only happen with
> > more then 3.5 GB RAM and with SCSI disks.
> >
> > I do have a system with FreeBSD/amd64 6.3-RELEASE with 4 GB RAM
> > and an Adaptec 29160 Ultra160 SCSI adapter (ahc) with only a tape
> > drive connected. The disks are on an Areca RAID controller. Access
> > to the disks and the tape drive does work just fine without any
> > crashes.
>
> This is interesting because the 29160 is exactly the controller with
> which I had all my problems, but I was running it with disks only.
>
> Maybe Scott, or someone, has fixed it in the meantime?  I haven't
> tried to use the full 4 GB in my box since January since I can't
> afford data corruption.
>


I guess his MB is not an AM2 socket 


-- 

João







A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[JoaoBR]

On Saturday 11 October 2008 13:52:50 Jeremy Chadwick wrote:
> On Sat, Oct 11, 2008 at 12:26:29PM -0400, Adam McDougall wrote:
> > Jeremy Chadwick wrote:
> >> On Sat, Oct 11, 2008 at 04:45:29PM +0200, Gary Jennejohn wrote:
> >>> On Sat, 11 Oct 2008 03:13:16 -0700
> >>>
> >>> Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
>  On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote:
> > On Fri, 10 Oct 2008 14:29:37 -0300
> >
> > JoaoBR <[EMAIL PROTECTED]> wrote:
> >> I tried MBs as Asus, Abit and Gigabyte all same result
> >>
> >> Same hardware with SATA works perfect
> >>
> >> Same hardware with scsi up to 3.5Gigs installed works perfect
> >>
> >> what calls my attention that all this MBs do not have the
> >> memroy hole remapping feature so the complete 4gigs are
> >> available what normally was not the case with amd64 Mbs for the
> >> Athlon 64 CPUs
> >>
> >> some has an opinion if this is a freebsd issue or MB falure or
> >> scsi drv problem?
> >
> > It's a driver problem.  If you want to use SCSI then you'll have to
> > limit memory to 3.5 GB.
> 
>  What you're saying is that Adaptec and LSI Logic SCSI controllers
>  behave badly (and can cause data loss) on amd64 systems which contain
>  more than 3.5GB of RAM.  This is a very big claim.
> 
>  Have you talked to Scott Long about this?
> 
>  Please expand on this, and provide evidence or references.  I need to
>  document this in my Wiki if it is indeed true.
> >>>
> >>> See the freebsd-scsi thread with Subject "data corruption with ahc
> >>> driver and 4GB of memory using a FBSD-8 64-bit installation?" from Wed,
> >>> 30 Jan 2008.
> >>>
> >>> This was for ahc, but the bit-rot which Scott mentions in his reply
> >>> might also apply to the LSI Logic controllers.
> >>>
> >>> Basically the driver doesn't correctly handle DMA above 4GB.  Since the
> >>> PCI hole gets mapped above 4GB it causes problems.  the (S)ATA drivers
> >>> don't seem to have this problem.
> >>
> >> Thank you -- this is the exact information I was looking for.
> >>
> >> I will update my Wiki page to reflect this quite major problem.
> >
> > I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS
> > controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac
> > driver) with a 5th generation RAID card with 8G of ram, both have no
> > such corruption problems.  Providing this as a counter-example just to
> > document some evidence of which products seem to work fine.
>
> Is your LSI SAS controller driven by mpt(4) or mfi(4)?
>
> Let's break down what we know for sure at this point:
>
> aac(4) - not affected
> aha(4) - unknown
> ahb(4) - unknown
> ahc(4) - affected
> ahd(4) - unknown; no one answered the OP's question in the thread
> asr(4) - unknown
> ips(4) - unknown
> mpt(4) - not affected
> mfi(4) - unknown
> sym(4) - unknown
>
> Could the problem be specific to certain firmware revisions on the
> cards?

no, I tried different card versions

AHD has the same problem
AHC also
AAC also
MPT as well

this is true for AM2 MBs

but not true S939 and S940 MBs



-- 

João







A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[JoaoBR]

On Saturday 11 October 2008 13:26:29 Adam McDougall wrote:
> Jeremy Chadwick wrote:
> > On Sat, Oct 11, 2008 at 04:45:29PM +0200, Gary Jennejohn wrote:
> >> On Sat, 11 Oct 2008 03:13:16 -0700
> >>
> >> Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> >>> On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote:
>  On Fri, 10 Oct 2008 14:29:37 -0300
> 
>  JoaoBR <[EMAIL PROTECTED]> wrote:
> > I tried MBs as Asus, Abit and Gigabyte all same result
> >
> > Same hardware with SATA works perfect
> >
> > Same hardware with scsi up to 3.5Gigs installed works perfect
> >
> > what calls my attention that all this MBs do not have the memroy hole
> > remapping feature so the complete 4gigs are available what normally
> > was not the case with amd64 Mbs for the Athlon 64 CPUs
> >
> > some has an opinion if this is a freebsd issue or MB falure or scsi
> > drv problem?
> 
>  It's a driver problem.  If you want to use SCSI then you'll have to
>  limit memory to 3.5 GB.
> >>>
> >>> What you're saying is that Adaptec and LSI Logic SCSI controllers
> >>> behave badly (and can cause data loss) on amd64 systems which contain
> >>> more than 3.5GB of RAM.  This is a very big claim.
> >>>
> >>> Have you talked to Scott Long about this?
> >>>
> >>> Please expand on this, and provide evidence or references.  I need to
> >>> document this in my Wiki if it is indeed true.
> >>
> >> See the freebsd-scsi thread with Subject "data corruption with ahc
> >> driver and 4GB of memory using a FBSD-8 64-bit installation?" from Wed,
> >> 30 Jan 2008.
> >>
> >> This was for ahc, but the bit-rot which Scott mentions in his reply
> >> might also apply to the LSI Logic controllers.
> >>
> >> Basically the driver doesn't correctly handle DMA above 4GB.  Since the
> >> PCI hole gets mapped above 4GB it causes problems.  the (S)ATA drivers
> >> don't seem to have this problem.
> >
> > Thank you -- this is the exact information I was looking for.
> >
> > I will update my Wiki page to reflect this quite major problem.
>
> I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS
> controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac
> driver) with a 5th generation RAID card with 8G of ram, both have no
> such corruption problems.  Providing this as a counter-example just to
> document some evidence of which products seem to work fine.
> ___


well this for sure is NOT a AM2 MB but any server MB which indeed run fine as 
Tyans, SMs and others I guess




-- 

João







A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: am2 MBs - 4g + SCSI wipes out root partition

[JoaoBR]

On Saturday 11 October 2008 07:13:16 Jeremy Chadwick wrote:
> On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote:
> > On Fri, 10 Oct 2008 14:29:37 -0300
> >
> > JoaoBR <[EMAIL PROTECTED]> wrote:
> > > I tried MBs as Asus, Abit and Gigabyte all same result
> > >
> > > Same hardware with SATA works perfect
> > >
> > > Same hardware with scsi up to 3.5Gigs installed works perfect
> > >
> > > what calls my attention that all this MBs do not have the memroy hole
> > > remapping feature so the complete 4gigs are available what normally was
> > > not the case with amd64 Mbs for the Athlon 64 CPUs
> > >
> > > some has an opinion if this is a freebsd issue or MB falure or scsi drv
> > > problem?
> >
> > It's a driver problem.  If you want to use SCSI then you'll have to limit
> > memory to 3.5 GB.
>
> What you're saying is that Adaptec and LSI Logic SCSI controllers behave
> badly (and can cause data loss) on amd64 systems which contain more than
> 3.5GB of RAM.  This is a very big claim.
>
> Have you talked to Scott Long about this?
>
> Please expand on this, and provide evidence or references.  I need to
> document this in my Wiki if it is indeed true.


I have an Asus AM2 Mb which support ECC mem and at least with the Adaptec raid 
card (aacd) the problem does not happen (when ECC support enabled) I did 10x 
buildworld, ahc and mpt still same issue, first build cracks the data on 
da0s1a


>On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote:

> 
> It's a driver problem.  If you want to use SCSI then you'll have to limit
> memory to 3.5 GB.


well indeed with less then 4G installed it works flawless, so the difference I 
see is that former athln64 MBs had memory hole remap options or when 4Gig 
installed they only gave 3.something to the OS even under amd64 - this is NOT 
the case with the AM2 MBs which should support up to 8/16Mb onboard but wth 
this amount freebsd amd64 does not even boot when a scsi adaptor is installed



-- 

João







A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: sade root only

[Dominic Fandrey]

Rink Springer wrote:
> Hi Dominic,
> 
> On Mon, Oct 13, 2008 at 10:51:04AM +0200, Dominic Fandrey wrote:
>> Certain md and da devices (usb-sticks, encrypted images) on my
>> systems are owned by certain users, which I want to be able to use
>> sade to partition their private partitions, disks, whatever.
> 
> FWIW, you currently can't use sade and/or sysinstall to partition md(4)
> devices - I have a patch available to resolve this, but never got around
> to committing it.
> 
> If there is interest in it, let me know.
> 
> Regards,
> 

Well, since this is one of my intended uses, sure I'm interested.
However, I don't see how this could be useful to me without the
ability to run sade as a user.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: sade root only

[Rink Springer]

Hi Dominic,

On Mon, Oct 13, 2008 at 10:51:04AM +0200, Dominic Fandrey wrote:
> Certain md and da devices (usb-sticks, encrypted images) on my
> systems are owned by certain users, which I want to be able to use
> sade to partition their private partitions, disks, whatever.

FWIW, you currently can't use sade and/or sysinstall to partition md(4)
devices - I have a patch available to resolve this, but never got around
to committing it.

If there is interest in it, let me know.

Regards,

-- 
Rink P.W. Springer- http://rink.nu
"Anyway boys, this is America. Just because you get more votes doesn't
 mean you win." - Fox Mulder
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

sade root only

[Dominic Fandrey]

Certain md and da devices (usb-sticks, encrypted images) on my
systems are owned by certain users, which I want to be able to use
sade to partition their private partitions, disks, whatever.

Souldn't sade simply be blocked by the system if a user tries to
change something he/she is not entitled to? Why this block?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Regression 7.0R -> 7-stable?

[Gerrit Kühn]

On Fri, 10 Oct 2008 11:22:15 -0400 John Baldwin <[EMAIL PROTECTED]> wrote
about Re: Regression 7.0R -> 7-stable?:

JB> Ok, can you run gdb on your kernel.debug and do
JB> 'l *0x804608c0'

0x804608c0 is in scheduler (/usr/src/sys/vm/vm_glue.c:670).

[...lines 665-674...]


Hope this helps,
Gerrit
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"