There is no such error in Yocto 1.1 M1 testing. Commit Information: Tree/Branch: Poky/Master Poky Commit: 2163461ec94528ecf046a04edc5db3d2dd3a6b8b Meta Branch: Master Meta Commit: 76d1178ba1a43cf6457c89717134aeb9f1275fae Image location: http://autobuilder02.pokylinux.org/sugarbay-master/nightly/20110617-1/machines/sugarbay/x86_32/core-image-sato-sdk-live-sugarbay-20110618064833.hddimg.bz2 The error log is as below: ########## FDC 0 is a National Semiconductor PC87306 parport_pc 00:0b: [io 0x0378-0x037b] parport_pc 00:0b: [io 0x0278-0x027b] parport_pc 00:0b: [io 0x03bc-0x03bf] parport_pc 00:0b: [io 0x0378-0x037b] parport_pc 00:0b: [io 0x0278-0x027b] parport_pc 00:0b: [io 0x03bc-0x03bf] parport_pc 00:0b: unable to assign resources parport_pc: probe of 00:0b failed with error -16 ##########
Bruce, have there been any relevant base or standard config changes that might cause this? Tom, any relevant sugarbay changes?
Nothing that hits the sugarbay. We've got quite a few meta changes, but they have all been in the tree for sometime, and none are near parport support. so no great ideas here.
There is no such issue in Yocto1.1 M2 RC3 testing. Tree/Branch: Poky/1.1_M2 Poky Commit id: fa4bcfdb73167f8159b88e5a4d711c0d37627a70 Image location: http://autobuilder03.jf.intel.com/crownbay-1.1_M2/nightly/20110717-1/machines/crownbay/x86_32/core-image-sato-sdk-live-crownbay-20110717223745.hddimg.bz2
Verify this bug.