Hi everyone,
I haven't been using my DVD-ROM in my Fujitsu/Siemens S-1540 series laptop
with FreeBSD for some time, so I don't know how long this problem has
been. (I used it quite a bit when installing, so it hasn't always been
like this) When I boot up or do a atacontrol reinit 0 I get
ata0:
It seems Ashley Penney wrote:
Hiya,
I recently upgraded my -current box, only to have my Serial ATA device move
from ar0 to ad6, making things cry.
Read UPDATING!! (hint you need to include device ataraid in your config).
-Søren
___
[EMAIL
hi,
i did a lot of changes and tests last night :)
-u were right there was a bug in the network config (i fixed some named
entries)
now netstat -r is really fast (no timeouts which occured before)
-i wrote a simple c test program using gethostname, gethostbyname,
gethostbyaddr as suggested
it
hi,
i did cvsup for /usr/src yesterday and did a build world.
i also build a new kernel without all these debugging things.
i rebooted the system and everything went fine first but then
i tried to recompile pf_freebsd and the system crashed.
i rebooted and did fsck and tried the rebuild again -
ASUS P5A or P5AB (one of each now) - won't boot without setting
hw.ata.ata_dma=0. GEOM recognizes the drive itself but then the reads
of the disklabels fail with a message that I can't find in the source,
about a DMA failure. System then prompts to mount root and nothing I
type works. I see
Well, I misspoke on the timer; the one that works is booting in non-acpi
mode by beasties choice; the older one still fails if I comment the acpi
ignore timer statement. Actually that one appears to run slow by about half.
Both fail equally in ATAng so acpi isn't making any difference (nor does
On Thu, Sep 11, 2003 at 02:44:55PM +0200, Harti Brandt wrote:
Hi,
I just tried to upgrade one of my systems from a static root from july to
an actual dynamic root. The installworld went fine 'til the place where
/bin/test is installed. At that point the installation stopped with ELF
Just a follow up.
I've since been able to get my -CURRENT system running under the new build.
However the booting process is still slow around those ata?: [MPSAFE]
messages. Any ideas on getting a speed up?
-Al
___
[EMAIL PROTECTED] mailing list
It seems Alastair G. Hogge wrote:
Just a follow up.
I've since been able to get my -CURRENT system running under the new build.
However the booting process is still slow around those ata?: [MPSAFE]
messages. Any ideas on getting a speed up?
I'm working on it...
-Søren
It seems Pete Carah wrote:
ASUS P5A or P5AB (one of each now) - won't boot without setting
hw.ata.ata_dma=0. GEOM recognizes the drive itself but then the reads
of the disklabels fail with a message that I can't find in the source,
about a DMA failure. System then prompts to mount root and
Hi...
Sorry to do a me too, but I have a similar problem after a cvsup midday
on the 13th September. The previous kernel was pre-ATAng.
The machine panic'd after inserting a friends wireless PCMCIA card
(but that's probably another unrelated issue), rebooted and left
me in single user after
hello,
as you know, there is no more -pthread gcc flag in -current. but many ports
(kde3, for example) still wants it. So what should I do to compile kde3
succesfully? The one way I see now is to s/-pthread/-lc_r/g in Makefiles :-)
maybe there is another way?
Thank you.
I've seen that too, although my problem was with my Alcatel Speedtouch
330 which routinely panics the system.
I'djust retrieved usr from a backup to get round it, and put it down to
the perils of -current, but if there is really a problem, I can
investigate further here.
Mark
Simon Brown
backing off to ata-lowlevel.c 1.10 allows me to boot again.
--On Saturday, September 13, 2003 18:54:18 -0500 Larry Rosenman
[EMAIL PROTECTED] wrote:
--On Saturday, September 13, 2003 18:09:21 -0500 Larry Rosenman
[EMAIL PROTECTED] wrote:
I have a ICH3 controller, and a 9/9 kernel works just
On Sun, 14 Sep 2003, tokza wrote:
hello,
as you know, there is no more -pthread gcc flag in -current. but many ports
(kde3, for example) still wants it. So what should I do to compile kde3
succesfully? The one way I see now is to s/-pthread/-lc_r/g in Makefiles :-)
maybe there is another
On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote:
i did cvsup for /usr/src yesterday and did a build world.
i also build a new kernel without all these debugging things.
If you're running FreeBSD-current, I would suggest that
you put the debugging options back into your
I'm seeing similar messages from fsck:
unexpected soft-update inconsistency, unable to write block, etc.
going back to my 9/9/2003 good kernel, it works.
so I think SOMETHING broke here.
LER
--On Sunday, September 14, 2003 08:30:51 -0700 Steve Kargl
[EMAIL PROTECTED] wrote:
On Sun, Sep 14,
Is there a known issue with recent -CURRENT (between September 10, 2003 and
today) where
you can't get a panic dump?
I have a kernel from yesterday's sources (modulo a reversion of
ata-lowlevel to version
1.10 because 1.11 won't boot), and some debugging code from Nate Lawson to
debug my
ACPI
Am Son, 2003-09-14 um 17.30 schrieb Steve Kargl:
On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote:
i did cvsup for /usr/src yesterday and did a build world.
i also build a new kernel without all these debugging things.
If you're running FreeBSD-current, I would suggest
It seems Larry Rosenman wrote:
Also, when coming back up after the Panic on the same kernel, we get
unexpected soft-update
inconsistencies, cannot write block type errors from FSCK.
Going back to my September 9, 2003 kernel, fsck deals with the same exact
filesystem just fine.
What if
--On Sunday, September 14, 2003 18:46:19 +0200 Soren Schmidt
[EMAIL PROTECTED] wrote:
It seems Larry Rosenman wrote:
Also, when coming back up after the Panic on the same kernel, we get
unexpected soft-update
inconsistencies, cannot write block type errors from FSCK.
Going back to my September
--On Sunday, September 14, 2003 18:46:19 +0200 Soren Schmidt
[EMAIL PROTECTED] wrote:
It seems Larry Rosenman wrote:
Also, when coming back up after the Panic on the same kernel, we get
unexpected soft-update
inconsistencies, cannot write block type errors from FSCK.
Going back to my September
On Sun, 14 Sep 2003 09:41:44 +0200 (CEST)
Niklas Saers Mailinglistaccount [EMAIL PROTECTED] wrote:
Hi everyone,
I haven't been using my DVD-ROM in my Fujitsu/Siemens S-1540 series laptop
with FreeBSD for some time, so I don't know how long this problem has
been. (I used it quite a bit when
Am Son, 2003-09-14 um 17.49 schrieb Larry Rosenman:
I'm seeing similar messages from fsck:
unexpected soft-update inconsistency, unable to write block, etc.
going back to my 9/9/2003 good kernel, it works.
i tried to use my old kernel; build with sources from fbsd 5.1 release).
i rebooted
--On Sunday, September 14, 2003 19:02:17 +0200 Sebastian Ssmoller
[EMAIL PROTECTED] wrote:
Am Son, 2003-09-14 um 17.49 schrieb Larry Rosenman:
I'm seeing similar messages from fsck:
unexpected soft-update inconsistency, unable to write block, etc.
going back to my 9/9/2003 good kernel, it
On Sat, 13 Sep 2003, Matt wrote:
After building world as of late last night I decided to portupgrade
-rRaf, mainly due to having the libintl.so.4 missing problem when I
tried to start X. Everything compiled perfectly fine (and X is now
working fine) except for databases/mysql40-client. I get
On Sat, 13 Sep 2003, masta wrote:
For some time now I've have an issue with a dell laptop I use. It spews a
bunch of kernel junk after init is spawned, and the spew causes my dmesg
to become too full to actually produce a file I can send to the list that
is meaningfull.
I remember this :)
On Sun, 07 Sep 2003 13:01:13 +, Arjan van Leeuwen wrote:
Hi,
Since the ATAng import, I can't use the cd ripper cdparanoia
(audio/cdparanoia) with my IDE CD-ROM drive. When I direct cdparanoia to
device /dev/acd0, it will exit with the message
006: Could not read any data from
It seems Dario Freni wrote:
ata0: resetting devices ..
ata0-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED
done
Does anyone recognize this or have any idea why this happens or how I can
debug it further to get an idea?
The same here (on a workstation) with an
On Friday, 12 September 2003 at 5:10:39 +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], [EMAIL PROTECTED]
ibsd.org writes:
Did you ever consider that your doing exactly what phk's logo protests? ;)
Maybe that is why phk hasn't responded any further, because he's laughing
at
I owe you a beer Doug (or a soda-pop)! ;)
You were correct about the sysctl.conf being the root-cause of the kernel
spew.
My sysctl.conf is having these lines:
#security.bsd.see_other_uids=0
sysctl net.inet.tcp.blackhole=1
sysctl net.inet.udp.blackhole=1
See the fau paux? I must have decided
Can ANYONE out there get a panic dump on an ATA disk with ATAng?
I can't get my 9/9/2003 kernel to dump, nor a current -CURRENT.
Thanks,
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat
mdmfs don't work on CURRENT diskless sparc64:
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point.
Starting file system checks:
nfs: can't update /var/db/mounttab for 1.1.1.1:/sparc64/netboot
cp: utmp: Read-only file system
/etc/rc.d/cleanvar: cannot create
On Sun, 14 Sep 2003 20:08:17 +0200 (CEST)
Soren Schmidt [EMAIL PROTECTED] wrote:
This is with an uptodate -current ?
pigra:/home/saturnero uname -a
FreeBSD pigra.saturnero.sat 5.1-CURRENT FreeBSD 5.1-CURRENT #10:
Mon Sep 8 01:15:32 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PIGRA
V so, 06. 09. 2003 v 21:41, Bruce Evans pe:
On Sat, 6 Sep 2003, Pav Lucistnik wrote:
after recent ATAng changes, cdcontrol close stopped working
with my CD-ROM drive. It used to close the tray. It works with -f
/dev/cd0 but not with /dev/acd0. cdcontrol eject still works fine.
I use
* Deiter Alexandr Valerievich [EMAIL PROTECTED] [2003-09-14 22:10]:
mdmfs: newfs exited with error code 36
This error seems to be generic, I see it on i386 too. I usually
mount /tmp with the following entry from fstab:
md /tmp mfs rw,-s250m 2 0
This gives the newfs error mentioned above.
On Sun, 14 Sep 2003, Pav Lucistnik wrote:
V so, 06. 09. 2003 v 21:41, Bruce Evans pí¹e:
On Sat, 6 Sep 2003, Pav Lucistnik wrote:
after recent ATAng changes, cdcontrol close stopped working
with my CD-ROM drive. It used to close the tray. It works with -f
/dev/cd0 but not with
I can confirm this on i386, and sparc also.
This is a semi-anoying hickup for those who wish to make tiny root-msf
images for a soekris boards, or nfs diskless, and/or mfs-root floppies,
etc.
I belive PHK is/was looking for the root cause of this, which was a thread
that had something to do with
TB --- 2003-09-14 20:08:26 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-09-14 20:08:26 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-14 20:11:56 - building world
TB --- cd
In message: [EMAIL PROTECTED]
Brandon S. Allbery KF8NH [EMAIL PROTECTED] writes:
: On Sat, 2003-09-13 at 18:49, M. Warner Losh wrote:
: and you cannot tell dhclient that interfaces have arrived.
:
: dhclient(8) seems to think otherwise, although it doesn't explain quite
: how (I
It seems Pav Lucistnik wrote:
This patch works for me. Any chance to get it committed?
I'll look at it...
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL
I am having troubles installing -current from JSNAP -current iso images
on my Dell Latitude C600 laptop. Everything is ok when / has not been
set on softupdates, but when softupdates is activated on / (and / is the
only partition besides swap) I get an error during extraction of base.
kernel:
With today's cvsup, I cannot create a md based /tmp. If I run
'mount_mfs -s 512m md /tmp' (what runs from the entry in fstab), it
says:
mount_mfs: newfs exited with error code 36
if I separate the operations, mdconfig runs fine, but newfs says:
/dev/md0: 512.0MB (1048576 sectors) block size
On Sat, Sep 13, 2003 at 03:37:51PM +0100, Stuart Walsh wrote:
On Fri, Sep 12, 2003 at 09:55:54PM -0400, Jung-uk Kim wrote:
I have my own *working* driver, which is for 4-STABLE. It works with
SK-9521 V2.0 (for me, at least) and it should work with 3C940.
Note: This driver is ported
Folks,
I've noted that the following inconsistency exists in make release. If
there is a install.cfg file in /usr/src/release when executing make
release (the file which if exists is placed into the root of mfs and
customises behaviour of sysinstall), /usr/src/release/install.cfg takes
Sep 14 17:46:52 local7.notice target logger: TCP_Wrappers ALLOW:
source/target,rshd,974,[EMAIL PROTECTED]
Sep 14 17:46:52 auth.info target inetd[974]: connection from source, service rshd
(tcp)
Sep 14 17:46:52 auth.info target rshd[974]: [EMAIL PROTECTED] as root: permission
denied
On Sunday, September 14, 2003, at 07:29 PM, [EMAIL PROTECTED]
wrote:
Sep 14 17:46:52 local7.notice target logger: TCP_Wrappers ALLOW:
source/target,rshd,974,[EMAIL PROTECTED]
Sep 14 17:46:52 auth.info target inetd[974]: connection from source,
service rshd (tcp)
Sep 14 17:46:52 auth.info
Yes - rsh target, after enabling login/rlogind ;), gives me a shell
on target. Even after enabling login/rlogind, rsh target command
still fails as outlined below.
On 14 Sep, David Rhodus wrote:
On Sunday, September 14, 2003, at 07:29 PM, [EMAIL PROTECTED]
wrote:
Sep 14 17:46:52
In message [EMAIL PROTECTED], [EMAIL PROTECTED]
writes:
Sep 14 17:46:52 local7.notice target logger: TCP_Wrappers ALLOW: source/tar
get,rshd,974,[EMAIL PROTECTED]
Sep 14 17:46:52 auth.info target inetd[974]: connection from source, servic
e rshd (tcp)
Sep 14 17:46:52 auth.info target
I get the same problem in the same place with current as of today.
Cheers,
Mark
On Sat, 2003-09-13 at 20:37, Matt wrote:
After building world as of late last night I decided to portupgrade
-rRaf, mainly due to having the libintl.so.4 missing problem when I
tried to start X. Everything
On Sun, 14 Sep 2003, masta wrote:
I owe you a beer Doug (or a soda-pop)! ;)
hehe :)
You were correct about the sysctl.conf being the root-cause of the kernel
spew.
Mike Smith ran into it one day and we spent some time debugging it.
Someone made the observation that they were sysctl items
51 matches
Mail list logo
