Re: USB scanner not attached when connected after system startup]

[Marc Fonvieille]

On Wed, Dec 29, 2004 at 04:49:05PM +0100, Harald Weis wrote:
> 
> My scanner (EPSON PERFECTION 1650) is working alright if it is connected 
> before system startup.
> But when connected to the running system it doesn't get attached by usbd. I 
> can't find out from Handbook, manpages or mailing lists what could be the 
> reason.
>

I assume you followed the Image Scanner section in the Handbook.
Is usbd really running?  Are you using the default usbd.conf?

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

Re: -stable, uhci and the iRiver H320.

[Jean-Sébastien Pédron]

Alexey Zakirov wrote:
On Thu, 30 Dec 2004, [ISO-8859-1] Jean-S?bastien P?dron wrote:
I am now looking into purchasing an iRiver H320 player.  There was not a lot
of information turning up on Google in regard to people being successful, or
not, with this device under either Linux or FreeBSD, so I am now turning to
this list in hopes of finding a firsthand experience with this device under
FreeBSD.
If anyone can indeed confirm proper function under FreeBSD, it would be most
appreciated.
I have an iRiver H340 and it works well under Linux (USB 2.0). Under
FreeBSD, umass(4) has some issues and the player doesn't work currently
(tested with FreeBSD 5-STABLE and 6-CURRENT) but I'm sure it's just a
matter of time :-)
Works for me ;)
You're right, It works great at my office (6-CURRENT, 6 dec. 2004). I 
should have tested it here before...

--
Jean-Sébastien Pédron
http://www.dumbbell.fr/
PGP Key: http://www.dumbbell.fr/pgp/pubkey.asc


signature.asc
Description: OpenPGP digital signature

Re: Memory handling problem with FreeBSD 5.3?

[Christian R .]

On Wed, 29 Dec 2004 19:32:04 -0700, you wrote:

>Christian R. wrote:
>> I have installed FreeBSD 5.3-STABLE i386 on a new Dell PowerEdge 2850,
>> but it crashes under load like "make buildworld" with a "panic: page
>> fault".
>> 
>> The server has following configuration: 2x Intel Xeon 3.4 GHz (800 MHz
>> FSB), 6x 1 GB DDR2 ECC RAM and Perc 4e/Di (LSI Logic/amr driver).
>> 
>> After some days working on the problem, I think there is some problem
>> with handling the memory. The only way I have got the server to become
>> stable was by switching a special option in the Dell BIOS, which
>> limits the system memory to 256 MB.
>> 
>> I have tried to limit the memory to 4 GB by activating a spare memory
>> bank, but the server still crashes. Disabling HTT in BIOS and ACPI in
>> the loader also didn't solved the problem.
>> 
>> The kernel is compiled with SMP of course and PAE because of >4 GB
>> memory. I have removed all the unnecessary devices.
>> 
>> Dells own diagnostic tool couldn't find any hardware errors. The
>> special memory test also passed all tests. I have also tried with
>> memtest (http://www.memtest.org/) which either could find any memory
>> errors.
>> 
>> Has anyone an idea to a solution? Has anyone succeeded running FreeBSD
>> 5.3 on similar hardware?
>> 
>> Would it maybe be better to run the AMD64 version of FreeBSD 5.3? I
>> think the i386 version should be more stable?
>> 
>
>Upgrade to 5-STABLE.  I fixed these problems a few weeks ago.

I already have done that. I'm using RELENG_5 "5.3-STABLE FreeBSD
5.3-STABLE #0: Tue Dec 28 17:56:04 CET 2004"

Setting hw.physmem=3G at boot time has also made the system stable,
but I want to use all of the memory.

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

Re: Memory handling problem with FreeBSD 5.3?

[Christian R .]

On Thu, 30 Dec 2004 10:02:31 +0100, you wrote:

>>Upgrade to 5-STABLE.  I fixed these problems a few weeks ago.
>
>I already have done that. I'm using RELENG_5 "5.3-STABLE FreeBSD
>5.3-STABLE #0: Tue Dec 28 17:56:04 CET 2004"
>
>Setting hw.physmem=3D3G at boot time has also made the system stable,
>but I want to use all of the memory.

I have updated my source again with cvsup (RELENG_5), compiled the
source and installed the new world and kernel, but the server is still
unstable with >= 4GB.

Would the AMD64 version of FreeBSD 5.3 be a better choice?

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

Problem mounting root from CD9660 on 4.x

[Peter Jeremy]

I have a 4.10 system that I'm trying to build a bootable DVD for (for
disaster recovery purposes).  Whilst it boots OK, it won't mount root
from the native ATAPI device but only off the SCSI emulation.  Has
anyone else seen this?

The ISO image is built with
mkisofs -b boot/cdboot -no-emul-boot -r -J -V MY_RELENG_4_10 -o foo.iso 
/home/root

The relevant parts of the dmesg are:
atapci0:  port 0xfc00-0xfc0f at device 17.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
acd0: DVD-R  at ata1-master UDMA33
cd0 at ata1 bus 0 target 0 lun 0
cd0:  Removable CD-ROM SCSI-0 device 
cd0: 33.000MB/s transfers
cd0: cd present [2295104 x 2048 byte records]

All the following root specifications failed with ENXIO:
cd9660:/dev/acd0c
cd9660:acd0
cd9660:acd0c

but cd9660:cd0c worked.

-- 
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: Dummynet related panic in 5.3-RELEASE-p1

[Christian Laursen]

Gleb Smirnoff <[EMAIL PROTECTED]> writes:

> is it easy to reproduce it? Can you set debug.mpsafenet=0 and
> try to reproduce it?

It looks like debug.mpsafenet=0 make the crashes happen more frequently.

I now managed to get a crashdump.

kernel.debug and vmcore.1 are in the tarball available here:
http://hoegaarden.pil.dk/~cfsl/ns3-crashdump.tar.bz2

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

Strange networking problems after update 5.2.1->5.3

[Gerrit Kühn]

Hi folks,

I recently updated my old Compaq Armada 1500c from 5.2.1 to 5-stable. 5.2.1
worked fine, the update went without any noticable problem according to the
docs. 5.3 behaves well apart from a strange networking problem.
The notebook lives in a /16 subnet with a /16 netmask and has a 16bit
NE2000 PCMCIA-card (Longshine).

Things that do work:
- ping to hosts in /24
- ssh to hosts in /24
- nis with a server in /24

Things that don't work:
- ping from any host
- ping to hosts outside /24
- nfs
- query dns in /16
- connecting ntp server in /16

My networking setup hasn't changed, netmask and everything are ok (and
worked before the update). I don't use any kind of filtering.
Even a portscan from a machine in /24 connected to the same switch doesn't
show a single thing. The packets are received by the notebook (I see the
LED of the card flashing), but ping -f doesn't create any noticable irq
load. netstat doesn't show any running daemons, though e.g. ssh and lpd are
definitely running.

I definitely don't have a clue what is going on here... anyone else?


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

backward compat in /etc/fstab?

[Mipam]

Hi,

In 5.2 when you wished to make mdmfs in an /etc/fstab entry, you were 
actually using the compatibility mode for the old mount_mfs. It was not 
possible to set permissions and ownerships in an /etc/fstab entry.
So a workaround should be made then in /etc/rc.local
It this still the same in 5.3 or will the compatibility mode be removed so 
that proper permissions and ownership can be set in an fstab entry?
Bye,

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

