mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jordan Breeding <jordan.breeding@sbcglobal.net>
To: Andrew Morton <akpm@digeo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.5.69-mm5 errors in dmesg
Date: Thu, 15 May 2003 22:41:41 -0700 (PDT)	[thread overview]
Message-ID: <20030516054141.17385.qmail@web80105.mail.yahoo.com> (raw)

Hello,

  When booting 2.5.69-mm5 I have two errors showing up
in dmesg, the first is the usb irq handler message
below which is listed multiple times at boot:

irq 16: nobody cared!
Call Trace:
 [<f010cf72>] report_bad_irq+0x3b/0x9c
 [<f010d042>] note_interrupt+0x6f/0x83
 [<f010d2d5>] do_IRQ+0xe7/0x193
 [<f010b608>] common_interrupt+0x18/0x20
 [<f03bdca0>] cfb_imageblit+0x390/0x610
 [<f010d349>] do_IRQ+0x15b/0x193
 [<f010b608>] common_interrupt+0x18/0x20
 [<f03b0ef3>] putcs_aligned+0x169/0x1ba
 [<f010cf0d>] handle_IRQ_event+0x3a/0x64
 [<f03b1274>] accel_putcs+0x93/0xc5
 [<f03b2982>] fbcon_redraw+0x1a2/0x209
 [<f03b306e>] fbcon_scroll+0x685/0xc5d
 [<f031f8ed>] scrup+0x12f/0x139
 [<f0321039>] lf+0x73/0x75
 [<f032397e>] vt_console_print+0x129/0x303
 [<f0123f3c>] __call_console_drivers+0x57/0x59
 [<f012402b>] call_console_drivers+0x78/0x113
 [<f01243a9>] release_console_sem+0x6f/0xf4
 [<f01242b9>] printk+0x18b/0x1d7
 [<f03c63f5>] usb_hcd_pci_probe+0x2ed/0x427
 [<f02e6aba>] pci_device_probe+0x5e/0x6c
 [<f0340f38>] bus_match+0x45/0x73
 [<f034103e>] driver_attach+0x59/0x5d
 [<f03412d4>] bus_add_driver+0xa9/0xbc
 [<f02e6bcf>] pci_register_driver+0x44/0x54
 [<f0655796>] uhci_hcd_init+0xd9/0x13b
 [<f0636874>] do_initcalls+0x27/0x93
 [<f01332f3>] init_workqueues+0xf/0x28
 [<f01050e2>] init+0x5a/0x1d0
 [<f0105088>] init+0x0/0x1d0
 [<f0108ab5>] kernel_thread_helper+0x5/0xb

handlers:
[<f03c3162>] (usb_hcd_irq+0x0/0x58)

  The second error message is a message from the
aic7xxx driver which I have seen before from some of
Justin's updates, I only get this error from my
Maxtor(Quantum) Atlas 10k III:

(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x83 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (56 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x83 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (56 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x83 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (56 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x83 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (56 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x83 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (56 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error
(scsi1:A:0:0): CDB: 0x12 0x1 0x80 0x0 0x60 0x0
(scsi1:A:0:0): Saw underflow (80 of 96 bytes). Treated
as error

  Please cc: me in replies, this is a new address and
I am not subscribed at it yet.

Jordan

             reply	other threads:[~2003-05-16  5:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  5:41 Jordan Breeding [this message]
2003-05-16  6:10 ` Andrew Morton
2003-05-16 22:54   ` Greg KH
2003-05-16 23:21     ` Andrew Morton

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=20030516054141.17385.qmail@web80105.mail.yahoo.com \
    --to=jordan.breeding@sbcglobal.net \
    --cc=akpm@digeo.com \
    --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

Powered by JetHome