-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Stern wrote:
|
| See http://marc.theaimsgroup.com/?l=linux-usb-users&m=109837385904817&w=2
|
| Alan Stern
|
|
The crash is gone. Many thanx
Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
I've got a system crash on 2.6.9 (i386) saying:
Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1688
AFAIK this has been reported before. But 2.6.8.1 works for
me. Can I help to get this fixed?
Regards
Harri
-BEGIN PGP SIGNATUR
Hi folks,
If I set CONFIG_BLK_DEV_UB, then the kernel dies at boot time.
I could reproduce this with 2.6.9-rc4 and the final 2.6.9
(both amd64).
AFAICS the ub driver is loaded automagically via hotplug.
Syslog says:
:
ACPI: PCI interrupt :00:02.2[C] -> GSI 11 (level, low) -> IRQ 11
ehci_hcd 000
PS: The ehci_hcd in 2.6.9-rc4-mm1 works better, as it seems.
Harri
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free Think
Hi folks,
Kernel 2.6.9-rc4, amd64:
If I do insmod ehci_hcd (which triggers some hotplug
events), then I get these messages in kern.log:
:
ACPI: PCI interrupt :00:02.2[C] -> GSI 11 (level, low) -> IRQ 11
ehci_hcd :00:02.2: nVidia Corporation nForce3 USB 2.0
PCI: Setting latency timer of devi
Greg KH wrote:
On Sun, Aug 03, 2003 at 09:42:10AM +0200, Harald Dunkel wrote:
Hi folks,
I run into a kernel panic if I shutdown my PC without
manually unmounting my external USB disk first. It said
unmounting local filesystems... bio too big device sdc1 (8 > 0)
bio too big dev
Hi folks,
I run into a kernel panic if I shutdown my PC without
manually unmounting my external USB disk first. It said
unmounting local filesystems... bio too big device sdc1 (8 > 0)
bio too big device sdc1 (8 > 0)
journal - 601, buffer write failed
--- cut here --
David Brownell wrote:
Harald Dunkel wrote:
Using the same disk on kernel 2.4.21 together with the patches
released on June 20th the disk worked very stable. I had written
about 40 GByte on this disk without a small hiccup.
Since test1 and that 2.4.22-pre1 code are essentially the same
in terms
Hi David,
David Brownell wrote:
And I notice you still didn't post the details about the disk
(and enclosure) in use on USB. IT's really no big surprise
that two different hardware+driver stacks don't act the same,
even though the (eventually) should.
Sorry, I did not realize that you are waiting
David Brownell wrote:
Harald Dunkel wrote:
Using the same disk on kernel 2.4.21 together with the patches
released on June 20th the disk worked very stable. I had written
about 40 GByte on this disk without a small hiccup.
Since test1 and that 2.4.22-pre1 code are essentially the same
in terms
Harald Dunkel wrote:
Hi folks,
I get random errors when reading or writing my USB 2.0 disk
with kernel 2.6.0-test1. Just a few minutes ago mkreiserfs
got stuck. Syslog says
Jul 15 20:05:28 styx kernel: SCSI error : <2 0 0 0> return code = 0x605
Jul 15 20:05:28 styx kernel: end_reques
Hi folks,
I get random errors when reading or writing my USB 2.0 disk
with kernel 2.6.0-test1. Just a few minutes ago mkreiserfs
got stuck. Syslog says
Jul 15 20:05:28 styx kernel: SCSI error : <2 0 0 0> return code = 0x605
Jul 15 20:05:28 styx kernel: end_request: I/O error, dev sdc, sector 1
12 matches
Mail list logo
