On Fri, Oct 17, 2008 at 03:21:48PM +0200, Aniruddha wrote:
On Thu, 2008-10-16 at 08:56 +0900, Pyun YongHyeon wrote:
It seems that msk(4) in HEAD does not build correctly on RELENG_7.
Try attached patch.
Save attached patch to /path/to/patch
#cd /usr/src/sys/dev/msk
#patch -p0
On Thu, 2008-10-16 at 08:56 +0900, Pyun YongHyeon wrote:
It seems that msk(4) in HEAD does not build correctly on RELENG_7.
Try attached patch.
Save attached patch to /path/to/patch
#cd /usr/src/sys/dev/msk
#patch -p0 /path/to/patch/msk.watchdog.diff
And rebuild your kernel.
This patch
I 'solved' this by buying a new nic. It's an Eminent with a RTL8139D
chipset.
--
Regards,
Aniruddha
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
I 'solved' this by buying a new nic. It's an Eminent with a RTL8139D
chipset.
you SOLVED it not 'solved'. onboard NICs are usually crap, except high end
motherboard.
they solder in what's cheapest in the moment. if chips are buggy, they add
workaround in windoze drivers.
and finally - for
Each time my internet connection is under heavy lead it gets killed
after a minute of 10. I tried the following commands to get the internet
back up, but nothing helped:
/etc/rc.d/netif restart
ifconfig mynic down
ifconfig mynic up
Even worse the last time I issued a '/etc/rc.d/netif restart'
On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
Each time my internet connection is under heavy lead it gets killed
after a minute of 10. I tried the following commands to get the internet
back up, but nothing helped:
/etc/rc.d/netif restart
ifconfig mynic down
ifconfig mynic
netstat -in
I have a Marvell Yukon onboard nic.
that's normal ;) but some NORMAL working NIC.
you may try to disable some features on that nic too
___
freebsd-questions@freebsd.org mailing list
On Wed, Oct 15, 2008 at 01:17:58PM +0200, Aniruddha wrote:
On Wed, 2008-10-15 at 00:26 -0700, Jeremy Chadwick wrote:
On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
Each time my internet connection is under heavy lead it gets killed
after a minute of 10. I tried the following
On Wed, 2008-10-15 at 21:09 +0900, PYUN Yong-Hyeon wrote:
This controller is known to buggy one. See below.
[...]
Trying to mount root from ufs:/dev/ad16s3a
WARNING: / was not properly dismounted
GEOM_LABEL: Label ext2fs/home removed.
GEOM_LABEL: Label ext2fs/data removed.
On Wed, Oct 15, 2008 at 04:24:21PM +0200, Aniruddha wrote:
On Wed, 2008-10-15 at 21:09 +0900, PYUN Yong-Hyeon wrote:
This controller is known to buggy one. See below.
[...]
Trying to mount root from ufs:/dev/ad16s3a
WARNING: / was not properly dismounted
GEOM_LABEL: Label
On Wed, 2008-10-15 at 00:26 -0700, Jeremy Chadwick wrote:
On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
Each time my internet connection is under heavy lead it gets killed
after a minute of 10. I tried the following commands to get the internet
back up, but nothing helped:
On Wed, Oct 15, 2008 at 04:31:01AM -0700, Jeremy Chadwick wrote:
On Wed, Oct 15, 2008 at 01:17:58PM +0200, Aniruddha wrote:
On Wed, 2008-10-15 at 00:26 -0700, Jeremy Chadwick wrote:
On Wed, Oct 15, 2008 at 09:13:00AM +0200, Aniruddha wrote:
Each time my internet connection is under
One thing worth trying would be to disable MSI/MSI-X. You can disable
these by adding the following to your /boot/loader.conf :
hw.pci.enable_msix=0
hw.pci.enable_msi=0
what's wrong in MSI interrupts?
mskc0: Uncorrectable PCI Express error
mskc0: Uncorrectable PCI Express error
Those
On Wed, Oct 15, 2008 at 09:09:11PM +0900, PYUN Yong-Hyeon wrote:
On Wed, Oct 15, 2008 at 04:31:01AM -0700, Jeremy Chadwick wrote:
On Wed, Oct 15, 2008 at 01:17:58PM +0200, Aniruddha wrote:
On Wed, 2008-10-15 at 00:26 -0700, Jeremy Chadwick wrote:
On Wed, Oct 15, 2008 at 09:13:00AM
On Wed, 2008-10-15 at 07:43 -0700, Jeremy Chadwick wrote:
Now you need to rebuild the kernel and install the kernel. In this
scenario, when building the kernel DO NOT use any -j flags, as if the
driver doesn't build, you'll be scrolling back through pages of data to
try and find out why.
On Wed, Oct 15, 2008 at 01:40:45PM +0200, Wojciech Puchar wrote:
One thing worth trying would be to disable MSI/MSI-X. You can disable
these by adding the following to your /boot/loader.conf :
hw.pci.enable_msix=0
hw.pci.enable_msi=0
what's wrong in MSI interrupts?
Nothing -- but there
On Wed, Oct 15, 2008 at 07:26:36PM +0200, Aniruddha wrote:
On Wed, 2008-10-15 at 07:43 -0700, Jeremy Chadwick wrote:
Now you need to rebuild the kernel and install the kernel. In this
scenario, when building the kernel DO NOT use any -j flags, as if the
driver doesn't build, you'll be
On Wed, Oct 15, 2008 at 10:02:46PM +0200, Aniruddha wrote:
On Wed, 2008-10-15 at 11:49 -0700, Jeremy Chadwick wrote:
How exactly did you download the URLs I gave you?
Can you show me what's on line 241 of if_msk.c?
A 'grep ^#include if_msk.c' for me returns lines which only include
On Wed, Oct 15, 2008 at 04:24:21PM +0200, Aniruddha wrote:
On Wed, 2008-10-15 at 21:09 +0900, PYUN Yong-Hyeon wrote:
This controller is known to buggy one. See below.
[...]
Trying to mount root from ufs:/dev/ad16s3a
WARNING: / was not properly dismounted
19 matches
Mail list logo
