reply-all didn't get this to list ... posting.
On Fri, Jul 9, 2010 at 8:15 AM, 0bo0 <[email protected]> wrote:
> On Fri, Jul 9, 2010 at 12:46 AM, Jan Beulich <[email protected]> wrote:
>> The question then is why request_firmware() succeeds. We're not
>> talking about a kernel you built yourself, do we?
>
> no, not custom. atm, this is,
>
> uname -a
> Linux server 2.6.34.1-2-xen #1 SMP 2010-07-06 15:11:07 +0200 x86_64
> x86_64 x86_64 GNU/Linux
> lsb_release -a
> LSB Version:
> core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
> Distributor ID: SUSE LINUX
> Description: openSUSE 11.3 (x86_64)
> Release: 11.3
> Codename: n/a
> grep base /etc/zypp/repos.d/Kernel_113.repo
> baseurl=http://download.opensuse.org/repositories/Kernel:/openSUSE-11.3/openSUSE_11.3
>
>> Again, this is a different thing. Can we please finally get to know how
>> a native kernel of the same version behaves?
>>
>> You may want to set udev_log="info" in /etc/udev/udev.conf and
>> USE_SYSLOG="yes" in /etc/sysconfig/hardware/config to get
>> relevant output from /lib/udev/firmware.sh.
>
>> You may want to set udev_log="info" in /etc/udev/udev.conf and
>> USE_SYSLOG="yes" in /etc/sysconfig/hardware/config to get
>
> mkdir -p /etc/sysconfig/hardware
>
> udev_log="info" < -- /etc/udev/udev.conf
> USE_SYSLOG="yes" <-- /etc/sysconfig/hardware/config to get
>
> reboot
> uname -a
> Linux server 2.6.34.1-2-default #1 SMP 2010-07-06 15:11:07 +0200
> x86_64 x86_64 x86_64 GNU/Linux
>
> egrep -i "amd|microcode" /var/log/*
> boot.msg:<6>[ 0.000000] RAMDISK: 374ec000 - 37ff0000
> boot.msg:<4>[ 0.000000] ACPI: SSDT 00000000cff87950 0088C (v01 A M
> I POWERNOW 00000001 AMD 00000001)
> boot.msg:<6>[ 0.000000] #2 [00374ec000 - 0037ff0000] RAMDISK
> boot.msg:<6>[ 0.108011] Performance Events: AMD PMU driver.
> boot.msg:<6>[ 0.389812] CPU0: AMD Phenom(tm) II X4 920 Processor stepping
> 02
> boot.msg:<6>[ 6.049868] ehci_hcd 0000:00:12.2: applying AMD
> SB600/SB700 USB freeze workaround
> boot.msg:<6>[ 6.410466] ehci_hcd 0000:00:13.2: applying AMD
> SB600/SB700 USB freeze workaround
> boot.msg:<6>[ 70.960588] EDAC amd64_edac: Ver: 3.3.0 Jul 7 2010
> boot.msg:<5>[ 70.972413] EDAC amd64: This node reports that Memory
> ECC is currently disabled, set F3x44[22] (0000:00:18.3).
> boot.msg:<5>[ 70.995125] EDAC amd64: ECC disabled in the BIOS or no
> ECC capability, module will not load.
> boot.msg:<4>[ 71.052063] amd64_edac: probe of 0000:00:18.2 failed
> with error -22
> boot.msg:<6>[ 101.168845] microcode: CPU0: patch_level=0x1000086
> boot.msg:<6>[ 101.179148] platform microcode: firmware: requesting
> amd-ucode/microcode_amd.bin
> boot.msg:<3>[ 161.196043] microcode: failed to load file
> amd-ucode/microcode_amd.bin
> boot.msg:<6>[ 161.209155] microcode: CPU1: patch_level=0x1000086
> boot.msg:<6>[ 161.218814] platform microcode: firmware: requesting
> amd-ucode/microcode_amd.bin
> boot.msg:<3>[ 183.217466] microcode: failed to load file
> amd-ucode/microcode_amd.bin
> boot.msg:<6>[ 183.231803] microcode: CPU2: patch_level=0x1000086
> boot.msg:<6>[ 183.244129] platform microcode: firmware: requesting
> amd-ucode/microcode_amd.bin
> boot.msg:<3>[ 183.947110] microcode: failed to load file
> amd-ucode/microcode_amd.bin
> boot.msg:<6>[ 183.960985] microcode: CPU3: patch_level=0x1000086
> boot.msg:<6>[ 183.973330] platform microcode: firmware: requesting
> amd-ucode/microcode_amd.bin
> boot.msg:<3>[ 184.714601] microcode: failed to load file
> amd-ucode/microcode_amd.bin
> boot.msg:<6>[ 184.729013] microcode: Microcode Update Driver: v2.00
> <[email protected]>, Peter Oruba
> boot.msg:<6>[ 184.736631] microcode: AMD microcode update via
> /dev/cpu/microcode not supported
> boot.msg:<6>[ 184.736649] microcode: AMD microcode update via
> /dev/cpu/microcode not supported
> boot.msg:<6>[ 184.784460] microcode: AMD microcode update via
> /dev/cpu/microcode not supported
> boot.msg:<6>[ 184.833775] microcode: AMD microcode update via
> /dev/cpu/microcode not supported
> boot.msg:<6>[ 184.870692] microcode: AMD microcode update via
> /dev/cpu/microcode not supported
> boot.msg:<6>[ 185.577429] microcode: AMD microcode update via
> /dev/cpu/microcode not supported
> boot.msg:<6>[ 186.324561] microcode: AMD microcode update via
> /dev/cpu/microcode not supported
> boot.msg:udevd[851]: reading '/lib/udev/rules.d/89-microcode.rules' as
> rules file
> boot.msg:udevadm[853]: device 0x622140 has devpath
> '/bus/pci/drivers/agpgart-amd64'
> boot.msg:device 0x622140 has devpath '/bus/pci/drivers/agpgart-amd64'
> boot.msg:udevd[852]: mknod '/dev/cpu/microcode' c10:184
> boot.msg:udevd-work[854]: device 0x621e00 has devpath
> '/bus/pci/drivers/agpgart-amd64'
> messages:Jul 9 07:58:02 server kernel: [ 256.426728] powernow-k8:
> Found 1 AMD Phenom(tm) II X4 920 Processor (4 cpu cores) (version
> 2.20.00)
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x622140 has
> devpath '/devices/platform/microcode'
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x6221c0 has
> devpath '/devices/virtual/misc/microcode'
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc10 has
> devpath '/devices/platform/microcode'
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 has
> devpath '/devices/virtual/misc/microcode'
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:03 server udevadm[3583]: device 0x63fc90 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x622140 has
> devpath '/devices/platform/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x6221c0 has
> devpath '/devices/virtual/misc/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x6402f0 has
> devpath '/devices/platform/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 has
> devpath '/devices/virtual/misc/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled
> with db symlink data '/dev/cpu/microcode'
> messages:Jul 9 07:58:11 server udevadm[4195]: device 0x640370 filled
> with db symlink data '/dev/cpu/microcode'
>
> if you want udev_log -> debug level, or other, output, happy to provide it.
>
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
