Re: 5.3 - 5.4 breaks ATA (Intel ICH2)

2005-09-24 Thread Peter Jeremy
On Fri, 2005-Sep-23 22:52:09 -0400, Tim Howe wrote:
I've got several other Pentium 3-based machines running 5.4-RELEASE-p3
with a GENERIC kernel, and I have a 5.3 installer disk, so my strategy
was to do a minimal install of 5.3, then NFS mount /usr/src and /usr/obj
from my organizational build server and upgrade to 5.4 from there.

Did you reboot after the 5.3 install or do the upgrade whilst booted
from that install disk?

root filesystem.  Further investigation found that it wasn't able to
find the ATA HDD (master on ata0) at all, but could find the ATAPI CDROM
drive (master on ata0).

You shouldn't have two masters on ata0.  I hope that's a typo.

How far through the boot process do you get?  I gather the loader runs
successfully and loads the kernel but the kernel can't find ad0.  Does
it find the controller (ata0 or whatever)?

-- 
Peter Jeremy
___
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 - 5.4 breaks ATA (Intel ICH2)

2005-09-24 Thread Owe Jørgensen
I'm no expert on this, but I'd let that machine have it's own build  
environment instead of NFS importing it from a server.
It _does_ require more disk space, but in the long run, it might be for  
the better. If you _must_ export from server, then export only /usr/src  
and not /usr/obj


Owe Jørgensen

On Fri, 23 Sep 2005 22:52:09 -0400, Tim Howe  
[EMAIL PROTECTED] wrote:



I've got a machine here that I'm trying to install FreeBSD 5.4 on.  It's
identical (except for the hard drive) to another machine that I ran the
4.x series on for some time with no issues.

I've got several other Pentium 3-based machines running 5.4-RELEASE-p3
with a GENERIC kernel, and I have a 5.3 installer disk, so my strategy
was to do a minimal install of 5.3, then NFS mount /usr/src and /usr/obj
from my organizational build server and upgrade to 5.4 from there.

The 5.3 install went smoothly, make installkernel went smoothly, but
when I tried to reboot I got an error saying that it couldn't find the
root filesystem.  Further investigation found that it wasn't able to
find the ATA HDD (master on ata0) at all, but could find the ATAPI CDROM
drive (master on ata0).

I verified that the drive had not gone bad by again booting off the 5.3
installer disk, which found ad0 with no difficulty.  I then downloaded
the 5.4 mini-CD, which was unable to find ad0.  Finally, I swapped in
another hard drive with identical results.

Neither booting with ACPI disabled (didn't bother to check whether this
machine even has it) nor booting in safe mode helped at all.

I did happen to notice that when the 5.3 CD boots, there is a delay of
several seconds when probing ata0.  Could this be a timing issue with
regard to the controller?

The machine is a Gateway ATXSTF FED Pro M1000 with a 1GHz Pentium III
and 256MB of RAM.  It has an onboard Intel ICH2 UDMA100 controller.  The
first HDD I tried was a Western Digital Caviar 32500 2559.8MB drive, and
the second was a Caviar 24300 4311.9MB drive.

If necessary, I'm willing to build custom kernels for testing purposes
or to add debugging statements etc, if anyone can give me pointers in
the right direction.

Thanks in advance.





--
mvh,
Owe André Jørgensen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


geom_mirror and ggatec/d safe for filesystem replication?

2005-09-24 Thread Brian Candler
Consider the following scenario:

- Machine 1 has a UFS filesystem on a block device.
- It is mirrored to a block device on machine 2, using geom_mirror
  and ggatec/ggated
- Machine 2 mounts this filesystem read only.

My question is: is this last step safe?

When an update occurs on machine 1, certain disk blocks will change under
the nose of machine 2's mounts. Will all necessary caches be invalidated?
(e.g. block caches, inode caches) Or could this result in nasty behaviour,
up to and including panics?

If so, is there a safer or better way of performing real-time filesystem
replication?

Thanks,

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


Re: em(4) support for 82573 1000/PRO nic on 5.x [was: Re: em on 5.x]

2005-09-24 Thread Pertti Kosunen

Mike Tancsa wrote:


At 04:53 AM 21/09/2005, Pertti Kosunen wrote:

Do i need to do something special with gstripe when upgrading to 
RELENG_6 from RELENG_5?



Sorry, dont know, but a search through the archives might have the 
answer.  I suspect it wont be an issue 


Everything went fine even without reboot after make installkernel.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: timeout waiting for read

2005-09-24 Thread Patrick Bowen

Claus Guttesen wrote:


Hi.

