similar to: DAHDI: TCM PCI Master abort

Displaying 20 results from an estimated 9000 matches similar to: "DAHDI: TCM PCI Master abort"

2020 May 11
0
[PATCH] vhost: scsi: notify TCM about the maximum sg entries supported per command.
vhost-scsi pre-allocates the maximum sg entries per command and if a command requires more than VHOST_SCSI_PREALLOC_SGLS entries, then that command is failed by it. This patch lets vhost communicate the max sg limit when it registers vhost_scsi_ops with TCM. With this change, TCM would report the max sg entries through "Block Limits" VPD page which will be typically queried by the SCSI
2020 Jun 18
0
[PATCH AUTOSEL 5.7 077/388] scsi: vhost: Notify TCM about the maximum sg entries supported per command
From: Sudhakar Panneerselvam <sudhakar.panneerselvam at oracle.com> [ Upstream commit 5ae6a6a915033bfee79e76e0c374d4f927909edc ] vhost-scsi pre-allocates the maximum sg entries per command and if a command requires more than VHOST_SCSI_PREALLOC_SGLS entries, then that command is failed by it. This patch lets vhost communicate the max sg limit when it registers vhost_scsi_ops with TCM. With
2020 Jun 18
0
[PATCH AUTOSEL 5.4 059/266] scsi: vhost: Notify TCM about the maximum sg entries supported per command
From: Sudhakar Panneerselvam <sudhakar.panneerselvam at oracle.com> [ Upstream commit 5ae6a6a915033bfee79e76e0c374d4f927909edc ] vhost-scsi pre-allocates the maximum sg entries per command and if a command requires more than VHOST_SCSI_PREALLOC_SGLS entries, then that command is failed by it. This patch lets vhost communicate the max sg limit when it registers vhost_scsi_ops with TCM. With
2009 Aug 19
7
* 1.4 -> 1.6, zaptel -> dahdi
This has got to be an FAQ, so if someone can point me to where it is answered, I would be greatly appreciated. The documentation for all this stuff is scattered and (to me at least) either very sketchy or hard to find. What I want is a guide for how to convert from 1.4 with zaptel to 1.6 with dahdi. All the recent kernel vulnerabilities are forcing me to upgrade my home server from
2007 Mar 21
2
store_class_name for Comatose:Page model
Hi, I have three models: Comatose::Page, Article and Product. In all of them, store_class_name is set to true. Now, when i do: results = Comatose::Page.multi_search("*", [Article,Product], options) I get: wrong constant name Comatose::Page #{RAILS_ROOT}/vendor/plugins/acts_as_ferret/lib/class_methods.rb:438:in `const_get''
2009 Sep 04
1
1.4.26-2, DAHDI-2.2.0, B410P and BRI
Hello everybody, I try to install -Ubuntu 8.04 server- a B410P and a TDM2400P together with Asterisk 1.4.26-2, dahdi-linux-2.2.0.2 and dahdi-tools-2.2.0. Problem I face is the following one: CLI> module load chan_dahdi.so == Registered application 'DAHDISendKeypadFacility' == Registered application 'ZapSendKeypadFacility' == Parsing
2006 Aug 03
1
routeset mapper problem
hello, I installed a rails app on dreamhost, which I''m building based on the Comatose plugin, and it went smoothly for the first version. Now I uploaded a second version where I broke down the Comatose code into a regular rails app, which works alright locally, but can''t get routing to work the same as before on the server. I believe I double-checked all gotchas mentioned
2005 Sep 08
2
TDM PCI Master abort
I keep getting this error randomly. I have a TDM400P, I've tried disabling everything in the BIOS. I'm running Fedora core 2.6.11 and asterisk 1.0. Any pointers would be greatly appreciated. Thanks! -Paul
2006 Nov 16
1
FXO PCI Master abort
So I'm all excited, ready to install Trixbox at home. Purchased my X100p card installed in a computer. I run Trixbox setup and boom I get this error message "FXO PCI Master abort" It repaets across the screen and I have to reboot. When I reboot the system hangs at adding hardware. Loading wcfxo and the system will not go any further. If anyone has an idea of something to try let me
2003 Jul 07
3
PCI Master Abort
I am always getting multiple PCI Master Abort messages when I try to plug in a second TDM400P. I have asked this question before, but I nothing really solved my problem and I just put it on the back burner for a while. I am at a point where this is a crucial issue. I have read that the Zaptel devices share an IRQ, is this causing the problem? Is there a way that I can manually change the IRQs of
2005 Aug 13
0
[Asterisk-Dev] Re: FXO PCI Master abort
Dear Zaptel and wcfxo devellopers, Hi, so far I have had no success moving this issue forward. Carl Andersson has been kind enough to help build various kernels to try, but with no success. So, I have tried to debug the problem directly. So far I have applied the patch below to wcfxo.c. (on the latest CVS head) This makes my system stable again (in that I dont have to keep pressing the big
2007 Jan 25
1
issue with ivtv & wctdm zaptel drivers (TDM PCI Master abort)
Hi, I'm experiencing an issue with my x86_64 machine containing a Hauppauge PVR-500 (ivtv) and a Digium TDM400p (wctdm, part of zaptel) PCI cards. Independently of each other both cards work fine, but once the wctdm driver is loaded and mythtv tries to record something on the PVR-500 the wctdm driver freaks out. The error message is see is "TDM PCI Master abort" printed over and
2005 Jan 10
3
FXO PCI Master abort
Recently I started getting weird errors. All of a sudden I see the harddrive of my box glowing steadily and syslog is getting filled (and the cpu hogged) with these errors: It seems to start with this line: Jan 1 03:28:04 kernel: FXO PCI Master abort Jan 1 03:28:04 last message repeated 12 times Jan 1 03:28:06 kernel: CI Master abort Jan 1 03:28:06 kernel: FXO PCI Master abort and seems to
2019 Jun 06
2
error compiling dahdi for recent kernels
Seems like I post about this about once a year, when it's time to upgrade Fedora. I first got this error trying to compile a patched version of dahdi-linux-2.11.1; I noticed that there is now a dahdi-linux-complete-3.0.0+3.0.0, so I tried that one with the same result. If I compile it while running kernel-4.16.8-300.fc28.x86_64, it compiles fine, but when I try to compile it while running
2019 Jun 06
3
error compiling dahdi for recent kernels
On Thu, Jun 6, 2019 at 12:17 PM Malcolm Davenport <malcolmd at sangoma.com> wrote: > Howdy, > > There's a dahdi-linux-complete-3.1.0-rc1+3.1.0-rc1.tar.gz. > > Try that. > I noticed that was there, but I didn't try it originally because it's obviously a beta version. However, I did download it and try it. It does compile, but doesn't work correctly. For one
2008 Mar 12
0
CMS act_as_tree problem and template_root
Hi, I want use the comatose CMS plug in for creatin one application. I installed all the things. When I run this application I got this error. "template_root". Please clear my problem. And How can I create one application by using the comatose. Please send the sample application if available. Thank you, srinivas rao.pala -- Posted via http://www.ruby-forum.com/.
2009 Sep 07
1
dahdi/DTMF problem
I posted about this before without ever finding a solution, so I'm trying again. I am upgrading from Fedora 8, asterisk-1.4.21, and zaptel 1.4.11 to Fedora 11, asterisk-1.6.1 and dahdi-2.1 . I have a couple of VOIP phones via SIP and one Wildcard TDM400P REV I with 3 FXS and one FXO port. I am using the same extensions.conf with as few mods as possible. Obviously I have had to convert from a
2010 Jan 07
1
error compile dahdi with latest kernels.
hello, all of users: there are header files missed when you compile dahdi with kernel-2.6.29 or 2.6.33. i believe that few files are affected: wctdm.c dahdi-base.c wcb4xxp/base.c, opvxa1200.c... the errors look like these: ================================================ from?/usr/src/dahdi-linux-complete-2.2.0.2+2.2.0/linux/drivers/dahdi/dahdi-base.c:61:
2009 Mar 25
2
New CentOS 5 repo: dahdi, asterisk, freepbx RPMs
Dear list, I've set up an RPM repository with several asterisk-related RPMs that I think contain some improvements upon what are already out there. The first goal is to be able to build an Asterisk + FreePBX system on CentOS 5 with the EPEL repo enabled; in our environment, where all our systems are under configuration management, either an appliance-type solution or a manual
2011 Jul 23
1
Why are all repos < 5.6 listed?
Greetings all. I just enabled all repos on my system, to enable me to find a particular package. This is the first time I have noticed all the Centos repos < 5.6 being listed. Is this a new feature, to include all repos pre 5.6 now? Here's the output of the aforementioned yum command - sorry it's a little bit long: [root at karsites ~]# yum --enablerepo '*' --disablerepo