Re: Memory handling problem with FreeBSD 5.3?

[Christian R .]

On Thu, 30 Dec 2004 12:02:16 +0100, you wrote:

>Would the AMD64 version of FreeBSD 5.3 be a better choice?

I have now installed the AMD64 version on the server. It has been
running stable now for some hours with alot of load and all the 6 GB
activated. It seems to be a problem with the i386 version og FreeBSD
5.3.

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

clock running fast

[Federico Galvez-Durand Besnard]

what do you have in :
/etc/ntp.conf

*alk-ml at prairienet.org* dtalk-ml at prairienet.org 

/Wed Dec 29 19:13:42 PST 2004/

   * Previous message: Multiple Vinum Problems Since Upgrade From 4.9
 To 4.10
 

   * Next message: Problem mounting root from CD9660 on 4.x
 

   * *Messages sorted by:* [ date ]
 

 [ thread ]
 

 [ subject ]
 

 [ author ]
 


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salutations --
I have an old board with an installation of STABLE whose time keeps 
running away.  ntpd is not helping.  I can manually set the time using 
ntpdate, and my ntpq queries look fine, yet the clock persists in 
running very fast (seems to be about 1.5x speed).  The BIOS clock 
remains correct, and the machine therefore has the correct time at each 
reboot, but quickly runs away.

Data points:
- - I have set kern.timecounter.hardware=TSC, and this has not helped. 
- - Two other hosts on the same network, using the same ntp server, do not 
have this problem.
- - This box did not display this behavior under FreeBSD 5.2. 
- - I have replaced the board on the problem box (with the same age 
and type), and the problem persists.
- - dmesg for this machine, an old Dell Optiplex 590, 
is below.

What other information might help diagnose the problem?
Thank you ... -d
- --
David Talkington
dtalk-ml at prairienet.org 


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

Re: how to remote update 4.10 -> 5.3?

[Igor Pokrovsky]

On Wed, Dec 29, 2004 at 04:38:23PM -0500, Paul Mather wrote:
> Palle Girgensohn wrote:
> 
> >I've tried the UPDATING instructions, both locally and remotely (the 
> >latter failed ;-). But really, everything has to be reinstalled, ports 
> >and the lot, so a new install is probably the best way...
> >
> 
> That's not so bad.  A reinstall means you can newfs your partitions as 
> UFS2 filesystems, which wouldn't be the case if you upgraded 4.10 in-place.

Are there any other advantages of UFS2 over UFS except maximum disk size?

-ip

-- 
Do whatever your enemies don't want you to do.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Memory handling problem with FreeBSD 5.3?

[Scott Long]

Christian R. wrote:
On Thu, 30 Dec 2004 12:02:16 +0100, you wrote:

Would the AMD64 version of FreeBSD 5.3 be a better choice?

I have now installed the AMD64 version on the server. It has been
running stable now for some hours with alot of load and all the 6 GB
activated. It seems to be a problem with the i386 version og FreeBSD
5.3.
i386 and amd64 have the exact same code for handling the needs of the
amr driver.  I'm a bit worried that one works for you while the other
doesn't; I extensively tested the code on both platforms with 8GB of
RAM.
Scott
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dump/restore with ufs2

[Ceri Davies]

On Tue, Dec 28, 2004 at 01:23:50PM -0500, Brian Szymanski wrote:
> When I run the following script, I get a warning message, and I'm
> wondering if it's ignorable or indicates there is a little more work to be
> done in getting dump/restore happy with ufs2...
> 
> $ cd /altroot
> $ dump -L -0 -a -f - /dev/$ROOT | restore -rf -
>   ...
> warning: ./.snap: File exists
> 
> Does this mean my snapshots are being overwritten on the target disk? And
> if so, that's a good thing, right?

That's just a warning that .snap already exists in the current directory
(which is because it gets created by newfs); the contents will remain
unaffected since snapshots are not dumped (I believe).

Ceri
-- 
Only two things are infinite, the universe and human stupidity, and I'm
not sure about the former.-- Einstein (attrib.)


pgpTWRsW6BDcy.pgp
Description: PGP signature

Re: icc8 failed on 4.10: Illegal instruction

[Igor Sysoev]

On Wed, 29 Dec 2004, Igor Sysoev wrote:

> On Tue, 28 Dec 2004, Kris Kennaway wrote:
>
> > On Wed, Dec 29, 2004 at 10:21:05AM +0300, Igor Sysoev wrote:
> >
> > > > > > > Then I installed the port and I ran 
> > > > > > > /usr/local/intel_cc_80/bin/icc,
> > > > > > > but it always failed with message "Illegal instruction".
> > > > > >
> > > > > > You forgot to mention what type of CPU you have.
> >
> > > > > Sorry, it was so obvious for me that is not CPU problem in this case,
> > > > > so I forgot to mention it. From dmesg:
> > > > >
> > > > > CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2679.56-MHz 686-class CPU)
> > > > >   Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
> >
> > > 0x80b13d7 <__intel_proc_init_ftzdaz+79>:stmxcsr (%esp,1)
> >
> > > Strange, the code in __intel_proc_init_ftzdaz looks like the right code.
> > > Right now I can not say from what extention "stmxcsr" come from.
> > > Here is the features from dmesg:
> > >   
> > > Features=0xbfebfbff > > MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> >
> > It's an SSE instruction, and you need to enable support for SSE in
> > your kernel.
>
> Thank you. The "options CPU_ENABLE_SSE" resolves the problem.
> I think it should be mention in the port for 4.x.
>
> However, it seems that 4.10's headers are not good for icc8:
>
> >cat q.c
> #include 
>
> >/usr/local/intel_cc_80/bin/icc q.c
> /usr/include/wchar.h(79): error: "__mbstate_t" has already been declared in 
> the current scope
>   } __mbstate_t;
> ^
>
> /usr/include/libio.h(463): error: identifier "__gnuc_va_list" is undefined
> _IO_va_list, int *__restrict) __THROW;
> ^
>
> /usr/include/libio.h(465): error: identifier "__gnuc_va_list" is undefined
>  _IO_va_list) __THROW;
>  ^
>
> /usr/include/stdio.h(307): error: identifier "__gnuc_va_list" is undefined
>  _G_va_list __arg) __THROW;
>  ^
>
> /usr/include/stdio.h(309): error: identifier "__gnuc_va_list" is undefined
>   extern int vprintf (__const char *__restrict __format, _G_va_list __arg)
>  ^
>
> /usr/include/stdio.h(313): error: identifier "__gnuc_va_list" is undefined
>  _G_va_list __arg) __THROW;
>  ^
>
> /usr/include/stdio.h(324): error: identifier "__gnuc_va_list" is undefined
>   __const char *__restrict __format, _G_va_list __arg)
>  ^
>
> compilation aborted for q.c (code 2)

The port maintainer Alexander Leidinger said that it is because
the linux_devtools port was installed, and he is right - just
after I deleted the linux_devtools, icc ran without problems.


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

Re: Memory handling problem with FreeBSD 5.3?

[Bosko Milekic]

