I wrote:
I am getting this too - update from RELENG_7 @12 Jan src to 20 Jan and
I have:
panic: free: guard1 fail @ 0x511d
from /usr/src/sys/boot/i386/loader/../../common/module.c:959
Can't work out which disk we are booting from.
Guessed BIOS device 0x not found by probes, defaulting
On Tue, Jan 20, 2009 at 07:14:25AM +0300, Marat N.Afanasyev wrote:
> Marat N.Afanasyev wrote:
> >Dan Langille wrote:
> >>Marat N.Afanasyev wrote:
> >>>Dan Langille wrote:
> Dan Langille wrote:
> >Hi,
> >
> >I'm getting this:
> >
> >kernel: interrupt storm detected
Hello,
Perhaps mine is a different issue but I ran into this today.
I loaded FreeBSD 7.1-RELEASE from a DVD onto an Apple Mac Pro after
partitioning a drive with bootcamp. The install went quite well and the
machine came up with no issues. I configured networking, X, and got gnome
working. I s
On Tue, Jan 20, 2009 at 08:25:23PM +0100, Ralf van der Enden wrote:
> Hi,
>
> I've recently upgraded my box from FreeBSD 7.0-RELEASE to 7.1-RELEASE.
>
> Now, whenever I reboot my machine it hangs during the boot proces.
>
> I have a Fasttrak TX2 100 card in my system which is used for booting Fr
yes
On Tue, 20 Jan 2009, Eduardo Meyer wrote:
Hello,
I have a certain disk where da0s1a and da0s1d are inverted. By some
reason someone labelled root as 'd' and home as 'a'.
Can I just
bsdlabel -n da0s1 > savedabel.txt
Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel)
Hi,
I've recently upgraded my box from FreeBSD 7.0-RELEASE to 7.1-RELEASE.
Now, whenever I reboot my machine it hangs during the boot proces.
I have a Fasttrak TX2 100 card in my system which is used for booting FreeBSD
and it shows fine while it's searching for attached drives, but after it lo
According to pluknet:
> To clarify:
> I.e. on older versions you had no errors with COMPAT_IA32 and without SYSV* ?
I think so.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
Dons / donation Ondine : http://ondine.keltia.net/
On Tue, Jan 20, 2009 at 03:36:34PM -0200, Eduardo Meyer wrote:
> On Tue, Jan 20, 2009 at 2:13 PM, Patrick M. Hausen wrote:
> > Hello,
> >
> > On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote:
> >> I have a certain disk where da0s1a and da0s1d are inverted. By some
> >> reason someone
Dan Langille wrote:
Please.
btw, did you try to set hw.acpi.osname="Linux" in /boot/loader.conf?
--
SY, Marat
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "fre
On Tue, Jan 20, 2009 at 03:36:34PM -0200, Eduardo Meyer wrote:
> ...
> > Why not simply use bsdlabel -e da0s1?
>
> Because I didnt know about that? ;-)
>
> Thank you for the hint.
>
> However I still have the same doubt. Since basically its the same
> task, Is it safe do relabel this way?
I hav
On Tue, Jan 20, 2009 at 2:13 PM, Patrick M. Hausen wrote:
> Hello,
>
> On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote:
>> I have a certain disk where da0s1a and da0s1d are inverted. By some
>> reason someone labelled root as 'd' and home as 'a'.
>>
>> Can I just
>>
>> bsdlabel -n da
Hello,
On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote:
> I have a certain disk where da0s1a and da0s1d are inverted. By some
> reason someone labelled root as 'd' and home as 'a'.
>
> Can I just
>
> bsdlabel -n da0s1 > savedabel.txt
>
> Edit savedlabel.txt, switch and restore? (b
On 20/01/2009, at 13:25, Steve Bertrand wrote:
Also, it may help to run tcpdump without the 'host' parameter on em0
while the pinging is occurring to see if you can find out whether the
ICMP replies are being sent out as the primary IP.
stewie# tcpdump -n -i em0 icmp
tcpdump: verbose output
Steve Bertrand wrote:
> Wendell Martins Borges wrote:
>
>>> # tcpdump -n -i em0 host 192.168.112.181
>> ping for another host:
>>
>> stewie# tcpdump -n -i em0 host 192.168.112.181
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on em0, link-type EN10MB (E
On 20/01/2009, at 13:22, Steve Bertrand wrote:
So, the box can be found on the network, but it is not returning
traffic
properly.
What does # arp -a have to say, on both boxes?
stewie# arp -a
stewie (192.168.112.1) at 00:15:17:16:bf:9a on em0 permanent [ethernet]
cartola (192.168.112.181
Hello,
I have a certain disk where da0s1a and da0s1d are inverted. By some
reason someone labelled root as 'd' and home as 'a'.
Can I just
bsdlabel -n da0s1 > savedabel.txt
Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel)
--
===
Eduardo Meyer
pessoal: dudu.me...
Wendell Martins Borges wrote:
>> # tcpdump -n -i em0 host 192.168.112.181
>
> ping for another host:
>
> stewie# tcpdump -n -i em0 host 192.168.112.181
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on em0, link-type EN10MB (Ethernet), capture size 96 byt
On 20/01/2009, at 12:26, Gavin Atkinson wrote:
Can you try the following:
ping -S 192.168.112.181 host
and then try pinging 192.168.112.181 from the host?
stewie# ping -S 192.168.112.181 192.168.112.8
PING 192.168.112.8 (192.168.112.8) from 192.168.112.181: 56 data bytes
64 bytes from 192.16
On 20/01/2009, at 12:00, Steve Bertrand wrote:
Wendell, what does #netstat -rn say? Also, if you run tcpdump
listening
on the alias IP address, do you see the ingress traffic from the
remote
workstations? ie:
stewie# netstat -rn | grep 192.168.112.181
192.168.112.18100:15:17:16:bf:9a
Patrick M. Hausen wrote:
Hello,
seems like I cannot find out if this card is supported
or not. LSI provide drivers for Windows and Linux as
usual, and mfi(4) doesn't mention that particular one.
But possibly it's of the "MegaRAID Firmware Interface"
type that mfi(4) supports?
Unfortunately for
Patrick M. Hausen wrote:
> Hi, all,
>
> On Tue, Jan 20, 2009 at 08:52:18AM -0500, Steve Bertrand wrote:
>> For how long? On a 7.0-R box, it works ok with a /32 prefix len:
>>
>> %ifconfig
>> re0: flags=8843 metric 0 mtu 1500
>> options=9b
>> ether 00:0f:b5:80:53:85
>> inet
On Tue, 2009-01-20 at 11:12 -0200, Wendell Martins Borges wrote:
> I had a 7.0 server and my card worked fine, upgraded to 7.1 and
> aliases stopped working, below some information from my server.
>
> # uname -a
> FreeBSD stewie.ramenzoni.com.br 7.1-RELEASE FreeBSD 7.1-RELEASE #0:
> Thu Jan 1
Hi, all,
On Tue, Jan 20, 2009 at 08:52:18AM -0500, Steve Bertrand wrote:
> For how long? On a 7.0-R box, it works ok with a /32 prefix len:
>
> %ifconfig
> re0: flags=8843 metric 0 mtu 1500
> options=9b
> ether 00:0f:b5:80:53:85
> inet 208.70.104.210 netmask 0xff00 bro
Patrick M. Hausen wrote:
Hello,
On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote:
ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0"
ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255"
I don't know if this can be the cause of your problem, but
the
Steve Bertrand wrote:
> Patrick M. Hausen wrote:
>> Hello,
>>
>> On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote:
>>
>>> ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0"
>>> ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255"
>> I don't know if this can
Patrick M. Hausen wrote:
> Hello,
>
> On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote:
>
>> ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0"
>> ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255"
>
> I don't know if this can be the cause of your probl
On 20/01/2009, at 11:43, Steve Bertrand wrote:
I'm confused. Given the /etc/rc.conf settings, the above ifconfig
output
appears to be exactly what I would expect.
What is not working?
Steve
Hi Steve,
The settings are really OK. However after the update does not
can access the alias of I
I suppose that was what was required with XP (normally used boot0, but
tinkered with using windows boot as an alternate method), but I haven't
had to update boot1 since I first installed everything on this laptop
...so far.
Andrew Lankford
Bruce Simpson wrote:
Andrew Lankford wrote:
FYI:
Hello,
On Tue, Jan 20, 2009 at 11:12:45AM -0200, Wendell Martins Borges wrote:
> ifconfig_em0="inet 192.168.112.1 netmask 255.255.255.0"
> ifconfig_em0_alias0="inet 192.168.112.181 netmask 255.255.255.255"
I don't know if this can be the cause of your problem, but
the /32 netmask for aliases has
Wendell Martins Borges wrote:
> I had a 7.0 server and my card worked fine, upgraded to 7.1 and aliases
> stopped working, below some information from my server.
>
> # uname -a
> FreeBSD stewie.ramenzoni.com.br 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu
> Jan 1 14:37:25 UTC 2009
> r...@logan.cse
I had a 7.0 server and my card worked fine, upgraded to 7.1 and
aliases stopped working, below some information from my server.
# uname -a
FreeBSD stewie.ramenzoni.com.br 7.1-RELEASE FreeBSD 7.1-RELEASE #0:
Thu Jan 1 14:37:25 UTC 2009 r...@logan.cse.buffalo.edu:/usr/obj/
usr/src/sys/GEN
On Jan 19, 2009, at 11:14 PM, Marat N.Afanasyev wrote:
Marat N.Afanasyev wrote:
Dan Langille wrote:
Marat N.Afanasyev wrote:
Dan Langille wrote:
Dan Langille wrote:
Hi,
I'm getting this:
kernel: interrupt storm detected on "irq22:"; throttling
interrupt source
what is your motherboard
2009/1/20 Ollivier Robert :
> I must have missed the HEADS-UP or something but it seems that the SYSV IPC
> options are now mandatory in order to compile an amd64 kernel with
> COMPAT_IA32... I get linking errors in kernel.debug because
> freebsd32_syscalls.o is referencing the SYSV syscalls...
>
Hello,
seems like I cannot find out if this card is supported
or not. LSI provide drivers for Windows and Linux as
usual, and mfi(4) doesn't mention that particular one.
But possibly it's of the "MegaRAID Firmware Interface"
type that mfi(4) supports?
Unfortunately for a particular server model t
Reuben wrote:
I was wondering if anyone else was seeing loader (v1.02) break after updating
from 7.1-RELEASE to 7.1-STABLE. After performing the prescribed updating
procedure (via the handbook), the system will go through the normal steps and
after the boot menu will present the following er
Marc UBM pisze:
Hiho! :-)
Occasionally, especially when uploading a large number of files, the
(brand-new, tested) sata disks in my fileserver spit out some of these
errors:
---
Jan 19 19:51:14 hamstor kernel: ad10: WARNING - WRITE_DMA48 UDMA ICRC
error (retrying request) L
36 matches
Mail list logo
