Bug 766544

Summary:	Login prompt at run level 3 shows password in clear text.
Product:	[Fedora] Fedora	Reporter:	George R. Goffe <grgoffe>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dennis, gansalmon, itamar, jonathan, kernel-maint, kzak, madhu.chinakonda, mluscon, mschmidt
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-20 14:38:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description George R. Goffe 2011-12-12 10:13:47 UTC

Description of problem:

Newly loaded AND up to date FC 16 system. Set run level target to 3. Login shows password in clear text

Version-Release number of selected component (if applicable):


How reproducible:

always

Steps to Reproduce:
1.see above
2.
3.
  
Actual results:

see above

Expected results:

see above

Additional info:

Comment 1 George R. Goffe 2012-02-14 11:36:33 UTC

Hi,

I'm at this kernel level now "config-3.2.5-3.fc16.x86_64.debug"... and I'm seeing the same thing. This kernel has other problems (display/kde not working right) so I went back to "config-3.2.3-2.fc16.x86_64.debug"

Additionally, the bash up/down arrows just print escape sequences or strange sets of characters like "^["...

George...

Comment 2 Michal Schmidt 2012-02-14 11:55:44 UTC

Does it help if you pass "rd.plymouth=0 plymouth.enable=0" as kernel command line parameters?

Comment 3 Karel Zak 2012-02-14 14:12:47 UTC

