> On 2009-06-30, Mike Andrews wrote:
> > Jaakko Heinonen wrote:
> > > On 2009-06-30, Danny Braniss wrote:
> > >> This pr is realy holding me back, I can't upgrade this server, and
> > >> telling serveral tens of users to us cp, etc is not an option.
hi,
This pr is realy holding me back, I can't upgrade this server, and
telling serveral tens of users to us cp, etc is not an option. The open
works fine if not using O_EXCL.
Thanks,
danny
___
freebsd-stable@freebsd.org mailing list
ht
> > I'm not 100% sure, but fairly sure that you'll have a hard time
> > finding something that combines the low-power standalone type spec with
> > a 64-bit capable processor. Once you get the higher-end processor,
>
> That was my experiense when shopping around yes - annoying as I
> don't need
> On Fri, Jun 12, 2009 at 10:57:42AM +0300, Danny Braniss wrote:
> > latest -stable (June 11) is causing problems:
> > MB is intel SE7320VP21,
> >
> > msk0: Ethernet address: 00:0e:0c:6a:85:a8
> > miibus0: on msk0
> > e1000phy0: PHY 0 on miibus0
> >
latest -stable (June 11) is causing problems:
MB is intel SE7320VP21,
msk0: Ethernet address: 00:0e:0c:6a:85:a8
miibus0: on msk0
e1000phy0: PHY 0 on miibus0
e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
msk0: watchdog timeout (missed Tx interrupts)
hi,
sporadically, I see this:
lockmgr: thread 0xff0004a8b390 unlocking unheld lock
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_lockmgr() at _lockmgr+0x6ae
VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46
unionfs_unlock() at unionfs_unlock+0x22f
VOP_UNLOCK_APV()
> Hello,
>
> I encounter this problem for the second time. The system is working
> perfectly well but suddenly the command `zfs list' don't work and can't
> be killed.
>
> Here is a procstat of the culprit:
>
> [r...@morzine ~]# procstat -k 91766
>PIDTID COMM TDNAME
hi,
Since I saw some activity, I decided to try out my msks,
so the Yukon 88E8050 on my Intel SE7320VP21 now works with
hw.msk.legacy_intr=0
which didn't before (sorry, but the best I can say is 'long time ago' ;-)
on an Asus P5K-VM with Yukon 88E8056, it panics when used to PXE bo
> I will be MFC'ing the newer ZFS support some time this afternoon. Both
> world and kernel will need to be re-built. Existing pools will
> continue to work without upgrade.
>
>
> If you choose to upgrade a pool to take advantage of new features you
> will no longer be able to use it with sources
> * Danny Braniss [2009-04-08 15:54:25 +0300]:
>
> >
> > > Garance A Drosihn wrote:
> > > > Some friends of mine are looking at the new "DroboPro", which makes a
> > > > lot of disk space available via iSCSI (in addition to firewire 800
> Danny Braniss wrote:
> >> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> >> --enig90DADA8437A99D893FB775F8
> >> Content-Type: text/plain; charset=3DUTF-8
> >> Content-Transfer-Encoding: quoted-printable
> >>
> >
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --enig90DADA8437A99D893FB775F8
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> Danny Braniss wrote:
> >> Garance A Drosihn wrote:
> >>>
> Garance A Drosihn wrote:
> > Some friends of mine are looking at the new "DroboPro", which makes a
> > lot of disk space available via iSCSI (in addition to firewire 800),
> > and they were wondering how well iSCSI works with FreeBSD. I haven't
> > paid attention to iSCSI support. Is there any
Hi Xin LI,
> (It would be probably good idea to redirect this discussion to -stable@,
> redirected)
>
ok by me.
> Hi, Danny,
>
> Danny Braniss wrote:
> > It's no longer working (for me) under 7.2, and so far
> > I am not getting any feedback, so since it seem
> Danny Braniss danny at cs.huji.ac.il writes:
> > at least for me :-)
> > [and sorry for the cross posting]
> >
> [...]
> >
> > amr0: mem
> > 0xfbef-0xfbef,0xfe58-0xfe5f
> > irq 27 at device 0.0 on pci4
> > amr0: [ITHREAD]
&
> Danny Braniss wrote:
> >> Danny Braniss wrote:
> >>> it seems March 12 was a bit off :-)
> >>> it took some time, but I managed to close the gap:
> >>> 189100 ok
> >>> 189150 fails
> >>> I will continue tomorrow, but t
> Danny Braniss wrote:
> > it seems March 12 was a bit off :-)
> > it took some time, but I managed to close the gap:
> > 189100 ok
> > 189150 fails
> > I will continue tomorrow, but this should be helpful.
> >
> >
>
> 189150 is in
> Danny Braniss wrote:
> >> Danny Braniss wrote:
> >>> at least for me :-)
> >>> [and sorry for the cross posting]
> >>>
> >>> old (March 12 , i know need the svn rev number but...)
> >> None of the commit activity on March 12
>
> Due to an issue I'm having with 7.x, and trying to track it down, I spent
> tonight getting my server setup to allow my to break into the debugger
> when it hangs, and hopefully dump core ...
>
> But, although I *think* I've got it all, I'm obviously missing something,
> as it isn't breaki
> Danny Braniss wrote:
> > at least for me :-)
> > [and sorry for the cross posting]
> >
> > old (March 12 , i know need the svn rev number but...)
>
> None of the commit activity on March 12 is jumping out at me as being
> suspicious. However, you are n
at least for me :-)
[and sorry for the cross posting]
old (March 12 , i know need the svn rev number but...)
dmesg | grep amr
amr0: mem 0xfbef-0xfbef,0xfe58-0xfe5f
irq 27 at device 0.0 on pci4
amr0: [ITHREAD]
amr0: delete logical drives supported by controller
amr0: Firmware 414
Hi,
After turning debuging on, it seems that the iir driver
is loosing an interrupt while probing:
...
gdt_next(0xc7666000)
gdt_mpr_test_busy(0xc7666000) gdt_intr(0xc7666000)
gdt_mpr_get_status(0xc7666000) gdt_mpr_intr(0xc7666000)
gdt_free_ccb(0xc7666000, 0xc767e444)
gdt_sync_event(0xc7666000, 3,
> Daniel O'Connor ÎÁÐÉÓÁ×(ÌÁ):
>
> On Tuesday 24 March 2009 11:55:07 Mikhail T. wrote:
>
>
> >> I'm trying to migrate a filesystem from one disk to another using:
> >>
> >> dump a0hCf 0 32 - /old | restore -rf -
> >>
> >> (/old is already mounted read-only). The process runs for a while an
Hi,
after upgrading to 7.2, booting the kernel gets stuck with:
run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config
from a 7.1 dmesg, it seems that it's in the iir driver.
danny
___
freebsd-stable@freebsd.org mailing list
http
> On Sun, Mar 22, 2009 at 03:10:07PM +0200, Mikolaj Golub wrote:
> >
> > On Sun, 22 Mar 2009 12:55:02 +0200 Danny Braniss wrote:
> >
> > DB> Hi,
> > DB> between March 16 and now, bge on a Sun X2200 stopped working,
> > DB> turning o
Hi,
between March 16 and now, bge on a Sun X2200 stopped working,
turning off msi (via hw..pci.enable_msi=0) got it working again.
I tried first replacing bge with an older version but that did not help.
please advice :-)
Danny
___
freebsd-stab
> > Now istgt is a part of ports. (net/istgt)
> > FreeBSD issue is solved by danny's patch.
> > After applying the patch, iscontrol can connect to istgt.
>
> I am interested in giving this a try, though not immediately as I
> am away from the office at the moment. Do I need to apply a patch
> to i
> On 12.02.2009 3:12 Uhr, SDH Support wrote:
> >
> >
> >> Yes, if you have (or plan to have) more than 3 GB of memory.
> >
> >
> > FYI I have had a lot of problems with FBSD7.x and HP DL-series hardware +
> > amd64. There is a bug IIRC in the loader.
> >
> >
>
> I had problems with DL3X0G5 when b
>
> On Sun, 8 Feb 2009, Danny Braniss wrote:
>
> >> On Sun, 8 Feb 2009, Danny Braniss wrote:
> >>
> >>> looking at the bce source, it's not clear (to me :-). If errors are
> >>> detected in bce_rx_intr(), the packet gets dropped, which
>
> On Sun, 8 Feb 2009, Danny Braniss wrote:
>
> > looking at the bce source, it's not clear (to me :-). If errors are
> > detected
> > in bce_rx_intr(), the packet gets dropped, which I would expect to be the
> > treatment of an offloded chekcum er
> On Sun, 8 Feb 2009, Peter Jeremy wrote:
>
> > On 2009-Feb-08 11:31:45 +0200, Danny Braniss wrote:
> >> Q: with rxcsum on, and a bad checksum packet is received, is it
> >> dropped by the NIC? if not, then it somewhat explains the behaviour
> >
> > I
>
> --jI8keyz6grp/JLjh
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On 2009-Feb-08 10:45:13 +0200, Danny Braniss wrote:
> >Feb 6 18:00:13 warhol-00.cs.huji.ac.il kernel: bce0: disc
I'm reposting this to hackers, and there is some more info.
> Hi,
> on 2 different servers, running 7.1-stable + zfs, I get this
> error rather frequently:
>
> Feb 5 17:01:03 warhol-00 kernel: impossible packet length (543383918) from
> nfs server sunfire:/dist
> Feb 5 17:01:03 warhol-00 kerne
> On 2009-Feb-06 08:32:27 +0200, Danny Braniss wrote:
> >on 2 different servers, running 7.1-stable + zfs, I get this
> >error rather frequently:
> >
> >Feb 5 17:01:03 warhol-00 kernel: impossible packet length (543383918) fro=
> m=20
> >nfs server sunfire
Hi,
on 2 different servers, running 7.1-stable + zfs, I get this
error rather frequently:
Feb 5 17:01:03 warhol-00 kernel: impossible packet length (543383918) from
nfs server sunfire:/dist
Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1936028704) from
nfs server sunfire:/dist
Feb
> As a general note, this is the second time in a row that an X.org
> upgrade broke X for a significant number of people. IMO, this
> suggests that our approach to X.org upgrades needs significant changes
> (see below). X11 is a critical component for anyone who is using
> FreeBSD as a desktop a
> On Fri, Jan 09, 2009 at 01:48:24PM +0200, Danny Braniss wrote:
> > hi, the mb is asus P5K-VM, the onboard nic is, acccording to pciconf:
> >
> > ms...@pci0:1:0:0: class=0x02 card=0x81f81043 chip=0x436411ab
> > rev=0x12 hdr=0x00
> > vendor
> On Fri, Jan 09, 2009 at 01:48:24PM +0200, Danny Braniss wrote:
> > hi, the mb is asus P5K-VM, the onboard nic is, acccording to pciconf:
> >
> > ms...@pci0:1:0:0: class=0x02 card=0x81f81043 chip=0x436411ab
> > rev=0x12 hdr=0x00
> > vendor
hi, the mb is asus P5K-VM, the onboard nic is, acccording to pciconf:
ms...@pci0:1:0:0: class=0x02 card=0x81f81043 chip=0x436411ab
rev=0x12 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = '88E8056 Yukon PCI-E Gigabit Ethernet Controller'
> On Mon, Jan 05, 2009 at 08:23:53PM +0100, Oliver Fromme wrote:
> >
> > This seems to be a bug in dumpfs(8). It simply prints
> > the value of the fs_size field of the superblock, which
> > is wrong.
> >
> > The -s option of newfs(8) expects the available size in
> > sectors (i.e. 512 bytes), b
> On Sat, Dec 27, 2008 at 01:03:54PM +0200, Danny Braniss wrote:
> > well, I'm running 7.1-PRERELEASE, what does the amd logs show?
> ..
> > Dec 27 10:37:01 sf-02 amd[856]: am-utils version 6.1.5 (build 1).
> > Dec 27 10:37:01 sf-02 amd[856]: Report bugs to
>
> I got "Couldn't lock process pages in memory using mlockall()" too:
[...]
> On Sat, Dec 27, 2008 at 9:07 PM, Rong-en Fan wrote:
> > On Sat, Dec 27, 2008 at 7:03 PM, Danny Braniss wrote:
> >>> No, we do not running amd with -S.
> >>>
> &
Dec 27 10:37:01 sf-02 amd[856]: My ip addr is 127.0.0.1
Dec 27 10:37:01 sf-02 amd[857]: released controlling tty using setsid()
Dec 27 10:37:01 sf-02 amd[857]: Locked process pages in memory
**
>
> On Sat, Dec 27, 2008 at 4:51 PM, Da
> Yes, we found that it crashes when swap is used.
on an amd64 architecture, amd could not plock it's pages in memory, and would,
under memory preasure be swapped out, and break.
I just run some tests under 7.1-PRERELEASE, and
- it seems that plock is working.
- amd is not being swapped out.
are y
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi, Nawfal,
>
> Nawfal bin Mohmad Rouyan wrote:
> > I have been using a Dell machine with 2 bce interfaces as a bridge
> > between my LAN and Firewall to shape the traffic. Since after the
> > update, the machine can only run for a few minutes
Hi,
I'm trying to tar a rather big directory via nfs (some 800gb), it
has many subdirectories, some of them with many files (close to 10^6 :-)
just before the server panics, the tar (on the client) starts complaining
about lost
files, or permition denied, but not in the pathological directories.
> This is a multi-part message in MIME format.
> --070205030901020808000803
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Danny Braniss wrote:
> > Hi,
>
Hi,
After changing cables,switches,ports, I came to the conclusion
that bce is reporting input errors that are not there, or creating them.
I checked this with 3 different boxes, all Dell-2950/Broadcom NetXtreme II
BCM5708 1000Base-T (B2), and one of them, while running Solaris, reported
0
> >
> > Hi,
> >
> > On 2008-12-10, Danny Braniss wrote:
> > > from a solaris or linux client, doing a ls(1) of a nfs exported zfs
> > > file,
> > > for example: ls /net/zfs-server/h/.zfs/snapshot,
> > > panics the server. The ser
>
> Hi,
>
> On 2008-12-10, Danny Braniss wrote:
> > from a solaris or linux client, doing a ls(1) of a nfs exported zfs
> > file,
> > for example: ls /net/zfs-server/h/.zfs/snapshot,
> > panics the server. The server is running latest 7.1-prerelease.
&g
hi,
from a solaris or linux client, doing a ls(1) of a nfs exported zfs
file,
for example: ls /net/zfs-server/h/.zfs/snapshot,
panics the server. The server is running latest 7.1-prerelease.
when client is freebsd, it mostly works, but in a few cases
the server just goes into comma
> Can someone please confirm or rule out my issue with dhclient sending
> bad IP checksum packets. It would really suck if 7.1 was released with a
> broken DHCP client.
>
I've had many problems lately, but none involved checksum nor the dhcpd
(btw, I assume that you are seeing bad checksum on th
latest pxeboot (7.1):
mother-boardNIC/LOM CPU
- --- ---
Intel SWV25 em xeonworks fine
SUN X2200bgeamd works fine
DELL PE 2950 bcexeonfailes 95% of the times
> Hi,
> i finally decided to try and use pxeboot to replace the etherboot
> method I was using so far for diskless setups.
>
> The goal is to fully share the server's root and /usr directories,
> as documented in diskless(8). I'd like to share the following
> notes, hopefully to go in the manpage.
>
> On Sat, 4 Oct 2008, Danny Braniss wrote:
>
> > at the moment, the best I can do is run it on a different hardware that has
> > if_em, the results are in
> > ftp://ftp.cs.huji.ac.il/users/danny/lock.prof/7.1-1000.em the
> > benchmark ran better with t
>
> On Fri, 3 Oct 2008, Danny Braniss wrote:
>
> >> On Fri, 3 Oct 2008, Danny Braniss wrote:
> >>
> >>> gladly, but have no idea how to do LOCK_PROFILING, so some pointers would
> >>> be helpfull.
> >>
> >> The LOCK_PROF
>
> On Fri, 3 Oct 2008, Danny Braniss wrote:
>
> > gladly, but have no idea how to do LOCK_PROFILING, so some pointers would
> > be
> > helpfull.
>
> The LOCK_PROFILING(9) man page isn't a bad starting point -- I find that the
> defaults work fine
forget it about LOCK_PROFILING, I'm RTFM now :-)
though some hints on values might be helpful.
have a nice weekend,
danny
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
>
> On Fri, 3 Oct 2008, Danny Braniss wrote:
>
> >> OK, so it looks like this was almost certainly the rwlock change. What
> >> happens if you pretty much universally substitute the following in
> >> udp_usrreq.c:
&g
>
> On Fri, 3 Oct 2008, Danny Braniss wrote:
>
> >>> it more difficult than I expected.
> >>> for one, the kernel date was missleading, the actual source update is the
> >>> key, so
> >>> the window of changes is now 28/July to 19/Aug
> > it more difficult than I expected.
> > for one, the kernel date was missleading, the actual source update is the
> > key, so
> > the window of changes is now 28/July to 19/August. I have the diffs, but
> > nothing
> > yet seems relevant.
> >
> > on the other hand, I tried NFS/TCP, and there t
> > it more difficult than I expected.
> > for one, the kernel date was missleading, the actual source update is the
> > key, so
> > the window of changes is now 28/July to 19/August. I have the diffs, but
> > nothing
> > yet seems relevant.
> >
> > on the other hand, I tried NFS/TCP, and there t
> > On Fri, 26 Sep 2008, Danny Braniss wrote:
> >
> > > after more testing, it seems it's related to changes made between Aug 4
> > > and
> > > Aug 29 ie, a kernel built on Aug 4 works fine, Aug 29 is slow. I'l now
> > > try
>
> On Fri, 26 Sep 2008, Danny Braniss wrote:
>
> > after more testing, it seems it's related to changes made between Aug 4 and
> > Aug 29 ie, a kernel built on Aug 4 works fine, Aug 29 is slow. I'l now try
> > and close the gap.
>
> I think this is
> --==_Exmh_1222467420_5817P
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> David,
>
> You beat me to it.
>
> Danny, read the iperf man page:
>-b, --bandwidth n[KM]
> set target bandwidth to n bits/sec (default 1 Mbit/sec). This
>
>
> :>-vfs.nfs.realign_test: 22141777
> :>+vfs.nfs.realign_test: 498351
> :>
> :>-vfs.nfsrv.realign_test: 5005908
> :>+vfs.nfsrv.realign_test: 0
> :>
> :>+vfs.nfsrv.commit_miss: 0
> :>+vfs.nfsrv.commit_blks: 0
> :>
> :> changing them did nothing - or at least with respec
> On Fri, Sep 26, 2008 at 12:27:08PM +0300, Danny Braniss wrote:
> > > On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
> > > > Hi,
> > > > There seems to be some serious degradation in performance.
> > > > Under 7.0 I get abou
> On Fri, 2008-09-26 at 10:04 +0300, Danny Braniss wrote:
> > Hi,
> > There seems to be some serious degradation in performance.
> > Under 7.0 I get about 90 MB/s (on write), while, on the same machine
> > under 7.1 it drops to 20!
> > Any ideas?
>
> The
> On Fri, Sep 26, 2008 at 12:27:08PM +0300, Danny Braniss wrote:
> > > On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
> > > > Hi,
> > > > There seems to be some serious degradation in performance.
> > > > Under 7.0 I get abou
> On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
> > Hi,
> > There seems to be some serious degradation in performance.
> > Under 7.0 I get about 90 MB/s (on write), while, on the same machine
> > under 7.1 it drops to 20!
> > Any ideas?
&g
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to 20!
Any ideas?
thanks,
danny
___
freebsd-stable@freebsd.org mailing list
http://li
> On Sat, Sep 20, 2008 at 08:05:33AM -0700, Jeremy Chadwick wrote:
> > On Sat, Sep 20, 2008 at 09:45:10AM -0500, Bob Willcox wrote:
> > > On Sat, Sep 20, 2008 at 07:04:56AM -0700, Jeremy Chadwick wrote:
> > > > On Sat, Sep 20, 2008 at 08:24:29AM -0500, Bob Willcox wrote:
> > > > > > 1) It would be
> Danny,
>
> Thanks for the suggestion, but my system is a P-III so there is only one
> CPU. At 1GHz, I think that this easily qualifies as an "older, slower,
> non-smp host".
I just tried it on a GEODE/7.0 stable - slower than a P-III :-), and
dump went smoothly so, to help isolate the problem,
take a look at:
http://www.freebsd.org/cgi/query-pr.cgi?pr=117603
danny
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> FreeBSD 7.0
>
> I have 2 machines with identical configurations/hardware, let's call them A
> (master)
> and B (slave). I have installed iscsi-target from ports and have set up 3
> targets
> representing the 3 drives I wish to be connected to from A.
>
> The Targets file:
> # extents
> hi,
> latest changes in dev/ata broke this, on older -stable> ...
> ata0-master: pio=PIO4 wdma=UNSUPPORTED udma=UNSUPPORTED cable=40 =wire
> ad0: success setting PIO4 on National chip
> ad0: 977MB at ata0-master PIO4
>
> on latest -stable:
> ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORT
hi,
latest changes in dev/ata broke this, on older -stable
...
ata0-master: pio=PIO4 wdma=UNSUPPORTED udma=UNSUPPORTED cable=40 wire
ad0: success setting PIO4 on National chip
ad0: 977MB at ata0-master PIO4
on latest -stable:
ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire
>
> --dc+cDN39EJAMEtIO
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> In the last episode (Apr 23), Tim Stoddard said:
> > I just upgraded from FreeBSD 6.2 ->
> > 6.3 (using source tree). I then recompiled my net-snmp port binaries (using
> > portupgrade). I am n
> On Thu, Mar 27, 2008 at 01:32:46PM +0200, Danny Braniss wrote:
> > > On Thu, Mar 27, 2008 at 12:57:31PM +0200, Danny Braniss wrote:
> > > > Hi,
> > > > Under load, the msk has problems, with hw.msk.legacy_intr=1
> and 0.
> > > >
> On Thu, Mar 27, 2008 at 12:57:31PM +0200, Danny Braniss wrote:
> > Hi,
> >Under load, the msk has problems, with hw.msk.legacy_intr=1 and 0.
> > with = 1, i get
> >TCP segementation error
> >watchdog timeout
> > with = 0,
> >
Hi,
Under load, the msk has problems, with hw.msk.legacy_intr=1 and 0.
with = 1, i get
TCP segementation error
watchdog timeout
with = 0,
Tx MAC parity error
watchdog timeout
the board is a Asus P5K-VM
Cheers,
danny
__
> On Sunday 09 March 2008 09:07:03 am Torfinn Ingolfsen wrote:
> > On Sat, 08 Mar 2008 18:44:50 -0800
> > Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> >
> > > Your boot0cfg line to reinstall the boot0 MBR looks fine, but I don't
> > > use boot0 myself (I prefer to go right into boot2/loader).
> >
is there support for this Promise card?
[EMAIL PROTECTED]:4:14:0: class=0x010400 card=0x0374105a chip=0x8350105a
rev=0x00 hdr=0x00
vendor = 'Promise Technology Inc'
class = mass storage
subclass = RAID
thanks,
danny
__
Hi Jeremy,
I'm very glad that you a) can write! b) that you are actually doing
something with respect to the zillions of missguided how-to's :-)
Having some experience with the subject, and please, don't read me
wrong, I see some different approaches:
- indeed this IS the 21'st cen
> Henri Hennebert wrote:
> > Jeremy Chadwick wrote:
> >> On Fri, Jan 25, 2008 at 06:17:24PM -0700, Joe Peterson wrote:
> >>> Glad you got it back! Yes, when I was first playing with ZFS, I noti=
> ced
> >>> that booting between single and multi user mode could make the pools
> >>> "invisible". I
> On 7-stable
> strings /boot/kernel/kernel | grep ___
> fails to show kernel config,
> whereas on 6.2-REL & before it worked.
> Also in 7 there's no
> START CONFIG FILE
> END CONFIG FILE
> Is this deliberate or a mistake ?
> strings are still there though, look for
> ^optio
> On Mon, Dec 10, 2007 at 11:03:47AM +0200, Danny Braniss wrote:
> > > On Sun, Dec 09, 2007 at 02:41:28PM +0200, Danny Braniss wrote:
> > > > with this onboard NIC (LOB?)
> > > >
> > > > mskc0:
> > > > e1000phy0: P
Zfs uses /boot/zfs to keep track of it's pools, but in a diskless
environment, this is a read-only fs. This causes several inconveniences,
- /etc/rc.d/zfs needs :
zfs_start_main()
{
dlv=`/sbin/sysctl -n vfs.nfs.diskless_valid 2> /dev/null`
if [ ${dlv:=0} -ne 0 ]; then
zpool import
Hi,
I'm also getting quiet a few of this can't happen. The system
is running 7.0-beta4, and is doing 'portsupgrade -af'
danny
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, s
with 7.0-Beta4, I'm getting quiet a few of these:
lockmgr: thread 0xff00039269f0 unlocking unheld lock
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_lockmgr() at _lockmgr+0x6ae
VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46
unionfs_unlock() at unionfs_unlock+0x22f
VOP_U
> On Sun, Dec 09, 2007 at 02:41:28PM +0200, Danny Braniss wrote:
> > with this onboard NIC (LOB?)
> >
> > mskc0:
> > e1000phy0: PHY 0 on miibus0
> >
> > [EMAIL PROTECTED]:1:0:0: class=0x02 card=0x81f81043
> chip=0x436411
with this onboard NIC (LOB?)
mskc0:
e1000phy0: PHY 0 on miibus0
[EMAIL PROTECTED]:1:0:0: class=0x02 card=0x81f81043 chip=0x436411ab
rev=0x12 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = '88E8056 Yukon PCI-E Gigabit Ethernet Control
try monitoring the traffic (tcpdump/wireshark), this should give you
a good starting point.
danny
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
newer kernels (after Oct. 20) are breacking bge.
i've checked the cvsdiffs, but nothing seems relevant.
the ilo (Integrated Lights Out) port, bge1, though not configured, gets
configured to 10baseT/UTP , and no magic will
get it to 100/full-duplex, which is what the ilo is using.
this works fine
> On Sun, Oct 28, 2007 at 12:37:45PM -0400, Andrew Lankford wrote:
> > Thanks for replying, but once again I've miscommunicated the issue. I
> > meant that MAKEDEV.8 is in /usr/src/share/man/man8/, and the
> > modification time is Oct 13th, recent, which suggests to me that it's still
> > in the
Hi,
these drivers don't work under 7.0
As soon as some mild preasure is applied, they start loosing interrupts, and
in my case the hosts come to a total stand-still, since they are diskless
and rely on the network.
This happens at 1gb and at 100mg.
Maybe the problem is with the shared inte
> I'm currently working on an embedded project which will be built
> around a BSD (I'm not sure which yet), currently I have an image up
> and running DragonFly and I'm currently attempting to do the same with
> FreeBSD for comparison.
>
> I'm more or less following the miniBSD tutorials (updating
> A couple comments just from reading through this, see below.
>
> > #!/bin/sh
> >
> > # PROVIDE: iscsi
> > # REQUIRE: NETWORKING
> > # BEFORE: DAEMON
> > # KEYWORD: nojail shutdown
> >
> > #
> > # Add the following lines to /etc/rc.conf to enable iscsi:
> > #
> > # iscsi_enable="YES"
> > # iscs
...
> > The message on the machine running scsi-target is: "Unsupported INQUIRY
> > VPD page 80"
> yes, I have tested it against ports/net/iscsi-target, I use it to try out
> errror recovery :-), and as far as I could tell it's harmelss.
> Anothere thing I can report is that running both (target/i
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --enig2465C3FB4D976B8B44FBA3F0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> Danny Braniss wrote:
> > Hi all,
> > I'm in the last mil
1 - 100 of 203 matches
Mail list logo