I was hoping that someone might have an idea, as
I've exhausted all of mine for the time being.
Boot0 is just a boot menu whose contents are in sector0 of your
hard disk. Another boot block (most likely the contents of
boot1) should located at or near the beginning of
your freebsd slice.
Harald Schmalzbauer wrote:
Bob Bishop wrote:
See
http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/developers-han
dbook/kerneldebug.html,
particularly 17.4 and 17.5
Thank you for that link, but that's far too complicated for me. I don't know
any of these gdb commands, I can just
Hi,
Somewhere along the line the code in FreeBSD that maps irq 2 to irq 9 has
gone away and a panic was added if one tries to use irq 2. This is all
well and fine, except that the pnp code was not notified of this. :-) So
if you have a pnp device that have irq 2 in its mask and FreeBSD then
I own an Abit IS7-G which includes an intergrated 3Com 3C940 card
currently not supported in any FreeBSD branch to my knowledge. Some
people said that the nic could world with the Tigon III driver but I
haven't been able to get it to work with it during install. Are there
any plans or
Hi all,
I'm not sure if this is a real problem or not, but if I set a group
ACL on a file, and then set a mask, when running getfacl the group names
are not listed.
I'm running 5.1 RELEASE.
The following sequence commands show the problem (I create a file, display
the ACL, set a group ACL,
Whoops - it helps if I attach the patch :)
Glen
-- Forwarded message --
Date: Thu, 24 Jul 2003 16:54:55 +1000 (EST)
From: Glen Gibb [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Possible problem with ACL masks and getfacl
Hi all,
I'm not sure if this is a real problem or
Hi all, a few weeks back I had asked whether -current supported ICH5's S-ATA
and Søren stated that he'd put code in to detect it and it should work but
there wasn't a lot of feedback yet from users. Well, I have some feedback. I
just got a new spiffy 120Gb Seagate S-ATA drive today and I can say
On Wed, Jul 23, 2003 at 10:13:20PM -0400, Garance A Drosihn wrote:
At 8:14 PM -0400 7/23/03, Garance A Drosihn wrote:
So indeed, that 'make depend' had not finished before
the 'make' for the object had started.
I was going to do some debugging of what 'make' is doing, but
it looks like
On Wed, Jul 23, 2003 at 02:48:41PM -0700, Julian Elischer wrote:
+ I'd like to have a suptr and fuptr to be able to save and read
+ user pointers in a machine independent manner..
+ at the moment ia need to know the size of a pointer and select the
+ appropriate 32 or 64 version.. It would jus tbe
Julian Elischer wrote:
I'd like to have a suptr and fuptr to be able to save and read
user pointers in a machine independent manner..
at the moment ia need to know the size of a pointer and select the
appropriate 32 or 64 version.. It would jus tbe another ENTRY files in
support.[sS]
Marcel Moolenaar wrote:
for i386 it would be an alternate name for fuword32() and suword32()
I'm not sure what it would be on other architectures
fuword64 and suword64. PowerPC is like i386.
PPC 970 explicitly supports mixed mode programming between user
and kernel, as do most other 64
Hi Bosko,
Well I went to go change my /boot/loader.conf options to reflect the
following:
kern.vm.kmem.size=35
kern.ipc.nmbclusters=8192
and enabled options DDB in my kernel.
Unfortunately, I ran into a problem on the reboot, the SMP kernel would fail
to load due to some of my
Thanks for getting back to me regarding that point Scott.
I recently realized that I was miss-understanding how much free memory I had
on the system, and I doubt I even need the full 4Gig's.
Perhaps I can re-confirm how to check how much free real memory is available
on the system.
Looking at
It seems John Reynolds wrote:
Hi all, a few weeks back I had asked whether -current supported ICH5's S-ATA
and Søren stated that he'd put code in to detect it and it should work but
there wasn't a lot of feedback yet from users. Well, I have some feedback. I
just got a new spiffy 120Gb Seagate
Hi there!
There's currently an inconsistency in how various makefiles
(that use crypto bits) check if these bits are available.
All of them check for the NOCRYPT knob, and some of them
also check if src/crypto/ exists, and some not. None of
them also check if src/secure/ exists, which is the
atapci1: Intel ICH5 SATA150 controller port
0xd000-0xd00f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007
irq 9 at device 31.2 on pci0
...
ata2: at 0xc000 on atapci1
ad4: success setting UDMA133 on Intel ICH5 chip
ad4: ST3120023AS/3.01 ATA-6 disk at ata2-master
ad4: 114473MB
Hi,
Not sure if this is useful, but I'm getting a perfectly reproducible
panic when doing 'grep -R foo .' (as normal user) in a read-only
mounted ntfs partition on a -current as of ~3 weeks ago:
Good dump found on device /dev/ad0s2b
Architecture: i386
Architecture version: 1
Dump length:
Yeah. My drive shows up as UDMA133 also. What I did notice is that
my WD Raptor was slightly outperformed a few times on UFS2 by
my actual
ATA-100 Western Digital drive. This seems somewhat bad as the Raptor
costs a hell of a lot more and one would hope that it would pound the
ATA-100
helo.
ata-disk.c
/* use tagged queueing if allowed and supported */
#if 0 /* disable tags for now */
if (ata_tags ad_tagsupported(adp)) {
adp-num_tags = atadev-param-queuelen;
adp-flags |= AD_F_TAG_ENABLED;
adp-device-channel-flags |= ATA_QUEUED;
if
On Thu, 2003-07-24 at 03:40, Terry Lambert wrote:
It's actually unlikely that IBM will ever release enough documentation
to get a full 64 bit Linux running on a PPC 970, let alone FreeBSD,
and that you will be stuck with a 32 bit kernel that runs 64 bit apps,
and which talks to IBM's internal
It seems mitrohin a.s. wrote:
ata-disk.c
/* use tagged queueing if allowed and supported */
#if 0 /* disable tags for now */
if (ata_tags ad_tagsupported(adp)) {
adp-num_tags = atadev-param-queuelen;
adp-flags |= AD_F_TAG_ENABLED;
adp-device-channel-flags |=
Hello.
I've found deadlock in gbde(4) and/or md(4).
Here is a complete procedure hot to repeat it:
# touch /mnt/test.file
# mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1
# mkdir /etc/gbde
# gbde init /dev/md1 -L /etc/gbde/md1
Enter new passphrase:
On Thursday 24 July 2003 07:53 am, [EMAIL PROTECTED] wrote:
Hello again!
Sorry for trolling.
I have just found one more way to have X and seculevel coexisting.
It's applicable for desktops mostly.Here's the trick:
Start the system with seculevel -1, run startx and then type
'/sbin/sysctl -w
mitrohin a.s. wrote:
helo.
ata-disk.c
/* use tagged queueing if allowed and supported */
#if 0 /* disable tags for now */
if (ata_tags ad_tagsupported(adp)) {
adp-num_tags = atadev-param-queuelen;
adp-flags |= AD_F_TAG_ENABLED;
adp-device-channel-flags |=
On Thu, Jul 24, 2003 at 03:57:07PM +0200, Pawel Jakub Dawidek wrote:
+ I've found deadlock in gbde(4) and/or md(4).
Yes, it is gbde fault:
db show lockedvnods
[...]
0xc3332920: tag ufs, type VREG, usecount 1, writecount 0, refcount 21, flags
(VV_OBJBUF), lock type
ufs: EXCL (count 1) by thread
On Thu, Jul 24, 2003 at 03:26:53PM +0200, Soeren Schmidt wrote:
It seems mitrohin a.s. wrote:
ata-disk.c
/* use tagged queueing if allowed and supported */
#if 0 /* disable tags for now */
if (ata_tags ad_tagsupported(adp)) {
adp-num_tags = atadev-param-queuelen;
On Thu, Jul 24, 2003 at 04:08:01PM +0200, Marcin Dalecki wrote:
tagged queueing broken in -current? i have IBM ICxAV drives and want
to use this feature. can i enable this block?
Don't. It's very frequently broken by *hardware* and not worth the trouble
in terms of performance.
hmm...
In message [EMAIL PROTECTED], Pawel Jakub Dawidek writ
es:
On Thu, Jul 24, 2003 at 03:57:07PM +0200, Pawel Jakub Dawidek wrote:
+ I've found deadlock in gbde(4) and/or md(4).
Yes, it is gbde fault:
I don't know what you have found, but I can guarantee you that it is
_not_ gbde that holds
In message [EMAIL PROTECTED], Pawel Jakub Dawidek writ
es:
# touch /mnt/test.file
You are probably missing:
dd if=/dev/null of=/mnt/test.file bs=1m count=512
# mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1
What you have found has nothing to do with GBDE, I think it
It seems mitrohin a.s. wrote:
On Thu, Jul 24, 2003 at 04:08:01PM +0200, Marcin Dalecki wrote:
tagged queueing broken in -current? i have IBM ICxAV drives and want
to use this feature. can i enable this block?
Don't. It's very frequently broken by *hardware* and not worth the trouble
I am using login.conf to set a minimul password length in the default class
and root class, after adding :minpasswordlen=8: to default and
:minpasswordlen=11: to root and then running
$ cap_mkdb /etc/login.conf
I can still use a password of 1 character. This is on FreeBSD 5.1-RELEASE
i386. I
Michael Carlson wrote:
I am using login.conf to set a minimul password length in the default
class and root class, after adding :minpasswordlen=8: to default and
:minpasswordlen=11: to root and then running
$ cap_mkdb /etc/login.conf
I can still use a password of 1 character. This is on
Michael Carlson wrote:
I am using login.conf to set a minimul password length in the default
class and root class, after adding :minpasswordlen=8: to default and
:minpasswordlen=11: to root and then running
$ cap_mkdb /etc/login.conf
I can still use a password of 1 character. This is on
Occasionally, one of my systems gets rpc.lockd stuck using all of the
CPU cycles. I fix it by running '/etc/rc.d/nfslocking restart'. That
works but it shows there is a syntax error somewhere. Here is the
output that I get:
[: checkyesno: unexpected operator
Stopping statd.
[: checkyesno:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Pawel Jakub Dawidek writ
es:
# touch /mnt/test.file
You are probably missing:
dd if=/dev/null of=/mnt/test.file bs=1m count=512
# mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1
What you have found has nothing to do with GBDE, I
Thanks! I just committed a fix (reproduced here for
your convenience).
Cheers.
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9
[EMAIL PROTECTED]| FreeBSD - Unleash the Daemon!
Index: etc/rc.subr
On Thu, Jul 24, 2003 at 05:03:23PM +0200, Poul-Henning Kamp wrote:
+ # touch /mnt/test.file
+
+ You are probably missing:
+
+ dd if=/dev/null of=/mnt/test.file bs=1m count=512
You mean /dev/zero? But this doesn't change anything.
+ # mdconfig -a -t vnode -f /mnt/test.file -s 512M
At 12:44 AM -0700 7/24/03, Gordon Tetlow wrote:
On Wed, Jul 23, 2003 at 10:13:20PM -0400, Garance A Drosihn wrote:
I was going to do some debugging of what 'make' is doing,
but it looks like crunchgen gets confused if make has any
kind of debugging flags turned on.
I just committed 1.14 of
In message [EMAIL PROTECTED], Pawel Jakub Dawidek writ
es:
+ dd if=3D/dev/null of=3D/mnt/test.file bs=3D1m count=3D512
You mean /dev/zero? But this doesn't change anything.
Yes, /dev/zero of course.
+# mdconfig -a -t vnode -f /mnt/test.file -s 512M -u 1
+=20
+ What you have found has
On Wed, Jul 23, 2003 at 11:00:18AM -0700, John-Mark Gurney wrote:
Please provide more information, such as dmesg including the controller
you are using. Also, you don't state if this is USB2.0 device or a
USB1.1 device. This makes it hard to debug and understand.
Also, I would recomment
On Wed, Jul 23, 2003 at 07:07:30PM +0300, Ruslan Ermilov wrote:
On Wed, Jul 23, 2003 at 11:57:58AM -0400, Jake Burkholder wrote:
Apparently, On Wed, Jul 23, 2003 at 09:16:43AM +0300,
Ruslan Ermilov said words to the effect of;
A similar change would be in order for sparc64. Patch
On Thu, Jul 24, 2003 at 08:38:02PM +0200, Poul-Henning Kamp wrote:
+ + What you have found has nothing to do with GBDE, I think it is the
+ + usual vnode backed md(4) deadlock.
+
+ Hmm? So you're trying to tell that this is somehow normal behaviour?
+
+ We've had problems like this before with
Garance A Drosihn wrote:
Wed Jul 23 20:08:06 EDT 2003 Starting make depend
in /usr/obj/usr/src/rescue/rescue/usr/src/gnu/usr.bin/gzip
Wed Jul 23 20:08:07 EDT 2003 Finished make depend
in /usr/obj/usr/src/rescue/rescue/usr/src/gnu/usr.bin/gzip
Wed Jul 23 20:08:09 EDT 2003 Starting make
Hi,
I have 160Mb of SDRAM (PC100) on a 233Mhz CyrixInstead machine and I seem to
have memory mangament problems. The BIOS indicates I have 160, so does the
BSD bootstrap program.
When I launch GNOME 2.2 everythings is good as gold untill I open the System
monitor program. It says that I have 149
Hi,
I have 160Mb of SDRAM (PC100) on a 233Mhz CyrixInstead machine and I
seem to have memory mangament problems. The BIOS indicates I have 160,
so does the BSD bootstrap program.
When I launch GNOME 2.2 everythings is good as gold untill I open the
System monitor program. It says that I have 149
Ahmed Al-Hindawi wrote:
Hi,
I have 160Mb of SDRAM (PC100) on a 233Mhz CyrixInstead machine and I
seem to have memory mangament problems. The BIOS indicates I have 160,
so does the BSD bootstrap program.
When I launch GNOME 2.2 everythings is good as gold untill I open the
System monitor program.
In message [EMAIL PROTECTED], Pawel Jakub Dawidek writ
es:
+ One way or another: It is _not_ a GBDE problem.
Hey, Poul! I'm not trying to show that gbde(4) is a buggy software,
I'm not trying to destroy you work, your image or FreeBSD, really.
I believe that this isn't bug in gbde(4), my
On Thu, 24 Jul 2003 15:53:21 -0400, Bill Moran [EMAIL PROTECTED]
wrote:
Ahmed Al-Hindawi wrote:
Hi,
I have 160Mb of SDRAM (PC100) on a 233Mhz CyrixInstead machine and I
seem to have memory mangament problems. The BIOS indicates I have 160,
so does the BSD bootstrap program.
When I launch GNOME
At 12:12 PM -0700 7/24/03, Tim Kientzle wrote:
Garance A Drosihn wrote:
So indeed, that 'make depend' had not finished before the
'make' for the object had started.
There's another possibility here: suppose two copies
of make are running simultaneously and both get to
this sequence at about the
Jeremy Messenger wrote:
On Thu, 24 Jul 2003 15:53:21 -0400, Bill Moran
[EMAIL PROTECTED] wrote:
Ahmed Al-Hindawi wrote:
Hi,
I have 160Mb of SDRAM (PC100) on a 233Mhz CyrixInstead machine and I
seem to have memory mangament problems. The BIOS indicates I have 160,
so does the BSD bootstrap
On Thu, Jul 24, 2003 at 11:55:10AM -0700, David O'Brien wrote:
On Wed, Jul 23, 2003 at 07:07:30PM +0300, Ruslan Ermilov wrote:
On Wed, Jul 23, 2003 at 11:57:58AM -0400, Jake Burkholder wrote:
Apparently, On Wed, Jul 23, 2003 at 09:16:43AM +0300,
Ruslan Ermilov said words to the effect
On Thu, 24 Jul 2003 16:46:12 -0400, Bill Moran [EMAIL PROTECTED]
wrote:
Jeremy Messenger wrote:
On Thu, 24 Jul 2003 15:53:21 -0400, Bill Moran
[EMAIL PROTECTED] wrote:
Ahmed Al-Hindawi wrote:
Hi,
I have 160Mb of SDRAM (PC100) on a 233Mhz CyrixInstead machine and I
seem to have memory
On Thu, 24 Jul 2003, Glen Gibb wrote:
Whoops - it helps if I attach the patch :)
Glen,
This looks good to me -- I've committed the patch. If you pick up
acl_to_text.c:1.11, it should have it. Let me know if there are any
problems.
Robert N M Watson FreeBSD Core Team,
Attached is a patch that disables ever sending 6 byte commands to buses
that do not support them. Numerous USB devices hang when receiving a 6
byte command. For testing, this patch comments out the scsi_da quirks for
devices that I believe are addressed by this patch and no longer need the
On Thu, Jul 24, 2003 at 02:14:20PM +0200, Karel J. Bosschaart wrote:
Not sure if this is useful, but I'm getting a perfectly reproducible
panic when doing 'grep -R foo .' (as normal user) in a read-only
mounted ntfs partition on a -current as of ~3 weeks ago:
[...]
Panicstring: bundirty:
On Wed, 23 Jul 2003, Kevin Oberman wrote:
From: Matthew Emmerton [EMAIL PROTECTED]
Date: Wed, 23 Jul 2003 18:21:23 -0400
The folks at Broadcom have not been willing to release any information
on their 800.11g chips for fear of violating FCC regs. The required
NDA would prohibit the
In message: [EMAIL PROTECTED]
Chris BeHanna [EMAIL PROTECTED] writes:
: Can't they just redact that information from the spec.?
Typically no. Even in a redacted spec it would be painfully obvious
what to do. Also, different regulatory domains have different
frequencies that are
On Thu, Jul 24, 2003, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Chris BeHanna [EMAIL PROTECTED] writes:
: Can't they just redact that information from the spec.?
Typically no. Even in a redacted spec it would be painfully obvious
what to do. Also, different
58 matches
Mail list logo