On Thu, Dec 30, 2004 at 10:41:27AM -0700, Scott Long wrote:
> Christian R. wrote:
> >On Thu, 30 Dec 2004 12:02:16 +0100, you wrote:
> >
> >
> >>Would the AMD64 version of FreeBSD 5.3 be a better choice?
> >
> >
> >I have now installed the AMD64 version on the server. It has been
> >running stable now for some hours with alot of load and all the 6 GB
> >activated. It seems to be a problem with the i386 version og FreeBSD
> >5.3.
> >
> 
> i386 and amd64 have the exact same code for handling the needs of the
> amr driver.  I'm a bit worried that one works for you while the other
> doesn't; I extensively tested the code on both platforms with 8GB of
> RAM.
> 
> Scott

  Maybe I missed something in this thread, but what does it have to do
  with the amr driver?  The first thing that came to mind was something
  with PAE and how it affects PDE modifications.

  On i386, it might be worth trying these combinations:

  1. SMP, NO PAE.
  2. UP, PAE.
  3. UP, NO PAE.
  
  As we already know that "SMP, PAE" for you has problems.

--
Bosko Milekic
[EMAIL PROTECTED]
[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: Strange networking problems after update 5.2.1->5.3

[Robert Watson]

On Thu, 30 Dec 2004, Gerrit Kühn wrote:

> I recently updated my old Compaq Armada 1500c from 5.2.1 to 5-stable. 5.2.1
> worked fine, the update went without any noticable problem according to the
> docs. 5.3 behaves well apart from a strange networking problem.
> The notebook lives in a /16 subnet with a /16 netmask and has a 16bit
> NE2000 PCMCIA-card (Longshine).
> 
> Things that do work:
> - ping to hosts in /24
> - ssh to hosts in /24
> - nis with a server in /24
> 
> Things that don't work:
> - ping from any host
> - ping to hosts outside /24
> - nfs
> - query dns in /16
> - connecting ntp server in /16

The summary appears to be "known local things work, less local things
don't", although for the NFS instance it's unclear if that's local or not. 
This suggests a routing or ARP problem.

I think I'd begin diagnosing the problem by checking the routing and arp
configurations to make sure that the configuration seems alright (or at
least, to see if any symptoms are visible).  This would mean doing things
like:

  route -n get default
  route -n get {host in /24}
  route -n get {host in /16}

Check "arp -a" and make sure that the default gateway is what you expect,
and check to make sure it's hardware address is right.  You may want to
compare against what you see on another machine on the segment.  Make sure
you can ping the default gateway.

Next, I'd get out a packet sniffer and look for on-the-wire problems -- in
particular, to make sure that packets destined for non-local destinations
are getting stamped with the right destination hardware address (that of
the right default gateway).  I'd load up a sniffer on the remote system
and see if the problem is that your outgoing traffic doesn't get there, or
if it's the return traffic that's failing to be properly received.  I'd
use the sniffer also to inspect the return traffic and make sure it's what
is expected.

Somewhere during all of this, you will probably find the broken bit --
packets missing at some step, the wrong address, or the like.  If you find
anything that isn't fixed via a configuration change (i.e., failed
checksums, no way to explain the address being put in the packet, etc),
let us know.

Robert N M Watson

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

Re: how to remote update 4.10 -> 5.3?

[Palle Girgensohn]

--On torsdag, december 30, 2004 20.36.56 +0300 Igor Pokrovsky 
<[EMAIL PROTECTED]> wrote:

On Wed, Dec 29, 2004 at 04:38:23PM -0500, Paul Mather wrote:
Palle Girgensohn wrote:
> I've tried the UPDATING instructions, both locally and remotely (the
> latter failed ;-). But really, everything has to be reinstalled, ports
> and the lot, so a new install is probably the best way...
>
That's not so bad.  A reinstall means you can newfs your partitions as
UFS2 filesystems, which wouldn't be the case if you upgraded 4.10
in-place.
Are there any other advantages of UFS2 over UFS except maximum disk size?
acl -- access control lists
mac -- Mandatory Access Control
haven't used them yet, though.
/Palle
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Memory handling problem with FreeBSD 5.3?

[Scott Long]

Bosko Milekic wrote:
On Thu, Dec 30, 2004 at 10:41:27AM -0700, Scott Long wrote:
Christian R. wrote:
On Thu, 30 Dec 2004 12:02:16 +0100, you wrote:

Would the AMD64 version of FreeBSD 5.3 be a better choice?

I have now installed the AMD64 version on the server. It has been
running stable now for some hours with alot of load and all the 6 GB
activated. It seems to be a problem with the i386 version og FreeBSD
5.3.
i386 and amd64 have the exact same code for handling the needs of the
amr driver.  I'm a bit worried that one works for you while the other
doesn't; I extensively tested the code on both platforms with 8GB of
RAM.
Scott

  Maybe I missed something in this thread, but what does it have to do
  with the amr driver?  The first thing that came to mind was something
  with PAE and how it affects PDE modifications.
  On i386, it might be worth trying these combinations:
  1. SMP, NO PAE.
  2. UP, PAE.
  3. UP, NO PAE.
  
  As we already know that "SMP, PAE" for you has problems.

Bounce buffers were horribly broken in 5.3-RELEASE for amd64 and i386,
and the amr driver itself was unreliable in using them even when they
worked (the amr driver cannot do 64-bit S/G right now).  I fixed all of
this stuff a few weeks ago.  I tested all of this extensively under PAE,
but you're correct that this particular problem could very well be
related to pmap problems specific to i386.
Scott
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to remote update 4.10 -> 5.3?

[John-Mark Gurney]

Igor Pokrovsky wrote this message on Thu, Dec 30, 2004 at 20:36 +0300:
> > That's not so bad.  A reinstall means you can newfs your partitions as 
> > UFS2 filesystems, which wouldn't be the case if you upgraded 4.10 in-place.
> 
> Are there any other advantages of UFS2 over UFS except maximum disk size?

faster fsck times due to not all inodes are allocated at fs creation
time...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 "All that I will do, has been done, All that I have, has not."
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clock running fast

[David Talkington]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Federico Galvez-Durand Besnard wrote:
what do you have in :
/etc/ntp.conf
Only:
server 		time.u.washington.edu
server  127.127.1.0 
fudge   127.127.1.0 stratum 10

Command line:
/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \
- -f /var/db/ntpd.drift
Thank you ... -d

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salutations --
I have an old board with an installation of STABLE whose time keeps running 
away.  ntpd is not helping.  I can manually set the time using ntpdate, and my 
ntpq queries look fine, yet the clock persists in running very fast (seems to 
be about 1.5x speed).  The BIOS clock remains correct, and the machine 
therefore has the correct time at each reboot, but quickly runs away.

Data points:
- - I have set kern.timecounter.hardware=TSC, and this has not helped. - - Two 
other hosts on the same network, using the same ntp server, do not have this 
problem.
- - This box did not display this behavior under FreeBSD 5.2. - - I have 
replaced the board on the problem box (with the same age and type), and the 
problem persists.
- - dmesg for this machine, an old Dell Optiplex 590, is below.

What other information might help diagnose the problem?
Thank you ... -d
- --
David Talkington
dtalk-ml at prairienet.org 



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

