All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guennadi Liakhovetski" <g.liakhovetski@gmx.de>
To: Christian Roessner <info@roessner-net.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: tmscsim broken on amd64 with 2.6.5?
Date: Tue, 13 Apr 2004 13:05:06 +0200 (MEST)	[thread overview]
Message-ID: <17727.1081854306@www36.gmx.net> (raw)
In-Reply-To: 200404131025.43474.info@roessner-net.com

Hi

> drivers/scsi/tmscsim.c: In function `dc390_pci_map':
> drivers/scsi/tmscsim.c:1028: warning: unsigned int format, different type
> arg
> (arg 4)
> drivers/scsi/tmscsim.c:1049: warning: unsigned int format, different type
> arg
> (arg 4)
> drivers/scsi/tmscsim.c: In function `dc390_pci_unmap':
> drivers/scsi/tmscsim.c:1066: warning: unsigned int format, different type
> arg
> (arg 3)
> drivers/scsi/tmscsim.c:1076: warning: unsigned int format, different type
> arg
> (arg 3)

Ok, just some printk's formats. Will fix that, thanks.

> > kern.*                          -/var/log/tmscsim.log
> 
> I use metalong and I have not spent time looking for the configuration. I
> thin /var/log/everthing/current should also contain kern.*

Doesn't look like that. I think, at least, KERN_DEBUG messages are missing.
So, now you have both patches applied, right? Could you then uncomment
additionally DC390_DEBUG0 and DC390_DCBDEBUG, and also specify
scsi_logging_level=0x1ff, when loading the scsi_mod module (which also means
you need scsi-logging enabled in scsi configuration), or scsi_logging=0x1ff
as a kernel boot-parameter. Of course, this is only feasible, if you can
refrain from using SCSI for anything else during these tests.

Thanks
Guennadi


  reply	other threads:[~2004-04-13 11:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  8:25 tmscsim broken on amd64 with 2.6.5? Christian Roessner
2004-04-13 11:05 ` Guennadi Liakhovetski [this message]
2004-04-13 12:16   ` Christian Roessner
2004-04-13 12:32     ` Guennadi Liakhovetski
2004-04-13 14:14       ` Christian Roessner
2004-04-13 17:12         ` Guennadi Liakhovetski
2004-04-13 20:17           ` Christian Roessner
2004-04-13 20:40             ` Guennadi Liakhovetski
2004-04-15 16:05               ` Roessner Christian
2004-04-15 18:07                 ` [PATCH] " Guennadi Liakhovetski
2004-04-15 16:11               ` Roessner Christian
2004-04-13 21:24             ` Guennadi Liakhovetski
  -- strict thread matches above, loose matches on Subject: below --
2004-04-10 13:58 Christian Roessner
2004-04-10 16:42 ` Guennadi Liakhovetski
2004-04-10 19:14   ` Guennadi Liakhovetski
2004-04-10 20:39     ` Christian Roessner
2004-04-10 21:42       ` Guennadi Liakhovetski
2004-04-10 21:14     ` Guennadi Liakhovetski
2004-04-11  9:20       ` Christian Roessner
2004-04-12 11:11         ` Guennadi Liakhovetski
2004-04-12 11:38           ` Jeff Garzik
2004-04-13 21:26             ` Guennadi Liakhovetski
2004-04-13 21:52               ` Jeff Garzik

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=17727.1081854306@www36.gmx.net \
    --to=g.liakhovetski@gmx.de \
    --cc=info@roessner-net.com \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.