On Wed, 2007-03-07 at 10:10 -0800, Pete Zaitcev wrote:
Anyway, please look at the patch which I sent and see if you find any
races, especially on rmmod and reader exits.
I'm sorry for the long delay in answering your mail. The last few days
where pretty busy and I've no better hope for next :-(
On Tue, 13 Mar 2007 00:51:32 -0700 [EMAIL PROTECTED] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=8190
Summary: ehci_hcd can't reinitialize scanner after suspendresume
Kernel Version: 2.6.20, 2.6.21-rc3-gbe521466
Status: NEW
Severity: normal
Am Dienstag, 13. März 2007 10:00 schrieb Andrew Morton:
On Tue, 13 Mar 2007 00:51:32 -0700 [EMAIL PROTECTED] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=8190
Summary: ehci_hcd can't reinitialize scanner after suspendresume
Kernel Version: 2.6.20,
Hi,
there is a gross endianness violation in mos7720_interrupt_callback.
You cannot assume that you can simply cast into unsigned int data
coming over the wire.
Could you clarify which order is the correct wire order?
Regards
Oliver
--
SUSE LINUX Products GmbH, GF:
On Po, 2007-03-12 at 16:06 -0400, Alan Stern wrote:
On Sun, 11 Mar 2007, Milan Plzik wrote:
Hello,
I noticed that there could potentially be a sort of race condition in
ohci-hcd.c file, related to interrupt handling. This caused Oops when
removing ohci_hcd driver on one device I
On Mon, Mar 12, 2007 at 09:55:14PM -0400, Mark Lord wrote:
Jim Radford wrote:
On Mon, Mar 12, 2007 at 05:18:19PM -0700, Greg KH wrote:
On Mon, Mar 12, 2007 at 03:59:22PM -0700, Jim Radford wrote:
On Mon, Mar 12, 2007 at 03:42:35PM -0700, Jim Radford wrote:
On Mon, Mar 12, 2007 at 01:33:31PM
Am Dienstag, 13. März 2007 10:14 schrieb Jim Radford:
So where does the memory get freed -- the structure pointed at
by the serial-port[i] thingie ? It's not a leak, is it?
It gets free'd through device_unregister
for (i = 0; i num_ports; ++i) {
...
Hi,
this driver has an interesting way of handling ENOMEM: complain and ignore.
If you decide to live with allocation failures, you must
1. guard against URBs without corresponding buffers
2. complete allocation failures
3. always test entries for NULL before you follow the pointers
This patch
Oliver Neukum wrote:
If we get to destroy_serial(), how can ports still be open?
(1) open up a ckermit session on /dev/usb_serial_port_0.
(2) suspend the machine (to RAM).
(3) the suspend logic removes all USB devices.
Cheers
Am Dienstag, 13. März 2007 14:39 schrieb Mark Lord:
Oliver Neukum wrote:
If we get to destroy_serial(), how can ports still be open?
(1) open up a ckermit session on /dev/usb_serial_port_0.
(2) suspend the machine (to RAM).
(3) the suspend logic removes all USB devices.
No,
any open
Jim Radford wrote:
On Mon, Mar 12, 2007 at 09:55:14PM -0400, Mark Lord wrote:
So where does the memory get freed -- the structure pointed at
by the serial-port[i] thingie ? It's not a leak, is it?
It gets free'd through device_unregister
for (i = 0; i num_ports; ++i) {
...
Hi Dirk,
the driver has some additional flaws. The attached patch together
with the two other patches I sent you today should fix them. Would
you test this?
Regards
Oliver
--
--- a/drivers/usb/serial/mos7720.c 2007-03-13 14:11:20.0 +0100
+++
This patch (as865) fixes a race in the HCD removal code discovered by
Milan Plzik. Arrival of an interrupt after the root hub was
unregistered could cause the root-hub status timer to start up, even
after it was supposed to have been shut down. The problem is fixed by
moving the del_timer_sync()
On Thu, 8 Mar 2007, Linos wrote:
Wow your trick save my life :), it works like a charm, it detects now
and print very well in cups hehehe, many thanks Alan. The problem i have
now it is that i will have to patch any new kernel version with this
hack and i will have to admin about 70 Debian
On Tue, 13 Mar 2007, Greg KH wrote:
On Tue, Mar 13, 2007 at 11:10:52AM -0400, Alan Stern wrote:
This patch (as865) fixes a race in the HCD removal code discovered by
Milan Plzik. Arrival of an interrupt after the root hub was
unregistered could cause the root-hub status timer to start up,
I'm moving this thread over to the linux-usb-devel list, because it now
seems more appropriate here.
To bring people up to speed, Gordon has noticed that his low-speed USB
mouse gets frequent -EILSEQ errors, every 20 seconds or so, even when the
mouse is just sitting idle. This is a low-level
On Tue, Mar 13, 2007 at 09:55:41AM -0400, Mark Lord wrote:
Jim Radford wrote:
On Mon, Mar 12, 2007 at 09:55:14PM -0400, Mark Lord wrote:
So where does the memory get freed -- the structure pointed at
by the serial-port[i] thingie ? It's not a leak, is it?
It gets free'd through
This email lists some known regressions in Linus' tree compared to 2.6.20.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any other way
possibly
Jim Radford wrote:
...
This patch reverts d9a7ecacac5f8274d2afce09aadcf37bdb42b93a since it
breaks drivers that need to access the -port[] array in shutdown
(most of them).
Patch applied, tested, works for me.
Signed-Off: Jim Radford [EMAIL PROTECTED]
Acked-by: Mark Lord [EMAIL PROTECTED]
On Tue, Mar 13, 2007 at 07:04:15PM +0100, Toralf F?rster wrote:
Hello,
the build with the attached .config failed, make ends with:
...
HOSTCC arch/i386/boot/tools/build
BUILD arch/i386/boot/bzImage
Root device is (3, 8)
Boot sector 512 bytes.
Setup is 6872 bytes.
System is 2559
This patch (as866) adds new entry points for external USB device
suspend and resume requests, as opposed to internally-generated
autosuspend or autoresume. It also changes the existing
remote-wakeup code paths to use the new routines, since remote wakeup
is not the same as autoresume.
As part of
This patch (as867) adds an entry for the new power/autosuspend
attribute in Documentation/ABI/testing, and it changes the behavior of
the delay value. Now a delay of 0 means to autosuspend as soon as
possible, and negative values will prevent autosuspend.
Signed-off-by: Alan Stern [EMAIL
Alan Stern wrote:
It would help if you could try out 2.6.20, since it is the most recent
kernel. Verify that changing those two config settings causes the errors
to start, whereas changing any one of them eliminates the errors.
2.6.20 behaves the same. If I built a preemptible kernel,
On Ut, 2007-03-13 at 11:32 -0400, Alan Stern wrote:
On Tue, 13 Mar 2007, Greg KH wrote:
On Tue, Mar 13, 2007 at 11:10:52AM -0400, Alan Stern wrote:
This patch (as865) fixes a race in the HCD removal code discovered by
Milan Plzik. Arrival of an interrupt after the root hub was
Hi,
On vanilla kernel 2.6.20, Netac OnlyDisk Mini 512MB usb stick lets you
write a file and copy it from the device until it is unmounted. Upon
mounting the device again, attempts to copy the file written on last
mount results in SCSI I/O errors and the cp command eventually failing
(see error
On Tue, 13 Mar 2007, Gordon Messmer wrote:
Alan Stern wrote:
It would help if you could try out 2.6.20, since it is the most recent
kernel. Verify that changing those two config settings causes the errors
to start, whereas changing any one of them eliminates the errors.
2.6.20
On Wed, 14 Mar 2007, Edward Chapman wrote:
Hi,
On vanilla kernel 2.6.20, Netac OnlyDisk Mini 512MB usb stick lets you
write a file and copy it from the device until it is unmounted. Upon
mounting the device again, attempts to copy the file written on last
mount results in SCSI I/O errors
独占広告━━━
◆家のパソコンを利用して、収入を得たい方
◆空いた時間を利用して副業したい方
◆自由な時間を利用しておこづかいを稼ぎたい主婦の方
FSS Home Office World Office inc.
≪第１７期募集要項≫
http://www.j-netshop.com/business.htm
※すでにアメリカとヨーロッパで成功しているシステムを
28 matches
Mail list logo
