Bruce Evans wrote:
-current doesn't write extended attributes unless you enabled them.
OK. I'm wrong. Really I don't understand a problem. Superblock was
corrupted. I've fix it with fsck (from other sector). But I decided
remake the FS and run newfs from -stable again. Now I write on it buth
Andrew Thompson wrote:
Nate Lawson wrote:
On Wed, 17 Sep 2003, Andrew Thompson wrote:
It has helped and the laptop is able to suspend with the serial cable
attached (further than before). It now panics on the first resume with
the following (gdb output at bottom).
You should do a quick grep
Le 2003-09-22, Dan Naumov écrivait :
Speaking of failing, should I completely disregard the probe2:ata1
warnings during boot which you saw in the dmesg output I sent you ?
Yes, these messages are perfectly inocuous, they mean that your CD drive
does not provide serial number information. You
Le 2003-09-22, Matthias Andree écrivait :
I'm getting complaints from ata or atapicam during boot-up, but my
From CAM actually, and you can safely ignore them.
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
Le 2003-09-21, Sascha Holzleiter écrivait :
i still have problems with atapicam and atang, while booting with
atapicam i get these messages:
There is nothing abnormal with these messages.
When trying to burn a disk with cdrecord i get the following panic:
panic: mutex vm object not owned
Hello.
While trying to install recent snapshot of -CURRENT on Netfinity 6000R,
sysinstall and other tools reported the size of RAID partition much smaller
than expected.
After looking into source code, I noticed a small bug in calculation
of d_mediasize:
Index: ips_disk.c
Hi crowd,
I have seen this problems several months ago and posted on -current, but
noone seemed to care. Was really disappointed then. I assume there's not
many people in the world running both -current and -stable on the same
box...
My symptoms were thus: newfs (-st) and fill filesystem works
Hi,
after I had a kernel with broken atapicam that wouldn't boot, I tried
disabling the secondary onboard channel of my main board (AMI BIOS, VIA
KT133 chip set).
The BIOS thought oh well, we don't need ATA1, so we have IRQ 15 free,
let's route xl0 and xl2 there. So far so good.
ATAng happily
On Sun, 21 Sep 2003 12:56:53 -0700 (PDT)
Doug White [EMAIL PROTECTED] wrote:
On Sun, 21 Sep 2003, Bruce Mackay wrote:
I actually tried hw.pci.allow_unsupported_io_range = 1 to no
avail. I've tried building pcm into my kernel, I've tried loading them
as modules with no success. I
On Fri, Sep 19, 2003 at 09:41:51AM +0200, Christoph Kukulies wrote:
Strange, very strange. SOeren, you know my hardware, it is the same MB
(ASUS P4S8X or the like - off memory).
I built a couple of worlds during the past months.
But with the recent cvsups I don't get through. make world
On Sun, Sep 21, 2003 at 01:25:29PM -0700, Doug White wrote:
On Sun, 21 Sep 2003, Ceri Davies wrote:
I'm confused; how does one disable PAE? I don't see a kernel option for
it.
'options PAE' turns it on. Without it turns it off. :)
Any reason it's not in LINT, then?
Ceri
--
User: DO
While trying to install recent snapshot of -CURRENT on Netfinity 6000R,
sysinstall and other tools reported the size of RAID partition much smaller
than expected.
After looking into source code, I noticed a small bug in calculation
of d_mediasize:
Please disregard this message, it's already
On Sun, 21 Sep 2003, Scott Long wrote:
Doug Barton wrote:
E... I'm not sure this is an optimal solution. There is an awful
lot of software out there which expects -pthread to just work.
Wouldn't it make more sense to default it to one thing or the other,
then make it configurable
In message [EMAIL PROTECTED], Daniel Rock
[EMAIL PROTECTED] writes
Mark Knight schrieb:
Current from approximately 0500 BST on 16th September is giving me
errors like this from boot:
ad0: WARNING - WRITE_MUL write data underrun 81922048
ad0: WARNING - WRITE_MUL write data underrun 81926144
Hi.
I'm getting more confirmations that ATAng works strange when cable, motherboard and
device supports different modes. I was told (no logs) that when using DPTA hdd
(UDMA33) with UDMA100 motherboard, ATAng ends up with quite weird results, like
resetting hdd and Device disappeared error
My system:
FreeBSD jsmith.org 5.1-RELEASE-p3 FreeBSD 5.1-RELEASE-p3 #0: Sat Sep 20
14:37:32 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL i386
I'm running a P4 2.4 Ghz processor with 512meg of ram.
I've had the problem of getting signal 11 and signal 4 when I make
buildworld
I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the
9/20 snapshot. That also wouldn't complete a buildworld without breaking
with the hard drive error.
I booted windows and stress tested the drive with all kinds of I/O. Not a
hiccup.
It isn't the hardware, it has to
On Mon, 22 Sep 2003 09:43:39 -0400
Justin Smith [EMAIL PROTECTED] wrote:
make world builds and installs gcc 3.2.3? It can't be as simple as
replacing the compiler source in /usr/src with that of gcc 3.2.3 (or
is it?).
For 3.2.2-to-3.2.3 upgrade the newer sources in
Justin Smith ([EMAIL PROTECTED]) wrote:
I'm running a P4 2.4 Ghz processor with 512meg of ram.
I've had the problem of getting signal 11 and signal 4 when I make
buildworld and buildkernel.
I tested my system with memtest86 (for several hours) and it says
everything is OK.
We had similar
On Mon, 2003-09-22 at 06:54, Derek Ragona wrote:
I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the
9/20 snapshot. That also wouldn't complete a buildworld without breaking
with the hard drive error.
I booted windows and stress tested the drive with all kinds of
Holger Kipp wrote:
...
imho memtest seems to be suitable for this-is-real-broken-memory(tm) only.
Yes, memtest86 could only detect bad memory. No reported failure doesn't
says anything except memtest86 didn't found any error.
It might be that due to differnent optimisations (gcc 3.2.2 vs gcc
Thank you for your email. Please note that I am out of the office on business from
Monday, September 15th through Friday, September 19th. I will check email and
voicemail as often as possible. If your need is urgent, please reach Matt Kellogg at
530-893-1134 or [EMAIL PROTECTED] Thanks
From: Harald Schmalzbauer [EMAIL PROTECTED]
Scot W. Hetzel wrote:
From: Dan Naumov [EMAIL PROTECTED]
Seeing as -pthread support has been removed from -CURRENT breaking
_LOTS_ of ports, is it possible to get it back into a local source
tree ? If so, how ? Thanks in advance.
All you
On Mon, 22 Sep 2003, Bruce Mackay wrote:
Yeah the only thing I can change in this stupid BIOS is the time.
PnP cannot be turned off through the BIOS apparently. What do you mean
by wiping the device configuration? Maybe I'll try doing that anyway
and see what happens.
Is this some
On Mon, 22 Sep 2003, Ceri Davies wrote:
On Sun, Sep 21, 2003 at 01:25:29PM -0700, Doug White wrote:
On Sun, 21 Sep 2003, Ceri Davies wrote:
I'm confused; how does one disable PAE? I don't see a kernel option for
it.
'options PAE' turns it on. Without it turns it off. :)
Any
On Mon, Sep 22, 2003 at 02:25:27PM +, Holger Kipp wrote:
Justin Smith ([EMAIL PROTECTED]) wrote:
I'm running a P4 2.4 Ghz processor with 512meg of ram.
I've had the problem of getting signal 11 and signal 4 when I make
buildworld and buildkernel.
I tested my system with memtest86
While trying to build mysql-server i get this:
Making all in mysys
Making all in extra
/bin/sh ../libtool --mode=link cc -DDBUG_OFF -O -pipe -march=pentium2
-o resolveip resolveip.o ../mysys/libmysys.a ../dbug/libdbug.a
../strings/libmystrings.a -lz -lcrypt -lm -pthread
cc -DDBUG_OFF -O
Hello
I saw many posts in the archive about Creative Labs Audigy and Audigy 2
sound cards, but quite nothing about SBLive. I have an old one, packaged
as Platinum, the one that came with an 51/4 extension, called Live
Drive II. And I wanted to know if somebody had been able to use it under
On Sun, 21 Sep 2003, Scott Long wrote:
Most everyone that writes threaded applications and runs on
multiple platforms knows that most thread libraries are
called libpthread and are linked to with -lpthread. Once
we rename libkse to libpthread, the problem largely goes
away. The porter,
On Mon, 22 Sep 2003, David Schwartz wrote:
There will be a libpthread and -pthread will be NOOP'd. It
should be a very familiar environment.
You know another environment that has '-pthread' (that is, it does not
produce an error) but fails to compile and link pthreads code when that
NFS Server:
FreeBSD titan.klemm.apsfilter.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Sep 21
13:16:17 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TITAN i386
NFS Client:
FreeBSD aklemm.klemm.apsfilter.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Sep 22
21:29:32 CEST 2003 [EMAIL
Same machines like in my other mail ...
NFS server
FreeBSD titan.klemm.apsfilter.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Sep 21
13:16:17 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TITAN i386
NFS client, Laptop
FreeBSD aklemm.klemm.apsfilter.org 5.1-CURRENT FreeBSD
I don't want to get into some flame war here. I am trying to provide what
information I can. If Soren, or anyone else wants more debugging
information I will be happy to do what I can to provide that
information. I simply need them to tell me what and how to capture the
information. As the
I thought I'd relate this success story to all of you -current people.
We are the webhost for talklikeapirate.com -- the official site for
International Talk Like a Pirate Day that happened this past friday.
This is about as big an event that the small regional ISP I work for
has ever seen.
On Mon, 22 Sep 2003 09:27:52 -0700 (PDT)
Doug White [EMAIL PROTECTED] wrote:
On Mon, 22 Sep 2003, Bruce Mackay wrote:
Yeah the only thing I can change in this stupid BIOS is the time.
PnP cannot be turned off through the BIOS apparently. What do you mean
by wiping the device
On Monday 22 September 2003 04:28 pm, Andreas Klemm wrote:
The panic here is:
(kgdb) symbol-file kernel.debug
Reading symbols from kernel.debug...done.
(kgdb) core-file /var/crash/vmcore.0
No kernel exec file specified
(kgdb) exec-file kernel
(kgdb) core-file /var/crash/vmcore.0
panic:
On Mon, 22 Sep 2003, Bruce Mackay wrote:
Most BIOSen with PnP support have an option to clear the device config and
force a PCI/PnP resource reconfiguration on next boot.
snip
Laugh, it's actually a toshiba POS. I wish I had realised that
the BIOS was so feeble. One of the
Daniel Eischen wrote:
This is about 3rd party applications built outside of
ports. The only possible problem you are going to
have is on the link command, and it should be obvious
that you're missing a link to the threads library.
This is trivial to fix. It's not like we're making
someone change
On Mon, Sep 22, 2003 at 10:35:10PM -0600, Scott Long wrote:
[...]
Scott said it all for me. Seriously. The whole idea of breaking
backwards de-facto compatibility is bad, bad, bad.
Regards,
--
wca
___
[EMAIL PROTECTED] mailing list
On Mon, Sep 22, 2003 at 10:35:10PM -0600, Scott Long wrote:
Daniel Eischen wrote:
This is about 3rd party applications built outside of
ports. The only possible problem you are going to
have is on the link command, and it should be obvious
that you're missing a link to the threads library.
Steve Kargl wrote:
On Mon, Sep 22, 2003 at 10:35:10PM -0600, Scott Long wrote:
Daniel Eischen wrote:
This is about 3rd party applications built outside of
ports. The only possible problem you are going to
have is on the link command, and it should be obvious
that you're missing a link to the
On Mon, Sep 22, 2003 at 06:48:14PM -0500, Jonathan E Fosburgh wrote:
On Monday 22 September 2003 04:28 pm, Andreas Klemm wrote:
The panic here is:
(kgdb) symbol-file kernel.debug
Reading symbols from kernel.debug...done.
(kgdb) core-file /var/crash/vmcore.0
No kernel exec file
42 matches
Mail list logo
