October 2011 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] SLOW boot: device reported invalid CHS sector 0
by Felix Miata 09 Oct '11

09 Oct '11

[32 bit 12.1B1 freshly dup'd] lspci, hwinfo --disk, fdisk -l, dmesg, /var/log/boot.omsg, /var/log/boot.msg & /var/log/messages from booting without any eSATA HD attached is at http://fm.no-ip.com/Tmp/SUSE/big31-sil3512-0hd.txt Two RC-210 SATA RTL and two RC-220 RTL PCI cards I bought from Newegg arrived yesterday. I put a 210 in one Dell, one 220 in another Dell, and tried one of each one at a time in a non-Dell built on a Biostar G31-M7 TE motherboard with G31/ICH7 chipset and P4HT (single core) CPU. Either card is recognized by the BIOS and the kernel well enough to load the applicable sata_sil module. However, booting with an eSATA HD attached to the SiL 3512's external port causes various failures, depending on which openSUSE release I try to boot. Some only take extra long to boot (11.0, 11.2, 11.4), while 12.1B1 with 3.1.rc7 don't appear capable of finishing a boot. Right now I'm looking at a boot screen showing [ 2023.8111498] and repeating the same messages over and over, one of which is in the subject. Another is lost interrupt (Status 0x50), another exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen, another hard resetting link. Early in the attempt to boot were a number of messages involving failure to initialize non-existent md devices. The system normally has two internal HDs with most partitions configured as software RAID1, but I pulled their cables and renamed mdadm.conf in order to simplify troubleshooting. Is there some way to accelerate timeout to finish booting and get logs and dmesg sooner? The numbers finally stopped at [ 2577.848249], but I don't know how to convert it to how long it took to boot. http://fm.no-ip.com/Tmp/SUSE/big31-sil3512-1hd.txt is logs from waiting for this forever boot with eSATA HD attached to finish. Anyone know what's going on? P.S. Choosing failsafe boot stanza, or older 3.0.0 or 3.1.rc5 kernels were no help. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0

[opensuse-kernel] Xen Dom0 support
by Carlos Gonçalves 06 Oct '11

06 Oct '11

Hi all, Starting with Linux 3.0, Xen dom0 support has been added in to the kernel tree as is KVM support. My question is why there is still a kernel-xen package available in openSUSE 12.1? I would expect Dom0 support to be included in kernel-{pae,desktop,default} and not have to install yet another kernel package. Thanks! Carlos Gonçalves -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] [patch #2 0/5] scripts/sequence-patch.sh: Add some useful options
by Jeff Mahoney 05 Oct '11

05 Oct '11

Hi all - There are a few things I do every time I expand the source tree with sequence-patch.sh. Or, rather, things I should do and forget to do a lot. The first I always remember to do: Copy the config I want to test with to my build directory. The second I forget more often than not: Expand the kABI references into my build directory. One of the things that bites me occasionally is when there are kABI changes that go un-noticed until the automated build checker flags them and sends me an email yelling at me for my carelessness. This patch adds three options to scripts/sequence-patch.sh to take care of these automatically. --build-dir=PATH allows you to specify the build directory you'll be using. It will create the directory if it doesn't exist. It defaults to $PATCH_DIR. --config=ARCH-FLAVOR allows you to specify the config you'll use. It will copy the config to your build directory. It is not a fatal error if the config does not exist. It will just not copy one. --kabi allows you to direct sequence-patch to expand the kABI references into your build directory. Since the references are arch/flavor specific, it depends on --config=ARCH-FLAVOR. It is not a fatal error if the kABI reference doesn't exist since this is always the case in the master branch. The --build-dir PATH is subject to shell expansion. It is expanded late enough in the script that most variables should be available. There are also three new variables available when --config is used: $CONFIG contains the --config contents. $CONFIG_ARCH contains the arch part of the config. $CONFIG_FLAVOR contains the flavor part. For reference, I have this in my .bashrc: export SEQUENCE_PATCH_ARGS="--config=x86_64-desktop --build-dir=~/src/scratch/build/\$CONFIG_ARCH/linux-\$SRCVERSION-\$TAG-\$CONFIG_FLAVOR --kabi" I've also added patches for --ctags and --cscope which will automatically generate the databases for either of those tools in the build directory after the source tree is expanded. - Issues addressed in patchset #2: - Help text is now a here document for easy addition of more documentation - Explanation of which variables are allowed by --build-dir - Missing rpm/modversions script is not an error on older branches - Missing symvers files are not errors - Uses true/false for simple feature flags -Jeff -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

5 13

[opensuse-kernel] Kernel-defined memdesk dosn't mach the one from EFI!
by Günther J. Niederwimmer 05 Oct '11

05 Oct '11

Hello, is this a kernel, (U)EFI or Bios Problem? Or is this normal ? I have 168 entry in the boot log like [0.00000] EFI mem00: type 3, attr=0xf, range [0x0000000000000000-0x0000000000001000] -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0