--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Looking at the code, class
> device is already doing it that way, so here's the full-assed fix.
> Chris, can you please test the attached patch?
Tejun,
So far so good; my 2.6.20.11+patch kernel hasn't oopsed yet. I'm going to start
using this kernel
as
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Okay, here's a half-assed fix. With this patch applied, if you try to
> unload a module while you're opening it's dev attribute, kernel will
> oops later when the file is accessed or closed later but it should fix
> the bug winecfg triggers. I really dun
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> So, we can fix the problem Chris is seeing by breaking module unload (by
> allowing it to unload too early). It doesn't sound too hot but module
> unloading race is much less likely than sysfs node deletion/open race.
Yikes! Just temporary breakage, I ho
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Okay, here's patch against 2.6.20.11. Let's hope we're not chasing
> something which is already fixed.
Doh! I was expecing an "oops" (it still hasn't), but maybe this is what you
were expecting
instead?
Cheers,
Chris
__
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Okay, here's patch against 2.6.20.11. Let's hope we're not chasing
> something which is already fixed.
Hi,
I've been trying to trigger this bug on a patched 2.6.20.11 kernel for over 30
minutes without
success. sysfs operations are noticeably slower to
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Ah.. one thing to note. The echo'ing should happen before the node is
> created, so you can...
>
> 1. unplug and replug the particular device after specifying the node to
> trace.
>
> 2. (unload and) load usb host module after echoing
>
> 3. boot the k
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Okay, here's patch against 2.6.20.11. Let's hope we're not chasing
> something which is already fixed.
Thanks. I doubt it is fixed - there was a suspiciously similar report in a very
late rc candidate
for 2.6.21. From Ingo Molnar, I believe.
Cheers,
Ch
Will this patch apply against 2.6.20.x? I haven't tried triggering this problem
on 2.6.21.x yet.
Cheers,
Chris
___
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
--
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> However it is usually the same endpoint number and the same device (even
> if the device number changes)? In that case we can tell the code where to
> look for errors, because we will always know when that particular endpoint
> file is created and whe
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> When the crash does occur, does it always involve the same sysfs file (or
> at least, the same endpoint number for the same device)?
Not always, no. But it *usually* does. This is the endpoint whose directory is
being repeatedly
created and destroyed.
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> I'm curious whether recent sysfs rework makes the problem go
> away but as -mm containing those updates aren't released yet, there's no
> easy tree to test.
I'm not sure that this would help much. All I've ever been able to do here is
hammer on a
particu
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> How much hammering does it usually take?
Typically, I sit at the keyboard for between 5 and 10 minutes starting and
exiting winecfg over
and over again. Opening the "Audio" tab sometimes (but not always) helps. Once,
I was "lucky"
enough to see the prob
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> Dear me, what makes you think we are unconcerned?
Probably because this sentence:
> > > There may indeed be a race condition somewhere, but so far you haven't
> > > proved there is or pinned down exactly where.
reads like "Go away and find it then!".
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> There may indeed be a race condition somewhere, but so far you haven't
> proved there is or pinned down exactly where.
However, I have *definitely* demonstrated the existence of a memory-corrupting
**BUG**. I am
consistently amazed by how unconcerned ev
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> I see. They're static alright. That leaves us with sd pointing to
> the wrong attr. I'll take a look whether that's possible.
I put a few printks in sysfs_remove_file() to see precisely what winecfg is
doing, and it looks as
if the ALSA OSS emulation
Hi,
I have been hitting this bug regularly in the 2.6.20.x kernels:
http://bugzilla.kernel.org/show_bug.cgi?id=8198
What *seems* to be happening is that something (winecfg?) is causing the USB
layer to allocate a
new endpoint directory in /sys, and then quickly deallocate it again. However,
so
Hi,
I few weeks ago, my USB DVB device oopsed when I unplugged it:
Apr 14 14:47:53 volcano kernel: usb 4-6: new high speed USB device using
ehci_hcd and address 3
Apr 14 14:47:53 volcano kernel: usb 4-6: configuration #1 chosen from 1 choice
Apr 14 14:47:53 volcano kernel: dvb-usb: found a 'Haup
--- David Brownell <[EMAIL PROTECTED]> wrote:
> According to the descriptors you posted, regular cdc_ether should work
> with this device. Maybe even rndis_host. If that doesn't work, please
> post the "lsusb -v" output for the device, as well as CONFIG_USB_DEBUG
> diagnostics for any failures y
--- David Brownell <[EMAIL PROTECTED]> wrote:
> According to the descriptors you posted, regular cdc_ether should work
> with this device. Maybe even rndis_host. If that doesn't work, please
> post the "lsusb -v" output for the device, as well as CONFIG_USB_DEBUG
> diagnostics for any failures y
Hi,
The BT Voyager 210 USB ADSL modem is a small Linux box that has both a USB and
an Ethernet port
internally bound into a bridge device. I can't see why anyone would choose to
use the USB 1.1
network port over the Ethernet one for multi-Mbps ADSL, but that's no reason
why the USB port
shouldn
Hi,
I am trying to get the ball rolling on writing a new
hostap_usb driver for Prism2.5 / 3 devices. I am
moderately familiar with how the linux-wlan-ng driver
works, although I don't have any official
documentation from Intersil on the subject.
Basically, prism2_usb uses the Bulk-In and Bulk-Ou
Hi,
I've booted 2.6.9-final on this machine and tried
using the PL2303 again. I'm happy to report that the
oops is now gone:
...
usb 5-5.4: new full speed USB device using address 3
drivers/usb/serial/usb-serial.c: USB Serial support
registered for Generic
usbcore: registered new driver usbserial
Linux 2.6.8.1-SMP on a UP machine, devfs, gcc-3.4.2
I received this error when unplugging my PL2303 USB
serial converter from my USB 2.0 hub. (Not that the
device worked when I tried to use it anyway.)
Here's the tail of the dmesg output:
...
usb 5-5.4: PL-2303 converter now attached to ttyUSB0
Hi,
I am running an SMP 2.6.8.1 Linux kernel on a
uni-processor PIII machine. The kernel is compiled
with gcc-3.4.1.
I have just added a USB 2.0 internal powererd hub to
this machine so that I have four convenient ports on
the front of the box rather then 3 inaccessible ones
on the back. The new
> If you can, could
> you try out the 2.4.18-rc2-gregkh-1 patch that will apply cleanly on top
> of 2.4.18 and let us know if that fixes your problem?
>
>http://www.kernel.org/pub/linux/kernel/people/gregkh/usb/linux-2.4.18-rc2-gregkh-1.patch.gz
Hi,
I have just tried the rc2-gregkh-1 pat
Hi,
This "bug" message has just turned up in my log, and I'm not sure
whose bug it is:
Dec 29 00:22:45 twopit kernel: usb-ohci.c: bug in call from f888f0b2; use async!
Dec 29 00:22:45 twopit kernel: hfa384x_docmd: hfa384x_docmd:ctlx failure=REQ_TIMEOUT
Dec 29 00:22:45 twopit kernel: hfa384x_drvr
Hi,
I noticed that the USB scanner module is still using the Linux 2.2
module locking scheme. Here is a patch to make it use the v2.4 scheme.
Cheers,
Chris
--- linux-2.4.17/drivers/usb/scanner.c.orig Sat Dec 22 00:10:06 2001
+++ linux-2.4.17/drivers/usb/scanner.c Sat Dec 22 00:13:14 2001
@
Hi,
I have discovered that Linux has a macro called SET_MODULE_OWNER()
which sets an "owner" field to THIS_MODULE. This macro has the added
benefit of not generating any code for non-modular builds, and so I
have modified my patches accordingly.
Cheers,
Chris
--- linux-2.4.16/drivers/usb/CDCEth
Hi,
And while I'm at it, here is a module-locking patch for the USB
scanner devices.
Cheers,
Chris
--- linux-2.4.16/drivers/usb/scanner.c.orig Wed Dec 5 00:18:19 2001
+++ linux-2.4.16/drivers/usb/scanner.c Wed Dec 5 00:19:29 2001
@@ -348,8 +348,6 @@
int err=0;
- MOD_INC
Hi,
This patch is along the same lines as the module-locking patch I made
for the pegasus.o driver, and updates the kaweth.o driver to use the
2.4-style locks.
Cheers,
Chris
--- linux-2.4.16/drivers/usb/kaweth.c.orig Tue Dec 4 23:37:07 2001
+++ linux-2.4.16/drivers/usb/kaweth.c Tue Dec
Hi,
Here's a quick patch that updates the module locking in the Linux
2.4.16 USB OV511 video driver. I can successfully compile the module,
but cannot actually test it because I don't have suitable hardware.
Cheers,
Chris
--- linux-2.4.16/drivers/usb/ov511.c.orig Tue Dec 4 17:36:05 2001
Hi,
I was poking around with the USB code and I noticed that the SE401
module used the old Linux 2.2-style module locking. I have created a
patch which I *think* will update the driver to 2.4-style module
locking, but unfortunately I don't have any such hardware to test
with. However, I can at le
Hi,
I have noticed that the Pegasus II driver in the Linux 2.4.16 kernel
uses the old Linux 2.2-style module locking. I have attached a patch
that updates the driver to the new 2.4-style module locking instead.
Cheers,
Chris
--- drivers/usb/pegasus.c.orig Tue Dec 4 13:35:54 2001
+++ drivers/u
Hi,
I recently saw an article in Linux Journal about writing a USB device
driver. One thing that leapt out at me was that the skeleton driver
code called MOD_INC_USE_COUNT and MOD_DEC_USE_COUNT in the
file_operations open and release methods. Aren't these macros Linux
2.2-isms that have been made
Hi,
The khubd kernel thread is still allowing zombie processes:
$ pstree
init-+-agetty
|-bdflush
|-cron
|-devfsd
|-inetd-+-in.telnetd---bash---pstree
| `-in.telnetd---bash
|-kacpid
|-keventd
|-khubd-+-scsi_eh_0
| `-usb-storage-0
|-klo
35 matches
Mail list logo
