On Fri, 2009-03-27 at 19:44 -0700, David Johnson wrote:
> I update -STABLE about once a week. On Wednesday I update, and subsequently
> started getting hangs and lockups. This happens only when DRI is enabled.
> When
> DRI is disabled there is no problem. The seriousness can vary. Sometimes I
>
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 breaking ...
Fir
I update -STABLE about once a week. On Wednesday I update, and subsequently
started getting hangs and lockups. This happens only when DRI is enabled. When
DRI is disabled there is no problem. The seriousness can vary. Sometimes I can
ssh in from another machine to reboot, other times I can't. Th
> On Sun, Mar 22, 2009 at 08:29:57PM +0100, barbara wrote:
> >
> > Any news about that?
> >
> > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html
> >
>
> I'm sorry, I forgot this issue which was caused by my disk crash
> happened in the end of Jan, 2009.
> I've updated age(
On 3/27/09, John wrote:
> Weongyo Jeong wrote:
>>
>> It looks something goes wrong so could you please patch if_malo_pci.c
>> manually it's a very simple patch and test? Sorry for inconvenience.
>
> After editing, is it sufficient to just build and install a new kernel?
Yes, (or only if_malo mod
Weongyo Jeong wrote:
>
> It looks something goes wrong so could you please patch if_malo_pci.c
> manually it's a very simple patch and test? Sorry for inconvenience.
After editing, is it sufficient to just build and install a new kernel?
thanks
--
John
_
On Fri, Mar 27, 2009 at 06:52:32PM +0300, 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 is jumping out at me as bein
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 is jumping out at me as being
suspicious. However, you are now the second person who has told me
abou
> 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 now the second person who has told me
> a
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 now the second person who has told me
about AMR problems in 7.
Weongyo Jeong wrote:
> It looks something goes wrong so could you please patch if_malo_pci.c
> manually it's a very simple patch and test? Sorry for inconvenience.
No worries. I've edited if_malo_pci.c now and will build a new kernel
when I get back home. I'll let you know how I get on
thanks
Hello,
On Sun, Mar 22, 2009 at 04:31:56AM -0500, Scott Lambert wrote:
> > I added this machine to our AMANDA setup on March 13, 2009.
> >
> > I noticed that mksnap_ffs was running on /home, cpu time used: 0:00.77,
> > as things began to circle the drain. That was about 30 minutes after
> > th
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
13 matches
Mail list logo
