EG>> Does kern/130011 look similar?
EG>> http://www.freebsd.org/cgi/query-pr.cgi?pr=130011
> Do you have RTL8168C controller? If not, it's not related with
> Walter's issue as 7.0-RELEASE didn't have a support for RTL8168C.
Look into kern/130011. As far as I can see I do have RTL8168C.
EG>> The
> Date: Mon, 12 Jan 2009 08:22:40 +0200
> From: Andrei Kolu
> Sender: owner-freebsd-sta...@freebsd.org
>
> Mike Lempriere wrote:
> > Thanks everyone for the advice -- I got it working this time just
> > fine. Works much better when one follows the directions accurately
> > instead of by memory
On Mon, Jan 12, 2009 at 09:32:20AM +0300, eug...@donpac.ru wrote:
> EG>> Does kern/130011 look similar?
> EG>> http://www.freebsd.org/cgi/query-pr.cgi?pr=130011
>
> > Do you have RTL8168C controller? If not, it's not related with
> > Walter's issue as 7.0-RELEASE didn't have a support for RTL
Mike Lempriere wrote:
Thanks everyone for the advice -- I got it working this time just
fine. Works much better when one follows the directions accurately
instead of by memory -- the bottom line is that this time I remembered
to jot down the commands before heading downtown to the machine rack
On Sat, Jan 10, 2009 at 11:49:01AM -0500, Robert Noland wrote:
> > If you are experiencing a "garbled" screen with certain pci/pci-e based
> > radeons, I have another patch in HEAD that isn't included yet.
>
> I decided to go ahead and fully sync to HEAD, so this should be resolved
> as well. Th
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
> Walter,
>
> Thursday, January 8, 2009, 2:50:40 AM, you wrote:
>
> WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all
> WV> problems. I believe this roundly confirms that this is a bug in the
> WV>
On Sun, Jan 11, 2009 at 4:45 AM, Pete French
wrote:
>> I noticed a similar problem testing 7.1-RC1, It seemed to be a deep
>> deadlock, as it was triggered by lighttpd doing kern_sendfile, and
>> never returning. The side effects (being unable to create processes,
>> etc) is similar.
>
> Interesti
Hi,
I noticed an odd behavior regarding IPv6 after upgrading my 7.0R box
to 7.1R. The situation and symptom are the following:
1. The box has two NICs. One has an address 2001:0db8:1::1/64 (NIC
A), and another has 2001:0db8:2::1/64 (NIC B). These addresses
are assigned manually ($ip
> Not Found
sorry, see the subsequent email, there are more links there to working PNG's
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubsc
On Sun, Jan 11, 2009 at 11:27 AM, Pete French
wrote:
>> My kernconf is below, try building the kernel, and send an email
>> containing the backtrace from any process that has blocked (in my
>
> Well, I havent managed to get a backtrace, but immediately upon
> booting the system halts with the foll
Here is a better set of images. This machine was compiled
with the following config file:
include GENERIC
ident DEBUG
options KDB
options DDB
options SW_WATCHDOG
options DEBUG_VFS_LOCKS
options MUTEX_DEBUG
options WITNESS
options
Walter,
Thursday, January 8, 2009, 2:50:40 AM, you wrote:
WV> Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all
WV> problems. I believe this roundly confirms that this is a bug in the
WV> 7.1-RELEASE re kernel drivers.
Does kern/130011 look similar? http://www.freebsd.org/cg
> My kernconf is below, try building the kernel, and send an email
> containing the backtrace from any process that has blocked (in my
Well, I havent managed to get a backtrace, but immediately upon
booting the system halts with the following:
http://www.twisted.org.uk/~pete/71_lor1.jpg
Is any plans to backport ZFSv13 from CURRENT to RELENG7 branxh or not?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Fri, Jan 09, 2009 at 07:10:07PM +, Ben Morrow wrote:
> I would guess that your CD has both Rock Ridge and Joliet extensions,
> and that the creator has hidden the Win32-specific files from the Unix
> directory tree because they thought they wouldn't be useful. If for some
> reason you need
> I noticed a similar problem testing 7.1-RC1, It seemed to be a deep
> deadlock, as it was triggered by lighttpd doing kern_sendfile, and
> never returning. The side effects (being unable to create processes,
> etc) is similar.
Interesting - did you get any responses from anyone else regarding
th
16 matches
Mail list logo
