On Mon, 19 Mar 2007, Michael Schwarz wrote:
> Yeah; But here was where I lacked confidence. I used to know every inch of
> my kernel and my hardware, but, as previously stated, that was back in the
> 2.2.x days. I wasn't confident that I could run my hardware with a
> plain-vanilla kernel or that
Comments below.
--
Michael Schwarz
> On Mon, 19 Mar 2007, Michael Schwarz wrote:
>
>> I'm going to hang on to the hardware. This is a pilot/demo that may lead
>> to development of a new device, and, if so, I'll be getting back into
>> device driver writing. Working this problem would be great pr
On Mon, 19 Mar 2007, Michael Schwarz wrote:
> I'm going to hang on to the hardware. This is a pilot/demo that may lead
> to development of a new device, and, if so, I'll be getting back into
> device driver writing. Working this problem would be great practice for
> that. So I will do it. The only
I'm going to hang on to the hardware. This is a pilot/demo that may lead
to development of a new device, and, if so, I'll be getting back into
device driver writing. Working this problem would be great practice for
that. So I will do it. The only problem is I don't know when!
I believe I can repli
Michael Schwarz wrote:
> More than ever, I am convinced that it is actually a hardware problem, but
> I am curious for the opinions of both of you on whether the "system"
> (meaning, I guess, the combination of usb-storage driver and raid) is
> really doing the best with what it has.
>
See belo
More than ever, I am convinced that it is actually a hardware problem, but
I am curious for the opinions of both of you on whether the "system"
(meaning, I guess, the combination of usb-storage driver and raid) is
really doing the best with what it has.
My last effort was to switch to a different
On Sunday March 18, [EMAIL PROTECTED] wrote:
> cp -rv /mnt/* fs2d2/
>
> At this point, the process hangs. So I ran:
>
> echo t > /proc/sysrq-trigger
> dmesg > dmesg-5-hungread.log
Unfortunate (as you say) the whole trace doesn't fit.
Could you try compiling the kernel with a larger value for
CON
Just tried in on a stock Ubuntu Edgy install. Same thing. Locks on read.
I've got a dmesg (w/stack trace) file from the ubuntu attempt (it was
clean prior to doing the read) which I will send to Alan and Neil (any
anyone else who asks for it). There were no error messages in dmesg prior
to running
Michael Schwarz wrote:
> I've tried both single and multiple files. The files are not sparse. They
> are highly compressed files (mpeg files) that would, to the filesystem, be
> nearly random with no repeated patterns or voids.
>
>
Good, one possible cause eliminated.
--
bill davidsen <[EMAIL
As I suspected, majordomo doesn't like attachments.
I looked through the logs. The only odd thing I see before the read that
hangs is this message:
smartd[3069]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
Which I only see in /var/log/messages because the stack dump blows
whatever
I've tried both single and multiple files. The files are not sparse. They
are highly compressed files (mpeg files) that would, to the filesystem, be
nearly random with no repeated patterns or voids.
--
Michael Schwarz
> Michael Schwarz wrote:
>> Update:
>>
>> (For those who've been waiting breat
Michael Schwarz wrote:
> Update:
>
> (For those who've been waiting breathlessly). It hangs at a particular
> point in a particular file. In other words, it doesn't depend on the total
> number of bytes transfered. Rather, when it reaches a particular point in
> a particular file (12267520 bytes in
Yeah, I understand that.
Sorry, I use squirrelmail. Pretty limited...
I'll get you a "raw" dmseg output when I replicate the problem.
Let me clarify on khubd: There is such an entry in my process table, but
there was no kernel thread stack trace for it when I dumped the traces. I
don't know if t
On Sat, 17 Mar 2007, Michael Schwarz wrote:
> Nasty big stack trace set follows:
This format is kind of awkward. For one thing, a lot of lines were
wrapped by your email program.
For another, you copied the stack trace from the syslog log file. That is
not a good way to do it; syslogd is lia
On Sat, 17 Mar 2007, Michael Schwarz wrote:
> Comments/questions below...
>
> --
> Michael Schwarz
>
> > This isn't much help. The important processes here are khubd,
> > usb-storage, and scsi_eh_*. Possibly some raid-related processes too, but
> > I don't know which they would be.
>
> I have
Comments/questions below...
--
Michael Schwarz
>
> This isn't much help. The important processes here are khubd,
> usb-storage, and scsi_eh_*. Possibly some raid-related processes too, but
> I don't know which they would be.
I have no copy khubd running. What is the list policy on attachment
On Sat, 17 Mar 2007, Michael Schwarz wrote:
> Neil:
>
> Relevant stack trace follows. Any suggestions? blk_backing_dev_unplug...
> Does that mean the raid subsystem thinks one of the usb drives has been
> removed? I assure you that physically this is untrue, but that doesn't
> mean that some sort
Update:
(For those who've been waiting breathlessly). It hangs at a particular
point in a particular file. In other words, it doesn't depend on the total
number of bytes transfered. Rather, when it reaches a particular point in
a particular file (12267520 bytes into a file that is 1073709056 bytes
I'll try playing around with IO sizes with dd.
What I'm finding so far is ABSOLUTE consistency on where it locks. If it
were a race condition with kernel locks I guess I would expect it to be
more indeterminate (in my limited experience) unless it is due to specific
"deadly embrace" condition betw
Neil:
Relevant stack trace follows. Any suggestions? blk_backing_dev_unplug...
Does that mean the raid subsystem thinks one of the usb drives has been
removed? I assure you that physically this is untrue, but that doesn't
mean that some sort logical disconnect hasn't happened...
Makes me wonder i
On Friday March 16, [EMAIL PROTECTED] wrote:
> I'm not a Linux newbie (I've even written a couple of books and done some
> very light device driver work), but I'm completely new to the software
> raid subsystem.
>
> I'm doing something rather oddball. I'm making an array of USB flash
> drives and
Hi,
I hope this is the right list for this question.
I have an Audigy 2 NX USB external sound device. It works correctly
under XP, and worked briefly under linux. Now I cannot get it to
initialize, with the same error on the machine which previously
worked. It also fais to initialize from my l
The file you have sent was infected with a virus but InterScan E-Mail VirusWall
could not clean it.
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which produ
The file you have sent was infected with a virus but InterScan E-Mail VirusWall
could not clean it.
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which produ
Hello all,
I have a quickcam express and when I load the drivers it finds the
camera but I get this error,
usb_unlink_urb()=-19 failed!
Any help will be appreciated.
Thanks,
Craig
---
This SF.net email is sponsored by: SF.net Giveback Progra
25 matches
Mail list logo
