From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 36822] New: Slow boot with dc395x compiled into the kernel.
Date: Tue, 7 Jun 2011 09:29:45 GMT [thread overview]
Message-ID: <bug-36822-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=36822
Summary: Slow boot with dc395x compiled into the kernel.
Product: SCSI Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: DC395X
AssignedTo: scsi_drivers-dc395x@kernel-bugs.osdl.org
ReportedBy: taxi@a-city.de
Regression: No
I'm using a Tekram TRM-S1040 Card with a HP Scanner connected to it.
When I compile the driver directly into the kernel the kernel needs about 7
secounds to boot with a noticabe delay here:
[ 3.107686] scsi 7:0:0:3: Direct-Access Generic USB MS Reader 1.03
PQ: 0 ANSI: 0
[ 6.130981] scsi 0:0:0:0: Attached scsi generic sg0 type 3
(where sg0 is the scanner)
Also my internal drives correlate with the USB Card-Reader, so my drives are:
sda: card reader
sdb: fist harddrive
sdc-sde: card reader
sdf: secound harddrive
But if I compile the driver as a Module (so it's loaded by udev) the kernel
boot time is only about 2.5 secounds, my drives are:
sda: first or secound harddrive
sdb: first or secound harddrive
sdc-sdf: card reader
also the boot-time of the whole machine (kernel + init) is reduced by around 6
to 8 secounds.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-06-07 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 9:29 bugzilla-daemon [this message]
2012-05-14 14:23 ` [Bug 36822] Slow boot with dc395x compiled into the kernel bugzilla-daemon
2012-05-14 14:23 ` bugzilla-daemon
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=bug-36822-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).