public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Harald Dunkel" <harald.dunkel@t-online.de>
To: linux-kernel@vger.kernel.org
Subject: USB Problem (was: 2.6.9-rc4: Aiee on amd64)
Date: Tue, 12 Oct 2004 08:57:10 +0200	[thread overview]
Message-ID: <416B8046.8080809@t-online.de> (raw)
In-Reply-To: <416A98B3.7050805@t-online.de>

Harald Dunkel wrote:
> Hi folks,
> 
> I installed 2.6.9-rc4 this morning, but it died at boot time
> (a lot of hex output and something about "Aiee" :-). I tried
> to redirect syslog to another host, but the error message did
> not show up in the foreign log files.
> 
> Any idea how to catch this message? The problem seems to be
> reproducable, and I would be glad to help.
> 

I disabled ehci_hcd.ko in the boot procedure and loaded
it manually when syslog was running. This was written into
kern.log:

:
ACPI: PCI interrupt 0000:00:02.2[C] -> GSI 11 (level, low) -> IRQ 11
ehci_hcd 0000:00:02.2: nVidia Corporation nForce3 USB 2.0
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: irq 11, pci mem ffffff0000b98000
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
usb 1-3: new high speed USB device using address 2
ub: sizeof ub_scsi_cmd 88 ub_dev 1112
uba: device 2 capacity nsec 50 bsize 512
uba: made changed
uba: device 2 capacity nsec 50 bsize 512
uba: device 2 capacity nsec 50 bsize 512
  /dev/ub/a:end_request: I/O error, dev uba, sector 0
Buffer I/O error on device uba, logical block 0
end_request: I/O error, dev uba, sector 2
Buffer I/O error on device uba, logical block 1
end_request: I/O error, dev uba, sector 4
Buffer I/O error on device uba, logical block 2
end_request: I/O error, dev uba, sector 6
Buffer I/O error on device uba, logical block 3
end_request: I/O error, dev uba, sector 6
Buffer I/O error on device uba, logical block 3
end_request: I/O error, dev uba, sector 4
Buffer I/O error on device uba, logical block 2
end_request: I/O error, dev uba, sector 2
Buffer I/O error on device uba, logical block 1
end_request: I/O error, dev uba, sector 0
Buffer I/O error on device uba, logical block 0
  unable to read partition table
  /dev/ub/a:end_request: I/O error, dev uba, sector 2
Buffer I/O error on device uba, logical block 1
end_request: I/O error, dev uba, sector 4
Buffer I/O error on device uba, logical block 2
end_request: I/O error, dev uba, sector 6
Buffer I/O error on device uba, logical block 3
end_request: I/O error, dev uba, sector 0
Buffer I/O error on device uba, logical block 0
  unable to read partition table
usbcore: registered new driver ub
usb 1-4: new high speed USB device using address 3


If I keep ehci_hcd in the boot procedure, then the
kernel dies immediately after printing these messages.
In my test environment there was no crash, though.


Regards

Harri

  parent reply	other threads:[~2004-10-12  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 14:29 2.6.9-rc4: Aiee on amd64 Harald Dunkel
2004-10-11 14:58 ` Jesper Juhl
2004-10-12  6:57 ` Harald Dunkel [this message]
2004-10-15 13:35 ` Alexander Nyberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=416B8046.8080809@t-online.de \
    --to=harald.dunkel@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox