1. 21 6月, 2008 1 次提交
  2. 15 5月, 2008 2 次提交
  3. 07 5月, 2008 1 次提交
  4. 30 4月, 2008 2 次提交
  5. 29 4月, 2008 2 次提交
  6. 17 4月, 2008 5 次提交
  7. 05 3月, 2008 2 次提交
  8. 04 3月, 2008 1 次提交
  9. 19 2月, 2008 1 次提交
  10. 10 2月, 2008 1 次提交
    • C
      [S390] sclp_vt220: Fix vt220 initialization · 59eb1ca7
      Christian Borntraeger 提交于
      There are two problems in the vt220 intialization:
      
      o Currently the vt220 console looses early printk events until the
        the vt220 tty is registered.
      o console should work if tty_register fails
      
      sclp_vt220_con_init calls __sclp_vt220_init and register_console.
      It does not register the driver with the sclp core code via
      sclp_register. That results in an sclp_send_mask=0. Therefore,
      __sclp_vt220_emit will reject buffers with EIO. Unfortunately
      register_console will cause the printk buffer to be sent to the
      console and, therefore, every early message gets dropped. The
      sclp_send_mask is set later during boot, when sclp_vt220_tty_init
      calls sclp_register.
      
      The solution is to move the sclp_register call from sclp_vt220_tty_init
      to __sclp_vt220_init. This makes sure that the console is properly
      registered with the sclp subsystem before the first log buffer messages
      are passed to the vt220 console.
      
      We also adopt the cleanup on error to keep the console alive if
      tty_register fails.
      
      Thanks to Peter Oberparleiter and Heiko Carstens for review and ideas
      for improvement.
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      59eb1ca7
  11. 05 2月, 2008 1 次提交
    • C
      [S390] sclp_tty/sclp_vt220: Fix scheduling while atomic · e35e1fad
      Christian Borntraeger 提交于
      Under load the following bug message appeared while using sysrq-t:
      
      BUG: scheduling while atomic: bash/3662/0x00000004
      0000000000105b74 000000003ba17740 0000000000000002 0000000000000000
             000000003ba177e0 000000003ba17758 000000003ba17758 0000000000105bfe
             0000000000817ba8 000000003f2a5350 0000000000000000 0000000000000000
             000000003ba17740 000000000000000c 000000003ba17740 000000003ba177b0
             0000000000568630 0000000000105bfe 000000003ba17740 000000003ba17790
      Call Trace:
      ([<0000000000105b74>] show_trace+0x13c/0x158)
       [<0000000000105c58>] show_stack+0xc8/0xfc
       [<0000000000105cbc>] dump_stack+0x30/0x40
       [<000000000012a0c8>] __schedule_bug+0x84/0x94
       [<000000000056234e>] schedule+0x5ea/0x970
       [<0000000000477cd2>] __sclp_vt220_write+0x1f6/0x3ec
       [<0000000000477f00>] sclp_vt220_con_write+0x38/0x48
       [<0000000000130b4a>] __call_console_drivers+0xbe/0xd8
       [<0000000000130bf0>] _call_console_drivers+0x8c/0xd0
       [<0000000000130eea>] release_console_sem+0x1a6/0x2fc
       [<0000000000131786>] vprintk+0x262/0x480
       [<00000000001319fa>] printk+0x56/0x68
       [<0000000000125aaa>] print_cfs_rq+0x45e/0x4a4
       [<000000000012614e>] sched_debug_show+0x65e/0xee8
       [<000000000012a8fc>] show_state_filter+0x1cc/0x1f0
       [<000000000044d39c>] sysrq_handle_showstate+0x2c/0x3c
       [<000000000044d1fe>] __handle_sysrq+0xae/0x18c
       [<00000000002001f2>] write_sysrq_trigger+0x8a/0x90
       [<00000000001f7862>] proc_reg_write+0x9a/0xc4
       [<00000000001a83d4>] vfs_write+0xb8/0x174
       [<00000000001a8b88>] sys_write+0x58/0x8c
       [<0000000000112e7c>] sysc_noemu+0x10/0x16
       [<0000020000116f68>] 0x20000116f68
      
      The problem seems to be, that with a full console buffer, release_console_sem
      disables interrupts with spin_lock_irqsave and then calls the console function
      without enabling interrupts. __sclp_vt220_write checks for in_interrupt, to
      decide if it can schedule. It should check for in_atomic instead.
      
      The same is true for sclp_tty.c.
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      e35e1fad
  12. 28 1月, 2008 1 次提交
  13. 26 1月, 2008 9 次提交
  14. 22 10月, 2007 1 次提交
  15. 20 10月, 2007 1 次提交
  16. 17 10月, 2007 1 次提交
  17. 12 10月, 2007 5 次提交
  18. 10 10月, 2007 2 次提交
  19. 22 8月, 2007 1 次提交