(In reply to comment #1)
> I'm at this kernel level now "config-3.2.5-3.fc16.x86_64.debug"... and I'm
> seeing the same thing. This kernel has other problems (display/kde not working
> right) so I went back to "config-3.2.3-2.fc16.x86_64.debug"

Do you want to say that downgrade to the kernel 3.2.3 fixed the problem?

Anyway, I'm not able to reproduce this problem with

  kernel-3.2.3-2.fc16.x86_64
  kernel-3.2.5-3.fc16.x86_64
  util-linux-2.20.1-2.2.fc16.x86_64

and with runlevel5.target.

Comment 4 George R. Goffe 2012-02-14 19:05:49 UTC

Michal/Karel,

I'll try the "plymouth" settings tonight and post the results here.

The downgrade in kernel fixed the problem.

I'm using runlevel3.target

THANKS for your help!

George...

Comment 5 Karel Zak 2012-02-15 10:51:07 UTC

(In reply to comment #4)
> The downgrade in kernel fixed the problem.

 reassigning to kernel...

Comment 6 Josh Boyer 2012-02-15 14:29:10 UTC

(In reply to comment #4)
> Michal/Karel,
> 
> I'll try the "plymouth" settings tonight and post the results here.
> 
> The downgrade in kernel fixed the problem.
> 
> I'm using runlevel3.target
> 
> THANKS for your help!
> 
> George...

I really doubt this is a kernel problem.  What do you mean when you say "downgraded" kernel?  Did you just select a different kernel from the grub menu on that boot?

When you do that, it boots the older kernel but it also uses the older initramfs that matches that kernel.  If you rebuild the initramfs while booted in that older kernel and reboot, do the same symptoms show up?

Comment 7 George R. Goffe 2012-02-16 05:12:31 UTC

Josh,

"downgraded" kernel means that I selected an older kernel from my grub2.cfg at boot time.

I'm running 3.2.3-2.fc16.x86_64.debug now and do NOT have the problems described in this bug report.

Are you asking me to reboot the problematic kernel (i.e.,3.2.5-3.fc16.x86_64.debug) and run mkinitrd and reboot that same kernel and see if the problems still appear?

Regards,

George...

Comment 8 Josh Boyer 2012-02-16 12:25:30 UTC

(In reply to comment #7)
> Josh,
> 
> "downgraded" kernel means that I selected an older kernel from my grub2.cfg at
> boot time.

OK.

> I'm running 3.2.3-2.fc16.x86_64.debug now and do NOT have the problems
> described in this bug report.
> 
> Are you asking me to reboot the problematic kernel
> (i.e.,3.2.5-3.fc16.x86_64.debug) and run mkinitrd and reboot that same kernel
> and see if the problems still appear?

No.  Boot 3.2.3-2.fc16.x86_64.debug, log in and run "sudo dracut --force" to rebuild the initramfs-3.2.3-2.fc16 file from the current on-disk contents.  Make sure the timestamp of the file reflects that it was rebuilt.  Then reboot into that same kernel and see if the problem exists.

You could try the same steps with the 3.2.5-3.fc16.x86_64 kernel if the above still results in the problem not appearing.

Also, is there a particular reason you're running the kernel-debug kernels?

Comment 9 George R. Goffe 2012-02-16 19:10:23 UTC

Josh,

I'm using Fedora Core so I can help further the cause with open source software.

I haven't had the time to find out exactly what the debug kernels provide but my initial thoughts were that if/when I run into a bug, there will be the largest amount of debug info available.

Do you have thoughts about this?

Regards,

George...

Comment 10 Josh Boyer 2012-02-16 20:27:07 UTC

(In reply to comment #9)
> Josh,
> 
> I'm using Fedora Core so I can help further the cause with open source
> software.

Great!  Thank you.  (Btw, there is no Core any more.  We haven't called it Fedora Core for about 10 releases now)

> I haven't had the time to find out exactly what the debug kernels provide but
> my initial thoughts were that if/when I run into a bug, there will be the
> largest amount of debug info available.

Yes, that should be quite true.

> Do you have thoughts about this?

I think it's great.  Not many people choose to run the debug kernels as the added debugging options can decrease performance.  There is really nothing wrong with you running them though.  I was just curious.

Comment 11 George R. Goffe 2012-02-20 06:04:33 UTC

Josh,

All the problems have gone away now except for the route command failure ("route add default gw 10.28.0.1 1" fails with "SIOCADDRT: No such device". Without the metric, it succeeds) AND another bug relating to USB and Sata disks.

BTW, I've noticed that the new initramfs from dracut --force for the 3.2.3-2.fc16.x86_64.debug kernel is smaller than what comes from the rpm.

I've gone back to this kernel because a MAJOR (to me) problem has reared it's ugly head, again? The problem still appears! Similar to this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=782280

I have a few NEW Seagate sata laptop drives in "docking stations" connected to the external USB port(s) on my laptop. With the newer kernel, the above bug has me running scared. I'm seeing some UGLY messages from e2fsck. I have no backup for this drive, all the drives are rather new. Sigh...

Any thoughts?

George...

Here's a snippet from /var/log/messages:

      5 Feb 19 21:48:50 joker kernel: [ 2333.639048] usb 2-1.4.3: reset high-speed USB device number 8 using ehci_hcd
      6 Feb 19 21:48:58 joker kernel: [ 2341.970057] sd 6:0:0:0: Device offlined - not ready after error recovery
      7 Feb 19 21:48:58 joker kernel: [ 2341.970074] sd 6:0:0:0: [sdb] Unhandled error code
      8 Feb 19 21:48:58 joker kernel: [ 2341.970075] sd 6:0:0:0: [sdb]  Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
      9 Feb 19 21:48:58 joker kernel: [ 2341.970078] sd 6:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 3f 00 00 20 00
     10 Feb 19 21:48:58 joker kernel: [ 2341.970086] end_request: I/O error, dev sdb, sector 63
     11 Feb 19 21:48:58 joker kernel: [ 2341.970090] Buffer I/O error on device sdb1, logical block 0
     12 Feb 19 21:48:58 joker kernel: [ 2341.970098] Buffer I/O error on device sdb1, logical block 1
     13 Feb 19 21:48:58 joker kernel: [ 2341.970104] Buffer I/O error on device sdb1, logical block 2
     14 Feb 19 21:48:58 joker kernel: [ 2341.970110] Buffer I/O error on device sdb1, logical block 3
     15 Feb 19 21:48:58 joker kernel: [ 2341.970134] Buffer I/O error on device sdb1, logical block 4
     16 Feb 19 21:48:58 joker kernel: [ 2341.970144] Buffer I/O error on device sdb1, logical block 5
     17 Feb 19 21:48:58 joker kernel: [ 2341.970155] Buffer I/O error on device sdb1, logical block 6
     18 Feb 19 21:48:58 joker kernel: [ 2341.970165] Buffer I/O error on device sdb1, logical block 7
     19 Feb 19 21:48:58 joker kernel: [ 2341.970175] Buffer I/O error on device sdb1, logical block 8
     20 Feb 19 21:48:58 joker kernel: [ 2341.970185] Buffer I/O error on device sdb1, logical block 9
     21 Feb 19 21:48:58 joker kernel: [ 2341.970212] sd 6:0:0:0: rejecting I/O to offline device
     22 Feb 19 21:48:58 joker kernel: [ 2341.970395] usb 2-1.4.3: USB disconnect, device number 8
     23 Feb 19 21:49:00 joker kernel: [ 2343.721505] usb 2-1.4.3: new high-speed USB device number 9 using ehci_hcd
     24 Feb 19 21:49:00 joker kernel: [ 2343.808537] usb 2-1.4.3: New USB device found, idVendor=152d, idProduct=2336
     25 Feb 19 21:49:00 joker kernel: [ 2343.808541] usb 2-1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=5
     26 Feb 19 21:49:00 joker kernel: [ 2343.808543] usb 2-1.4.3: Product: JM20336 SATA, USB Combo
     27 Feb 19 21:49:00 joker kernel: [ 2343.808545] usb 2-1.4.3: Manufacturer: JMicron
     28 Feb 19 21:49:00 joker kernel: [ 2343.808546] usb 2-1.4.3: SerialNumber: 606688888888
     29 Feb 19 21:49:00 joker kernel: [ 2343.811105] scsi7 : usb-storage 2-1.4.3:1.0
     30 Feb 19 21:49:00 joker mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4.3"
     31 Feb 19 21:49:00 joker mtp-probe: bus: 2, device: 9 was not an MTP device
     32 Feb 19 21:49:01 joker kernel: [ 2344.814078] scsi 7:0:0:0: Direct-Access     ST975042 0AS                   PQ: 0 ANSI: 2 CCS
     33 Feb 19 21:49:01 joker kernel: [ 2344.820406] sd 7:0:0:0: Attached scsi generic sg2 type 0
     34 Feb 19 21:49:01 joker kernel: [ 2344.820824] sd 7:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
     35 Feb 19 21:49:01 joker kernel: [ 2344.821929] sd 7:0:0:0: [sdb] Write Protect is off
     36 Feb 19 21:49:01 joker kernel: [ 2344.823032] sd 7:0:0:0: [sdb] Asking for cache data failed
     37 Feb 19 21:49:01 joker kernel: [ 2344.823036] sd 7:0:0:0: [sdb] Assuming drive cache: write through
     38 Feb 19 21:49:01 joker kernel: [ 2344.828428] sd 7:0:0:0: [sdb] Asking for cache data failed
     39 Feb 19 21:49:01 joker kernel: [ 2344.828431] sd 7:0:0:0: [sdb] Assuming drive cache: write through
     40 Feb 19 21:49:01 joker kernel: [ 2344.871122]  sdb: sdb1
     41 Feb 19 21:49:01 joker kernel: [ 2344.876905] sd 7:0:0:0: [sdb] Asking for cache data failed
     42 Feb 19 21:49:01 joker kernel: [ 2344.876910] sd 7:0:0:0: [sdb] Assuming drive cache: write through
     43 Feb 19 21:49:01 joker kernel: [ 2344.876921] sd 7:0:0:0: [sdb] Attached SCSI disk
     44 Feb 19 21:49:01 joker ata_id[24260]: HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument
     45 Feb 19 21:49:09 joker kernel: [ 2352.494163] usb 2-1.4.3: USB disconnect, device number 9
     46 Feb 19 21:49:33 joker kernel: [ 2376.708291] usb 2-1.4.3: new high-speed USB device number 10 using ehci_hcd
     47 Feb 19 21:49:33 joker kernel: [ 2376.796443] usb 2-1.4.3: New USB device found, idVendor=152d, idProduct=2336
     48 Feb 19 21:49:33 joker kernel: [ 2376.796447] usb 2-1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=5
     49 Feb 19 21:49:33 joker kernel: [ 2376.796450] usb 2-1.4.3: Product: JM20336 SATA, USB Combo
     50 Feb 19 21:49:33 joker kernel: [ 2376.796451] usb 2-1.4.3: Manufacturer: JMicron
     51 Feb 19 21:49:33 joker kernel: [ 2376.796453] usb 2-1.4.3: SerialNumber: 606688888888
     52 Feb 19 21:49:33 joker kernel: [ 2376.799103] scsi8 : usb-storage 2-1.4.3:1.0

Comment 12 Josh Boyer 2012-02-20 14:38:29 UTC

(In reply to comment #11)
> Josh,
> 
> All the problems have gone away now except for the route command failure
> ("route add default gw 10.28.0.1 1" fails with "SIOCADDRT: No such device".
> Without the metric, it succeeds) AND another bug relating to USB and Sata
> disks.

OK, well since the specific problem for this bug was solved by rebuilding the initramfs, I'm going to close it out.  We try and stick to one problem per bug report, and the disk one already has a bug opened for it.