- -- 
David Talkington
Computing and Communications
University of Washington
206-543-2144
- --
[EMAIL PROTECTED]
- --
PGP key: http://staff.washington.edu/dtalk/004B8F8B.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFB1FN55FKhdwBLj4sRAknTAJ9Wq/I64DpzBoblMmH2JMl2UR08NgCgkLuL
qlB7DOSkWlOmR2OLZ32O1NA=
=8B5z
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

USB flash not working anymore

[Peter Radcliffe]

I'm running FreeBSD 4-STABLE from Dec 28 on an IBM X30 laptop.

I'm having increasingly worse USB problems as time goes on. Nothing
that I try new works and various older devices that I bought
specificly because they were supported and worked fine for years now
do not work.

My SanDisk CF reader (SDDR-31) used to work perfectly, now gives me;

  umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 2
  umass0: Get Max Lun not supported (STALLED)
  usb_block_allocmem: in interrupt context, size=4096
  da0 at umass-sim0 bus 0 target 0 lun 0
  da0:  Removable Direct Access SCSI-2 device 
  da0: 650KB/s transfers
  da0: 489MB (1001953 512 byte sectors: 64H 32S/T 489C)

here I try to mount hte filesystem or use mtools;

  usb_block_allocmem: in interrupt context, size=4096
  usb_block_allocmem: in interrupt context, size=4096
  usb_block_allocmem: in interrupt context, size=4096
  usb_block_allocmem: in interrupt context, size=65536
  usb_block_allocmem: in interrupt context, failed
  umass0: BBB reset failed, STALLED
  usb_block_allocmem: in interrupt context, size=65536
  usb_block_allocmem: in interrupt context, failed
  umass0: BBB reset failed, STALLED
  usb_block_allocmem: in interrupt context, size=65536
  usb_block_allocmem: in interrupt context, failed
  umass0: BBB reset failed, STALLED

and it hangs. Sometimes the process hangs, sometimes the machine hangs.


My crucial gizmo flashdrive gives me;

  umass0: Crucial Gizmo, rev 2.00/0.01, addr 2
  usb_block_allocmem: in interrupt context, size=4096
  da0 at umass-sim0 bus 0 target 0 lun 0
  da0:  Fixed Direct Access SCSI-CCS device 
  da0: 650KB/s transfers
  da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C)
[mount the drive]
  usb_block_allocmem: in interrupt context, size=4096
  usb_block_allocmem: in interrupt context, size=4096
[repeated about 30 times]
  usb_block_allocmem: in interrupt context, size=4096
  usb_block_allocmem: in interrupt context, size=4096
  umass0: at uhub1 port 1 (addr 2) disconnected
  (da0:umass-sim0:0:0:0): lost device
  (da0:umass-sim0:0:0:0): removing device entry
  umass0: detached

This at least works when mounted but mtools will hang hard.

The Iomega mini flashdrive hard hung my machine so I have no logs.


Anyone seen these problems before or working on usb in 4.x ? I'll do
what I can to help debugging...

Thanks,
P.

-- 
pir

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

Re: clock running fast

[Brooks Davis]

