problem with starting 2.5.25-rc1 and latest git - Kernel

This is a discussion on problem with starting 2.5.25-rc1 and latest git - Kernel ; Hello, I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem. Linux boots but with huge delay due to some issue with loading usb modules. Udev complains: 'Could not lock modprobe uhci_hcd' 'Could not lock ...

+ Reply to Thread
Results 1 to 12 of 12

Thread: problem with starting 2.5.25-rc1 and latest git

  1. problem with starting 2.5.25-rc1 and latest git

    Hello,

    I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    Linux boots but with huge delay due to some issue with loading usb modules.
    Udev complains:

    'Could not lock modprobe uhci_hcd'
    'Could not lock modprobe yenta_socket'
    'Unknown symbol usb_*'
    'Gave up waiting for init of module usbcore'

    at the same time I can see these messages in syslog (look at timing - grep by usb):

    Feb 13 21:34:22 laptop kernel: usbcore: registered new interface driver usbfs
    Feb 13 21:34:22 laptop kernel: usbcore: registered new interface driver hub
    Feb 13 21:34:22 laptop kernel: usbcore: registered new device driver usb
    Feb 13 21:34:22 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:34:22 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_suspend
    Feb 13 21:34:22 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:34:22 laptop kernel: ehci_hcd: Unknown symbol usb_free_urb
    Feb 13 21:34:31 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:34:31 laptop kernel: ehci_hcd: Unknown symbol usb_hub_tt_clear_buffer
    Feb 13 21:35:01 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:35:01 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_resume_root_hub
    Feb 13 21:35:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:35:32 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_probe
    Feb 13 21:36:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:36:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_unlink_urb_from_ep
    Feb 13 21:36:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:36:32 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_check_unlink_urb
    Feb 13 21:37:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:37:02 laptop kernel: ehci_hcd: Unknown symbol usb_calc_bus_time
    Feb 13 21:37:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:38:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:38:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_shutdown
    Feb 13 21:38:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:38:32 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_link_urb_to_ep
    Feb 13 21:39:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:39:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_resume
    Feb 13 21:39:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:39:32 laptop kernel: ehci_hcd: Unknown symbol usb_get_urb
    Feb 13 21:40:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:40:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_giveback_urb
    Feb 13 21:40:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:40:32 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_poll_rh_status
    Feb 13 21:41:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:41:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_remove
    Feb 13 21:41:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    Feb 13 21:41:32 laptop kernel: ehci_hcd: Unknown symbol usb_root_hub_lost_power

    Sysrq says:

    Feb 13 21:35:06 laptop kernel: Showing all locks held in the system:
    Feb 13 21:35:06 laptop kernel: 1 lock held by modprobe/1130:
    Feb 13 21:35:06 laptop kernel: #0: (module_mutex){--..}, at: [] sys_init_module+0x3d/0x1749
    Feb 13 21:35:06 laptop kernel: 1 lock held by modprobe/1131:
    Feb 13 21:35:06 laptop kernel: #0: (module_mutex){--..}, at: [] sys_init_module+0x128/0x1749
    Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1143:
    Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1144:
    Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1352:
    Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1354:
    Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1547:
    Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1555:
    Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/3916:
    Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f

    and

    Feb 13 21:35:12 laptop kernel: SysRq : Show Blocked State
    Feb 13 21:35:12 laptop kernel: task PC stack pid father
    Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1131 693
    Feb 13 21:35:12 laptop kernel: dce00500 00000082 dcc18158 c032771c c04180a4 c04180a0 00000246 c04180a4
    Feb 13 21:35:12 laptop kernel: dcc18000 c03276cb 00000000 00000002 c0139d54 00000000 c0139d54 c04180c0
    Feb 13 21:35:12 laptop kernel: dcee3ef0 dcd6bef0 dcc18000 c04180a0 ddb72ea4 00000000 deee7580 00000001
    Feb 13 21:35:12 laptop kernel: Call Trace:
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    Feb 13 21:35:12 laptop kernel: [] sys_init_module+0x128/0x1749
    Feb 13 21:35:12 laptop last message repeated 2 times
    Feb 13 21:35:12 laptop kernel: [] bus_register+0x0/0x1f7
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x9a/0xa5
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    Feb 13 21:35:12 laptop kernel: =======================
    Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1143 671
    Feb 13 21:35:12 laptop kernel: ddbb6780 00000082 dcd6a158 c032771c c04180a4 c04180a0 00000246 c04180a4
    Feb 13 21:35:12 laptop kernel: dcd6a000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    Feb 13 21:35:12 laptop kernel: ddb72ea4 dcc3eef0 dcd6a000 c04180a0 dcd6bef0 dcd6bf40 dccb3a50 c017752b
    Feb 13 21:35:12 laptop kernel: Call Trace:
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    Feb 13 21:35:12 laptop kernel: =======================
    Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1144 805
    Feb 13 21:35:12 laptop kernel: ddbb6500 00000082 dcc0b158 c032771c c04180a4 c04180a0 00000246 c04180a4
    Feb 13 21:35:12 laptop kernel: dcc0b000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    Feb 13 21:35:12 laptop kernel: dcd6bef0 c04180c0 dcc0b000 c04180a0 dcc3eef0 dcc3ef40 dccb3bb0 c017752b
    Feb 13 21:35:12 laptop kernel: Call Trace:
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    Feb 13 21:35:12 laptop kernel: =======================
    Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1352 1200
    Feb 13 21:35:12 laptop kernel: dcdfa000 00000082 dcdae158 c032771c c04180a4 c04180a0 00000246 c04180a4
    Feb 13 21:35:12 laptop kernel: dcdae000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    Feb 13 21:35:12 laptop kernel: dd9bcef0 ddb72ea4 dcdae000 c04180a0 dcee3ef0 dcee3f40 dccb34d0 c017752b
    Feb 13 21:35:12 laptop kernel: Call Trace:
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    Feb 13 21:35:12 laptop kernel: =======================
    Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1354 1210
    Feb 13 21:35:12 laptop kernel: dcdfa280 00000082 ddb8e158 c032771c c04180a4 c04180a0 00000246 c04180a4
    Feb 13 21:35:12 laptop kernel: ddb8e000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    Feb 13 21:35:12 laptop kernel: dceccef0 dcee3ef0 ddb8e000 c04180a0 dd9bcef0 dd9bcf40 dccb30b0 c017752b
    Feb 13 21:35:12 laptop kernel: Call Trace:
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    Feb 13 21:35:12 laptop kernel: =======================
    Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1547 710
    Feb 13 21:35:12 laptop kernel: dcc72780 00000082 ddb95158 c032771c c04180a4 c04180a0 00000246 c04180a4
    Feb 13 21:35:12 laptop kernel: ddb95000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    Feb 13 21:35:12 laptop kernel: ddbfaef0 dd9bcef0 ddb95000 c04180a0 dceccef0 dceccf40 ddb549a0 c017752b
    Feb 13 21:35:12 laptop kernel: Call Trace:
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    Feb 13 21:35:12 laptop kernel: =======================
    Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1555 666
    Feb 13 21:35:12 laptop kernel: dcd22280 00000082 dcd46158 c032771c c04180a4 c04180a0 00000246 c04180a4
    Feb 13 21:35:12 laptop kernel: dcd46000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    Feb 13 21:35:12 laptop kernel: dce5aef0 dceccef0 dcd46000 c04180a0 ddbfaef0 ddbfaf40 ddb548f0 c017752b
    Feb 13 21:35:12 laptop kernel: Call Trace:
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    Feb 13 21:35:12 laptop kernel: =======================
    Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 3916 3914
    Feb 13 21:35:12 laptop kernel: ddb82780 00000082 dce52158 c032771c c04180a4 c04180a0 00000246 c04180a4
    Feb 13 21:35:12 laptop kernel: dce52000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    Feb 13 21:35:12 laptop kernel: c04180c0 ddbfaef0 dce52000 c04180a0 dce5aef0 dce5af40 dcc42a50 c017752b
    Feb 13 21:35:12 laptop kernel: Call Trace:
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    Feb 13 21:35:12 laptop kernel: =======================

    How can I solve this?

    Regards,

    Mariusz


  2. Re: problem with starting 2.5.25-rc1 and latest git

    Of course there is a typo in the subject

    2.5.25-rc1 -> 2.6.25-rc1

    > Hello,
    >
    > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > Linux boots but with huge delay due to some issue with loading usb modules.
    > Udev complains:
    >
    > 'Could not lock modprobe uhci_hcd'
    > 'Could not lock modprobe yenta_socket'
    > 'Unknown symbol usb_*'
    > 'Gave up waiting for init of module usbcore'
    >
    > at the same time I can see these messages in syslog (look at timing - grep by usb):
    >
    > Feb 13 21:34:22 laptop kernel: usbcore: registered new interface driver usbfs
    > Feb 13 21:34:22 laptop kernel: usbcore: registered new interface driver hub
    > Feb 13 21:34:22 laptop kernel: usbcore: registered new device driver usb
    > Feb 13 21:34:22 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:34:22 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_suspend
    > Feb 13 21:34:22 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:34:22 laptop kernel: ehci_hcd: Unknown symbol usb_free_urb
    > Feb 13 21:34:31 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:34:31 laptop kernel: ehci_hcd: Unknown symbol usb_hub_tt_clear_buffer
    > Feb 13 21:35:01 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:35:01 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_resume_root_hub
    > Feb 13 21:35:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:35:32 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_probe
    > Feb 13 21:36:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:36:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_unlink_urb_from_ep
    > Feb 13 21:36:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:36:32 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_check_unlink_urb
    > Feb 13 21:37:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:37:02 laptop kernel: ehci_hcd: Unknown symbol usb_calc_bus_time
    > Feb 13 21:37:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:38:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:38:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_shutdown
    > Feb 13 21:38:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:38:32 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_link_urb_to_ep
    > Feb 13 21:39:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:39:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_resume
    > Feb 13 21:39:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:39:32 laptop kernel: ehci_hcd: Unknown symbol usb_get_urb
    > Feb 13 21:40:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:40:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_giveback_urb
    > Feb 13 21:40:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:40:32 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_poll_rh_status
    > Feb 13 21:41:02 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:41:02 laptop kernel: ehci_hcd: Unknown symbol usb_hcd_pci_remove
    > Feb 13 21:41:32 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.
    > Feb 13 21:41:32 laptop kernel: ehci_hcd: Unknown symbol usb_root_hub_lost_power
    >
    > Sysrq says:
    >
    > Feb 13 21:35:06 laptop kernel: Showing all locks held in the system:
    > Feb 13 21:35:06 laptop kernel: 1 lock held by modprobe/1130:
    > Feb 13 21:35:06 laptop kernel: #0: (module_mutex){--..}, at: [] sys_init_module+0x3d/0x1749
    > Feb 13 21:35:06 laptop kernel: 1 lock held by modprobe/1131:
    > Feb 13 21:35:06 laptop kernel: #0: (module_mutex){--..}, at: [] sys_init_module+0x128/0x1749
    > Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1143:
    > Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    > Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    > Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1144:
    > Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    > Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    > Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1352:
    > Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    > Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    > Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1354:
    > Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    > Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    > Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1547:
    > Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    > Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    > Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/1555:
    > Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    > Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    > Feb 13 21:35:06 laptop kernel: 2 locks held by modprobe/3916:
    > Feb 13 21:35:06 laptop kernel: #0: (&p->lock){--..}, at: [] seq_read+0x26/0x2b5
    > Feb 13 21:35:06 laptop kernel: #1: (module_mutex){--..}, at: [] m_start+0xf/0x1f
    >
    > and
    >
    > Feb 13 21:35:12 laptop kernel: SysRq : Show Blocked State
    > Feb 13 21:35:12 laptop kernel: task PC stack pid father
    > Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1131 693
    > Feb 13 21:35:12 laptop kernel: dce00500 00000082 dcc18158 c032771c c04180a4 c04180a0 00000246 c04180a4
    > Feb 13 21:35:12 laptop kernel: dcc18000 c03276cb 00000000 00000002 c0139d54 00000000 c0139d54 c04180c0
    > Feb 13 21:35:12 laptop kernel: dcee3ef0 dcd6bef0 dcc18000 c04180a0 ddb72ea4 00000000 deee7580 00000001
    > Feb 13 21:35:12 laptop kernel: Call Trace:
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    > Feb 13 21:35:12 laptop kernel: [] sys_init_module+0x128/0x1749
    > Feb 13 21:35:12 laptop last message repeated 2 times
    > Feb 13 21:35:12 laptop kernel: [] bus_register+0x0/0x1f7
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x9a/0xa5
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    > Feb 13 21:35:12 laptop kernel: =======================
    > Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1143 671
    > Feb 13 21:35:12 laptop kernel: ddbb6780 00000082 dcd6a158 c032771c c04180a4 c04180a0 00000246 c04180a4
    > Feb 13 21:35:12 laptop kernel: dcd6a000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    > Feb 13 21:35:12 laptop kernel: ddb72ea4 dcc3eef0 dcd6a000 c04180a0 dcd6bef0 dcd6bf40 dccb3a50 c017752b
    > Feb 13 21:35:12 laptop kernel: Call Trace:
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    > Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    > Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    > Feb 13 21:35:12 laptop kernel: =======================
    > Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1144 805
    > Feb 13 21:35:12 laptop kernel: ddbb6500 00000082 dcc0b158 c032771c c04180a4 c04180a0 00000246 c04180a4
    > Feb 13 21:35:12 laptop kernel: dcc0b000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    > Feb 13 21:35:12 laptop kernel: dcd6bef0 c04180c0 dcc0b000 c04180a0 dcc3eef0 dcc3ef40 dccb3bb0 c017752b
    > Feb 13 21:35:12 laptop kernel: Call Trace:
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    > Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    > Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    > Feb 13 21:35:12 laptop kernel: =======================
    > Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1352 1200
    > Feb 13 21:35:12 laptop kernel: dcdfa000 00000082 dcdae158 c032771c c04180a4 c04180a0 00000246 c04180a4
    > Feb 13 21:35:12 laptop kernel: dcdae000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    > Feb 13 21:35:12 laptop kernel: dd9bcef0 ddb72ea4 dcdae000 c04180a0 dcee3ef0 dcee3f40 dccb34d0 c017752b
    > Feb 13 21:35:12 laptop kernel: Call Trace:
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    > Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    > Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    > Feb 13 21:35:12 laptop kernel: =======================
    > Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1354 1210
    > Feb 13 21:35:12 laptop kernel: dcdfa280 00000082 ddb8e158 c032771c c04180a4 c04180a0 00000246 c04180a4
    > Feb 13 21:35:12 laptop kernel: ddb8e000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    > Feb 13 21:35:12 laptop kernel: dceccef0 dcee3ef0 ddb8e000 c04180a0 dd9bcef0 dd9bcf40 dccb30b0 c017752b
    > Feb 13 21:35:12 laptop kernel: Call Trace:
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    > Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    > Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    > Feb 13 21:35:12 laptop kernel: =======================
    > Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1547 710
    > Feb 13 21:35:12 laptop kernel: dcc72780 00000082 ddb95158 c032771c c04180a4 c04180a0 00000246 c04180a4
    > Feb 13 21:35:12 laptop kernel: ddb95000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    > Feb 13 21:35:12 laptop kernel: ddbfaef0 dd9bcef0 ddb95000 c04180a0 dceccef0 dceccf40 ddb549a0 c017752b
    > Feb 13 21:35:12 laptop kernel: Call Trace:
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    > Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    > Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    > Feb 13 21:35:12 laptop kernel: =======================
    > Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 1555 666
    > Feb 13 21:35:12 laptop kernel: dcd22280 00000082 dcd46158 c032771c c04180a4 c04180a0 00000246 c04180a4
    > Feb 13 21:35:12 laptop kernel: dcd46000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    > Feb 13 21:35:12 laptop kernel: dce5aef0 dceccef0 dcd46000 c04180a0 ddbfaef0 ddbfaf40 ddb548f0 c017752b
    > Feb 13 21:35:12 laptop kernel: Call Trace:
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    > Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    > Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    > Feb 13 21:35:12 laptop kernel: =======================
    > Feb 13 21:35:12 laptop kernel: modprobe D c032771c 0 3916 3914
    > Feb 13 21:35:12 laptop kernel: ddb82780 00000082 dce52158 c032771c c04180a4 c04180a0 00000246 c04180a4
    > Feb 13 21:35:12 laptop kernel: dce52000 c03276cb 00000000 00000002 c0138fd1 00000000 c0138fd1 c04180c0
    > Feb 13 21:35:12 laptop kernel: c04180c0 ddbfaef0 dce52000 c04180a0 dce5aef0 dce5af40 dcc42a50 c017752b
    > Feb 13 21:35:12 laptop kernel: Call Trace:
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0x132/0x27b
    > Feb 13 21:35:12 laptop kernel: [] mutex_lock_nested+0xe1/0x27b
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] m_start+0xf/0x1f
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0xdb/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] seq_read+0x0/0x2b5
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x58/0x79
    > Feb 13 21:35:12 laptop kernel: [] vfs_read+0x89/0x11a
    > Feb 13 21:35:12 laptop kernel: [] proc_reg_read+0x0/0x79
    > Feb 13 21:35:12 laptop kernel: [] sys_read+0x41/0x6a
    > Feb 13 21:35:12 laptop kernel: [] sysenter_past_esp+0x5f/0xa5
    > Feb 13 21:35:12 laptop kernel: =======================
    >
    > How can I solve this?
    >
    > Regards,
    >
    > Mariusz
    >



    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. Re: problem with starting 2.6.25-rc1 and latest git

    On Thu, 14 Feb 2008 00:27:34 +0100, Mariusz Kozlowski wrote:
    > Of course there is a typo in the subject
    >
    > 2.5.25-rc1 -> 2.6.25-rc1
    >
    > > Hello,
    > >
    > > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > > Linux boots but with huge delay due to some issue with loading usb modules.
    > > Udev complains:
    > >
    > > 'Could not lock modprobe uhci_hcd'
    > > 'Could not lock modprobe yenta_socket'
    > > 'Unknown symbol usb_*'
    > > 'Gave up waiting for init of module usbcore'


    FWIW: I have the exact same problem here, running 2.6.25-rc1-git3 on x86_64.
    Distribution is openSuse 10.2, module-init-tools version 3.2.2, udev 103.
    I can do any test you want me to.

    --
    Jean Delvare
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  4. Re: problem with starting 2.5.25-rc1 and latest git

    On Wed, Feb 13, 2008 at 11:16:02PM +0100, Mariusz Kozlowski wrote:
    > Hello,
    >
    > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > Linux boots but with huge delay due to some issue with loading usb modules.
    > Udev complains:
    >
    > 'Could not lock modprobe uhci_hcd'
    > 'Could not lock modprobe yenta_socket'
    > 'Unknown symbol usb_*'
    > 'Gave up waiting for init of module usbcore'
    >
    > at the same time I can see these messages in syslog (look at timing - grep by usb):
    >
    > Feb 13 21:34:22 laptop kernel: usbcore: registered new interface driver usbfs
    > Feb 13 21:34:22 laptop kernel: usbcore: registered new interface driver hub
    > Feb 13 21:34:22 laptop kernel: usbcore: registered new device driver usb
    > Feb 13 21:34:22 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.


    I don't see how this is a usb issue, it looks to be a module loading
    issue, which is in the module core and module-init-tools.

    What version of module-init-tools do you have, and are you using an
    initramfs that loads these modules? If so, what distro and version are
    you using?

    thanks,

    greg k-h
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: problem with starting 2.5.25-rc1 and latest git

    Hello,

    > > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > > Linux boots but with huge delay due to some issue with loading usb modules.
    > > Udev complains:
    > >
    > > 'Could not lock modprobe uhci_hcd'
    > > 'Could not lock modprobe yenta_socket'
    > > 'Unknown symbol usb_*'
    > > 'Gave up waiting for init of module usbcore'
    > >
    > > at the same time I can see these messages in syslog (look at timing - grep by usb):
    > >
    > > Feb 13 21:34:22 laptop kernel: usbcore: registered new interface driver usbfs
    > > Feb 13 21:34:22 laptop kernel: usbcore: registered new interface driver hub
    > > Feb 13 21:34:22 laptop kernel: usbcore: registered new device driver usb
    > > Feb 13 21:34:22 laptop kernel: ehci_hcd: gave up waiting for init of module usbcore.

    >
    > I don't see how this is a usb issue, it looks to be a module loading
    > issue, which is in the module core and module-init-tools.


    Well ... that was just a guess.

    > What version of module-init-tools do you have, and are you using an
    > initramfs that loads these modules? If so, what distro and version are
    > you using?


    I'm using gentoo. No initramfs. The same configuration under 2.6.24 boots without
    delays.

    module-init-tools: 3.4
    udev: 115 (gentoo says 115-r1)

    this is my grub.conf entry (on 2.6.24 I have identical boot parameters):

    title 2.6.25-rc1
    root (hd0,0)
    kernel (hd0,0)/kernel-2.6.25-rc1 root=/dev/hda3 vga=0x318 video=vesafb:mtrr lapic pci=routeirq rootflags=data=writeback


    Linux laptop 2.6.24 #2 PREEMPT Sat Jan 26 00:48:39 CET 2008 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux

    Gnu C 4.1.2
    Gnu make 3.81
    binutils 2.18
    util-linux 2.13
    mount 2.13
    module-init-tools 3.4
    e2fsprogs 1.40.4
    pcmciautils 014
    pcmcia-cs 3.2.8
    PPP 2.4.4
    Linux C Library 2.6.1
    Dynamic linker (ldd) 2.6.1
    Procps 3.2.7
    Net-tools 1.60
    Kbd 1.13
    Sh-utils 6.9
    udev 115
    wireless-tools 29
    Modules Loaded orinoco_cs orinoco hermes pcmcia firmware_class ehci_hcd psmouse parport_pc parport 8139too uhci_hcd usbcore yenta_socket rsrc_nonstatic rtc floppy

    Regards,

    Mariusz
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  6. Re: problem with starting 2.5.26-rc1 and latest git

    On Thu, 14 Feb 2008 00:27:34 +0100, Mariusz Kozlowski wrote:
    > Of course there is a typo in the subject
    >
    > 2.5.25-rc1 -> 2.6.25-rc1
    >
    > > Hello,
    > >
    > > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > > Linux boots but with huge delay due to some issue with loading usb modules.
    > > Udev complains:
    > >
    > > 'Could not lock modprobe uhci_hcd'
    > > 'Could not lock modprobe yenta_socket'
    > > 'Unknown symbol usb_*'
    > > 'Gave up waiting for init of module usbcore'
    > > (...)


    Have you tried upgrading to rc2? I used to have the same problem you
    reported, but I was unable to reproduce it since I upgraded to rc2.

    --
    Jean Delvare
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  7. Re: problem with starting 2.5.26-rc1 and latest git

    Hello,

    > > Of course there is a typo in the subject
    > >
    > > 2.5.25-rc1 -> 2.6.25-rc1
    > >
    > > > Hello,
    > > >
    > > > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > > > Linux boots but with huge delay due to some issue with loading usb modules.
    > > > Udev complains:
    > > >
    > > > 'Could not lock modprobe uhci_hcd'
    > > > 'Could not lock modprobe yenta_socket'
    > > > 'Unknown symbol usb_*'
    > > > 'Gave up waiting for init of module usbcore'
    > > > (...)

    >
    > Have you tried upgrading to rc2? I used to have the same problem you
    > reported, but I was unable to reproduce it since I upgraded to rc2.


    Sorry I'm unable to test it right now. Will do ASAP.

    Mariusz
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  8. Re: problem with starting 2.5.26-rc1 and latest git

    Hello,

    > > > Of course there is a typo in the subject
    > > >
    > > > 2.5.25-rc1 -> 2.6.25-rc1
    > > >
    > > > > Hello,
    > > > >
    > > > > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > > > > Linux boots but with huge delay due to some issue with loading usb modules.
    > > > > Udev complains:
    > > > >
    > > > > 'Could not lock modprobe uhci_hcd'
    > > > > 'Could not lock modprobe yenta_socket'
    > > > > 'Unknown symbol usb_*'
    > > > > 'Gave up waiting for init of module usbcore'
    > > > > (...)

    > >
    > > Have you tried upgrading to rc2? I used to have the same problem you
    > > reported, but I was unable to reproduce it since I upgraded to rc2.


    Bad news is I tested rc2 and it still happens. Good news is I also tried
    latest git - e80af3a8 and it works fine!

    Mariusz
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  9. Re: problem with starting 2.5.26-rc1 and latest git

    On Mon, 18 Feb 2008 14:28:32 +0100, Jean Delvare wrote:
    > On Thu, 14 Feb 2008 00:27:34 +0100, Mariusz Kozlowski wrote:
    > > Of course there is a typo in the subject
    > >
    > > 2.5.25-rc1 -> 2.6.25-rc1
    > >
    > > > Hello,
    > > >
    > > > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > > > Linux boots but with huge delay due to some issue with loading usb modules.
    > > > Udev complains:
    > > >
    > > > 'Could not lock modprobe uhci_hcd'
    > > > 'Could not lock modprobe yenta_socket'
    > > > 'Unknown symbol usb_*'
    > > > 'Gave up waiting for init of module usbcore'
    > > > (...)

    >
    > Have you tried upgrading to rc2? I used to have the same problem you
    > reported, but I was unable to reproduce it since I upgraded to rc2.


    I take this back. It happened to me again today, while I am now running
    rc3.

    --
    Jean Delvare
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  10. Re: problem with starting 2.6.25-rc1 and latest git

    Hello,

    > On Mon, 18 Feb 2008 14:28:32 +0100, Jean Delvare wrote:
    > > On Thu, 14 Feb 2008 00:27:34 +0100, Mariusz Kozlowski wrote:
    > > > Of course there is a typo in the subject
    > > >
    > > > 2.5.25-rc1 -> 2.6.25-rc1
    > > >
    > > > > Hello,
    > > > >
    > > > > I tried 2.6.25-rc1 and latest git on my laptop (x86 32bit) and have a problem.
    > > > > Linux boots but with huge delay due to some issue with loading usb modules.
    > > > > Udev complains:
    > > > >
    > > > > 'Could not lock modprobe uhci_hcd'
    > > > > 'Could not lock modprobe yenta_socket'
    > > > > 'Unknown symbol usb_*'
    > > > > 'Gave up waiting for init of module usbcore'
    > > > > (...)

    > >
    > > Have you tried upgrading to rc2? I used to have the same problem you
    > > reported, but I was unable to reproduce it since I upgraded to rc2.

    >
    > I take this back. It happened to me again today, while I am now running
    > rc3.


    I can reproduce this here on rc3 as well. Weird - on git tree before
    rc3 was released this didn't happen. rc2 and rc1 are broken. I also
    don't know why nobody else see this but us And not sure how
    to debug it some more or provide more accurate information.

    Mariusz
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  11. Re: problem with starting 2.6.25-rc1 and latest git

    Hi Mariusz,

    On Tue, 26 Feb 2008 17:04:46 +0100, Mariusz Kozlowski wrote:
    > I can reproduce this here on rc3 as well. Weird - on git tree before
    > rc3 was released this didn't happen. rc2 and rc1 are broken. I also
    > don't know why nobody else see this but us And not sure how
    > to debug it some more or provide more accurate information.


    Here's a quick and dirty debugging patch I wrote in an attempt to find
    out what was going on. Unfortunately, the problem never happened to me
    when this debug patch was applied. Maybe you'll have more "luck"?

    kernel/module.c | 4 ++++
    1 file changed, 4 insertions(+)

    --- linux-2.6.25-rc1.orig/kernel/module.c 2008-02-14 09:16:15.000000000 +0100
    +++ linux-2.6.25-rc1/kernel/module.c 2008-02-14 23:20:22.000000000 +0100
    @@ -2153,8 +2153,10 @@ sys_init_module(void __user *umod,
    return PTR_ERR(mod);
    }

    + printk(KERN_WARNING "loading module %s, checkpoint 1\n", mod->name);
    /* Drop lock so they can recurse */
    mutex_unlock(&module_mutex);
    + printk(KERN_WARNING "loading module %s, checkpoint 2\n", mod->name);

    blocking_notifier_call_chain(&module_notify_list,
    MODULE_STATE_COMING, mod);
    @@ -2177,6 +2179,7 @@ sys_init_module(void __user *umod,

    /* Now it's a first class citizen! */
    mutex_lock(&module_mutex);
    + printk(KERN_WARNING "loading module %s, checkpoint 3\n", mod->name);
    mod->state = MODULE_STATE_LIVE;
    /* Drop initial reference. */
    module_put(mod);
    @@ -2186,6 +2189,7 @@ sys_init_module(void __user *umod,
    mod->init_size = 0;
    mod->init_text_size = 0;
    mutex_unlock(&module_mutex);
    + printk(KERN_WARNING "loading module %s, checkpoint 4\n", mod->name);
    wake_up(&module_wq);

    return 0;


    --
    Jean Delvare
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  12. Re: problem with starting 2.6.25-rc1 and latest git

    Hello Jean,

    > On Tue, 26 Feb 2008 17:04:46 +0100, Mariusz Kozlowski wrote:
    > > I can reproduce this here on rc3 as well. Weird - on git tree before
    > > rc3 was released this didn't happen. rc2 and rc1 are broken. I also
    > > don't know why nobody else see this but us And not sure how
    > > to debug it some more or provide more accurate information.

    >
    > Here's a quick and dirty debugging patch I wrote in an attempt to find
    > out what was going on. Unfortunately, the problem never happened to me
    > when this debug patch was applied. Maybe you'll have more "luck"?


    Sorry for the late response. I tried your patch and it seems we share this 'luck'.
    I couldn't reproduce that. I have a few other ideas to try. I'll see what I can do.
    Unfortunately my time got limited recently so I'm lagging behind LKML and
    kernel stuff :-/

    Mariusz

    > kernel/module.c | 4 ++++
    > 1 file changed, 4 insertions(+)
    >
    > --- linux-2.6.25-rc1.orig/kernel/module.c 2008-02-14 09:16:15.000000000 +0100
    > +++ linux-2.6.25-rc1/kernel/module.c 2008-02-14 23:20:22.000000000 +0100
    > @@ -2153,8 +2153,10 @@ sys_init_module(void __user *umod,
    > return PTR_ERR(mod);
    > }
    >
    > + printk(KERN_WARNING "loading module %s, checkpoint 1\n", mod->name);
    > /* Drop lock so they can recurse */
    > mutex_unlock(&module_mutex);
    > + printk(KERN_WARNING "loading module %s, checkpoint 2\n", mod->name);
    >
    > blocking_notifier_call_chain(&module_notify_list,
    > MODULE_STATE_COMING, mod);
    > @@ -2177,6 +2179,7 @@ sys_init_module(void __user *umod,
    >
    > /* Now it's a first class citizen! */
    > mutex_lock(&module_mutex);
    > + printk(KERN_WARNING "loading module %s, checkpoint 3\n", mod->name);
    > mod->state = MODULE_STATE_LIVE;
    > /* Drop initial reference. */
    > module_put(mod);
    > @@ -2186,6 +2189,7 @@ sys_init_module(void __user *umod,
    > mod->init_size = 0;
    > mod->init_text_size = 0;
    > mutex_unlock(&module_mutex);
    > + printk(KERN_WARNING "loading module %s, checkpoint 4\n", mod->name);
    > wake_up(&module_wq);
    >
    > return 0;
    >
    >



    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread