On Sun, 19 Sep 2004, David Brownell wrote:
> On Saturday 18 September 2004 8:18 pm, Alan Stern wrote:
>
> > The "known bug" is that when an HCD module is rmmod'ed it doesn't wait for
> > all the USB device refcounts to go to 0 -- but when they do a routine in
> > the HCD is called to release some
On Saturday 18 September 2004 8:18 pm, Alan Stern wrote:
> The "known bug" is that when an HCD module is rmmod'ed it doesn't wait for
> all the USB device refcounts to go to 0 -- but when they do a routine in
> the HCD is called to release some memory.
That should be nearly fixable now, if it is
On Sun, 2004-09-19 at 08:31, Alan Stern wrote:
> > I think I'll simply kluge it: I'll add a line that says "modprobe
> > ehci-hcd" to the script responsible for umounting local file systems
> > upon shutdown. *shrug*
>
> No, don't do that! You'll still have unflushed buffers and lack of a
> clea
On Sat, 18 Sep 2004, Nix N. Nix wrote:
> On Sat, 2004-09-18 at 21:18, Alan Stern wrote:
> > The "known bug" is that when an HCD module is rmmod'ed it doesn't wait for
> > all the USB device refcounts to go to 0 -- but when they do a routine in
> > the HCD is called to release some memory. Of cour
On Sat, 2004-09-18 at 21:18, Alan Stern wrote:
> The "known bug" is that when an HCD module is rmmod'ed it doesn't wait for
> all the USB device refcounts to go to 0 -- but when they do a routine in
> the HCD is called to release some memory. Of course, if the HCD code has
> already been unloaded
On Sat, 18 Sep 2004, Nix N. Nix wrote:
> Rather, when I mount a partition, it should become impossible
> to rmmod ehci_hcd (or uhci_hcd, or whichever host controller the drive
> happens to be going through at the time) and all other modules involved
> in the access to the file system (such as s
On Sat, 18 Sep 2004 15:57:42 -0600
"Nix N. Nix" <[EMAIL PROTECTED]> wrote:
> On Sat, 2004-09-18 at 09:10, Alan Stern wrote:
> > At any rate, this oops occurs whenever a USB host controller driver is
> > unloaded while one of the devices it controls is still open. Your drive
> > was still open be
On Sat, 2004-09-18 at 09:10, Alan Stern wrote:
> At any rate, this oops occurs whenever a USB host controller driver is
> unloaded while one of the devices it controls is still open. Your drive
> was still open because it was mounted, and when the shutdown scripts
> unmounted it the oops was tri
On Fri, 17 Sep 2004, Nix N. Nix wrote:
> Just before the computer is about to start over, there's a crash. The
> last message is:
> INIT: No more processes left in this runlevel
>
> > For that matter, how did the kernel panic before when the system
> > was going down?
>
> Before the patch:
> sc
On Fri, 2004-09-17 at 08:12, Alan Stern wrote:
> > I just finished rebooting and, unfortunately the kernel panic-ed much as
> > it did before when the system was going down.
> >
> That's not much help to anybody. For one thing it's unclear: Did the
> kernel panic just as you finished rebooting or
On Thu, 16 Sep 2004, Nix N. Nix wrote:
> I have applied the patch, and now I am able to transfer files as large
> as 1.4GB to the drive. Nonetheless, messages such as the ones at the
> bottom of this mail are still being produced in the syslog. I find the
> fact that the messages are mangled - i
On Thu, 2004-09-16 at 16:06, Nix N. Nix wrote:
> I have applied the patch, and now I am able to transfer files as large
> as 1.4GB to the drive.
I just finished rebooting and, unfortunately the kernel panic-ed much as
it did before when the system was going down.
Conclusion: Transfers now seem
On Tue, 2004-09-14 at 11:39, Alan Stern wrote:
> Your problem is that the enclosure was made by Genesys Logic. It was only
> very recently that we have been able to get their USB-IDE bridges to work
> properly at high speed. The necessary changes aren't in 2.6.8.1, but they
> are in 2.6.9-rc1.
On Sun, 12 Sep 2004, Nix N. Nix wrote:
> Hi!
>
> I recently bought a USB drive enclosure and I'm experiencing the
> following problem with it:
>
> When I try writing to it, there's an I/O error after about 600MB, and
> the device corresponding to the destination partition (/dev/sda1)
> disappear
Hi!
I recently bought a USB drive enclosure and I'm experiencing the
following problem with it:
When I try writing to it, there's an I/O error after about 600MB, and
the device corresponding to the destination partition (/dev/sda1)
disappears from /dev.
I'm running kernel 2.6.8.1 (vanilla) on an
15 matches
Mail list logo