[Please don't top post].

On Thu, Dec 30, 2004 at 11:13:55AM -0800, David Talkington wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Federico Galvez-Durand Besnard wrote:
> 
> >what do you have in :
> >/etc/ntp.conf
> 
> Only:
> 
> servertime.u.washington.edu
> server  127.127.1.0 
> fudge   127.127.1.0 stratum 10
> 
> 
> Command line:
> 
> /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \
> - -f /var/db/ntpd.drift

It's generally recommended that you never trust your own clock since
it's completely crap as time sources go.  It's also recommended that you
use at least 5 time sources to avoid problems with bad clocks.

-- Brooks

> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >
> >Salutations --
> >
> >I have an old board with an installation of STABLE whose time keeps 
> >running away.  ntpd is not helping.  I can manually set the time using 
> >ntpdate, and my ntpq queries look fine, yet the clock persists in running 
> >very fast (seems to be about 1.5x speed).  The BIOS clock remains correct, 
> >and the machine therefore has the correct time at each reboot, but quickly 
> >runs away.
> >
> >Data points:
> >
> >- - I have set kern.timecounter.hardware=TSC, and this has not helped. - - 
> >Two other hosts on the same network, using the same ntp server, do not 
> >have this problem.
> >- - This box did not display this behavior under FreeBSD 5.2. - - I have 
> >replaced the board on the problem box (with the same age and type), and 
> >the problem persists.
> >- - dmesg for this machine, an old Dell Optiplex 590, is below.
> >
> >What other information might help diagnose the problem?
> >
> >Thank you ... -d
> >
> >- --
> >David Talkington
> >dtalk-ml at prairienet.org 
> >
> >
> >
> >
> >___
> >freebsd-stable@freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> >To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> >
> >
> 
> - -- 
> David Talkington
> Computing and Communications
> University of Washington
> 206-543-2144
> - --
> [EMAIL PROTECTED]
> - --
> PGP key: http://staff.washington.edu/dtalk/004B8F8B.asc
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.6 (FreeBSD)
> 
> iD8DBQFB1FN55FKhdwBLj4sRAknTAJ9Wq/I64DpzBoblMmH2JMl2UR08NgCgkLuL
> qlB7DOSkWlOmR2OLZ32O1NA=
> =8B5z
> -END PGP SIGNATURE-
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4


pgpt56ACz439C.pgp
Description: PGP signature

Re: how to remote update 4.10 -> 5.3?

[Frank Shute]

On Thu, Dec 30, 2004 at 07:32:20PM +0100, Palle Girgensohn wrote:
>
> 
> --On torsdag, december 30, 2004 20.36.56 +0300 Igor Pokrovsky 
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >Are there any other advantages of UFS2 over UFS except maximum disk size?
> 
> acl -- access control lists
> mac -- Mandatory Access Control
> 
> haven't used them yet, though.
> 

Background fsck? Useful if you've got big partitions.

Disclaimer: Haven't used UFS2 myself.

-- 

 Frank 

//-//

echo "f r a n k @ e s p e r a n c e - l i n u x . c o . u k" | sed -e 's/ //g'

//-PGP keyID: 0x10BD6F4B---//


pgplxnxzCMs0N.pgp
Description: PGP signature

Re: clock running fast

[Javier Henderson]

> > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \
> > - -f /var/db/ntpd.drift
> 
> It's generally recommended that you never trust your own clock since
> it's completely crap as time sources go.  It's also recommended that you
> use at least 5 time sources to avoid problems with bad clocks.

But isn't that what the drift file is for, to improve the accuracy of
the local clock during those times when the configured NTP servers aren't
available?

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

Re: clock running fast

[Federico Galvez-Durand Besnard]

Set /etc/localtime to your correct timezone before doing anything in 
your machine.
Remove /var/db/ntpd.drift before you reboot or restart your ntpd.

This is what I use in /etc/rc.conf:
+++
ntpd_enable="YES"   # Run ntpd Network Time Protocol (or NO).
ntpd_program="/usr/sbin/ntpd"   # path to ntpd, if you want a different one.
ntpd_flags="-p /var/run/ntpd.pid -f /etc/ntp/drift -l /var/log/ntp.log"
+++
Check ntpd messages with dmesg.
If it does not work, this is one ntp.conf (change server to 
time.u.washington.edu or whatever is closer to you) that worked well for me:

+ BEGIN /etc/ntp.conf +++
# NTP configuration file
#
# Thu Nov 11 20:06:40 GMT+1 2004
restrict192.168.1.0 mask 255.255.255.0 notrust nomodify notrap
restrict127.0.0.1
# servers to query
#---
server  clock.tix.ch
restrictclock.tix.chmask 255.255.255.255 nomodify notrap 
noquery

+ END /etc/ntp.conf +++
Once you get synchronised with your time-server, you can consider 
changing minpoll  maxpoll to polite values.

Fico//
David Talkington wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Federico Galvez-Durand Besnard wrote:
what do you have in :
/etc/ntp.conf

Only:
server time.u.washington.edu
server  127.127.1.0 fudge   127.127.1.0 stratum 10
Command line:
/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \
- -f /var/db/ntpd.drift
Thank you ... -d
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clock running fast

[dtalk-ml]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Federico Galvez-Durand Besnard wrote:
Set /etc/localtime to your correct timezone before doing anything in 
your machine. Remove /var/db/ntpd.drift before you reboot or restart 
your ntpd.
[ rc.conf and ntp.conf snipped ]
Thank you for the suggestions.  Unfortunately, I've been through all 
that, including the rude values of minpoll and maxpoll, using multiple 
servers, and starting with a fresh drift file.  I'm pretty sure ntpd 
isn't the problem.  In addition, the hardware clock itself appears to be 
plenty accurate, as it is always correct within a second or two when I 
check it directly in BIOS ... and two other 5.3-STABLE hosts on the same 
network, with the same ntpd configuration, but on different hardware, do 
not have this problem, which began when I updated (reinstalled) to 
5.3-STABLE from 5.2.

- -- 
David Talkington
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFB1FwQ5FKhdwBLj4sRArSqAJwK8MAvUfB69ixoHNzu8700Pvd52QCgl0dD
07gb7ipg0ENIcUN/PPHhXpw=
=Lv+T
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to remote update 4.10 -> 5.3?

[Paul Mather]

Igor Pokrovsky wrote:
Are there any other advantages of UFS2 over UFS except maximum disk size?
 

There's FFS snapshots capability in UFS2, for starters...
Cheers,
Paul.
--
e-mail: [EMAIL PROTECTED]
"Without music to decorate it, time is just a bunch of boring production
deadlines or dates by which bills must be paid."
   --- Frank Vincent Zappa
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clock running fast

[Brooks Davis]

On Thu, Dec 30, 2004 at 11:37:04AM -0800, Javier Henderson wrote:
> > > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \
> > > - -f /var/db/ntpd.drift
> > 
> > It's generally recommended that you never trust your own clock since
> > it's completely crap as time sources go.  It's also recommended that you
> > use at least 5 time sources to avoid problems with bad clocks.
> 
> But isn't that what the drift file is for, to improve the accuracy of
> the local clock during those times when the configured NTP servers aren't
> available?

Yes, but it can only do so much.  The clock crystals in your average PC
are OK as clocks, but much better as thermometers so the drift
calculations are only approximate.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4


pgp5BEU1OFD1v.pgp
Description: PGP signature

Re: clock running fast

[Federico Galvez-Durand Besnard]

Brooks Davis wrote:
On Thu, Dec 30, 2004 at 11:37:04AM -0800, Javier Henderson wrote:
 

/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \
- -f /var/db/ntpd.drift
   

It's generally recommended that you never trust your own clock since
it's completely crap as time sources go.  It's also recommended that you
use at least 5 time sources to avoid problems with bad clocks.
 

But isn't that what the drift file is for, to improve the accuracy of
the local clock during those times when the configured NTP servers aren't
available?
   

Yes, but it can only do so much.  The clock crystals in your average PC
are OK as clocks, but much better as thermometers so the drift
calculations are only approximate.
-- Brooks
 

Yeap, but only if your NTPD is running fine and stable, otherwise 
drift-file can be very messy.
Check your dmesg for NTPD log before you trust drift-files.

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

New Ad-aware software!

[heung]

   Ad-Aware is designed to provide advanced protection from known
   Data-mining, aggressive advertising, Parasites, Scumware, selected
   traditional Trojans, Dialers, Malware, Browser hijackers, and tracking
   components. With the release of Ad-Aware SE Personal edition, Lavasoft
   takes the fight against Spyware to the next level. 
   With Lavasofts all new Code Sequence Identification (CSI) technology,
   you will not only be protected from known content, but will also have
   advanced protection against many of their unknown variants. To further
   protect you, Ad-Aware SE Personal Edition also has the capability to
   scan and list Alternate Data Streams (ADS) in NTFS enabled volumes. In
   combination with the new scanning engine, Ad-Aware SE will scan your
   computer faster and more thoroughly than ever before!
   Whats new in Ad-Aware SE Personal edition?
   Hardened against third party uninstall with encrypted preference files
   Scanning engine improvements 

 Extended protection against DLL-injection, SE can unload process
   modules on the fly

 Extended Memory scanning

 Now scans all modules loaded by a process

 Uses our all new CSI (Code Sequence Identification) technology to
   identify new and unknown variants of known targets
   Extended Registry scanning
   
 Now scans registry branches of multiple user accounts

 Performs additional smart checks to detect dynamically created
   references

 Scanning speed noticeably faster

 Extended Scanning for known and unknown/possible Browser-Hijackers
   Extended Disk scanning
   
 Now scans and lists alternate Data-streams on NTFS volumes

 Now Ad-Aware supports scanning of Cabinet files, (including spanned
   archives)

 Scanning speed increased

 Improved Hosts-file scan

 Now Ad-Aware and Ad-Watch use much smaller reference files
   Several User Interface improvements
   
 Improved Graphical UI

 Ad-Aware now supports custom graphical Skins

 More user friendly Plug-in/Extension GUI (Plug-ins and Extensions
   now shown on separate screens)

 New Scan Result view, includes a scan summary and detailed view

 Ad-Aware now linked to the online TAC database
   Multiple New Tweak options
   
 Unloading of process modules during a scan

 Obtaining command line of scanned processes

 Ignoring spanned cab files

 Permanent archive caching

 Always try to unload modules before deletion

 Disable manual quarantine if auto quarantine is selected

 Write protect system files after repair

 Use gridlines in item lists

 Logfile detail section condensed
   Several logfile improvements
   
 Includes support for separate removal logfiles

 Allows adding a Reference summary/index to logfiles

 Logfile contains overall more detailed information
   Ad-Aware SE is compatible with Microsoft Windows
   98/Me/NT/2000/XP/2003.
   Download Ad-Aware + Keygen: www.warezdownload.ws/adaware.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dump/restore with ufs2

[Roland Smith]

On Thu, Dec 30, 2004 at 05:54:25PM +, Ceri Davies wrote:
> On Tue, Dec 28, 2004 at 01:23:50PM -0500, Brian Szymanski wrote:
> > When I run the following script, I get a warning message, and I'm
> > wondering if it's ignorable or indicates there is a little more work to be
> > done in getting dump/restore happy with ufs2...
> > 
> > $ cd /altroot
> > $ dump -L -0 -a -f - /dev/$ROOT | restore -rf -
> >   ...
> > warning: ./.snap: File exists
> > 
> > Does this mean my snapshots are being overwritten on the target disk? And
> > if so, that's a good thing, right?
> 
> That's just a warning that .snap already exists in the current directory
> (which is because it gets created by newfs); the contents will remain
> unaffected since snapshots are not dumped (I believe).

A snapshot _is_ what is being dumped when you use the -L option to
dump. See the manual page.

Roland
-- 
R.F. Smith   /"\ASCII Ribbon Campaign
r s m i t h @ x s 4 a l l . n l  \ /No HTML/RTF in email
http://www.xs4all.nl/~rsmith/ X No Word docs in email
 / \Respect for open standards


pgpObEyA0W86I.pgp
Description: PGP signature

Re: clock running fast

[Harlan Stenn]

> But isn't that what the drift file is for, to improve the accuracy of
> the local clock during those times when the configured NTP servers aren't
> available?

Yes.

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

Re: clock running fast

[Federico Galvez-Durand Besnard]

Hmmm, are you using the same localtime in all machines?
I remember having the same problem several years ago, in 3.x, with a 
server. The clock kept walking. Hardware was OK. It came back to normal 
after setting localtime correctly.
Remember, if you are in Pacific Time you are GMT+8 (some people wrongly 
uses GMT-8), it means you have to add 8h to your localtime in order to 
get GMT. Your NTPD will never be stable with a wrong localtime setting.
Fico//

[EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Federico Galvez-Durand Besnard wrote:
Set /etc/localtime to your correct timezone before doing anything in 
your machine. Remove /var/db/ntpd.drift before you reboot or restart 
your ntpd.

[ rc.conf and ntp.conf snipped ]
Thank you for the suggestions.  Unfortunately, I've been through all 
that, including the rude values of minpoll and maxpoll, using multiple 
servers, and starting with a fresh drift file.  I'm pretty sure ntpd 
isn't the problem.  In addition, the hardware clock itself appears to 
be plenty accurate, as it is always correct within a second or two 
when I check it directly in BIOS ... and two other 5.3-STABLE hosts on 
the same network, with the same ntpd configuration, but on different 
hardware, do not have this problem, which began when I updated 
(reinstalled) to 5.3-STABLE from 5.2.

- -- David Talkington
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQFB1FwQ5FKhdwBLj4sRArSqAJwK8MAvUfB69ixoHNzu8700Pvd52QCgl0dD
07gb7ipg0ENIcUN/PPHhXpw=
=Lv+T
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clock running fast

[Harlan Stenn]

> Remove /var/db/ntpd.drift before you reboot or restart your ntpd.

Why would you want to do this?

And in config files, iburst is your friend.

See http://ntp.isc.org/Support/ for more informaion.

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

Re: clock running fast

[Federico Galvez-Durand Besnard]

Harlan Stenn wrote:
Remove /var/db/ntpd.drift before you reboot or restart your ntpd.
   

Why would you want to do this?
And in config files, iburst is your friend.
See http://ntp.isc.org/Support/ for more informaion.
H
 

True only when NTPD is running in stable steady state.
In this case, NTPD is not performing... so drift file can be recording 
very messy values.
Better get it from scratch than having a very bad initial condition.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clock running fast

[Harlan Stenn]

No way.

ntpd operates in gmt/utc only; localtime is completely out of the question.

H
--
> Hmmm, are you using the same localtime in all machines?
> I remember having the same problem several years ago, in 3.x, with a 
> server. The clock kept walking. Hardware was OK. It came back to normal 
> after setting localtime correctly.
> Remember, if you are in Pacific Time you are GMT+8 (some people wrongly 
> uses GMT-8), it means you have to add 8h to your localtime in order to 
> get GMT. Your NTPD will never be stable with a wrong localtime setting.
> Fico//
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

problem burning iso images

[Warren Liddell]

next writeable LBA 0
writing from file 5.3-RELEASE-i386-miniinst.iso size 274400 KB
written this track 274400 KB (100%) total 274400 KB
next writeable LBA 137352
writing from stdin

Every time i goto burn a iso filoe of onto CD it ends up getting stuck at the 
above part.  any reasons why this may be happening ?
-- 
Yours Sincerely
Shinjii
http://virusinfo.rdksupportinc.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clock running fast

[Federico Galvez-Durand Besnard]

Oops, I meant:
cp  /usr/share/zoneinfo/Etc/GMT+8/etc/localtime
if you want  Pacific Time in GMT format (don't use GMT-8).
Harlan Stenn wrote:
No way.
ntpd operates in gmt/utc only; localtime is completely out of the question.
H
--
 

Hmmm, are you using the same localtime in all machines?
I remember having the same problem several years ago, in 3.x, with a 
server. The clock kept walking. Hardware was OK. It came back to normal 
after setting localtime correctly.
Remember, if you are in Pacific Time you are GMT+8 (some people wrongly 
uses GMT-8), it means you have to add 8h to your localtime in order to 
get GMT. Your NTPD will never be stable with a wrong localtime setting.
Fico//
   

 

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

Re: problem burning iso images

[John-Mark Gurney]

Warren Liddell wrote this message on Fri, Dec 31, 2004 at 07:14 +1000:
> next writeable LBA 0
> writing from file 5.3-RELEASE-i386-miniinst.iso size 274400 KB
> written this track 274400 KB (100%) total 274400 KB
> next writeable LBA 137352
> writing from stdin
> 
> Every time i goto burn a iso filoe of onto CD it ends up getting stuck at the 
> above part.  any reasons why this may be happening ?

It'd be useful to provide the command that you are using to get this
problem...  It sounds like you might have a - at the end of your command
and it's trying to burn a track from stdin...  if you hit ctrl-d, it'll
burn an empty track and continue, though it'll be better to not try to
burn stdin in the first place...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 "All that I will do, has been done, All that I have, has not."
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: USB flash not working anymore

[Julian Elischer]

Peter Radcliffe wrote:
I'm running FreeBSD 4-STABLE from Dec 28 on an IBM X30 laptop.
I'm having increasingly worse USB problems as time goes on. Nothing
that I try new works and various older devices that I bought
specificly because they were supported and worked fine for years now
do not work.

[...]

 usb_block_allocmem: in interrupt context, size=4096
Anyone seen these problems before or working on usb in 4.x ? I'll do
what I can to help debugging...
this means exactly what it sounds like... something in the usb system 
tried to allocate memory while
in an interrupt context.
I don't see what USB controller you have.  OHCI or UHCI (or EHCI).

Thanks,
P.
 

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

Re: USB flash not working anymore

[Peter Radcliffe]

Julian Elischer <[EMAIL PROTECTED]> probably said:
> this means exactly what it sounds like... something in the usb system 
> tried to allocate memory while in an interrupt context.

I don't know anything about the USB subsystem, nor what can or cannot
be done while handling an interrupt.

> I don't see what USB controller you have.  OHCI or UHCI (or EHCI).

uhci0:  port 0x1800-0x181f
 irq 11 at device 29.0 on pci0
usb0:  on uhci0
uhci1:  port 0x1820-0x183f
 irq 3 at device 29.1 on pci0
usb1:  on uhci1
uhci2:  port 0x1840-0x185f
 irq 5 at device 29.2 on pci0
usb2:  on uhci2

P.

-- 
pir

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

Re: clock running fast

[Kevin Kinsey]

> [ rc.conf and ntp.conf snipped ]
> 
> Thank you for the suggestions.  Unfortunately, I've been through all 
> that, including the rude values of minpoll and maxpoll, using multiple 
> servers, and starting with a fresh drift file.  I'm pretty sure ntpd 
> isn't the problem.  In addition, the hardware clock itself appears to be 
> plenty accurate, as it is always correct within a second or two when I 
> check it directly in BIOS ... and two other 5.3-STABLE hosts on the same 
> network, with the same ntpd configuration, but on different hardware, do 
> not have this problem, which began when I updated (reinstalled) to 
> 5.3-STABLE from 5.2.
> 
> - -- 
> David Talkington
> [EMAIL PROTECTED]

I apparently misposted this earlier, my apologies.

Have you tried all possible values for kern.timecounter.hardware?

#sysctl kern.timecounter.choice

My most recent encounter with this issue, a K6-2/500 on an
Asus P5A mobo, needed "i8254".

HTH,

Kevin Kinsey

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

Re: USB flash not working anymore

[Julian Elischer]

Peter Radcliffe wrote:
Julian Elischer <[EMAIL PROTECTED]> probably said:
 

this means exactly what it sounds like... something in the usb system 
tried to allocate memory while in an interrupt context.
   

do you have access to anything with an EHCI or OHCI controller for 
comparison with that device?

I don't know anything about the USB subsystem, nor what can or cannot
be done while handling an interrupt.
 

I don't see what USB controller you have.  OHCI or UHCI (or EHCI).
   

uhci0:  port 0x1800-0x181f
irq 11 at device 29.0 on pci0
usb0:  on uhci0
uhci1:  port 0x1820-0x183f
irq 3 at device 29.1 on pci0
usb1:  on uhci1
uhci2:  port 0x1840-0x185f
irq 5 at device 29.2 on pci0
usb2:  on uhci2
P.
 

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

Re: clock running fast

[David Magda]

On Dec 30, 2004, at 15:58, Federico Galvez-Durand Besnard wrote:
Your NTPD will never be stable with a wrong localtime setting.
NTP does not care about local time. All values that NTP uses are in 
UTC: local time is a function of the operating system and is not used 
when calculating time values.

Another place to ask questions would be the Usenet group:
comp.protocols.time.ntp
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

iTE IT8212 card/ata problems

[Brian Szymanski]

Hello...

FreeBSD 5.3 on x86

I've installed an addon ATA card, an IT8212(F), and it comes in at bios
time, detects drives and such, but freebsd doesn't see it on booting. I
thought maybe this was because no drives were attached, but no dice with a
drive attached (even though the card sees this drive at boot time).

My system has a somewhat unusual ATA situation - a built in 2-port ATA
controller, another built in 2-port SATA controller, and now this card (2
port ATA as well). Is it possible that freebsd just doesn't expect so many
ata devices, or is the card just not supported?

I don't see it in hardware-i386.html, but generic ata cards have worked
for me in the past - was I just been getting lucky before?

Thanks for any ideas.

Cheers,
Brian Szymanski
[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: iTE IT8212 card/ata problems

[John Fox Maule]

Brian,

See
http://www.xl0.org/FreeBSD/13-12-04.html#ite-it8212f-gigabyte-raid-controlle
r-supported


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Szymanski
Sent: 31. december 2004 01:52
To: freebsd-stable@freebsd.org
Subject: iTE IT8212 card/ata problems

Hello...

FreeBSD 5.3 on x86

I've installed an addon ATA card, an IT8212(F), and it comes in at bios
time, detects drives and such, but freebsd doesn't see it on booting. I
thought maybe this was because no drives were attached, but no dice with a
drive attached (even though the card sees this drive at boot time).

My system has a somewhat unusual ATA situation - a built in 2-port ATA
controller, another built in 2-port SATA controller, and now this card (2
port ATA as well). Is it possible that freebsd just doesn't expect so many
ata devices, or is the card just not supported?

I don't see it in hardware-i386.html, but generic ata cards have worked for
me in the past - was I just been getting lucky before?

Thanks for any ideas.

Cheers,
Brian Szymanski
[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]"

5.3-RELEASE: SMP: system clock has died

[Stephane Raimbault]

I have an ASUS P2B-DS motherboard with dual P2 400MHz CPU's.  I have 
compiled the SMP kernel and noticed that something is not right.  In "top" 
the CPU values indicate 0% across the board, even idle!

last pid:  9462;  load averages:  0.00,  0.00,  0.00up 2+18:57:30  
13:11:47
14 processes:  1 running, 13 sleeping
CPU states:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  0.0% 
idle
Mem: 5232K Active, 115M Inact, 59M Wired, 60M Buf, 315M Free
Swap: 999M Total, 999M Free

Also, when I run systat and go to the vmstat page I get this error:
The alternate system clock has died!
 Reverting to ``pigs'' display.
There seems to be no errors in /var/log/messages.
here is my /var/run/dmesg.boot file
sol# cat /var/run/dmesg.boot
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
   The Regents of the University of California. All rights reserved.
FreeBSD 5.3-RELEASE #1: Mon Dec 27 17:45:44 MST 2004
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
MPTable: 
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU)
 Origin = "GenuineIntel"  Id = 0x652  Stepping = 2
 
Features=0x183fbff
real memory  = 536858624 (511 MB)
avail memory = 515788800 (491 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID:  1
cpu1 (AP): APIC ID:  0
ioapic0: Assuming intbase of 0
ioapic0  irqs 0-23 on motherboard
ACPI disabled by blacklist.  Contact your BIOS vendor.
npx0: [FAST]
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  pcibus 0 on motherboard
pir0:  on motherboard
pci0:  on pcib0
agp0:  mem 0xe400-0xe7ff 
at device 0.0 on pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
isab0:  at device 4.0 on pci0
isa0:  on isab0
atapci0:  port 
0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
uhci0:  port 0xb400-0xb41f irq 11 
at device 4.2 on pci0
uhci0: [GIANT-LOCKED]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
piix0:  port 0xe800-0xe80f at device 4.3 on pci0
Timecounter "PIIX" frequency 3579545 Hz quality 0
ahc0:  port 0xb000-0xb0ff mem 
0xe180-0xe1800fff irq 11 at device 6.0 on pci0
ahc0: [GIANT-LOCKED]
aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
pci0:  at device 9.0 (no driver attached)
fxp0:  port 0xa800-0xa83f mem 
0xdf80-0xdf8f,0xe000-0xefff irq 10 at device 10.0 on pci0
miibus0:  on fxp0
inphy0:  on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:90:27:8c:08:17
cpu0 on motherboard
cpu1 on motherboard
orm0:  at iomem 0xc8000-0xcd7ff,0xc-0xc7fff on isa0
pmtimer0 on isa0
atkbdc0:  at port 0x64,0x60 on isa0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
fdc0:  at port 0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0:  on ppc0
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
Timecounters tick every 10.000 msec
ata0-master: FAILURE - SETFEATURES SET TRANSFER MODE 
status=51 error=4
acd0: CDROM  at ata0-master BIOSPIO
Waiting 15 seconds for SCSI devices to settle
da0 at ahc0 bus 0 target 0 lun 0
da0:  Fixed Direct Access SCSI-2 device
da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
da1 at ahc0 bus 0 target 1 lun 0
da1:  Fixed Direct Access SCSI-2 device
da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
da2 at ahc0 bus 0 target 2 lun 0
da2:  Fixed Direct Access SCSI-2 device
da2: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing 
Enabled
da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
SMP: AP CPU #1 Launched!
Mounting root from ufs:/dev/da0s1a
sol#


What is happening?  This is a test box I have here so I can do some testing 
as necessary.

Thank you,
Stephane.
_
Powerful Parental Controls Let your child discover the best the Internet has 
to offer.  
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1

Re: USB flash not working anymore

[Peter Radcliffe]

Julian Elischer <[EMAIL PROTECTED]> probably said:
> do you have access to anything with an EHCI or OHCI controller for 
> comparison with that device?

My (now usually windows only) amd64 desktop box has ohci, but it doesn't
have any ethernet devices that 4 has support for (5 does, apparently)
so I can't easily give direct logs.


Booting i386 FreeBSD from an old partition taken to 4-STABLE from
earlier this month shows that the SanDisk CF redaer works fine with
mtools to read from (when I try to write to it I get lots of umass0:
BBB reset failed, STALLED) and the Iomega micro mini thumbdrive also
works fine with mtools for read/write.

The crucial gizmo does not work at all, I get a umass0 message, a
disconnection and then detatch message and then another "umass0:
Crucial Gizmo, rev 2.00/0.01, addr" message and nothing else, no da0;

  can't re-use a leaf (minimum_cmd_size)!
  umass0: at uhub1 port 4 (addr 2) disconnected
  (da0:umass-sim0:0:0:0): lost device
  (da0:umass-sim0:0:0:0): removing device entry
  umass0: detached
  umass0: Crucial Gizmo, rev 2.00/0.01, addr 2
  umass0: at uhub1 port 4 (addr 2) disconnected
  umass0: detached
  umass0: Crucial Gizmo, rev 2.00/0.01, addr 2

Shortly after removing the Gizmo the machine page faulted in kernel
mode and crashed.

After enabling crashdumps I tried this again and the gizmo as the
first device worked;

  umass0: Crucial Gizmo, rev 2.00/0.01, addr 2
  umass0: at uhub1 port 4 (addr 2) disconnected
  da0 at umass-sim0 bus 0 target 0 lun 0
  da0:  Fixed Direct Access SCSI-CCS device 
  da0: 650KB/s transfers
  da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C)
  (da0:umass-sim0:0:0:0): lost device
  (da0:umass-sim0:0:0:0): removing device entry
  umass0: detached
  umass0: Crucial Gizmo, rev 2.00/0.01, addr 2
  da0 at umass-sim0 bus 0 target 0 lun 0
  da0:  Fixed Direct Access SCSI-CCS device 
  da0: 650KB/s transfers
  da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C)
  can't re-use a leaf (minimum_cmd_size)!

then I got a panic: ohci_abort_xfer: not in process context and a very
big crashdump;

  IdlePTD at physical address 0x003ef000
  initial pcb at physical address 0x00346b20
  panicstr: ohci_abort_xfer: not in process context
  panic messages:
  ---
  panic: ohci_abort_xfer: not in process context
  syncing disks...
  done
  Uptime: 4m35s
  (kgdb) bt
  #0  0xc018b9aa in dumpsys ()
  #1  0xc018b77b in boot ()
  #2  0xc018bba0 in poweroff_wait ()
  #3  0xc0246760 in ohci_abort_xfer ()
  #4  0xc024641f in ohci_timeout_task ()
  #5  0xc024a101 in usb_task_thread ()

Further down the rabbit hole, I build a kernel.debug and try to
copy things over to a flash drive to get them to another machine;

  umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 2
  umass0: Get Max Lun not supported (STALLED)
  da0 at umass-sim0 bus 0 target 0 lun 0
  da0:  Removable Direct Access SCSI-2 device 
  da0: 650KB/s transfers
  da0: 489MB (1001953 512 byte sectors: 64H 32S/T 489C)
  umass0: BBB reset failed, STALLED
  umass0: Invalid CSW: tag 96 should be 97
  umass0: BBB reset failed, STALLED
  umass0: Invalid CSW: tag 97 should be 98
[lots of these pairs]
  umass0: Invalid CSW: tag 150 should be 151
  umass0: BBB reset failed, STALLED
  (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi
status == 0x0
  umass0: Invalid CSW: tag 151 should be 152
  umass0: BBB reset failed, STALLED
  umass0: BBB reset failed, STALLED
  umass0: BBB reset failed, STALLED
  umass0: Invalid CSW: tag 234 should be 235
  umass0: BBB reset failed, STALLED
[lots more of these pairs]
  umass0: Invalid CSW: tag 235 should be 236
  umass0: BBB reset failed, STALLED
  umass0: BBB reset failed, STALLED
  (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi
status == 0x0
  umass0: Invalid CSW: tag 248 should be 250
  umass0: BBB reset failed, STALLED
  umass0: BBB reset failed, STALLED
  umass0: BBB reset failed, STALLED

This didn't crash the machine, at least.

Trying to reprovoke the crash it seems to only fail with a panic from
one pair of usb ports, the rest work better. I get another page fault
in kernel mode and it dumps;

  IdlePTD at physical address 0x003ec000
  initial pcb at physical address 0x00346b20
  panicstr: page fault
  panic messages:
  ---
  Fatal trap 12: page fault while in kernel mode
  fault virtual address   = 0x4c
  fault code  = supervisor read, page not present
  instruction pointer = 0x8:0xc024b23e
  stack pointer   = 0x10:0xe1d91f30
  frame pointer   = 0x10:0xe1d91f44
  code segment= base 0x0, limit 0xf, type 0x1b
  = DPL 0, pres 1, def32 1, gran 1
  processor eflags= interrupt enabled, resume, IOPL = 0
  current process = 4 (usbtask)
  interrupt mask  = bio
  trap number = 12
  panic: page fault
  syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
  giving up on 1 buffers
  Uptime: 7m9s

 

Re: clock running fast

[dtalk-ml]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin Kinsey wrote:
Have you tried all possible values for kern.timecounter.hardware?
#sysctl kern.timecounter.choice
My most recent encounter with this issue, a K6-2/500 on an
Asus P5A mobo, needed "i8254".
Thank you vociferously.  A value of i8254 for kern.timecounter.hardware 
seems to have had the desired effect.

Cheers ... -d
- -- 
David Talkington
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFB1O/d5FKhdwBLj4sRAkAcAKCkG4sD4+8sWszGSsocj0gpIAwYrQCfVNwV
24g6apBqGznNfM28YjaWZMI=
=P4Pa
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: clock running fast

[Harlan Stenn]

I'd appreciate it if somebody would add this information to:

 http://ntp.isc.org/Support/KnownOsIssues

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

Re: clock running fast

[Peter Jeremy]

On Thu, 2004-Dec-30 15:59:10 -0500, Harlan Stenn wrote:
>> Remove /var/db/ntpd.drift before you reboot or restart your ntpd.
>
>Why would you want to do this?

On a number of occasions, I've had the ntpd PLL start oscillating and
winding up saturated at +500ppm or -500ppm.  Removing ntpd.drift lets
it recover.  Admittedly, this was mostly on old versions of ntpd - I'm
not sure if the problem is still present.

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