Re: [Linux-usb-users] USB device not detected
On Fri, 13 Jul 2007, Haines Brown wrote: > > To get more information, build a kernel with CONFIG_USB_DEBUG turned > > > on. Then post the dmesg log showing what happens when you plug in the > > camera. > > Sorry, I should have mentioned I'm running a stock kernel. > > Over the years I never dared to build a custom kernel, for not only do > I lack the time for it, but I'm intimidated by the prospect. It can indeed be intimidating. But it's also interesting; you might want to try it. The key is to avoid building too many drivers. Configuring only the ones you need will save a tremendous amount of time. > Am I to infer from your statement that one can't really find out how > the kernel is responding to the attachment of my camera without > turning CONFIG_USB_DEBUG on? I gather is off in the stock kernel. It's the simplest way. If your kernel has usbmon and debugfs configured then you can use them instead (see the kernel source file Documentation/usb/usbmon.txt for instructions). Alan Stern - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] dingy flamboyantly
SZSN Goes Through The Roof! UP 37.5% Shandong Zhouyuan Seed and Nursery Co., Ltd (SZSN) $0.33 UP 37.5% Brokers are grabbing up SZSN like crazy after two news releases this week. Huge expansion plus multi-million dollar development projects are pushing share prices through the roof. Act fast and get on SZSN first thing Monday! Business relationshipsThis Web site may provide links or references to non-IBM Web sites and resources. WITHOUT LIMITATION, IBM MAKES NO WARRANTY OR GUARANTEE THAT THIS WEB SITE WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE. ALL MATERIALS, INFORMATION, PRODUCTS, SOFTWARE, PROGRAMS, AND SERVICES ARE PROVIDED "AS IS," WITH NO WARRANTIES OR GUARANTEES WHATSOEVER. Personally-identifiable information that you submit to IBM for the purpose of receiving products or services will be handled in accordance with our privacy policies. If you do not agree to these terms, please do not use this Web site. WITHOUT LIMITATION, IBM MAKES NO WARRANTY OR GUARANTEE THAT THIS WEB SITE WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE. government restricted rightsIBM provides the software downloaded from this Web site to U. Confidential informationIBM does not want to receive confidential or proprietary information from you through our Web site. government restricted rightsIBM provides the software downloaded from this Web site to U. When you access a non-IBM Web site, even one that may contain the IBM-logo, please understand that it is independent from IBM, and that IBM does not control the content on that Web site. About IBM Privacy Contact THIS EXCLUSION AND WAIVER OF LIABILITY APPLIES TO ALL CAUSES OF ACTION, WHETHER BASED ON CONTRACT, WARRANTY, TORT, OR ANY OTHER LEGAL THEORIES. You also agree that IBM is free to use any ideas, concepts, know-how, or techniques that you send us for any purpose. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] USB device not detected
> On Fri, 13 Jul 2007, Haines Brown wrote: > > > $ uname -a > > Linux teufel 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 > > GNU/Linux > To get more information, build a kernel with CONFIG_USB_DEBUG turned > on. Then post the dmesg log showing what happens when you plug in the > camera. Sorry, I should have mentioned I'm running a stock kernel. Over the years I never dared to build a custom kernel, for not only do I lack the time for it, but I'm intimidated by the prospect. Am I to infer from your statement that one can't really find out how the kernel is responding to the attachment of my camera without turning CONFIG_USB_DEBUG on? I gather is off in the stock kernel. Haines Brown - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] Seagate Device Timing Out -- Needs Reset.
I have a Seagate external 500GB drive that has a problem with Linux. What's going on (I'm guessing) is that, after a period of inactivity, the drive goes into an odd state (probably low-power), and the next read request results in a read error. (see below). What catches my eye is: Jul 13 14:30:49 steve-dev kernel: [344664.233185] Additional sense: Logical unit not ready, initializing command required It seems to me that this error is requesting that the device be restarted. Couldn't the normal response to this sense code be to reset the device and/or allow it to resettle, rather than throwing an error back into user space? It's really annoying to have your external hard drive 'randomly' disappear when you go for lunch. # dd if=/dev/sdd of=/dev/null skip=22 count=3 dd: reading `/dev/sdd': Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.0405675 seconds, 0.0 kB/s # = Jul 13 14:30:49 steve-dev kernel: [344664.227652] sd 11:0:0:0: Device not ready: <6>: Current: sense key: Not Ready Jul 13 14:30:49 steve-dev kernel: [344664.227665] Additional sense: Logical unit not ready, initializing command required Jul 13 14:30:49 steve-dev kernel: [344664.227674] end_request: I/O error, dev sdd, sector 16 Jul 13 14:30:49 steve-dev kernel: [344664.227679] Buffer I/O error on device sdd, logical block 2 Jul 13 14:30:49 steve-dev kernel: [ 344664.233173] sd 11:0:0:0: Device not ready: <6>: Current: sense key: Not Ready Jul 13 14:30:49 steve-dev kernel: [344664.233185] Additional sense: Logical unit not ready, initializing command required Jul 13 14:30:49 steve-dev kernel: [ 344664.233193] end_request: I/O error, dev sdd, sector 16 Jul 13 14:30:49 steve-dev kernel: [344664.233199] Buffer I/O error on device sdd, logical block 2 lsusb output available on request. This is running ubuntu 7.0.4 # uname -a Linux steve-dev 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux # -- Stephen Samuel http://www.bcgreen.com 778-861-7641 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] [PATCH 5/5] use mutex instead of semaphore in the FTDI ELAN driver
The FTDI ELAN driver uses a semaphore as mutex. Use the mutex API
instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/usb/misc/ftdi-elan.c b/drivers/usb/misc/ftdi-elan.c
index e0f122e..7cc6883 100644
--- a/drivers/usb/misc/ftdi-elan.c
+++ b/drivers/usb/misc/ftdi-elan.c
@@ -44,6 +44,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -64,7 +65,7 @@ static struct workqueue_struct *respond_queue;
* ftdi_module_lock exists to protect access to global variables
*
*/
-static struct semaphore ftdi_module_lock;
+static struct mutex ftdi_module_lock;
static int ftdi_instances = 0;
static struct list_head ftdi_static_list;
/*
@@ -199,10 +200,10 @@ static void ftdi_elan_delete(struct kref *kref)
dev_warn(&ftdi->udev->dev, "FREEING ftdi=%p\n", ftdi);
usb_put_dev(ftdi->udev);
ftdi->disconnected += 1;
-down(&ftdi_module_lock);
+mutex_lock(&ftdi_module_lock);
list_del_init(&ftdi->ftdi_list);
ftdi_instances -= 1;
-up(&ftdi_module_lock);
+mutex_unlock(&ftdi_module_lock);
kfree(ftdi->bulk_in_buffer);
ftdi->bulk_in_buffer = NULL;
}
@@ -2780,10 +2781,10 @@ static int ftdi_elan_probe(struct usb_interface
*interface,
return -ENOMEM;
}
memset(ftdi, 0x00, sizeof(struct usb_ftdi));
-down(&ftdi_module_lock);
+mutex_lock(&ftdi_module_lock);
list_add_tail(&ftdi->ftdi_list, &ftdi_static_list);
ftdi->sequence_num = ++ftdi_instances;
-up(&ftdi_module_lock);
+mutex_unlock(&ftdi_module_lock);
ftdi_elan_init_kref(ftdi);
init_MUTEX(&ftdi->sw_lock);
ftdi->udev = usb_get_dev(interface_to_usbdev(interface));
@@ -2909,7 +2910,7 @@ static int __init ftdi_elan_init(void)
int result;
printk(KERN_INFO "driver %s built at %s on %s\n",
ftdi_elan_driver.name,
__TIME__, __DATE__);
-init_MUTEX(&ftdi_module_lock);
+mutex_init(&ftdi_module_lock);
INIT_LIST_HEAD(&ftdi_static_list);
status_queue = create_singlethread_workqueue("ftdi-status-control");
if (!status_queue)
--
Matthias Kaehlcke
Linux Application Developer
Barcelona
If liberty means anything at all, it means the
right to tell people what they do not want to hear
(George Orwell)
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] [PATCH 4/5] use mutex instead of semaphore in the Adutux driver
The Adutux driver uses a semaphore as mutex. Use the mutex API
instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/usb/misc/adutux.c b/drivers/usb/misc/adutux.c
index d72c42e..274d08e 100644
--- a/drivers/usb/misc/adutux.c
+++ b/drivers/usb/misc/adutux.c
@@ -24,6 +24,7 @@
#include
#include
#include
+#include
#include
#ifdef CONFIG_USB_DEBUG
@@ -80,7 +81,7 @@ MODULE_DEVICE_TABLE(usb, device_table);
/* Structure to hold all of our device specific stuff */
struct adu_device {
- struct semaphoresem; /* locks this structure */
+ struct mutexmtx; /* locks this structure */
struct usb_device* udev; /* save off the usb device pointer */
struct usb_interface* interface;
unsigned char minor; /* the starting minor number for this
device */
@@ -269,8 +270,8 @@ static int adu_open(struct inode *inode, struct file *file)
}
/* lock this device */
- if ((retval = down_interruptible(&dev->sem))) {
- dbg(2, "%s : sem down failed", __FUNCTION__);
+ if ((retval = mutex_lock_interruptible(&dev->mtx))) {
+ dbg(2, "%s : mutex lock failed", __FUNCTION__);
goto exit_no_device;
}
@@ -299,7 +300,7 @@ static int adu_open(struct inode *inode, struct file *file)
if (retval)
--dev->open_count;
}
- up(&dev->sem);
+ mutex_unlock(&dev->mtx);
exit_no_device:
dbg(2,"%s : leave, return value %d ", __FUNCTION__, retval);
@@ -347,7 +348,7 @@ static int adu_release(struct inode *inode, struct file
*file)
}
/* lock our device */
- down(&dev->sem); /* not interruptible */
+ mutex_lock(&dev->mtx); /* not interruptible */
if (dev->open_count <= 0) {
dbg(1," %s : device not opened", __FUNCTION__);
@@ -357,7 +358,7 @@ static int adu_release(struct inode *inode, struct file
*file)
if (dev->udev == NULL) {
/* the device was unplugged before the file was released */
- up(&dev->sem);
+ mutex_unlock(&dev->mtx);
adu_delete(dev);
dev = NULL;
} else {
@@ -367,7 +368,7 @@ static int adu_release(struct inode *inode, struct file
*file)
exit:
if (dev)
- up(&dev->sem);
+ mutex_unlock(&dev->mtx);
dbg(2," %s : leave, return value %d", __FUNCTION__, retval);
return retval;
}
@@ -390,7 +391,7 @@ static ssize_t adu_read(struct file *file, __user char
*buffer, size_t count,
dev = file->private_data;
dbg(2," %s : dev=%p", __FUNCTION__, dev);
/* lock this object */
- if (down_interruptible(&dev->sem))
+ if (mutex_lock_interruptible(&dev->mtx))
return -ERESTARTSYS;
/* verify that the device wasn't unplugged */
@@ -522,7 +523,7 @@ static ssize_t adu_read(struct file *file, __user char
*buffer, size_t count,
exit:
/* unlock the device */
- up(&dev->sem);
+ mutex_unlock(&dev->mtx);
dbg(2," %s : leave, return value %d", __FUNCTION__, retval);
return retval;
@@ -543,7 +544,7 @@ static ssize_t adu_write(struct file *file, const __user
char *buffer,
dev = file->private_data;
/* lock this object */
- retval = down_interruptible(&dev->sem);
+ retval = mutex_lock_interruptible(&dev->mtx);
if (retval)
goto exit_nolock;
@@ -571,9 +572,9 @@ static ssize_t adu_write(struct file *file, const __user
char *buffer,
retval = -EINTR;
goto exit;
}
- up(&dev->sem);
+ mutex_unlock(&dev->mtx);
timeout =
interruptible_sleep_on_timeout(&dev->write_wait, timeout);
- retval = down_interruptible(&dev->sem);
+ retval = mutex_lock_interruptible(&dev->mtx);
if (retval) {
retval = bytes_written ? bytes_written : retval;
goto exit_nolock;
@@ -638,7 +639,7 @@ static ssize_t adu_write(struct file *file, const __user
char *buffer,
exit:
/* unlock the device */
- up(&dev->sem);
+ mutex_unlock(&dev->mtx);
exit_nolock:
dbg(2," %s : leave, return value %d", __FUNCTION__, retval);
@@ -698,7 +699,7 @@ static int adu_probe(struct usb_interface *interface,
goto exit;
}
- init_MUTEX(&dev->sem);
+ mutex_init(&dev->mtx);
spin_lock_init(&dev->buflock);
dev->udev = udev;
init_waitqueue_head(&dev->read_wait);
@@ -835,16 +836,16 @@ static void adu_disconnect(struct usb_interface
*interface)
usb_deregister_dev(interface, &adu_class);
dev->minor = 0;
- dow
[Linux-usb-users] [PATCH 3/5] use mutex instead of semaphore in the ELAN U132 adapter driver
The ELAN U132 adapter driver uses the semaphore u132_module_lock
as mutex. Use the mutex API instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/usb/host/u132-hcd.c b/drivers/usb/host/u132-hcd.c
index e98df2e..7f765ec 100644
--- a/drivers/usb/host/u132-hcd.c
+++ b/drivers/usb/host/u132-hcd.c
@@ -52,6 +52,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -83,7 +84,7 @@ static DECLARE_WAIT_QUEUE_HEAD(u132_hcd_wait);
* u132_module_lock exists to protect access to global variables
*
*/
-static struct semaphore u132_module_lock;
+static struct mutex u132_module_lock;
static int u132_exiting = 0;
static int u132_instances = 0;
static struct list_head u132_static_list;
@@ -258,10 +259,10 @@ static void u132_hcd_delete(struct kref *kref)
struct platform_device *pdev = u132->platform_dev;
struct usb_hcd *hcd = u132_to_hcd(u132);
u132->going += 1;
-down(&u132_module_lock);
+mutex_lock(&u132_module_lock);
list_del_init(&u132->u132_list);
u132_instances -= 1;
-up(&u132_module_lock);
+mutex_unlock(&u132_module_lock);
dev_warn(&u132->platform_dev->dev, "FREEING the hcd=%p and thus the
u13"
"2=%p going=%d pdev=%p\n", hcd, u132, u132->going, pdev);
usb_put_hcd(hcd);
@@ -3111,10 +3112,10 @@ static int __devinit u132_probe(struct platform_device
*pdev)
int retval = 0;
struct u132 *u132 = hcd_to_u132(hcd);
hcd->rsrc_start = 0;
-down(&u132_module_lock);
+mutex_lock(&u132_module_lock);
list_add_tail(&u132->u132_list, &u132_static_list);
u132->sequence_num = ++u132_instances;
-up(&u132_module_lock);
+mutex_unlock(&u132_module_lock);
u132_u132_init_kref(u132);
u132_initialise(u132, pdev);
hcd->product_desc = "ELAN U132 Host Controller";
@@ -3216,7 +3217,7 @@ static int __init u132_hcd_init(void)
INIT_LIST_HEAD(&u132_static_list);
u132_instances = 0;
u132_exiting = 0;
-init_MUTEX(&u132_module_lock);
+mutex_init(&u132_module_lock);
if (usb_disabled())
return -ENODEV;
printk(KERN_INFO "driver %s built at %s on %s\n", hcd_name, __TIME__,
@@ -3232,9 +3233,9 @@ static void __exit u132_hcd_exit(void)
{
struct u132 *u132;
struct u132 *temp;
-down(&u132_module_lock);
+mutex_lock(&u132_module_lock);
u132_exiting += 1;
-up(&u132_module_lock);
+mutex_unlock(&u132_module_lock);
list_for_each_entry_safe(u132, temp, &u132_static_list, u132_list) {
platform_device_unregister(u132->platform_dev);
} platform_driver_unregister(&u132_platform_driver);
--
Matthias Kaehlcke
Linux Application Developer
Barcelona
The salvation of mankind lies only in making everything the concern of all
(Alexander Solzhenitsyn)
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] (no subject)
TO：财务部、财务（收） 你好: 本公司从事全国发票代开业务。（建筑、运输、服务、广告、 商品销售、海关缴款书、增值税、），等均可对外开出， 开出的发票都可以到税务局得到验证和网上查询.欢迎来电咨询! 谢谢 联系人：钟先生 电话：13590451515 电话/传真： 电话：0755-81915430 E-mail:[EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] USB device not detected
On Fri, 13 Jul 2007, Haines Brown wrote: > $ uname -a > Linux teufel 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 > GNU/Linux > > I have a camera (Canon A510) that until recently could be accessed by > gphoto2, but now it is no longer seen on the bus. In syslog/kernlog, > there is no message when the camera is attached or detached. In > various gphoto2 debug messages, the camera not seen. The camera was > working with my computer in the past couple of weeks, and I don't > recall having done anything that might affect it. > > I assume that there are several possible reasons why the USB bus won't > show a device: a) the camera has to be powered up, b) the USB bus has > to be functional, c) the right drivers must be loaded, and d) device > hardware must not be broken. > > a) I connect the camera via the usual USB cable to an external USB hub, > plug in the external power, and I switch the camera on. > > b) The bus works with other devices, both on the root hub and extenral > hub. I changed the usb cable and plugged it into a different port on my > hub, but that didn't help. > > c) For my camera, I suspect all I need are the usual usb modules: > > $ lsmod | grep usb > usb_storage71840 0 > usblp 12768 0 > scsi_mod 124168 6 usb_storage,sbp2,sd_mod,libata, > aic79xx,scsi_transport_spi > ide_core 110504 4 usb_storage,ide_cd,amd74xx,generic > usbcore 112644 5 usb_storage,usblp,ohci_hcd,ehci_hcd > > d) What are the odds that the camera itself has broken? Is there > anything I might do to narrow the range of possibilities? I'm not > anxious to replace the camera and then find out that the problem > remains. To get more information, build a kernel with CONFIG_USB_DEBUG turned on. Then post the dmesg log showing what happens when you plug in the camera. Alan Stern - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] USB device not detected
$ uname -a Linux teufel 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686 GNU/Linux I have a camera (Canon A510) that until recently could be accessed by gphoto2, but now it is no longer seen on the bus. In syslog/kernlog, there is no message when the camera is attached or detached. In various gphoto2 debug messages, the camera not seen. The camera was working with my computer in the past couple of weeks, and I don't recall having done anything that might affect it. I assume that there are several possible reasons why the USB bus won't show a device: a) the camera has to be powered up, b) the USB bus has to be functional, c) the right drivers must be loaded, and d) device hardware must not be broken. a) I connect the camera via the usual USB cable to an external USB hub, plug in the external power, and I switch the camera on. b) The bus works with other devices, both on the root hub and extenral hub. I changed the usb cable and plugged it into a different port on my hub, but that didn't help. c) For my camera, I suspect all I need are the usual usb modules: $ lsmod | grep usb usb_storage71840 0 usblp 12768 0 scsi_mod 124168 6 usb_storage,sbp2,sd_mod,libata, aic79xx,scsi_transport_spi ide_core 110504 4 usb_storage,ide_cd,amd74xx,generic usbcore 112644 5 usb_storage,usblp,ohci_hcd,ehci_hcd d) What are the odds that the camera itself has broken? Is there anything I might do to narrow the range of possibilities? I'm not anxious to replace the camera and then find out that the problem remains. Haines Brown - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the "irqpoll" option)
On Fri, 13 Jul 2007, Dylan Taft wrote: > Thanks for the reply. > This started happening in 2.6.21 suddenly, which is why I tried > upgrading to 2.6.22. It seemed to have started happening when my > bluetooth light mysteriously went on one day. I went into bios and > disabled some IO devices earlier today; "Wireless USB", my firewire > port, and the bluetooth adapter. The bluetooth light went off, and > this has not happened since. I think it's safe to say it's not going > to happen again, since I was getting the IRQ messages every few > minutes and it's not happening at all now. I don't have any hardware > to test of those IO ports were working or not anyway... > > Some of the hardware in this laptop behaves strangely, like using the > madwifi drivers with the Atheros wireless will throw the device into a > state where it will not be recognized by ndiswrapper or anything until > I power down and pull the battery or boot Vista and then boot linux. > That's a known issue with the madwifi drivers and my chipset, I'm > wondering if something similar happened with the bluetooth > chipset/drivers. > > If anyone needs more info or wants me to try to reproduce the problem > let me know, but it's working for the moment again. It looks like > others have had the same issue. > http://www.thinkwiki.org/wiki/Installing_Debian_Lenny_on_a_ThinkPad_T61#Problems It would be a good idea for you to post this on the Bluetooth development list, to make those people aware of the possible problem. Alan Stern - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] All best software! EVER!
Adieu there , Riley DONT BE SILLY TO PAY HUNDREDS FOR SOFTWARE. Just check it out and get the most wanted latest 2007 edition softwared at dirt cheap rates. http://soffrkk.blogspot.com/ Microsoft Vista , office 2007/ Adobe / Macromedia / Corel and others Download Now http://sounerry.blogspot.com/ Download now before prices increase! Thank for reading. Riley Internet Marketing Manager http://sokjudduyi.blogspot.com/ discontinuing traditional activity might be - or if it will communicate thoughts on a widespread level - but to what level of confusing the general population with the meaning of the term. happen at all. The potential is real and the outcome might be efficiency? Is something lost in the philosophy if the artist is k4 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the "irqpoll" option)
Thanks for the reply. This started happening in 2.6.21 suddenly, which is why I tried upgrading to 2.6.22. It seemed to have started happening when my bluetooth light mysteriously went on one day. I went into bios and disabled some IO devices earlier today; "Wireless USB", my firewire port, and the bluetooth adapter. The bluetooth light went off, and this has not happened since. I think it's safe to say it's not going to happen again, since I was getting the IRQ messages every few minutes and it's not happening at all now. I don't have any hardware to test of those IO ports were working or not anyway... Some of the hardware in this laptop behaves strangely, like using the madwifi drivers with the Atheros wireless will throw the device into a state where it will not be recognized by ndiswrapper or anything until I power down and pull the battery or boot Vista and then boot linux. That's a known issue with the madwifi drivers and my chipset, I'm wondering if something similar happened with the bluetooth chipset/drivers. If anyone needs more info or wants me to try to reproduce the problem let me know, but it's working for the moment again. It looks like others have had the same issue. http://www.thinkwiki.org/wiki/Installing_Debian_Lenny_on_a_ThinkPad_T61#Problems Thanks, Dylan On 7/12/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Thu, 12 Jul 2007, Dylan Taft wrote: > > > Hi all. I'm using a vanilla linux-2.6.22 kernel. I just noticed I > > get these messages while my laptop is sitting around doing nothing, 2 > > of my USB ports get disabled. I'm not sure what's causing them, to > > reproduce I just let the laptop sit idle for maybe 5 minutes. rmmod > > uhci_hcd > > Sure you don't mean ehci_hcd? Acoording to your /proc/interrupts > listing, it is the driver using IRQ 23. > > > and modprobeing it brings it back for a few more minutes but > > the message pops back up. I'm using a Lenovo T61. Does anyone have > > any possible suggestions or kernel patches I can try? Thanks! > > These errors occur because some device is using IRQ 23 but the kernel > doesn't know it. Maybe the kernel thinks it is using some other IRQ or > maybe the kernel doesn't know of the device's existence at all. > > You could compare /proc/interrupts with earlier kernel versions to see > if anything has changed. > > Sometimes problems in the ACPI drivers can cause this behavior. You > can try booting with acpi=noirq. > > Alan Stern > > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
