| View previous topic :: View next topic |
| Author |
Message |
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
 Posted: Wed Apr 04, 2012 8:04 pm Post subject: root fails to mount at boot time [solved, sort of] |
 |
|
I've seen some other posts in the forum similar to this (like http://forums.gentoo.org/viewtopic-p-6942940.html), but the eventual solutions to those (if any) didn't seem to apply to my situation, although I could be wrong and just misunderstand what's going on.
I have a 3.0.6 kernel that has been working. I had a power outage last night, and my box didn't boot today. The kernel loads, but then fails when it tries to mount the rootfs, like this:
| Code: | !!The filesystem mounted at /dev/sdb3 does not appear to be a valid /. Try again
!!Could not find the root block device in.
Please specify another value or: press Enter for the same , type "shell" ...... |
I dropped into ash, but ash doesn't include fdisk, and I couldn't mount /dev/sdb3 from there, so I rebooted to a livecd to look around. When I tried to mount /dev/sdb3 (it's a JFS partition), the command failed with some message about a bad superblock (sorry - the message is long gone, so I can't paste it here). I did a jfs_fsck on it, and mounted after that. Same story for /dev/sda1 (mounted as /usr) and /dev/sda3 (mounted as /var).
Here's my grub.conf:
| Code: | default 0
timeout 10
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title Gentoo Linux 3.0.6
root (hd0,0)
kernel /boot/kernel-genkernel-x86_64-3.0.6-gentoo root=/dev/ram0 real_root=/dev/sdb3
initrd /boot/initramfs-genkernel-x86_64-3.0.6-gentoo
|
The kernel was build by genkernel on a livecd when I did the installation. Not sure how to get the config.
Any ideas?
Last edited by aggieben on Tue May 01, 2012 2:45 am; edited 2 times in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Thu Apr 05, 2012 7:33 pm Post subject: |
|
|
aggieben,
| Code: | !!The filesystem mounted at /dev/sdb3 does not appear to be a valid /. Try again
!!Could not find the root block device in.
Please specify another value or: press Enter for the same , type "shell" ...... |
is significant for what it does not say.
The kernel has loaded but can see no block devices at all or that message would list them after | Code: | | !!Could not find the root block device in |
This suggests that you initrd is broken as it should provide the modules needed to see the root block device.
I notice that you have a separate /usr and /var. Thats a warning sign.
udev newer than version 179 needs /usr to be mounted by thi initrd before udev starts.
Further, openrc-9.9.3 sppears to not mount things unles you have DEVTMPFS defined in your kernel.
I masked udev because I knew about the issue before it happened to me but my KVM host won't boot unaided at the moment as it has separete /usr and /var.
You may have been bitten by an update as well as an unclean shutdown.
Chroot into your install, update genkernel (you need a new one to make the initrd correctly), update your kernel and try again.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Thu Apr 12, 2012 11:22 pm Post subject: |
|
|
Neddy, thanks for the reply.
I took your advice and tried rebuilding my kernel and rebooting, and nothing changed, really. Here's what I did:
- reboot into livecd
- mount /dev/sdb3 /mnt/gentoo
- mount /dev/sdb1 /mnt/gentoo/boot
- mount -t proc none /mnt/gentoo/proc
- mount --rbind /dev /mnt/gentoo/dev
- chroot /mnt/gentoo
- env-update
- emerge -u genkernel
- emerge -u gentoo-sources
- eselect kernel set 3 (selecting 3.2.12-gentoo)
- genkernel --install initramfs
- genkernel all
- nano /boot/grub/grub.conf (update kernel filename, remove "root" option, add "ro" option to support JFS journal replay at boot)
- grep -v rootfs /proc/mounts > /etc/mtab
- grub-install --no-floppy /dev/sdb (I can't remember why, but despite the /dev ordering I think /dev/sdb is where the MBR is)
- reboot
I get this message at reboot:
| Code: | **snip**
:: Scanning for jfs...jfs loaded.
:: Scanning for nfs...sunrpc, lockd, nfs loaded.
:: Scanning for fuse...fuse loaded.
:: Scanning for e1000.1000 loaded.
:: Scanning for tg3...libphy, tg3 loaded.
:: Scanning for scsi_transport_iscsi...scsi_transport_iscsi loaded.
:: Scanning for libiscsi...libisci loaded.
>> Hint: Use parameter scandelay[=seconds] if you need waiting here
>> Activating mdev
>> Determining root device...
>> Mounting root...
>> Using mount -t auto -o ro
!! The filesystem mounted at /dev/sdb3 does not appear to be a valid /, try again
!! Could not find the root block device in .
Please specify another value or: press Enter for the same, type "shell" for a shell, or "q" to skip...
root block device() :: |
Had to hand-transcribe this from the console, so my apologies for any typos.
Did I miss something in my steps above, or is there something non-obvious going on here? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Fri Apr 13, 2012 6:58 pm Post subject: |
|
|
aggieben
Do the | Code: | reboot into livecd
mount /dev/sdb3 /mnt/gentoo |
again.
Now do | Code: | lspci -k | wgetpaste
wgetpaste /mnt/gentoo/usr/src/linux/.config |
and tell us the URLs you get back.
The first one tells about your hardware, the second one is you kernel config.
It looks like the kernel cannot see your hardware.
You can also do someting to identinfy your drives at the grub splash screen. Press 'e' for edit, instead of selecting a kernel.
Read the instructions. :)
Find the line tat says and change it to read press the tab key and grub will list your drives. Fill in a drive number so the root statement looks like press tab. Grub will list the partitions on the selected drive.
If you do this for all your drives, you can probably tell which is which.
I don't think you have a grub issue, unless you have grub on both drives ... that way lies madness.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Mon Apr 16, 2012 1:36 am Post subject: |
|
|
Neddy, first of all, thanks a ton for taking the time to think through this.
Anyway, here are my pastes:
http://paste.pocoo.org/show/582144/ (lspci output)
http://paste.pocoo.org/show/582145/ (kernel config)
I noticed that the sata_sil driver (which is what the livecd apparently uses for the SiI 3512 controller) is compiled as a module, as is the jfs driver. I watched the output carefully to see that they are both loaded (and they are).
I used the grub editor to tab like you suggested to verify that the grub config is pointed at the right root partition, and it's pointed to /dev/sdb1, which is the ext2fs where the kernel is located.
I'm quite baffled. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Mon Apr 16, 2012 6:00 pm Post subject: |
|
|
aggieben,
To get booted, you don't actually need a great deal correct in the kernel. We can tell you have something fairly basic incorrect as | Code: | | Could not find the root block device in . |
should include a list of all the block devices the kernel can see. You have none.
From the top, you need the following items:-
The Block Layer - thats really difficult to turn off.
The SCSI high level disk driver
The SATA menu items for your chipset, or the kernel cant talk to your drives at all.
The Partition Table code for the partition table type you used
The File System driver for your Root partition.
Thats about it to mount root. You need lots of other stuff for a working system but just now, thats just nice to have. Looking through your kernel settings
| Code: | CONFIG_BLOCK=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y |
thats the block layer, the high level SCSI layer, and the high level SCSI drivers for your Hard drives and CDROM. Thats all good.
Looking at the hardware specific parts, your lspci says:-
| Code: | 01:02.0 IDE interface: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
Subsystem: IBM Device 3512
Kernel driver in use: sata_sil
Kernel modules: ata_generic, pata_acpi, sata_sil
83:04.0 SCSI storage controller: Adaptec AIC-7902B U320 (rev 10)
Subsystem: IBM Device 02b7
Kernel driver in use: aic79xx
Kernel modules: aic79xx
83:04.1 SCSI storage controller: Adaptec AIC-7902B U320 (rev 10)
Subsystem: IBM Device 02b7
Kernel driver in use: aic79xx
Kernel modules: aic79xx |
Thats interesting - real SCSI. This looks like it might have been a server at some point in its life.
| Code: | CONFIG_SATA_SIL=m
# CONFIG_ATA_GENERIC is not set
CONFIG_PATA_ACPI=m |
Thats a "go to jail, go directly to jail, do not pass go, do not collect 200 <insert local currency here>" problem.
Your SATA seems to need CONFIG_ATA_GENERIC.
| Code: | CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=5000
# CONFIG_AIC79XX_DEBUG_ENABLE is not set |
is correct for your SCSI card.
Before you fix your kernel, use the grub editor to add doscsi to the kernel command line to see if that makes a difference. It probably won't but its a lot easier than a kernel build.
If that fails, use genkernel to rebuild your kernel again. This time, use the --menuconfig option, so you can make changes to the configuration before the build happens.
Once in menuconfig, press / to search and enter ATA_GENERIC. The kernel will tell you where in the menu system the option is and what the propmt is you need to look for. Set it to <*>.
Exit menuconfig being careful to save the change. Genkernel will carry on.
| Code: | CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y |
are the only two partition types you are likely to need.
You have all the common filesystems set and most of the uncommoon ones too.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Fri Apr 20, 2012 2:24 pm Post subject: |
|
|
I thought I replied a couple days ago, but I guess not. I tried what you suggested, and experienced no change in the outcome. I've double-checked my kernel config for the selections you pointed out, and they're all set accordingly.
I did a diff of the livecd config and my 3.2.12 config, and I didn't see any differences that gave me pause (although I admit it's not comparing apples to apples because the livecd kernel isn't booting from my disk). Here's the config I'm trying to boot with: http://paste.pocoo.org/show/584636/
I agree that it seems the basic problem is that the kernel can't see the block devices, but the basic reason for it isn't presenting itself. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Fri Apr 20, 2012 5:59 pm Post subject: |
|
|
aggieben,
Its time to trach things by file timestamp because it appeas that whatever you do, nothing changes. This is a symptom of not installing your kernel properly, so you may have fixed the probem, you are just not using the fixed kernel.
Run the command on the following files. They should get progresively newer.
| Code: | | /usr/src/linux/.config |
thats the kernel config file. The timestamp should be the time you last used menuconfig. If not, you have a problem here.
| Code: | | /usr/src/linux/arch/x86/boot/bzImage |
this is the kernel file as built, before its copied to /boot. IF it came from the .config file above, it must be newer than the .config.
Lastly, look at the timestamp on the kernel files in /boot. The one you are using should have the same timestamp as the bzImage above, as its a copy of it.
f all that looks good, post and your grub.conf file.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Mon Apr 23, 2012 3:28 am Post subject: |
|
|
Good idea. Here's what I found, chrooted into /mnt/gentoo:
| Code: | livecd / # ls -l /usr/src/linux/.config
-rw-r--r-- 1 root root 88860 Apr 16 15:27 /usr/src/linux/.config
livecd / # ls -l /usr/src/linux/arch/x86_64/boot/bzImage
lrwxrwxrwx 1 root root 22 Apr 16 15:34 /usr/src/linux/arch/x86_64/boot/bzImage -> ../../x86/boot/bzImage
livecd / # ls -l /usr/src/linux/arch/x86/boot/bzImage
-rw-r--r-- 1 root root 3318880 Apr 16 15:34 /usr/src/linux/arch/x86/boot/bzImage
livecd / # ls -l /boot
total 17384
-rw-r--r-- 1 root root 1876490 Dec 8 11:09 System.map-genkernel-x86_64-3.0.6-gentoo
-rw-r--r-- 1 root root 1902165 Apr 16 15:34 System.map-genkernel-x86_64-3.2.12-gentoo
lrwxrwxrwx 1 root root 1 Dec 8 20:45 boot -> .
drwxr-xr-x 2 root root 1024 Apr 11 11:34 grub
-rw-r--r-- 1 root root 3779604 Dec 8 11:23 initramfs-genkernel-x86_64-3.0.6-gentoo
-rw-r--r-- 1 root root 3720761 Apr 16 15:48 initramfs-genkernel-x86_64-3.2.12-gentoo
-rw-r--r-- 1 root root 3107648 Dec 8 11:09 kernel-genkernel-x86_64-3.0.6-gentoo
-rw-r--r-- 1 root root 3318880 Apr 16 15:34 kernel-genkernel-x86_64-3.2.12-gentoo
drwx------ 2 root root 12288 Dec 8 14:21 lost+found
livecd / # ls -l /boot/grub/grub.conf
-rw-r--r-- 1 root root 629 Apr 16 14:59 /boot/grub/grub.conf |
It looks like the config was completed at about 15:27, followed by the bzImage being built, followed by the initramfs, followed by grub.conf (which was my edit to fix the kernel filename).
Is there a way to verify after booting the new kernel what it's config was? |
|
| Back to top |
|
|
Dont Panic
Guru
Joined: 20 Jun 2007
Posts: 317
Location: SouthEast U.S.A.
|
| Posted: Mon Apr 23, 2012 1:57 pm Post subject: |
|
|
| aggieben wrote: | | Is there a way to verify after booting the new kernel what it's config was? |
If you built your kernel with Kernel .config support and access through /proc/config.gz (under General setup --->), then yes.
| Code: | <*> Kernel .config support
[*] Enable access to .config through /proc/config.gz |
You can then type 'less /proc/config.gz' to examine the .config file used in the active kernel.
If you built without Kernel .config support, you can always just check the kernel's build time with 'cat /proc/version'. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Mon Apr 23, 2012 6:01 pm Post subject: |
|
|
aggieben,
Provided the box boots, uname -a will say something like | Code: | $ uname -a
Linux NeddySeagoon 3.3.1-gentoo #2 SMP PREEMPT Sat Apr 14 16:12:25 BST 2012 x86_64 AMD Phenom(tm) II X6 1090T Processor AuthenticAMD GNU/Linux |
The #2 is the number of times the kernel has been built, the Sat Apr 14 16:12:25 BST 2012 is the build date and time.
Its significant that you have two kernels in /boot and every time you boot, nothing changes. I expect that grub.conf is booting kernel-genkernel-x86_64-3.0.6-gentoo, from 8 Dec, not kernel-genkernel-x86_64-3.2.12-gentoo from nowish.
Your time sequence is correct.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Mon Apr 23, 2012 7:07 pm Post subject: |
|
|
Neddy, after booting back into the broken kernel, I dropped into the ash shell and got the uname, which is the following:
| Code: | | Linux (none) 3.2.12-gentoo #1 SMP Mon Apr 16 15:34:28 CDT 2012 x86_64 GNU/Linux |
It appears that the new kernel is indeed loading, but is still unable to see the block devices. Is it possible that a hardware failure could cause this kind of behavior (i.e., where the kernel can't see them during the boot process, but the livecd is able to mount them)? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Mon Apr 23, 2012 7:56 pm Post subject: |
|
|
aggieben,
Its the same hardware in both cases, so if its a hardware failure, its the same problem for both your kernel and the liveCD.
Can you get into the shell on a failed boot and see if your have any /dev/sdX modes?
will show them. If so, what are they?
If not, do if there is no error, do you have and disk nodes now.
Try too. Which one, if any makes your /dev/sd nodes appear ?
As you are using genkernel, you may need to add doscsi to the kernel line in grub.conf.
Press e at the grub splash screen then follow the instructions.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Dont Panic
Guru
Joined: 20 Jun 2007
Posts: 317
Location: SouthEast U.S.A.
|
| Posted: Mon Apr 23, 2012 8:18 pm Post subject: |
|
|
Looking back at your first post, I see you have /usr mounted as a separate partition, and I see we are having problems with devices.
You may have run into the new initramfs/udev/"usr on separate partition" problem.
I see where you are generating an initramfs. Is your grub entry correctly using the generated initramfs?
Did you recently upgrade udev?
Maybe see if anything in this thread (udev update killed my system - HELP please) rings a bell:
http://forums.gentoo.org/viewtopic-t-917082.html |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Mon Apr 23, 2012 8:36 pm Post subject: |
|
|
Dont Panic,
Well caught!.
udev-182 requires openrc-0.9.9.3 and a very new genkernel to make a suitable inird.
However thats all in ~arch.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Tue Apr 24, 2012 2:22 pm Post subject: |
|
|
Neddy, all my /dev/sd* devices are present with no intervention.
/dev/sda
/dev/sda1 <=== /usr
/dev/sda2 <=== /home
/dev/sda3 <=== /var
/dev/sdb
/dev/sdb1 <=== /boot
/dev/sdb2 <=== /swap
/dev/sdb3 <=== / |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Tue Apr 24, 2012 2:23 pm Post subject: |
|
|
| Re: udev and openrc, I'll reboot into the livecd again and chroot into the env to see what versions of things I have merged. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Tue Apr 24, 2012 2:43 pm Post subject: |
|
|
| I've got udev-164-r2 and openrc-0.9.4 installed, so it seems that the udev issues shouldn't be in play here. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Tue Apr 24, 2012 5:46 pm Post subject: |
|
|
Also, here's the output of dmesg on the failed kernel. Note in particular the last few lines. Why is mount trying to mount a GFS2 filesystem, when mount on the livecd correctly recognizes (and, incidentally, so does mount from the initramfs after the boot fails. When I drop into the ash shell in the initramfs, I can mount those same block devices that fail during the boot process)? It seems as though mount fails to see that /dev/sdb3 is formatted as JFS, and then proceeds to try out UDF, OCFS2, and GFS2 and when they all fail (as they should), the whole process bombs.
| Code: | ng Node 0, Processors #1 Ok.
smpboot cpu 1: start_ip = 98000
Brought up 2 CPUs
Total of 2 processors activated (8774.98 BogoMIPS).
PM: Registering ACPI NVS region at bff72000 (57344 bytes)
NET: Registered protocol family 16
node 0 link 2: io port [0, 2fff]
node 0 link 0: io port [3000, 4fff]
node 0 link 0: io port [9000, 9fff]
TOM: 00000000c0000000 aka 3072M
node 0 link 2: mmio [c0000000, c04fffff]
node 0 link 0: mmio [c0500000, c09fffff]
node 0 link 0: mmio [d0000000, dfffffff]
node 0 link 2: mmio [fec00000, fec0ffff]
node 0 link 0: mmio [a0000, bffff]
node 0 link 0: mmio [e0000000, efffffff]
TOM2: 0000000140000000 aka 5120M
bus: [00, 7f] on node 0 link 2
bus: 00 index 0 [io 0x0000-0x2fff]
bus: 00 index 1 [io 0x5000-0x8fff]
bus: 00 index 2 [io 0xa000-0xffff]
bus: 00 index 3 [mem 0xc0000000-0xc04fffff]
bus: 00 index 4 [mem 0xf0000000-0xffffffff]
bus: 00 index 5 [mem 0xc0a00000-0xcfffffff]
bus: 00 index 6 [mem 0x140000000-0xfcffffffff]
bus: [80, ff] on node 0 link 0
bus: 80 index 0 [io 0x3000-0x4fff]
bus: 80 index 1 [io 0x9000-0x9fff]
bus: 80 index 2 [mem 0xc0500000-0xc09fffff]
bus: 80 index 3 [mem 0xd0000000-0xefffffff]
bus: 80 index 4 [mem 0x000a0000-0x000bffff]
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 80-ff] at [mem 0xe8000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe8000000-0xefffffff] reserved in E820
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7f])
pci_root PNP0A03:00: host bridge window [mem 0x000d8000-0x000dbfff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000dc000-0x000dffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000e0000-0x000e3fff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000e4000-0x000e7fff] (ignored)
pci_root PNP0A03:00: host bridge window [io 0x0000-0x03af] (ignored)
pci_root PNP0A03:00: host bridge window [io 0x03bc-0x03bf] (ignored)
pci_root PNP0A03:00: host bridge window [io 0x03e0-0x0cf7] (ignored)
pci_root PNP0A03:00: host bridge window [io 0x0d00-0x0fff] (ignored)
pci_root PNP0A03:00: host bridge window [io 0x1000-0x2fff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0xc0000000-0xc04fffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0xfec00000-0xfec0ffff] (ignored)
pci 0000:00:06.0: [1022:7460] type 1 class 0x000604
pci 0000:00:07.0: [1022:7468] type 0 class 0x000601
pci 0000:00:07.1: [1022:7469] type 0 class 0x000101
pci 0000:00:07.1: reg 20: [io 0x1460-0x146f]
pci 0000:00:07.2: [1022:746a] type 0 class 0x000c05
pci 0000:00:07.2: reg 10: [io 0x1440-0x145f]
pci 0000:00:07.3: [1022:746b] type 0 class 0x000680
pci 0000:00:07.5: [1022:746d] type 0 class 0x000401
pci 0000:00:07.5: reg 10: [io 0x1000-0x10ff]
pci 0000:00:07.5: reg 14: [io 0x1400-0x143f]
pci 0000:00:0a.0: [1022:7450] type 1 class 0x000604
pci 0000:00:0a.1: [1022:7451] type 0 class 0x000800
pci 0000:00:0b.0: [1022:7450] type 1 class 0x000604
pci 0000:00:0b.1: [1022:7451] type 0 class 0x000800
pci 0000:00:18.0: [1022:1100] type 0 class 0x000600
pci 0000:00:18.1: [1022:1101] type 0 class 0x000600
pci 0000:00:18.2: [1022:1102] type 0 class 0x000600
pci 0000:00:18.3: [1022:1103] type 0 class 0x000600
PCI: peer root bus 00 res updated from pci conf
pci 0000:01:02.0: [1095:3512] type 0 class 0x000101
pci 0000:01:02.0: reg 10: [io 0x2020-0x2027]
pci 0000:01:02.0: reg 14: [io 0x2014-0x2017]
pci 0000:01:02.0: reg 18: [io 0x2018-0x201f]
pci 0000:01:02.0: reg 1c: [io 0x2010-0x2013]
pci 0000:01:02.0: reg 20: [io 0x2000-0x200f]
pci 0000:01:02.0: reg 24: [mem 0xc0106000-0xc01061ff]
pci 0000:01:02.0: reg 30: [mem 0x00000000-0x0007ffff pref]
pci 0000:01:02.0: supports D1 D2
pci 0000:01:03.0: [1033:0035] type 0 class 0x000c03
pci 0000:01:03.0: reg 10: [mem 0xc0107000-0xc0107fff]
pci 0000:01:03.0: supports D1 D2
pci 0000:01:03.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:01:03.0: PME# disabled
pci 0000:01:03.1: [1033:0035] type 0 class 0x000c03
pci 0000:01:03.1: reg 10: [mem 0xc0108000-0xc0108fff]
pci 0000:01:03.1: supports D1 D2
pci 0000:01:03.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:01:03.1: PME# disabled
pci 0000:01:03.2: [1033:00e0] type 0 class 0x000c03
pci 0000:01:03.2: reg 10: [mem 0xc0106400-0xc01064ff]
pci 0000:01:03.2: supports D1 D2
pci 0000:01:03.2: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:01:03.2: PME# disabled
pci 0000:01:04.0: [104c:8023] type 0 class 0x000c00
pci 0000:01:04.0: reg 10: [mem 0xc0106800-0xc0106fff]
pci 0000:01:04.0: reg 14: [mem 0xc0100000-0xc0103fff]
pci 0000:01:04.0: supports D1 D2
pci 0000:01:04.0: PME# supported from D0 D1 D2 D3hot
pci 0000:01:04.0: PME# disabled
pci 0000:00:06.0: PCI bridge to [bus 01-01]
pci 0000:00:06.0: bridge window [io 0x2000-0x2fff]
pci 0000:00:06.0: bridge window [mem 0xc0100000-0xc01fffff]
pci 0000:00:0a.0: PCI bridge to [bus 02-02]
pci 0000:03:02.0: [14e4:16a7] type 0 class 0x000200
pci 0000:03:02.0: reg 10: [mem 0xc0200000-0xc020ffff 64bit]
pci 0000:03:02.0: PME# supported from D3hot D3cold
pci 0000:03:02.0: PME# disabled
pci 0000:00:0b.0: PCI bridge to [bus 03-03]
pci 0000:00:0b.0: bridge window [mem 0xc0200000-0xc02fffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.TP2P._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.G0PA._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.G0PB._PRT]
pci0000:00: Requesting ACPI _OSC control (0x1d)
pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
ACPI _OSC control for PCIe not granted, disabling ASPM
ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-ff])
pci_root PNP0A03:01: host bridge window [io 0x03b0-0x03bb] (ignored)
pci_root PNP0A03:01: host bridge window [io 0x03c0-0x03df] (ignored)
pci_root PNP0A03:01: host bridge window [io 0x3000-0x4fff] (ignored)
pci_root PNP0A03:01: host bridge window [0x0-0x0] (ignored, not CPU addressable)
pci_root PNP0A03:01: host bridge window [mem 0xc0500000-0xc09fffff] (ignored)
pci_root PNP0A03:01: host bridge window [mem 0xd0000000-0xdfffffff] (ignored)
pci_root PNP0A03:01: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
pci_root PNP0A03:01: host bridge window [mem 0xe0000000-0xefffffff] (ignored)
pci 0000:80:00.0: [10de:005e] type 0 class 0x000580
pci 0000:80:01.0: [10de:00d3] type 0 class 0x000580
pci 0000:80:01.0: reg 14: [mem 0xc0500000-0xc0500fff]
pci 0000:80:0d.0: [10de:005d] type 1 class 0x000604
pci 0000:80:0d.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:80:0d.0: PME# disabled
pci 0000:80:0e.0: [10de:005d] type 1 class 0x000604
pci 0000:80:0e.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:80:0e.0: PME# disabled
PCI: peer root bus 80 res updated from pci conf
pci 0000:81:00.0: [1033:0125] type 1 class 0x000604
pci 0000:81:00.0: supports D1
pci 0000:81:00.0: PME# supported from D0 D1 D3hot D3cold
pci 0000:81:00.0: PME# disabled
pci 0000:81:00.1: [1033:0125] type 1 class 0x000604
pci 0000:81:00.1: supports D1
pci 0000:81:00.1: PME# supported from D0 D1 D3hot D3cold
pci 0000:81:00.1: PME# disabled
pci 0000:80:0d.0: PCI bridge to [bus 81-83]
pci 0000:80:0d.0: bridge window [io 0x3000-0x3fff]
pci 0000:80:0d.0: bridge window [mem 0xc0600000-0xc06fffff]
pci 0000:81:00.0: PCI bridge to [bus 82-82]
pci 0000:83:04.0: [9005:801d] type 0 class 0x000100
pci 0000:83:04.0: reg 10: [io 0x3400-0x34ff]
pci 0000:83:04.0: reg 14: [mem 0xc0600000-0xc0601fff 64bit]
pci 0000:83:04.0: reg 1c: [io 0x3000-0x30ff]
pci 0000:83:04.0: reg 30: [mem 0x00000000-0x0007ffff pref]
pci 0000:83:04.1: [9005:801d] type 0 class 0x000100
pci 0000:83:04.1: reg 10: [io 0x3c00-0x3cff]
pci 0000:83:04.1: reg 14: [mem 0xc0602000-0xc0603fff 64bit]
pci 0000:83:04.1: reg 1c: [io 0x3800-0x38ff]
pci 0000:83:04.1: reg 30: [mem 0x00000000-0x0007ffff pref]
pci 0000:81:00.1: PCI bridge to [bus 83-83]
pci 0000:81:00.1: bridge window [io 0x3000-0x3fff]
pci 0000:81:00.1: bridge window [mem 0xc0600000-0xc06fffff]
pci 0000:84:00.0: [1002:71d2] type 0 class 0x000300
pci 0000:84:00.0: reg 10: [mem 0xd0000000-0xdfffffff 64bit pref]
pci 0000:84:00.0: reg 18: [mem 0xc0700000-0xc070ffff 64bit]
pci 0000:84:00.0: reg 20: [io 0x4000-0x40ff]
pci 0000:84:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
pci 0000:84:00.0: supports D1 D2
pci 0000:84:00.1: [1002:71f2] type 0 class 0x000380
pci 0000:84:00.1: reg 10: [mem 0xc0710000-0xc071ffff 64bit]
pci 0000:84:00.1: supports D1 D2
pci 0000:80:0e.0: PCI bridge to [bus 84-84]
pci 0000:80:0e.0: bridge window [io 0x4000-0x4fff]
pci 0000:80:0e.0: bridge window [mem 0xc0700000-0xc07fffff]
pci 0000:80:0e.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
pci_bus 0000:80: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.XVR0.PCXA._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.XVR0.PCXB._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI1.XVR1._PRT]
pci0000:80: Requesting ACPI _OSC control (0x1d)
pci0000:80: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
ACPI _OSC control for PCIe not granted, disabling ASPM
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 *5 10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 5 10 11) *9
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 5 *10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 5 10 *11)
ACPI: PCI Interrupt Link [LNK1] (IRQs 48 49 50 51) *0, disabled.
ACPI: PCI Interrupt Link [LNK2] (IRQs 48 49 50 51) *0, disabled.
ACPI: PCI Interrupt Link [LNK3] (IRQs 48 49 50 51) *0, disabled.
ACPI: PCI Interrupt Link [LNK4] (IRQs 48 49 50 51) *0, disabled.
ACPI: PCI Interrupt Link [LNK5] (IRQs 48 49 50 51) *0, disabled.
vgaarb: device added: PCI:0000:84:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:84:00.0
SCSI subsystem initialized
libata version 3.00 loaded.
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
Expanded resource reserved due to conflict with PCI Bus #00
reserve RAM buffer: 000000000009d400 - 000000000009ffff
reserve RAM buffer: 00000000bff60000 - 00000000bfffffff
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:00: [bus 00-7f]
pnp 00:00: [mem 0x000c8000-0x000cbfff window]
pnp 00:00: [mem 0x000cc000-0x000cffff window]
pnp 00:00: [mem 0x000d0000-0x000d3fff window]
pnp 00:00: [mem 0x000d4000-0x000d7fff window]
pnp 00:00: [mem 0x000d8000-0x000dbfff window]
pnp 00:00: [mem 0x000dc000-0x000dffff window]
pnp 00:00: [mem 0x000e0000-0x000e3fff window]
pnp 00:00: [mem 0x000e4000-0x000e7fff window]
pnp 00:00: [io 0x0cf8-0x0cff]
pnp 00:00: [io 0x0000-0x03af window]
pnp 00:00: [io 0x0000 window]
pnp 00:00: [io 0x03bc-0x03bf window]
pnp 00:00: [io 0x0000 window]
pnp 00:00: [io 0x03e0-0x0cf7 window]
pnp 00:00: [io 0x0d00-0x0fff window]
pnp 00:00: [io 0x1000-0x2fff window]
pnp 00:00: [io 0x0000 window]
pnp 00:00: [io 0x0000 window]
pnp 00:00: [io 0x0000 window]
pnp 00:00: [mem 0xc0000000-0xc04fffff window]
pnp 00:00: [mem 0xffffffff-0x00000000 window]
pnp 00:00: [mem 0xffffffff-0x00000000 window]
pnp 00:00: [mem 0xffffffff-0x00000000 window]
pnp 00:00: [mem 0xfec00000-0xfec0ffff window]
pnp 00:00: [mem 0xffffffff-0x00000000 window]
pnp 00:00: [mem 0xffffffff-0x00000000 window]
pnp 00:00: [mem 0xffffffff-0x00000000 window]
pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
pnp 00:01: [io 0x0000-0x000f]
pnp 00:01: [io 0x0080-0x008f]
pnp 00:01: [io 0x00c0-0x00df]
pnp 00:01: [dma 4]
pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
pnp 00:02: [io 0x0070-0x0075]
pnp 00:02: [irq 8]
pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:03: [io 0x0061]
pnp 00:03: Plug and Play ACPI device, IDs PNP0800 (active)
pnp 00:04: [io 0x00f0-0x00ff]
pnp 00:04: [irq 13]
pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active)
pnp 00:05: [io 0x04d0-0x04d1]
pnp 00:05: [io 0x1100-0x117f]
pnp 00:05: [io 0x1180-0x11ff]
pnp 00:05: [io 0x0010-0x001f]
pnp 00:05: [io 0x0022-0x003f]
pnp 00:05: [io 0x0044-0x005f]
pnp 00:05: [io 0x0062-0x0063]
pnp 00:05: [io 0x0065-0x006f]
pnp 00:05: [io 0x0076-0x007f]
pnp 00:05: [io 0x0090-0x009f]
pnp 00:05: [io 0x00a2-0x00bf]
pnp 00:05: [io 0x00e0-0x00ef]
pnp 00:05: [io 0x0100-0x011f]
pnp 00:05: [mem 0xfff80000-0xffffffff]
pnp 00:05: [mem 0xff780000-0xff7fffff]
pnp 00:05: [mem 0xfee00000-0xfeefffff]
pnp 00:05: [mem 0xc0000000-0xc0000fff]
pnp 00:05: [mem 0xc0001000-0xc0001fff]
system 00:05: [io 0x04d0-0x04d1] has been reserved
system 00:05: [io 0x1100-0x117f] has been reserved
system 00:05: [io 0x1180-0x11ff] has been reserved
system 00:05: [io 0x0100-0x011f] has been reserved
system 00:05: [mem 0xfff80000-0xffffffff] has been reserved
system 00:05: [mem 0xff780000-0xff7fffff] has been reserved
system 00:05: [mem 0xfee00000-0xfeefffff] could not be reserved
system 00:05: [mem 0xc0000000-0xc0000fff] could not be reserved
system 00:05: [mem 0xc0001000-0xc0001fff] could not be reserved
system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:06: [io 0x03f0-0x03f5]
pnp 00:06: [io 0x03f7]
pnp 00:06: [irq 6]
pnp 00:06: [dma 2]
pnp 00:06: Plug and Play ACPI device, IDs PNP0700 (active)
pnp 00:07: [io 0x02f8-0x02ff]
pnp 00:07: [irq 3]
pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:08: [io 0x03f8-0x03ff]
pnp 00:08: [irq 4]
pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:09: [io 0x0378-0x037f]
pnp 00:09: [irq 7]
pnp 00:09: Plug and Play ACPI device, IDs PNP0400 (active)
pnp 00:0a: [irq 12]
pnp 00:0a: Plug and Play ACPI device, IDs PNP0f13 (active)
pnp 00:0b: [io 0x0060]
pnp 00:0b: [io 0x0064]
pnp 00:0b: [irq 1]
pnp 00:0b: Plug and Play ACPI device, IDs PNP0303 (active)
pnp 00:0c: [bus 80-ff]
pnp 00:0c: [io 0x03b0-0x03bb window]
pnp 00:0c: [io 0x03c0-0x03df window]
pnp 00:0c: [io 0x9000-0x9fff window]
pnp 00:0c: [io 0x3000-0x4fff window]
pnp 00:0c: [io 0x0000 window]
pnp 00:0c: [io 0x0000 window]
pnp 00:0c: [mem 0xffffffff-0x00000000 window]
pnp 00:0c: [mem 0xffffffff-0x00000000 window]
pnp 00:0c: [mem 0xc0500000-0xc09fffff window]
pnp 00:0c: [mem 0xd0000000-0xdfffffff window]
pnp 00:0c: [mem 0xffffffff-0x00000000 window]
pnp 00:0c: [mem 0x000a0000-0x000bffff window]
pnp 00:0c: [mem 0xffffffff-0x00000000 window]
pnp 00:0c: [mem 0xe0000000-0xefffffff window]
pnp 00:0c: Plug and Play ACPI device, IDs PNP0a03 (active)
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
Switching to clocksource acpi_pm
PCI: max bus depth: 2 pci_try_num: 3
pci 0000:00:06.0: BAR 9: assigned [mem 0xc0300000-0xc03fffff pref]
pci 0000:01:02.0: BAR 6: assigned [mem 0xc0300000-0xc037ffff pref]
pci 0000:00:06.0: PCI bridge to [bus 01-01]
pci 0000:00:06.0: bridge window [io 0x2000-0x2fff]
pci 0000:00:06.0: bridge window [mem 0xc0100000-0xc01fffff]
pci 0000:00:06.0: bridge window [mem 0xc0300000-0xc03fffff pref]
pci 0000:00:0a.0: PCI bridge to [bus 02-02]
pci 0000:00:0b.0: PCI bridge to [bus 03-03]
pci 0000:00:0b.0: bridge window [mem 0xc0200000-0xc02fffff]
pci 0000:80:0d.0: BAR 9: assigned [mem 0xc0800000-0xc08fffff pref]
pci 0000:81:00.1: BAR 9: assigned [mem 0xc0800000-0xc08fffff pref]
pci 0000:81:00.0: PCI bridge to [bus 82-82]
pci 0000:83:04.0: BAR 6: assigned [mem 0xc0800000-0xc087ffff pref]
pci 0000:83:04.1: BAR 6: assigned [mem 0xc0880000-0xc08fffff pref]
pci 0000:81:00.1: PCI bridge to [bus 83-83]
pci 0000:81:00.1: bridge window [io 0x3000-0x3fff]
pci 0000:81:00.1: bridge window [mem 0xc0600000-0xc06fffff]
pci 0000:81:00.1: bridge window [mem 0xc0800000-0xc08fffff pref]
pci 0000:80:0d.0: PCI bridge to [bus 81-83]
pci 0000:80:0d.0: bridge window [io 0x3000-0x3fff]
pci 0000:80:0d.0: bridge window [mem 0xc0600000-0xc06fffff]
pci 0000:80:0d.0: bridge window [mem 0xc0800000-0xc08fffff pref]
pci 0000:84:00.0: BAR 6: assigned [mem 0xc0720000-0xc073ffff pref]
pci 0000:80:0e.0: PCI bridge to [bus 84-84]
pci 0000:80:0e.0: bridge window [io 0x4000-0x4fff]
pci 0000:80:0e.0: bridge window [mem 0xc0700000-0xc07fffff]
pci 0000:80:0e.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
pci 0000:80:0d.0: setting latency timer to 64
pci 0000:81:00.0: power state changed by ACPI to D0
pci 0000:81:00.0: power state changed by ACPI to D0
pci 0000:81:00.0: setting latency timer to 64
pci 0000:81:00.1: power state changed by ACPI to D0
pci 0000:81:00.1: power state changed by ACPI to D0
pci 0000:81:00.1: setting latency timer to 64
pci 0000:80:0e.0: setting latency timer to 64
pci_bus 0000:00: resource 4 [io 0x0000-0x2fff]
pci_bus 0000:00: resource 5 [io 0x5000-0x8fff]
pci_bus 0000:00: resource 6 [io 0xa000-0xffff]
pci_bus 0000:00: resource 7 [mem 0xc0000000-0xc04fffff]
pci_bus 0000:00: resource 8 [mem 0xf0000000-0xffffffff]
pci_bus 0000:00: resource 9 [mem 0xc0a00000-0xcfffffff]
pci_bus 0000:00: resource 10 [mem 0x140000000-0xfcffffffff]
pci_bus 0000:01: resource 0 [io 0x2000-0x2fff]
pci_bus 0000:01: resource 1 [mem 0xc0100000-0xc01fffff]
pci_bus 0000:01: resource 2 [mem 0xc0300000-0xc03fffff pref]
pci_bus 0000:03: resource 1 [mem 0xc0200000-0xc02fffff]
pci_bus 0000:80: resource 4 [io 0x3000-0x4fff]
pci_bus 0000:80: resource 5 [io 0x9000-0x9fff]
pci_bus 0000:80: resource 6 [mem 0xc0500000-0xc09fffff]
pci_bus 0000:80: resource 7 [mem 0xd0000000-0xefffffff]
pci_bus 0000:80: resource 8 [mem 0x000a0000-0x000bffff]
pci_bus 0000:81: resource 0 [io 0x3000-0x3fff]
pci_bus 0000:81: resource 1 [mem 0xc0600000-0xc06fffff]
pci_bus 0000:81: resource 2 [mem 0xc0800000-0xc08fffff pref]
pci_bus 0000:83: resource 0 [io 0x3000-0x3fff]
pci_bus 0000:83: resource 1 [mem 0xc0600000-0xc06fffff]
pci_bus 0000:83: resource 2 [mem 0xc0800000-0xc08fffff pref]
pci_bus 0000:84: resource 0 [io 0x4000-0x4fff]
pci_bus 0000:84: resource 1 [mem 0xc0700000-0xc07fffff]
pci_bus 0000:84: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
UDP hash table entries: 2048 (order: 4, 65536 bytes)
UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
NET: Registered protocol family 1
pci 0000:00:07.3: boot interrupts on device [1022:746b] already disabled
pci 0000:00:0a.0: MSI quirk detected; subordinate MSI disabled
pci 0000:00:0a.0: AMD8131 rev 12 detected; disabling PCI-X MMRBC
pci 0000:00:0b.0: MSI quirk detected; subordinate MSI disabled
pci 0000:00:0b.0: AMD8131 rev 12 detected; disabling PCI-X MMRBC
pci 0000:01:03.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
pci 0000:01:03.0: PCI INT A disabled
pci 0000:01:03.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
pci 0000:01:03.1: PCI INT B disabled
pci 0000:01:03.2: PCI INT C -> GSI 16 (level, low) -> IRQ 16
pci 0000:01:03.2: PCI INT C disabled
pci 0000:80:00.0: nv_msi_ht_cap_quirk didn't locate host bridge
pci 0000:80:0d.0: nv_msi_ht_cap_quirk didn't locate host bridge
pci 0000:80:0d.0: Found disabled HT MSI Mapping
pci 0000:80:00.0: Found enabled HT MSI Mapping
pci 0000:80:0d.0: Linking AER extended capability
pci 0000:80:0e.0: nv_msi_ht_cap_quirk didn't locate host bridge
pci 0000:80:0e.0: Found disabled HT MSI Mapping
pci 0000:80:00.0: Found enabled HT MSI Mapping
pci 0000:80:0e.0: Linking AER extended capability
pci 0000:84:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 3636k freed
PCI-DMA: Disabling AGP.
PCI-DMA: aperture base @ b4000000 size 65536 KB
PCI-DMA: using GART IOMMU.
PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
audit: initializing netlink socket (disabled)
type=2000 audit(1335259754.029:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
OCFS2 1.5.0
ocfs2: Registered cluster interface o2cb
OCFS2 DLMFS 1.5.0
OCFS2 User DLM kernel interface loaded
OCFS2 Node Manager 1.5.0
OCFS2 DLM 1.5.0
GFS2 installed
msgmni has been set to 7922
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:80:0d.0: setting latency timer to 64
pcieport 0000:80:0d.0: irq 72 for MSI/MSI-X
pcieport 0000:80:0e.0: setting latency timer to 64
pcieport 0000:80:0e.0: irq 73 for MSI/MSI-X
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:07: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
AMD768 RNG detected
Linux agpgart interface v0.103
brd: module loaded
loop: module loaded
i8042: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mousedev: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
registered taskstats version 1
Freeing unused kernel memory: 472k freed
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
pata_amd 0000:00:07.1: version 0.4.1
scsi0 : pata_amd
scsi1 : pata_amd
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x1460 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1468 irq 15
ata2.00: ATAPI: HL-DT-ST RW/DVD GCC-4482B, 1.01, max UDMA/33
ata2.00: configured for UDMA/33
scsi 1:0:0:0: CD-ROM HL-DT-ST RW/DVD GCC-4482B 1.01 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sata_sil 0000:01:02.0: version 2.4
sata_sil 0000:01:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
scsi2 : sata_sil
scsi3 : sata_sil
ata3: SATA max UDMA/100 mmio m512@0xc0106000 tf 0xc0106080 irq 17
ata4: SATA max UDMA/100 mmio m512@0xc0106000 tf 0xc01060c0 irq 17
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata3.00: ATA-7: Maxtor 6V250F0, VA111630, max UDMA/133
ata3.00: 490234752 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/100
scsi 2:0:0:0: Direct-Access ATA Maxtor 6V250F0 VA11 PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 490234752 512-byte logical blocks: (251 GB/233 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 2:0:0:0: [sda] Attached SCSI disk
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata4.00: ATA-7: WDC WD800JD-23LSA0, 07.01D07, max UDMA/133
ata4.00: 156312576 sectors, multi 16: LBA48
ata4.00: configured for UDMA/100
scsi 3:0:0:0: Direct-Access ATA WDC WD800JD-23LS 07.0 PQ: 0 ANSI: 5
sd 3:0:0:0: [sdb] 156312576 512-byte logical blocks: (80.0 GB/74.5 GiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1 sdb2 sdb3
sd 3:0:0:0: [sdb] Attached SCSI disk
sr 1:0:0:0: Attached scsi generic sg0 type 5
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 3:0:0:0: Attached scsi generic sg2 type 0
aic79xx 0000:83:04.0: PCI INT A -> GSI 37 (level, low) -> IRQ 37
scsi4 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
<Adaptec AIC7902 Ultra320 SCSI adapter>
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100MHz, 512 SCBs
aic79xx 0000:83:04.1: PCI INT B -> GSI 36 (level, low) -> IRQ 36
scsi5 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
<Adaptec AIC7902 Ultra320 SCSI adapter>
aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100MHz, 512 SCBs
scsi: <fdomain> Detection failed (no card)
GDT-HA: Storage RAID Controller Driver. Version: 3.05
imm: Version 2.05 (for Linux 2.4.0)
Fusion MPT base driver 3.04.20
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.20
Fusion MPT FC Host driver 3.04.20
Fusion MPT SAS Host driver 3.04.20
3ware Storage Controller device driver for Linux v1.26.02.003.
3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
Compaq SMART2 Driver (v 2.6.0)
HP CISS Driver (v 3.6.26)
Adaptec aacraid driver 1.1-7[28000]-ms
megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
megasas: 00.00.06.12-rc1 Wed. Oct. 5 17:00:00 PDT 2011
qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.03.07.12-k.
Emulex LightPulse Fibre Channel SCSI driver 8.3.27
Copyright(c) 2004-2009 Emulex. All rights reserved.
aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:01:03.2: PCI INT C -> GSI 16 (level, low) -> IRQ 16
ehci_hcd 0000:01:03.2: EHCI Host Controller
ehci_hcd 0000:01:03.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:01:03.2: irq 16, io mem 0xc0106400
ehci_hcd 0000:01:03.2: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 3.2.12-gentoo ehci_hcd
usb usb1: SerialNumber: 0000:01:03.2
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 5 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
uhci_hcd: USB Universal Host Controller Interface driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd 0000:01:03.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:01:03.0: OHCI Host Controller
ohci_hcd 0000:01:03.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:01:03.0: irq 18, io mem 0xc0107000
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OHCI Host Controller
usb usb2: Manufacturer: Linux 3.2.12-gentoo ohci_hcd
usb usb2: SerialNumber: 0000:01:03.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ohci_hcd 0000:01:03.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ohci_hcd 0000:01:03.1: OHCI Host Controller
ohci_hcd 0000:01:03.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:01:03.1: irq 19, io mem 0xc0108000
hub 1-0:1.0: unable to enumerate USB device on port 2
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: OHCI Host Controller
usb usb3: Manufacturer: Linux 3.2.12-gentoo ohci_hcd
usb usb3: SerialNumber: 0000:01:03.1
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
sl811: driver sl811-hcd, 19 May 2005
usb 1-4: new high-speed USB device number 3 using ehci_hcd
usb 1-4: New USB device found, idVendor=0930, idProduct=6545
usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4: Product: USB Flash Memory
usb 1-4: SerialNumber: 001D0F0C73C85B88160A3E60
scsi6 : usb-storage 1-4:1.0
usb 3-1: new full-speed USB device number 2 using ohci_hcd
usb 3-1: New USB device found, idVendor=0451, idProduct=2046
usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 3-1:1.0: USB hub found
hub 3-1:1.0: 4 ports detected
scsi: waiting for bus probes to complete ...
scsi 6:0:0:0: Direct-Access USB Flash Memory PMAP PQ: 0 ANSI: 0 CCS
sd 6:0:0:0: Attached scsi generic sg3 type 0
sd 6:0:0:0: [sdc] 3966976 512-byte logical blocks: (2.03 GB/1.89 GiB)
sd 6:0:0:0: [sdc] Write Protect is off
sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 6:0:0:0: [sdc] No Caching mode page present
sd 6:0:0:0: [sdc] Assuming drive cache: write through
sd 6:0:0:0: [sdc] No Caching mode page present
sd 6:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
sd 6:0:0:0: [sdc] No Caching mode page present
sd 6:0:0:0: [sdc] Assuming drive cache: write through
sd 6:0:0:0: [sdc] Attached SCSI removable disk
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int64x1 1976 MB/s
raid6: int64x2 2290 MB/s
raid6: int64x4 1687 MB/s
raid6: int64x8 1267 MB/s
raid6: sse2x1 2642 MB/s
raid6: sse2x2 3462 MB/s
raid6: sse2x4 3917 MB/s
raid6: using algorithm sse2x4 (3917 MB/s)
async_tx: api initialized (async)
xor: automatically using best checksumming function: generic_sse
generic_sse: 7012.400 MB/sec
xor: using function: generic_sse (7012.400 MB/sec)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
md: raid10 personality registered for level 10
JFS: nTxBlock = 8192, nTxLock = 65536
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
fuse init (API version 7.17)
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
tg3.c:v3.121 (November 2, 2011)
tg3 0000:03:02.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
tg3 0000:03:02.0: eth0: Tigon3 [partno(BCM95703A30) rev 1002] (PCIX:100MHz:64-bit) MAC address 00:0d:60:53:3c:0d
tg3 0000:03:02.0: eth0: attached PHY is 5703 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
tg3 0000:03:02.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
tg3 0000:03:02.0: eth0: dma_rwctrl[769c4000] dma_mask[64-bit]
Loading iSCSI transport class v2.0-870.
mount: sending ioctl 5310 to a partition!
mount: sending ioctl 5310 to a partition!
mount: sending ioctl 5310 to a partition!
mount: sending ioctl 5310 to a partition!
UDF-fs: warning (device sdb3): udf_fill_super: No partition found (1)
(mount,14830,1):ocfs2_fill_super:1040 ERROR: superblock probe failed!
(mount,14830,1):ocfs2_fill_super:1234 ERROR: status = -22
GFS2: gfs2 mount does not exist
|
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Tue Apr 24, 2012 7:47 pm Post subject: |
|
|
aggieben,
It looks like your system is trying to mount root before the /dev entries are created.
Back in the ash shell, do That should show a file that ends something like
| Code: | #root filesystem
mount -r /dev/mapper/host-root /newroot || rescue_shell
#unmount pseudo FS
umount /sys
umount /proc
#root switch
exec /bin/busybox switch_root /newroot /sbin/init ${CMDLINE} |
Type the
lines at the end of your cat output into the shell, which is what the init script is supposed to do for you.
You may have more umount commands than my example. Just copy your output from mounting root on down.
Skip any || rescue_shell parts to commands. You are already in the rescue shell.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Last edited by NeddySeagoon on Tue Apr 24, 2012 7:48 pm; edited 1 time in total |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Tue Apr 24, 2012 7:48 pm Post subject: |
|
|
Well....poop.
I found the documentation for the rootfstype kernel parameter, and I set it to jfs. That got rid of the mount errors/warnings shown in my paste of the dmesg, but the boot process still bombed with the exact same error as before, except now there aren't any errors in the dmesg that I can see.
Grrr. |
|
| Back to top |
|
|
aggieben
n00b
Joined: 11 Dec 2008
Posts: 13
|
| Posted: Tue May 01, 2012 2:43 am Post subject: root fails to mount at boot time [solved] |
|
|
Well, I'm ashamed to say I just gave up and re-built the system. I spent well more time debugging and going through forum posts than it normally does to built a Gentoo box from scratch, so I just decided to do that.
One interesting finding in the process, though, was that Grub seems to see the disks in a different order when it is Grub running on the machine vs grub running in user space in a running Linux. First, I used dd (as described http://davestechshop.net/blog/dave/how-to-uninstall-grub-from-my-hard-disk-drive) to clear the MBR on both disks. After going through the setup process and still in LiveCD and chrooted to /mnt/gentoo, I ran grub to install it, and it saw /dev/sda as (hd0) and /dev/sdb as (hd1), which is exactly what I expected. I did
| Code: | root (hd0,0)
setup (hd0)
quit
|
and reboot. My system silently failed to boot, however, and I couldn't figure out why. I looked in my bios settings to see which disk was set up as the master, and it seems that the bios couldn't determine that, so I booted back into the LiveCD and installed ran
| Code: | root (hd0,0)
setup (hd1)
quit |
to see what would happen. When the system rebooted, it booted into grub, but the splash screen failed to load (leaving it with console-fuzzy stripes), and it failed to boot my kernel because it couldn't find the file at (hd0,0)/boot/kernel-{blahblah}. I edited the root line in the grub console and used grub's tab completion to see that the disk numbering was reversed. I edited the root line to point to (hd1,0), and was able to get booted from there. Once booted, I edited /boot/grub/grub.conf and now the system functions properly.
I'm still not quite sure why the disks come up in different orders (not sure which one is reversed), but I have a working system. Thanks, neddy, for giving my problem(s) so much of your attention. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 29956
Location: 56N 3W
|
| Posted: Tue May 01, 2012 6:56 pm Post subject: |
|
|
aggieben,
Some BIOSes report the boot drive as (hd0) regardless of which drive it is.
With such a BIOS, if you have told it to boot off some ither drive than the first one, it will be (hd0) to grub.
This is a PITA, as you have discoverd.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
