Kernel Bug Tracker – Bug 15332
Need printk's in drivers/usb/storage/usb.c
Last modified: 2012-02-22 21:05:55 UTC
The 'init' script in Puppy Linux needs the kernel log messages such as:
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
I looked at the changes in drivers/usb/storage/usb.c and the printk functions that produce these messages were removed in 2.6.33-rc1.
Can we please have them back?
No, you should not be grepping kernel logs for init sequences, no other distro
needs this. Please file a bug with your distro to fix their code.
What are the effects of this change upon users of Puppy Linux?
Wait, those messages are still there, I see them.
I think you do not have this module built in your kernel properly, given your
other bug report.
Have you really loaded the module?
Sorry about my other bug report (15333), it was invalid, I closed it.
Those messages are not there, they were removed in 2.6.33-rc1:
...hmmm, unless they have been put back after -rc8?
I'm one of the lead developers of Puppy Linux, and the founder.
Puppy has a unique 'init' script, and we have always relied on those messages. As they are not there, the init script times out waiting for them, and this results in a longer boot time.
The init script needs to know when the usb-storage module has found all devices and finished scanning. It has to know this at a certain point in the script before proceeding.
If you can tell us some other way to determine that usb_storage has finished scanning, then we will use it. Otherwise, if you won't put the printk's back, I will be forced to patch it myself and put them back.
Note, Puppy Linux does not use udevd in the initramfs.
"No, you should not be grepping kernel logs for init sequences, no other distro
...hmmm, how do you know this? Have you studied the init scripts of the hundreds of distros out there?
The thing is, those messages from usb-storage.ko have always been there. We have relied upon them for years.
Even if one kernel developer thinks that ideally they should not be there, they should not be removed just like that, at the whim of one kernel developer. Instead, it should be put out for wider discussion first.
All USB bugs should be sent to the firstname.lastname@example.org mailing
list, and not entered into bugzilla. Please bring this issue up there,
if it is still a problem in the latest kernel release.