From: Andrew Benton <b3nt@ukonline.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: Kernel Firmware Loading
Date: Tue, 01 Nov 2005 21:19:34 +0000 [thread overview]
Message-ID: <4367DBE6.40701@ukonline.co.uk> (raw)
In-Reply-To: <4365DBD9.2040407@ukonline.co.uk>
Alexander E. Patrakov wrote:
> Details for firmware-loading initramfs (untested, since none of my
> devices generate firmware hotplug events):
> <snip>
Hi Alexander,
thanks for taking the time to type such a long message. Unfortunately it isn't working. It boots OK but the firmware doesn't load and I get some rather ominous messages in the sys.log
Nov 1 20:52:31 hame kernel: usb 3-2: reset full speed USB device using uhci_hcd and address 3
Nov 1 20:52:31 hame kernel: Badness in kref_get at lib/kref.c:32
Nov 1 20:52:31 hame kernel: usbcore: registered new driver speedtch
Nov 1 20:52:31 hame kernel: [<c01f3394>] kref_get+0x3d/0x3f
Nov 1 20:52:31 hame kernel: [<c01f2b8f>] kobject_get+0xf/0x13
Nov 1 20:52:31 hame kernel: [<c027b2db>] class_get+0xe/0x1e
Nov 1 20:52:31 hame kernel: [<c027b9ef>]<6>ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 17
Nov 1 20:52:31 hame kernel: nvidiafb: nVidia device/chipset 10DE0322
Nov 1 20:52:31 hame kernel: class_device_add+0x3c/0x210
Nov 1 20:52:31 hame kernel: [<c01f2b8f>] kobject_get+0xf/0x13
Nov 1 20:52:31 hame kernel: [<c01f295d>] kobject_init+0x23/0x36
Nov 1 20:52:31 hame kernel: [<c027e6e0>] fw_register_class_device+0xfe/0x12d
Nov 1 20:52:31 hame kernel: [<c027e730>] fw_setup_class_device+0x21/0xca
Nov 1 20:52:31 hame kernel: [<c027e82c>] _request_firmware+0x53/0x180
Nov 1 20:52:31 hame kernel: [<c027e968>] request_firmware+0xf/0x13
Nov 1 20:52:31 hame kernel: [<c0222af6>] speedtch_find_firmware+0x54/0x130
Nov 1 20:52:31 hame kernel: [<c0222bed>] speedtch_heavy_init+0x1b/0x5f
Nov 1 20:52:31 hame kernel: [<c02247b7>] usbatm_do_heavy_init+0x32/0x69
Nov 1 20:52:31 hame kernel: [<c0224785>] usbatm_do_heavy_init+0x0/0x69
Nov 1 20:52:31 hame kernel: [<c0101099>] kernel_thread_helper+0x5/0xb
Nov 1 20:52:31 hame kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000c
Nov 1 20:52:31 hame kernel: printing eip:
Nov 1 20:52:31 hame kernel: c017d34a
Nov 1 20:52:31 hame kernel: *pde = 00000000
Nov 1 20:52:31 hame kernel: Oops: 0000 [#1]
Nov 1 20:52:31 hame kernel: SMP
Nov 1 20:52:31 hame kernel: CPU: 0
Nov 1 20:52:31 hame kernel: EIP: 0060:[<c017d34a>] Not tainted VLI
Nov 1 20:52:31 hame kernel: EFLAGS: 00010286 (2.6.14-git4)
Nov 1 20:52:31 hame kernel: EIP is at create_dir+0xd/0x16e
Nov 1 20:52:31 hame kernel: eax: dff0e988 ebx: dff0e988 ecx: dff0e98c edx: 00000000
Nov 1 20:52:31 hame kernel: esi: dff0e98c edi: c045a6bc ebp: 00000000 esp: dfc8be90
Nov 1 20:52:31 hame kernel: ds: 007b es: 007b ss: 0068
Nov 1 20:52:31 hame kernel: Process speedtch (pid: 215, threadinfoflc8a000 task¡5ee530)
Nov 1 20:52:31 hame kernel: Stack: 00000000 ffffffff ffffffff dff0e988 00000000 c045a6bc c045a6a0 c017d4ef
Nov 1 20:52:31 hame kernel: dfc8beb4 00000000 dff0e988 c01f2841 dff0e988 fffffffe c01f2a03 dff0e9f0
Nov 1 20:52:31 hame kernel: dff0e980 00000000 c027ba35 dff0e988 c0418099 dff0e9f0 dff0e988 c01f295d
Nov 1 20:52:31 hame kernel: Call Trace:
Nov 1 20:52:31 hame kernel: [<c017d4ef>] sysfs_create_dir+0x2c/0x66
Nov 1 20:52:31 hame kernel: [<c01f2841>] create_dir+0x13/0x37
Nov 1 20:52:31 hame kernel: [<c01f2a03>] kobject_add+0x5e/0x98
Nov 1 20:52:31 hame kernel: [<c027ba35>] class_device_add+0x82/0x210
Nov 1 20:52:31 hame kernel: [<c01f295d>] kobject_init+0x23/0x36
Nov 1 20:52:31 hame kernel: [<c027e6e0>] fw_register_class_device+0xfe/0x12d
Nov 1 20:52:31 hame kernel: [<c027e730>] fw_setup_class_device+0x21/0xca
Nov 1 20:52:31 hame kernel: [<c027e82c>] _request_firmware+0x53/0x180
Nov 1 20:52:31 hame kernel: [<c027e968>] request_firmware+0xf/0x13
Nov 1 20:52:31 hame kernel: [<c0222af6>] speedtch_find_firmware+0x54/0x130
Nov 1 20:52:31 hame kernel: [<c0222bed>] speedtch_heavy_init+0x1b/0x5f
Nov 1 20:52:31 hame kernel: [<c02247b7>] usbatm_do_heavy_init+0x32/0x69
Nov 1 20:52:31 hame kernel: [<c0224785>] usbatm_do_heavy_init+0x0/0x69
Nov 1 20:52:31 hame kernel: [<c0101099>] kernel_thread_helper+0x5/0xb
Nov 1 20:52:31 hame kernel: Code: 00 00 00 00 c7 80 9c 00 00 00 00 6c 44 c0 31 c0 c3 c7 80 98 00 00 00 a0 6d 44 c0 31 c0 c3 55 57 56 53 83 ec 0c 89 c3 89 d5 89 ce <8b> 52 0c f0 ff 4a 74 0f 88 7c 0b 00 00 31 c0 b9 ff ff ff ff 89
But at least it boots.
All my attempts to build an initramfs into the kernel end in Kernel panic:(
Andy
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-11-01 21:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 8:54 Kernel Firmware Loading Andrew Benton
2005-10-31 9:37 ` Alexander E. Patrakov
2005-10-31 10:04 ` Andrew Benton
2005-10-31 10:59 ` Duncan Sands
2005-10-31 10:59 ` Alexander E. Patrakov
2005-10-31 11:08 ` Marco d'Itri
2005-10-31 11:18 ` Duncan Sands
2005-10-31 11:50 ` Marco d'Itri
2005-10-31 13:10 ` Kay Sievers
2005-10-31 13:27 ` Duncan Sands
2005-10-31 14:35 ` Kay Sievers
2005-10-31 14:41 ` Duncan Sands
2005-10-31 14:54 ` Kay Sievers
2005-10-31 16:29 ` linas
2005-10-31 16:33 ` Marco d'Itri
2005-10-31 21:15 ` Andrew Benton
2005-11-01 9:48 ` Duncan Sands
2005-11-01 11:15 ` Andrew Benton
2005-11-01 15:56 ` Alexander E. Patrakov
2005-11-01 16:59 ` linas
2005-11-01 21:19 ` Andrew Benton [this message]
2005-11-02 2:09 ` Alexander E. Patrakov
2005-11-02 6:20 ` Alexander E. Patrakov
2005-11-02 6:28 ` Alexander E. Patrakov
2005-11-02 23:22 ` Andrew Benton
2005-11-03 8:08 ` Duncan Sands
2005-11-04 14:46 ` Alexander E. Patrakov
2005-11-04 14:52 ` Duncan Sands
2005-11-04 15:14 ` Alexander E. Patrakov
2005-11-07 15:48 ` Patrick Mansfield
2005-11-08 8:16 ` Alexander E. Patrakov
2005-11-08 17:54 ` Greg KH
2005-11-08 18:37 ` Patrick Mansfield
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=4367DBE6.40701@ukonline.co.uk \
--to=b3nt@ukonline.co.uk \
--cc=linux-hotplug@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).