On Sat, Aug 09, 2008 at 05:17:31PM -0400, John Baldwin wrote:
> > Sigh, it does not fix my problem described here:
> > http://groups.google.ru/group/muc.lists.freebsd.stable/browse_thread/thread
> >/538039f40b469e2a
> > I've just updated my 7.0-STABLE to latest sources, applied your patch
> > usin
On Sat, 9 Aug 2008, Larry Rosenman wrote:
On Sat, 9 Aug 2008, Larry Rosenman wrote:
I have a current RELENG_7 running on:
http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm
with the -3+ IPMI card.
I can interact with the BIOS, etc, but no joy once we get past the loader.
A
Larry Rosenman wrote:
There is a key release timeout checkbox on the keyboard/mouse
settings tab for the KVM that wasn't checked. Checking it
fixed it.
Sorry for the noise. :(
Actually, it worked *ONCE*, and now is not behaving itself.
Any ideas from other SuperMicro users?
In the IPMI car
What NIC does your server use? I'm currently trying to figure out a
similar issue with my server, which use bge(4)
I have a Sun Fire X2200. I can access the LOM no problem once Linux or
Solaris is booted. But, once FreeBSD boots, it's no longer accessible
from the NIC. Serial still works fi
On Sun, 10 Aug 2008, David Duchscher wrote:
On Aug 10, 2008, at 8:24 AM, Larry Rosenman wrote:
On Sat, 9 Aug 2008, Larry Rosenman wrote:
On Sat, 9 Aug 2008, Larry Rosenman wrote:
I have a current RELENG_7 running on:
http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm
with
On Aug 10, 2008, at 8:24 AM, Larry Rosenman wrote:
On Sat, 9 Aug 2008, Larry Rosenman wrote:
On Sat, 9 Aug 2008, Larry Rosenman wrote:
I have a current RELENG_7 running on:
http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm
with the -3+ IPMI card.
I can interact with the BI
On Sun, 10 Aug 2008, Daryl Richards wrote:
What NIC does your server use? I'm currently trying to figure out a similar
issue with my server, which use bge(4)
em(4), and the IPMI card has it's own NIC.
I have a Sun Fire X2200. I can access the LOM no problem once Linux or
Solaris is booted.
On Aug 10, 2008, at 10:22 AM, Larry Rosenman wrote:
I don't have that IPMI card but I can say we have other cards of
theirs working. I would make sure the card is at the latest
version of firmware. The AOC-SIMSO(+) card was not detected
correctly until we upgraded. I don't know why the ca
On Sun, 10 Aug 2008, David Duchscher wrote:
On Aug 10, 2008, at 10:22 AM, Larry Rosenman wrote:
I don't have that IPMI card but I can say we have other cards of theirs
working. I would make sure the card is at the latest version of firmware.
The AOC-SIMSO(+) card was not detected correctly u
09.08.08, 18:30, "Kurt Jaeger" <[EMAIL PROTECTED]>:
> Hi!
> > So I do not think that problem is with the network mask. Because of even
> > ping 10.11.16.14
> > returns network is unreachable!
> > Now when I upgraded to v7 I see trouble described earlier.
> > So this is must be counted as BUG o
09.08.08, 22:37, "Clifton Royston" <[EMAIL PROTECTED]>:
> On Sat, Aug 09, 2008 at 05:23:32PM +0400, KES wrote:
> > 09.08.08, 16:22, "Matthew Seaman" <[EMAIL PROTECTED]>:
> > > Andrew Snow wrote:
> > > > Usually if there is more than IP in a given subnet on an interface, you
> > > > give it a /32
I'm getting the following on a zpool scrub:
ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=54817587
ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=187521229
ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=187522189
ad8: WARNING - READ_DMA UDMA ICRC e
On Sun, Aug 10, 2008 at 06:01:34PM -0500, Larry Rosenman wrote:
> I'm getting the following on a zpool scrub:
>
> ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=54817587
>
> I replaced the drive at ad8 because the original one would get an ICRC and
> then hang the bus.
>
> Model Fa
I am trying to refresh my old groff skills, playing with it for the
first time on FreeBSD -- and getting very confused with understanding
groff's place and organization here. (I am writing this on FreeBSD 7.0
but I could start an 8.0 system if somebody suggested to take a look
there).
Let's start
On Sun, 10 Aug 2008, Jeremy Chadwick wrote:
On Sun, Aug 10, 2008 at 06:01:34PM -0500, Larry Rosenman wrote:
You have one or more of the following:
1. Faulty ATA cable
2. Faulty ATA port
3. Faulty ATA controller (doubtful, unless the errors are specific
to one role (e.g. master or slave))
4.
On Thu, 7 Aug 2008 11:34:41 +0200,
Milan Obuch <[EMAIL PROTECTED]> said:
> Funny observation: "r" is on LEFT keyboard side, "l" is on RIGHT keyboard
> side. I for one have problem at times precisely for this reason, but I know
> this is an important step and one need to act with great ca
Hi,
I am a kgdb newbie, so please be patient.
I suspect (just based on the fact that this is the 4th time I edit text files
on my NTFS partition through ntfs-3g, using Emacs, and getting frequent I/O
error messages inside Emacs, and then a kernel panic) that this is a ntfs-3g
related problem.
I
17 matches
Mail list logo