On Thu, Sep 15, 2011 at 12:13 AM, Dennis Koegel wrote:
> I'm not aware how licensing issues play in here, but apart from that, it
> should be easy to patch this into base. (I was already half-way there
> yesterday and I think I could work up a patch against HEAD and 8.x).
I won't worry about fili
On Wed, Sep 14, 2011 at 07:26:20PM -0700, Jeremy Chadwick wrote:
> I'm actually very surprised to hear there's an official FreeBSD driver
> on Adaptec's site that's actually intended for FreeBSD 8.x.
As far as I can tell from the source, it's the very same driver (same
source code and copyright no
On Thu, Sep 15, 2011 at 09:36:43AM +0800, Adrian Chadd wrote:
> On 15 September 2011 00:38, Elliot Finley wrote:
> > I was having the exact same problem using an Adaptec 52445. ?After
> > downloading and using the latest driver from the adaptec website, the
> > problems stopped. ?I haven't had a s
On 15 September 2011 00:38, Elliot Finley wrote:
> I was having the exact same problem using an Adaptec 52445. After
> downloading and using the latest driver from the adaptec website, the
> problems stopped. I haven't had a single freeze since using the new
> code. The newest driver from the w
2:08 AM, Dennis Koegel wrote:
> Cheers,
>
> we have a reproducible system freeze due to Adaptec driver (aac) timeouts:
>
> Sep 3 05:26:44 foo kernel: aac0: COMMAND 0xff80005ae4c0 (TYPE 502)
> TIMEOUT AFTER 129 SECONDS
> Sep 3 05:26:44 foo kernel: aac0: COMMAND 0xff80
Cheers,
we have a reproducible system freeze due to Adaptec driver (aac) timeouts:
Sep 3 05:26:44 foo kernel: aac0: COMMAND 0xff80005ae4c0 (TYPE 502) TIMEOUT
AFTER 129 SECONDS
Sep 3 05:26:44 foo kernel: aac0: COMMAND 0xff80005ac0e0 (TYPE 502) TIMEOUT
AFTER 129 SECONDS
Sep 3 05:26:44
> I'd like a technical explanation of exactly what this loader.conf
> tunable does. The sysctl -d explanation is useful if one has insight to
> what purpose it serves. I can find mention on Solaris lists about "txg
> timeout", but the context is over my head (intended for those very
> familiar wi
On Mon, Feb 08, 2010 at 05:58:53PM +0100, Guido Falsi wrote:
> On Mon, Feb 08, 2010 at 05:18:22PM +0100, Fabian Keil wrote:
> >
> > I experienced what I think is the same problem. ZFS's bulk disk flushes
> > caused vlc to occasionally stutter when viewing a DVD rip from disk while
> > ripping a DV
On Mon, Feb 08, 2010 at 05:18:22PM +0100, Fabian Keil wrote:
>
> I experienced what I think is the same problem. ZFS's bulk disk flushes
> caused vlc to occasionally stutter when viewing a DVD rip from disk while
> ripping a DVD at the same time.
>
> My workaround is to put "vfs.zfs.txg.timeout=3
Jeremy Chadwick wrote:
> On Mon, Feb 08, 2010 at 03:33:29PM +0100, Guido Falsi wrote:
> > I'm seeing this problem on my machine at work. It's an HP DC 7800,
> > mounts an ich9 chipset(not ahci capable). I'm attaching the dmesg.
> >
> > I noticed this in the past, but it got evident(and very ann
On Mon, Feb 08, 2010 at 06:51:47AM -0800, Jeremy Chadwick wrote:
> On Mon, Feb 08, 2010 at 03:33:29PM +0100, Guido Falsi wrote:
> >
> > It gets very annoying and I don't remember this happening before
> > activating the ATA_CAM flag. There was some slowdown with big disk
> > access, but not a tota
On Mon, Feb 08, 2010 at 03:41:14PM +0100, Ivan Voras wrote:
> On 02/08/10 15:33, Guido Falsi wrote:
>
> >It looks like it freezes the system for the second or two it takes
> >to flush buffers to disk when there are big outputs. This happens
> >when decompressiong big distfiles, mainly. The openoff
On Mon, Feb 08, 2010 at 03:33:29PM +0100, Guido Falsi wrote:
> Hi!
>
> I'm seeing this problem on my machine at work. It's an HP DC 7800,
> mounts an ich9 chipset(not ahci capable). I'm attaching the dmesg.
>
> I noticed this in the past, but it got evident(and very annoying)
> while recompiling
On 02/08/10 15:33, Guido Falsi wrote:
It looks like it freezes the system for the second or two it takes
to flush buffers to disk when there are big outputs. This happens
when decompressiong big distfiles, mainly. The openoffice port
triggers this almost continuosly every few seconds during comp
Hi!
I'm seeing this problem on my machine at work. It's an HP DC 7800,
mounts an ich9 chipset(not ahci capable). I'm attaching the dmesg.
I noticed this in the past, but it got evident(and very annoying)
while recompiling many ports today after the jpeg-8 update.
It looks like it freezes the sys
On Wed, 2 Dec 2009, Peter Pieczora wrote:
Hi,
You're absolutely right, adding dumpdev="AUTO" solved generating dump files.
I may be totally wrong, but it seems that wlan0 causes system panic:
I remember when using ndis device (linksys pcmcia wifi card) similar situation
took place.
Thanks for
On Wednesday 02 December 2009 22:17:20 Jeremy Chadwick wrote:
> On Wed, Dec 02, 2009 at 09:34:28PM +, Peter Pieczora wrote:
> > You're absolutely right, adding dumpdev="AUTO" solved generating dump
> > files.
> >
> > I may be totally wrong, but it seems that wlan0 causes system panic:
> > I rem
On Wed, 2 Dec 2009 14:17:20 -0800
Jeremy Chadwick wrote:
> You're welcome! (I often wonder if dumpdev should be set to "AUTO" by
> default these days, but that discussion is for elsewhere and another
> time...)
See
http://lists.freebsd.org/pipermail/svn-src-stable-8/2009-September/000224.html
f
On Wed, Dec 02, 2009 at 09:34:28PM +, Peter Pieczora wrote:
> You're absolutely right, adding dumpdev="AUTO" solved generating dump files.
>
> I may be totally wrong, but it seems that wlan0 causes system panic:
> I remember when using ndis device (linksys pcmcia wifi card) similar
> situatio
On Wed, Dec 2, 2009 at 17:22, Peter Pieczora wrote:
> Hi,
>
> I recently upgraded from 7.2-STABLE to 8.0-RELEASE, and I'm encountering
> frequent system freezes (hang ups), which end in a reboot.
>
> There is no indication of any panic, no messages are generated and no core
> dump files (sysctl ke
Hi,
You're absolutely right, adding dumpdev="AUTO" solved generating dump files.
I may be totally wrong, but it seems that wlan0 causes system panic:
I remember when using ndis device (linksys pcmcia wifi card) similar situation
took place.
Thanks for your help.
>>
On Wednesday 02 December 2009 17:22:13 Peter Pieczora wrote:
> Hi,
>
> I recently upgraded from 7.2-STABLE to 8.0-RELEASE, and I'm encountering
> frequent system freezes (hang ups), which end in a reboot.
>
> There is no indication of any panic, no messages are generated and no core
> dump files
On Wed, Dec 02, 2009 at 04:22:13PM +, Peter Pieczora wrote:
> I recently upgraded from 7.2-STABLE to 8.0-RELEASE, and I'm encountering
> frequent system freezes (hang ups), which end in a reboot.
>
> There is no indication of any panic, no messages are generated and no core
> dump files (sys
Hi,
I recently upgraded from 7.2-STABLE to 8.0-RELEASE, and I'm encountering
frequent system freezes (hang ups), which end in a reboot.
There is no indication of any panic, no messages are generated and no core
dump files (sysctl kern.coredump=1).
System runs on IBM T43 with intel wireless chi
Hello,
I'm running 7.0-BETA4 - i386 with the root fs on zfs.
This nigth, the system freeze.
I can enter kdb - see attached file - If I request the wrong
informations let me know for the next time...
I use the patch http://people.freebsd.org/~pjd/patches/zgd_done.patch .
Henri
* Dirk Arlt <[EMAIL PROTECTED]> wrote:
> Still the same problem, now using 6.2-STABLE.
>
> attached: dmesg and kernel-config
Mee too; system also locks up quite fast after kldloading atapicam when
already booted.
--
Ed Schouten <[EMAIL PROTECTED]>
WWW: http://g-rave.nl/
pgpwnrc205W7J.pgp
De
* Dirk Arlt <[EMAIL PROTECTED]> schrieb:
> Hi All,
>
> I found that issue in older mailings and as bugreport, but its not
> mentioned anymore.
>
> Loading atapicam freezes my system, with or without dvdram. Only
> solution is setting hw.ata.atapi_dma to 0.
>
> I'd like to see that issue reanima
* Dirk Arlt <[EMAIL PROTECTED]> schrieb:
> Hi All,
>
> I found that issue in older mailings and as bugreport, but its not
> mentioned anymore.
>
> Loading atapicam freezes my system, with or without dvdram. Only
> solution is setting hw.ata.atapi_dma to 0.
>
> I'd like to see that issue reanima
Hi Kris,
On Fri, 12 Jan 2007 02:33 am, Kris Kennaway wrote:
> On Sat, Jan 06, 2007 at 07:14:41PM +1100, Geoff Roberts wrote:
> > Hi,
> >
> > I can consistantly make my system freeze when building makeworld
> > and running dump at the same time. The system actually lo
On Sat, Jan 06, 2007 at 07:14:41PM +1100, Geoff Roberts wrote:
> Hi,
>
> I can consistantly make my system freeze when building makeworld and
> running dump at the same time. The system actually locks - I have to
> hit the reset switch to bring the system back to life.
>
&
On Sat, Jan 06, 2007 at 07:14:41PM +1100, Geoff Roberts wrote:
> I can consistantly make my system freeze when building makeworld and
> running dump at the same time. The system actually locks - I have to
> hit the reset switch to bring the system back to life.
I have an old SMP machin
Hi,
I can consistantly make my system freeze when building makeworld and
running dump at the same time. The system actually locks - I have to
hit the reset switch to bring the system back to life.
I also get a core dump on current.
I have mounted the file systems as follows:
/
/tmp
/usr
/usr
I got an error sending this message, so next try...
please excuse if its send to you twice.
* Forwarded message:
Date: Thu, 28 Dec 2006 18:12:42 +0100
From: Dirk Arlt <[EMAIL PROTECTED]>
To: freebsd-stable@freebsd.org
Subject: atapicam - System freeze with hw.ata.atapi_dma=1
Hi All,
I
Hi All,
I found that issue in older mailings and as bugreport, but its not
mentioned anymore.
Loading atapicam freezes my system, with or without dvdram. Only
solution is setting hw.ata.atapi_dma to 0.
I'd like to see that issue reanimated. Of course i'll give any
information necessary.
I am us
Hello List,
I just recently upgraded my machine a few days ago to 6.1-RC2 and have
noticed a problem when using pciconf to read the configuration space
register of one of my network interfaces. Attempting to read the
configuration space when the network is online produces the output I
would expec
investigations in order to get more
accurate information.
I plan to reinstall the laptop in order to be able to try -CURRENT on it
too but meanwhile, is there something I can do?
I am experiencing a whole system freeze by using gtk-apps under X with
the xorg ati driver. But how can I get deeper in finding
Hello,
It's been two months since this thread was started. To recap, I repeatedly
encountered what was identified by the gurus here as filesystem deadlock,
which froze my machine.
Now, after some time, I have an additional observation to add: The
deadlock *only* happens when Quanta (KDE HTML E
On Tue, 2004-Dec-28 03:27:00 +0100, Benjamin Lutz wrote:
>> The info you dumped shows that there's a filesystem deadlock on
>> ad4s1f.
>
>In case you haven't guessed, that'd be my /usr.
I hadn't really considered which filesystem it was. Locked root vnodes
are bad news anywhere - basically, once
On Tue, Dec 28, 2004 at 03:52:50AM +0100, Benjamin Lutz wrote:
> > Does xmms try to run with rtprio or idprio? Those are still broken,
> > and can lead to deadlocks, afaik.
>
> No, none all PIDs are listed as "normal" by idprio and rtprio, except the
> [pagezero] process, which is listed as "idl
> Does xmms try to run with rtprio or idprio? Those are still broken,
> and can lead to deadlocks, afaik.
No, none all PIDs are listed as "normal" by idprio and rtprio, except the
[pagezero] process, which is listed as "idle priority 31" by both
programs, and I suppose that's intentional.
Gree
On Tue, Dec 28, 2004 at 12:38:44PM +1100, Peter Jeremy wrote:
> On Sun, 2004-Dec-26 08:14:49 +0100, Benjamin Lutz wrote:
> >The freeze just happened again. I managed to get into the debugger and get
> >some info.
>
> The info you dumped shows that there's a filesystem deadlock on
> ad4s1f. This
Hello Peter,
> The info you dumped shows that there's a filesystem deadlock on
> ad4s1f.
In case you haven't guessed, that'd be my /usr.
> Unfortunately, it's not clear (to me) where to go next. Printing the
> locked vnodes might help but that's not easy to do without gdb.
You mean that's the
On Sun, 2004-Dec-26 08:14:49 +0100, Benjamin Lutz wrote:
>The freeze just happened again. I managed to get into the debugger and get
>some info.
The info you dumped shows that there's a filesystem deadlock on
ad4s1f. This is consistent with the behaviour you reported - the
system is running "nor
Hello,
The freeze just happened again. I managed to get into the debugger and get
some info. Since I haven't been able to aqcuire the equipment for a
serial console connection yet, I've made pictures again. Unfortunately,
my system doesn't support wide console modes, so it's a tad annoying to
On Sat, 2004-Dec-25 10:35:43 +0100, Benjamin Lutz wrote:
>> Hmm. I can't find that string anywhere in the sources. Are you sure
>> "rm.mutex_mtx" is correct?
>
>yes.
It seems that it's inside the NVidia driver - which isn't in the source
tree. That explains why I couldn't find it. I think this
Hello Peter,
I've photographed my console and uploaded the pics, you can see it here:
http://maxlor.com/log (844KB total).
After seeing trace's output, it occurred to me that the nvidia driver
might be the problem. And indeed, after disabling it, the panic on boot
went away.
Note however that
On Thu, 2004-Dec-23 18:01:24 +0100, Benjamin Lutz wrote:
>Well, this is unexpected. I enabled the debugging options as instructed
>(INVARIANT_SUPPORT, INVARIANTS, WITNESS, DDB, GDB), rebooted and then
...
>ioapic0 irqs 0-23 on motherboard
>panic: spin lock rm.mutex_mtx not in order list
Hmm. I c
Well, this is unexpected. I enabled the debugging options as instructed
(INVARIANT_SUPPORT, INVARIANTS, WITNESS, DDB, GDB), rebooted and then
I got this next time I booted:
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980,
Thanks for the detailed instructions, both of you. I'll see that I can
collect some information next time this happens (I can't really reproduce
it, it just happens about once a week).
> What still works when the system is frozen? Can you switch VTYs? Do\
> ping's work (from another system)?
On Thu, 23 Dec 2004, Benjamin Lutz wrote:
> I'm having a Problem with FreeBSD 5.3 here. The system slowly freezes.
>
> It starts with one application that just locks up. Other applications
> still work, but when I switch to them and do stuff in them, they usually
> lock up after a few seconds
On Thu, 2004-Dec-23 04:08:39 +0100, Benjamin Lutz wrote:
>I'm having a Problem with FreeBSD 5.3 here. The system slowly freezes.
>
>It starts with one application that just locks up. Other applications
>still work, but when I switch to them and do stuff in them, they usually
>lock up after a few
Hello,
I'm having a Problem with FreeBSD 5.3 here. The system slowly freezes.
It starts with one application that just locks up. Other applications
still work, but when I switch to them and do stuff in them, they usually
lock up after a few seconds as well. Starting new processes or logging in
52 matches
Mail list logo