Just upgraded to FreeBSD 6 beta5 (i386). During reboot I get this
message (in one line):

unknown: timeout waiting for read DRQunknown: timeout waiting for read
DRQSMP: AP CPU #1 Launched!

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

 

I had the same problem, and Søren Schmidt sent me this patch. It worked 
for me. If it works for you, be sure and send him a note saying thanks


Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
retrieving revision 1.71
diff -u -r1.71 ata-lowlevel.c
--- ata-lowlevel.c  14 Sep 2005 12:45:06 -  1.71
+++ ata-lowlevel.c  15 Sep 2005 07:35:41 -
@@ -278,7 +278,7 @@
   /* if read data get it */
   if (request-flags  ATA_R_READ) {
-   if (ata_wait(ch, atadev, (ATA_S_READY | ATA_S_DRQ))   0) {
+   if (ata_wait(ch, atadev, ATA_S_DRQ)  0) {
   device_printf(request-dev,
 timeout waiting for read DRQ\n);
   request-result = EIO;


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


lpt0 always busy

2005-09-24 Thread stanley jobson
hi,
i am now trying for weeks to get my lpt0 working without any success :(

i always get device busy (running lptcontrol, lptest,
open(/dev/lpt0)).  i found a lot of questions about this via google and
some hints too (e.g. excluding device ppi from kernel) but all this
didnt help :(

i should mention that my printer connected to lpt0 is a funny gdi
printer which only works under win98. so my idea was to use qemu to run
a emulated win98 to get my printer working - but therefore qemu needs to
be able to open /dev/lpt0 ...

finally i wrote a simple c prog which just calls open(/dev/lpt0) but it
also always fails with device busy :(

what are the requirements to successfully open lpt0 port (apart from
having connected a printer to it) ?

does fbsd expects a response from the printer (e.g. ready status)? maybe
my printer is not able to do this ... if so: what are possible
workarounds? could i convice the kernel that lpt0 is ready?

thx
regards,
stan

ps: i am running fbsd 5.4


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


Re: lpt0 always busy

2005-09-24 Thread Dan Ponte
On Sat, Sep 24, 2005 at 06:09:09PM +0200, stanley jobson [EMAIL PROTECTED] 
was witnessed plotting the following conspiracy:
 hi,
 i am now trying for weeks to get my lpt0 working without any success :(
 
 i always get device busy (running lptcontrol, lptest,
 open(/dev/lpt0)).  i found a lot of questions about this via google and
 some hints too (e.g. excluding device ppi from kernel) but all this
 didnt help :(
 
 i should mention that my printer connected to lpt0 is a funny gdi
 printer which only works under win98. so my idea was to use qemu to run
 a emulated win98 to get my printer working - but therefore qemu needs to
 be able to open /dev/lpt0 ...
 
 finally i wrote a simple c prog which just calls open(/dev/lpt0) but it
 also always fails with device busy :(
 
 what are the requirements to successfully open lpt0 port (apart from
 having connected a printer to it) ?
 
 does fbsd expects a response from the printer (e.g. ready status)? maybe
 my printer is not able to do this ... if so: what are possible
 workarounds? could i convice the kernel that lpt0 is ready?
 
 thx
 regards,
 stan
 
 ps: i am running fbsd 5.4
 
Usually, if you get device busy, it means that the printer is simply
not on or connected properly. Check your parallel cable.
-Dan
-- 
Dan Ponte
http://www.theamigan.net/
A great many people think they are thinking when they are merely
rearranging their prejudices.
-- William James
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Encrypt some services with ipsec

2005-09-24 Thread [EMAIL PROTECTED]

H all,

 I have two prodction servers with FreeBSD 5.4 (all security patches 
are applied). They running some services like dns, ssh, http, ftp, etc. 
But I woukd like to encrypt some services for some hosts with ipsec when 
it is accessed. For example:


 - DNS resolution: not encrypted.
 - DNS replication master-slave: encrypted by ipsec.
 - Telnet: encrypted by ipsec for some hosts. Deny for the rest.
 - SSH: not encrypted for some hosts, encryted by ipsec for the rest.
 - FTP: encrypted by ipsec.
 - HTTP: encrypted by ipsec.

 is it possible to encrypt only certains services under ipsec tunnel??

Thank you for your help.


--
CL Martinez
carlopmart {at} gmail {d0t} com
___
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 - 5.4 breaks ATA (Intel ICH2)

2005-09-24 Thread Tim Howe
Peter Jeremy [EMAIL PROTECTED] writes:

 Did you reboot after the 5.3 install or do the upgrade whilst booted
 from that install disk?

I rebooted into the freshly installed 5.3 system and it worked
perfectly.  The upgrade went fine also.  It was only upon booting into
the 5.4 kernel that I had problems.

  Further investigation found that it wasn't able to find the ATA HDD
  (master on ata0) at all, but could find the ATAPI CDROM drive
  (master on ata0).

 You shouldn't have two masters on ata0.  I hope that's a typo.

It is.  That should read CDROM drive (master on ata1).

 How far through the boot process do you get?  I gather the loader runs
 successfully and loads the kernel but the kernel can't find ad0.

That's correct.

 Does it find the controller (ata0 or whatever)?

I believe so.  I'm not near that machine presently, but I know it found
the ATA PCI controller because it was able to find the CDROM drive.  I
know it displayed a message saying ata0: something or other.  If it
displayed anything (not an error) does that mean that ata0 was found
then?

 - Tim

___
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 - 5.4 breaks ATA (Intel ICH2)

2005-09-24 Thread Tim Howe
Owe Jørgensen [EMAIL PROTECTED] writes:

 I'm no expert on this, but I'd let that machine have it's own build
 environment instead of NFS importing it from a server.

I'm not doing a separate build, just installing a prebuilt system.  The
machines are all Pentium IIIs and I'm using GENERIC kernels on all of
them.

 It _does_ require more disk space, but in the long run, it might be
 for the better. If you _must_ export from server, then export only
 /usr/src and not /usr/obj

I was following these instructions in the handbook:

 Secondly, it allows you to use NFS mounts to upgrade multiple machines
 on your network. If you have three machines, A, B and C that you want
 to upgrade, run make buildworld and make installworld on A. B and C
 should then NFS mount /usr/src and /usr/obj from A, and you can then
 run make installworld to install the results of the build on B and C.

-- 
Tim Howe
Software Engineer
Celebrity Resorts, Inc.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: geom_mirror and ggatec/d safe for filesystem replication?

2005-09-24 Thread Colin Farley

   I can't say if this config is safe because I don't have any exper   ieince 
with it. But, I can say that I use rsync to sync filesystems on
   two = boxes.  They are ftp servers running openbsd using carp for auto
   failo= ver.  The backup runs a script to sync a portion of it's
   filesyst= em with the master after checking to make sure it's still
   the backup. = The sync happens every 5 seconds over a Gbit private
   network between the t= wo.  The data that is being synced is
   normally fairly small. = ; Has been working very well in production
   for about 9 or 10 months.  = You might want to look into rsync as an
   alternative if it is practical for = the data you are wanting to
   replicate.



   Colin
   
   [EMAIL PROTECTED] wrote: --= ---

 To:= freebsd-stable@freebsd.org
 From: Brian Candler [EMAIL PROTECTED]= gt;
 Sent by: [EMAIL PROTECTED]
 Date: 09/24/2005 09:21A= M
 Subject: geom_mirror and ggatec/d safe for filesystem
 replication?
 Consider the following scenario:
 - Machine 1 has a UFS filesy= stem on a block device.
 - It is mirrored to a block device on machine 2,= using
 geom_mirror
  and ggatec/ggated
 - Machine 2 mounts this = filesystem read only.
 My question is: is this last step safe?
 When an update occurs on machine 1, certain disk blocks will change
 under the nose of machine 2's mounts. Will all necessary caches be
 invalidat= ed?
 (e.g. block caches, inode caches) Or could this result in nasty
 beha= viour,
 up to and including panics?
 If so, is there a safer or bet= ter way of performing real-time
 filesystem
 replication?
 Thanks,
 Brian Candler.
 _ __ 5F__= _
 freebsd-stable@freebsd.org mailing list
 [1]ht= tp://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscrib= e, send any mail to
 [EMAIL PROTECTED]
 
References

   1. file://localhost/tmp/3Dht___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD 4.10-RELEASE-p16 on ESX Server 2.5.1

2005-09-24 Thread Colin Farley

Thanks for your help, adding the two lines that you mentioned below fixed
the problem.

Thanks again,
Colin

[EMAIL PROTECTED] wrote: -


To: Colin Farley [EMAIL PROTECTED]
From: Tom Pepper [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
Date: 09/23/2005 05:27PM
cc: freebsd-stable@freebsd.org
Subject: Re: FreeBSD 4.10-RELEASE-p16 on ESX Server 2.5.1

vmware's virtual implementation of acpi collides with freebsd.  best
practice is to disable acpi altogether in the actual config file on
the host o/s for the VM by manually placing:

acpi.present = false
monitor_control.disable_apic = TRUE

in the whatever.vmx config file, and restarting the virtual machine.
read up on the vmware forums for some more information from yours
truly on trying to beat freebsd into running on ESX.  there's
additional problems you'll run into w/r/t crappy smbfs performance,
agent support, and some esoteric problems like nanosleep() calls
eating CPU instead of actually idling.

-t

On Sep 23, 2005, at 2:08 PM, Colin Farley wrote:


 I'm having a problem with my FreeBSD virtual machines on the
 production HP
 DL360 G4p servers we are using.  In test I used a weaker ESX box
 and never
 had the issue.  The problem is when rebooting the virtual machine
 it will
 sometimes hang at Waiting 15 seconds for SCSI devices to settle.
 This
 never happened on the test box and I have never encountered it before.
 Furthermore, if I use Vmotion (to move the virtual machine to a
 different
 ESX host) and bring the virtual machine up on another ESX server
 everything
 is fine and the virtual machine boots normally.  Because of this I
 figured
 that it was an ESX problem and decided to put a support ticket in with
 them.  They replied with this:

 The particular Waiting 15 seconds for SCSI devices to settle
 message you
 are getting with FreeBSD is a known issue with the FreeBSD system that
 occurs
 on physical systems as well.

 The work around for it is to edit your kernel config file with
 'OPTIONS
 SCSI_DELAY=1000' and to
 rebuild and install the new kernel

 To me this doesn't sound right, can anyone confirm?

 Thanks,
 Colin

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


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


Re: 5.3 - 5.4 breaks ATA (Intel ICH2)

2005-09-24 Thread Billy Newsom
Okay, Tim, I just reported the same bug in a previous post. So did 
Julian C. Dunn. I think this is an issue with some recent code changes 
in CVS...


See these threads:

critical BOOT failure updating to latest 5-Stable (5.4)
9/23/2005 12:07 AM

ATA lockup with 5.4-STABLE
9/21/2005 10:19 PM

I have privately emailed Mr. Dunn, and his problem seems a little 
different perhaps, but I see some similarities.  His system is an IBM 
(so is mine) and his uses the Intel PIIX4 ata chipset. Mine uses the 
PIIX3. Mine is by far the oldest, and yours is the newest system.


Of note maybe is that I was also using an older drive as you are, in my 
case an 8 or 9 GB Quantum Fireball.


Anyway, I count three systems that are normally boting with 5.3 or 5.4, 
and then the upgrade to the latest 5-Stable breaks the boot.


Perhaps you could test one of those identical machines with a simple 
hard disk swap? Just put the bad booting drive in a working system and 
see if the error is still there?


Has anyone checked the CVS repository for a possible change to the ATA 
detection or boot code?


Can you post your dmesg for 5.3 perhaps? BTW, you can boot that machine 
to the old kernel using the procedure


unload
load /boot/kernel.old/kernel
boot (or boot -v)

Do all of that with option 6 on the Boot Loader menu.

Thanks,
Billy

Tim Howe wrote:

I've got a machine here that I'm trying to install FreeBSD 5.4 on.  It's
identical (except for the hard drive) to another machine that I ran the
4.x series on for some time with no issues.

I've got several other Pentium 3-based machines running 5.4-RELEASE-p3
with a GENERIC kernel, and I have a 5.3 installer disk, so my strategy
was to do a minimal install of 5.3, then NFS mount /usr/src and /usr/obj
from my organizational build server and upgrade to 5.4 from there.

The 5.3 install went smoothly, make installkernel went smoothly, but
when I tried to reboot I got an error saying that it couldn't find the
root filesystem.  Further investigation found that it wasn't able to
find the ATA HDD (master on ata0) at all, but could find the ATAPI CDROM
drive (master on ata0).

I verified that the drive had not gone bad by again booting off the 5.3
installer disk, which found ad0 with no difficulty.  I then downloaded
the 5.4 mini-CD, which was unable to find ad0.  Finally, I swapped in
another hard drive with identical results.

Neither booting with ACPI disabled (didn't bother to check whether this
machine even has it) nor booting in safe mode helped at all.

I did happen to notice that when the 5.3 CD boots, there is a delay of
several seconds when probing ata0.  Could this be a timing issue with
regard to the controller?

The machine is a Gateway ATXSTF FED Pro M1000 with a 1GHz Pentium III
and 256MB of RAM.  It has an onboard Intel ICH2 UDMA100 controller.  The
first HDD I tried was a Western Digital Caviar 32500 2559.8MB drive, and
the second was a Caviar 24300 4311.9MB drive.

If necessary, I'm willing to build custom kernels for testing purposes
or to add debugging statements etc, if anyone can give me pointers in
the right direction.

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