Error Creating Sysfs Bridge Symlink Continuing
Affects Status Importance Assigned to Milestone linux (Ubuntu) Edit Won't Fix Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: linux (Ubuntu) Filed here by: Launchpad Janitor When: 2008-08-11 Completed: 2009-05-08 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Won't Fix Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report linux-source-2.6.20 (Ubuntu) Edit Won't Fix Undecided Unassigned Edit Ubuntu ubuntu-7.04 You need to log in to change this bug's status. Affecting: linux-source-2.6.20 (Ubuntu) Filed here by: Marc Tardif When: 2007-04-12 Completed: 2008-08-11 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Milestone Won't Fix Undecided Ubuntu ubuntu-7.04 Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description When attempting to install Ubuntu 20070411 from the alternate i386 CD on an Intel Bridgeport2 motherboard, there are a few messages that appear between selecting "Install in text mode" and selecting the language: Error creating sysfs bridge symlink, continuing... The message appears several times and then the installation proceeds successfully. Tags: cft-2.6.27 linux-source-2.6.20 Edit Tag help Marc Tardif (cr3) wrote on 2007-04-12: #1 syslog Edit (59.3 KiB, text/plain) Marc Tardif (cr3) wrote on 2007-04-12: #2 cpuinfo Edit (2.3 KiB, text/plain) Marc Tardif (cr3) wrote on 2007-04-12: #3 lspci -vv Edit (17.5 KiB, text/plain) Marc Tardif (cr3) wrote on 2007-04-12: #4 lspci -vvn Edit (15.1 KiB, text/plain) Fabio Massimo Di Nitto (
by: [ date ] [ thread ] [ subject ] [ author ] You could try recompiling again and instead of compiling those drivers as LKMs and subsequently creating an initrd image with them in it, compile those drivers into the kernel itself. Geoff. -----Original Message----- From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com] On Behalf Of Allen Chen Sent: Saturday, 24 November 2007 11:09 a.m. To: General Red Hat Linux discussion list Subject: Can't boot after compile kernel-2.6.23.1 Hi, everybody I have https://bugs.launchpad.net/bugs/105888 an IBM HS21 blade with LSISAS1064e controller. It works fine with RHEL 4 2.6.9-5.ELsmp. I downloaded linux-2.6.12.6.tar.gz and compiled it. The .config file is a copy of /boot/config-2.6.9-5.ELsmp and modified by running make xconfig(just add LSISAS1064e support. After I reboot with the new kernel, I got this error message at the very beginning of the boot process: ....... https://www.redhat.com/archives/redhat-list/2007-November/023125.html PCI 0000:00:1e.0: error creating sysfs bridge symlink, continuing PCI 0000:00:1e.0: error creating sysfs bridge symlink, continuing PCI 0000:00:1e.0: error creating sysfs bridge symlink, continuing PCI 0000:00:1e.0: error creating sysfs bridge symlink, continuing PCI 0000:00:1e.0: error creating sysfs bridge symlink, continuing PCI 0000:00:1e.0: error creating sysfs bridge symlink, continuing PCI 0000:00:1e.0: error creating sysfs bridge symlink, continuing insmod: error inserting "/lib/sd_mod.ko: -1 Unknown symbol in module insmod: error inserting "/lib/mptscsih.ko: -1 Unknown symbol in module insmod: error inserting "/lib/mptsas.ko: -1 Unknown symbol in module ............... mptsas.ko,mptscsih.ko and sd_mod.ko are created into initrd.img. I need these modules to boot into LSISAS1064e. Any help? Thanks Allen -- redhat-list mailing list unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list ========================================================== For more information on the Television New Zealand Group, visit us online at tvnz.co.nz ========================================================== CAUTION: This e-mail and any attachment(s) contain information that is intended to be read only by the named recipient(s). This information is not to be used or stored by any other person and/or organisation. Previous message: Can't boot after compile kernel-2.6.23.1 Next message:
thread ] [ subject ] [ author ] *Not sure if anyone has ran into this problem, but two, or three days error creating ago, I noticed upon booting up Ubuntu 7.10, it shows Starting up... [33.400902] pci 0000:00:01:0: Error creating sysfs bridge symlink continuing... Might anyone know what the problem is here...??? Thanks error creating sysfs Larry * -- Powered by Debian/GNU/Linux by Ubuntu ver 7.10 Gutsy Gibbon 73 de Larry/wd9esu 32yr's A.R.O. "This is Linux Country, on a quiet night you can hear WINDOZE ! Systems REBOOTING !!" GPG Fingerprint: A4D2 BFC2 B21B 8F7A C336 EFDC 7039 3CA5 3332 076E Public Key available from subkeys.pgp.net Previous message: how to disable fade before screensaver Next message: Problem w/ virtual terminals Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the ubuntu-users mailing list
"Re: [linux-pm] [PATCH v2] Add suspend/resume for HPET" Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Greg, A non-urgent and somwhat ugly patch; please review, and if it seems correct, please apply. --linas While fiddling with PCI hotplugging, I noticed the messages pci 0001:00:02.4: Error creating sysfs bridge symlink, continuing... pci 0001:00:02.2: Error creating sysfs bridge symlink, continuing... pci 0001:00:02.6: Error creating sysfs bridge symlink, continuing... pci 0001:00:02.0: Error creating sysfs bridge symlink, continuing... These are printed by pci_bus_add_devices(); the reason for the error is that these are all other bridges that are already in sysfs. For a while, I assumed that pci_bus_add_devices() was being called with the wrong argument, but this seems not to be the case. Thus, I simply added a flag to make these prints go quiet. This patch also cleans up some crazy whitespace indentation. This patch seems inelegant, but I'm not sure what else to do. Signed-off-by: Linas Vepstas