You are not logged in.

#101 2011-01-12 22:30:51

sportscliche
Member
From: Albuquerque, NM
Registered: 2010-11-30
Posts: 43

Re: Latest udev causes kernel panics (something about libata)

I also experienced the intermittent kernel panic related to "ioread32_rep..." after the system upgrade on a Thinkpad 42.  The video driver is:

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]

Booting to the fallback image was a 100% reliable workaround, but I also installed the two binaries that are generated by olive's PKBUILD above.  After five successful re-boots and playing a DVD, it seems the patch has fixed the problem with udev 165-1.

Thanks from an Arch newbie.

EDIT: I just had another kernel panic on boot-up, after installing the two binaries provided by olive.  I must have done something wrong with the patch.  Do I understand correctly that both should be installed by pacman?

Last edited by sportscliche (2011-01-13 09:29:44)

Offline

#102 2011-01-12 22:52:45

Kilzool
Member
From: Ireland
Registered: 2010-08-04
Posts: 232

Re: Latest udev causes kernel panics (something about libata)

REF: UDev, Kernel Panics, Fix

I began having kernel panics upon boot up again.. and like everyone else,
using the "fallback" was fine.

I got tired of this, and waited patiently for someone to release, "in an Arch" way, a fix.
I used one (a PKGBUILD) one, posted on this forum by Olive.

Thank you Olive.  smile

Further comment: Though sometimes coding is difficult because of the mass array of hardware, among other things,
I am happy we have some good people here in the Arch community, whether that be user, package manager, or coder, etc.
Because, in the end, we all want to know the end result, and have it fixed.   tongue

Last edited by Kilzool (2011-01-12 22:56:55)

Offline

#103 2011-01-13 04:58:42

silent
Member
Registered: 2008-08-05
Posts: 57

Re: Latest udev causes kernel panics (something about libata)

I had kernel panic also with Fallback. Downgraded to udev-164-3

Offline

#104 2011-01-13 11:49:31

Zoli86
Member
Registered: 2011-01-13
Posts: 6

Re: Latest udev causes kernel panics (something about libata)

I've also been having the kind of kernel panics mentioned here after the update of udev. (tho not as frequently, I boot up about 4-5 times a day and only had 4 crashes in about a week)
This morning i had 2 crashes in a row (one without the line "EIP: [<c11a6ad8>] ioread16_rep+0x38/0x50"... line and one without it):
I cant find any entries in my log files with the timestamp when the crash occured.

My current config:
lshw:

Motherboard:
       product: 770-G45 (MS-7599)
       vendor: MSI
BIOS:  American Megatrends Inc.
       version: V10.2
       date: 01/22/2010

        *-storage
             description: SATA controller
             product: SB700/SB800 SATA Controller [IDE mode]
             vendor: ATI Technologies Inc
             physical id: 11
             bus info: pci@0000:00:11.0
             logical name: scsi0
             logical name: scsi1
             version: 00
             width: 32 bits
             clock: 66MHz
             capabilities: storage pm ahci_1.0 bus_master cap_list emulated
             configuration: driver=ahci latency=64
             resources: irq:22 ioport:d000(size=8) ioport:c000(size=4) ioport:b000(size=8) ioport:a000(size=4) ioport:9000(size=16) memory:f7fffc00-f7ffffff
           *-disk:0
                description: ATA Disk
                product: SAMSUNG HD080HJ
                physical id: 0
                bus info: scsi@0:0.0.0
                logical name: /dev/sda
                version: WT10
                serial: S08EJ1LA178893
                size: 74GiB (80GB)
                capabilities: partitioned partitioned:dos
                configuration: ansiversion=5 signature=c303c303
           *-disk:1
                description: ATA Disk
                product: ST3500320AS
                vendor: Seagate
                physical id: 1
                bus info: scsi@1:0.0.0
                logical name: /dev/sdb
                version: SD15
                serial: 9QM7QE84
                size: 465GiB (500GB)
                capabilities: partitioned partitioned:dos
                configuration: ansiversion=5 signature=75b25822

current versions of packages i use:
kernel26 2.6.36.3-1
gcc 4.5.2-4
gcc-libs 4.5.2-4
udev 165-1

mkinitcpio.conf:
MODULES=""
HOOKS="base udev autodetect pata scsi sata filesystems"

the first time:
1
2

the second:
1
2

Offline

#105 2011-01-13 12:23:24

csslayer
Member
Registered: 2009-03-05
Posts: 85

Re: Latest udev causes kernel panics (something about libata)

I just compile udev with patch on #98
http://csslayer-aur-repo.googlecode.com … pkg.tar.gz

and just pkgbuild for download (patch and pkgbuild in core).
http://csslayer-aur-repo.googlecode.com … src.tar.gz

didn't increase pkgrel because I dont want anybody to miss offical update though.

And sorry, I've not tested so much yet, just few reboot.

Offline

#106 2011-01-13 13:24:26

Mic92
Member
From: Germany
Registered: 2009-07-05
Posts: 21
Website

Re: Latest udev causes kernel panics (something about libata)

Painless wrote:

I've been using udev 165 patched with the ata-pass-through-memalign patch (as per Amnon82's post above) for a couple of days now, no problems yet.

Same for me here.

Offline

#107 2011-01-13 16:38:25

windexh8er
Member
Registered: 2008-05-04
Posts: 32

Re: Latest udev causes kernel panics (something about libata)

So what is the best way to bring a system back that keeps hanging on boot with this issue?  I just installed a new box, system upgraded and now I can't boot it.

Offline

#108 2011-01-13 17:11:03

beerad
Member
Registered: 2011-01-10
Posts: 14

Re: Latest udev causes kernel panics (something about libata)

I looked at the memalign patch a little more, and I don't think it's doing what the author intended. He changed an array to a pointer so he could allocate a page aligned array. Unfortunately, he didn't change the sizeof(array) calls which are used to set up the buffer.

Personally, I wouldn't use that patch.

Offline

#109 2011-01-13 17:27:46

curson
Member
From: London
Registered: 2010-12-03
Posts: 32
Website

Re: Latest udev causes kernel panics (something about libata)

Apparently, so far, solved the problem with a downgrade of udev from 165 to 164-3. Been rebooting plenty of times since I've done it, and it seems to be working for me up to now.

Offline

#110 2011-01-13 19:57:27

windexh8er
Member
Registered: 2008-05-04
Posts: 32

Re: Latest udev causes kernel panics (something about libata)

Just as an update - I couldn't get booted on a clean install after an -Syu (as of today).  I booted off the install CD and downgraded udev to 151-3 (only version I had access to on the CD).  Boots fine now.  Installed with -fdU since there were two packages that required the newer udev.

Offline

#111 2011-01-13 23:01:22

madek
Member
From: Santiago, Chile
Registered: 2009-09-08
Posts: 98
Website

Re: Latest udev causes kernel panics (something about libata)

whit olive pkgbuild works fine

Offline

#112 2011-01-14 08:08:22

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Latest udev causes kernel panics (something about libata)

I too got 2 kernel panics while booting today. But, restarting the computer for the third time with the normal image worked. So, i didn't even have to use the fallback. And yes, the stack trace said something about libata, so believe it was the same issue, as is being experienced by others in this thread.

Last edited by x33a (2011-01-14 08:10:14)

Offline

#113 2011-01-14 15:16:53

windexh8er
Member
Registered: 2008-05-04
Posts: 32

Re: Latest udev causes kernel panics (something about libata)

I'm not sure how this isn't more widespread.  I've seen this on all 4 workstations now.  Some seem to have lower exposure to the problem (i.e. 1 in 10 reboots) whereas other boxes (namely older hardware) are much harder to get to boot past the libata panic.  I said yesterday downgrading udev helped on a freshly loaded box but today when reloading it I ran into the same issue.

Offline

#114 2011-01-14 15:52:04

beerad
Member
Registered: 2011-01-10
Posts: 14

Re: Latest udev causes kernel panics (something about libata)

Did you do a mkinitcpio to put the downgraded version on the ramdisk? Try grepping your logs to see if 165 was still starting up. That's bitten me..

Keep in mind that this is not a udev bug. It's a kernel bug that udev165 tickles. Even after patching udev to eliminate the offending call so the system doesn't crash at boot I can still crash the machine any time I want to by running some test code (or standard utilities) a few times. It isn't necessarily a new bug or a regression either, it may have been around a while. It looks like you need an ATAPI device in your system to see it, and it may be just a subset of the ATAPI devices are affected. Intermittent crashes, hard to show real cause and effect, fun stuff to debug and fix.

Offline

#115 2011-01-14 16:01:02

windexh8er
Member
Registered: 2008-05-04
Posts: 32

Re: Latest udev causes kernel panics (something about libata)

I just realized that running the kernel with 'edd=off' seems to allow me to boot now.  Only tried it a few times but I was getting 90% boot failure prior to this and I haven't not been able to boot yet.  Might help with some?!?!?!

Offline

#116 2011-01-14 17:21:00

wizzrobe
Member
Registered: 2007-03-22
Posts: 6

Re: Latest udev causes kernel panics (something about libata)

I have been seeing the same issue with both my archlinux server and workstation boxes. I've been having about a 50% boot success rate since I upgraded to kernel26 2.6.36.3-1 in early January.

Adding 'edd=off' to the kernel boot command appears to have resolved the issue for me as well. Great find windexh8er! How did you think of that?

Offline

#117 2011-01-14 17:28:42

windexh8er
Member
Registered: 2008-05-04
Posts: 32

Re: Latest udev causes kernel panics (something about libata)

I had a box a few weeks ago that wouldn't boot from the CD unless edd=off.  That box is one of them that won't boot the majority of the time after doing an -Syu after a fresh install.  Figured it couldn't hurt to try...  Glad it works for you wizzrobe!  I was getting quite frustrated and am hoping this fixes the issue for all the boxes I'm seeing this on.

Offline

#118 2011-01-15 00:15:29

Malte
Member
Registered: 2007-12-12
Posts: 3

Re: Latest udev causes kernel panics (something about libata)

Had the same problem with a Macbook Pro 7,1. "Something about libata" totally discribes my recent problem after updating to udev-165-1. However, "edd=off" fixed it. Thanks windexh8er.

Offline

#119 2011-01-15 01:25:41

dedanna1029
Member
From: Cheyenne, WY, US
Registered: 2010-10-01
Posts: 98

Re: Latest udev causes kernel panics (something about libata)

windexh8er wrote:

I just realized that running the kernel with 'edd=off' seems to allow me to boot now.  Only tried it a few times but I was getting 90% boot failure prior to this and I haven't not been able to boot yet.  Might help with some?!?!?!

Nope, it doesn't work here, sorry. sad

I've been dealing with this for the last several days, since the last kernel update. I updated udev to 165 back on Dec. 16th, with no ill effects, until the kernel update the other day.

I agree with beerad that this is probably a kernel bug therefore.

I've decided not to use the patch, and to wait for an update that fixes the issue - was hoping it would be sooner than this though, as it seemed an easy fix. I have reported on Bug #22343 (the exact symptoms in the reporter's original post is what I'm getting as well), and will continue to as long as I have any input to give. I'm deliberately not using patches, etc., so that I can report symptoms, give info, whatever on the bug report. If I fix it, then that defeats the purpose on the bug, and so far I haven't found anything that really fixes it, other than to await a fix in the repos.

Fallback is working for me, and as long as it is, I see no reason to play with anything, but rather to help to resolve the bug.

Thanks.

Last edited by dedanna1029 (2011-01-15 01:47:12)

Offline

#120 2011-01-15 07:47:46

pdork3
Member
Registered: 2011-01-15
Posts: 1

Re: Latest udev causes kernel panics (something about libata)

i'm reading this thread for some days now. it seems that no one really knows whats the problem, yet.
on my machine i'm having the same issues as described. kernel panics at boot, sometimes 5 times in a row.
panics occur at different boot states. sometimes very early, sometimes later (when daemons loading).
i have a fresh installed arch with all updates. no patches, no nothing.
my system has pata hard disc and pata optical.
mounting cd/dvd also gives kernel panic sometimes. see picture!

http://img156.imagevenue.com/img.php?im … _504lo.jpg

i think its a pata problem. anyone with sata drives having problems?

Offline

#121 2011-01-15 08:56:12

azleifel
Member
Registered: 2007-10-28
Posts: 486

Re: Latest udev causes kernel panics (something about libata)

I've got all SATA drives.  The update to udev 165-1 was first and didn't cause me any problems.  After the update to kernel26 2.6.36.3-1 my PC started pausing during every boot with the following:

Jan 15 07:38:33 localhost kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 15 07:38:33 localhost kernel: ata3.00: failed command: IDENTIFY PACKET DEVICE
Jan 15 07:38:33 localhost kernel: ata3.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Jan 15 07:38:33 localhost kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jan 15 07:38:33 localhost kernel: ata3.00: status: { DRDY }
Jan 15 07:38:33 localhost kernel: ata3: hard resetting link
Jan 15 07:38:33 localhost kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jan 15 07:38:33 localhost kernel: ata3.00: configured for UDMA/100
Jan 15 07:38:33 localhost kernel: ata3: EH complete

(ata3 is the DVD drive).  The only other issue after the kernel update is that the processing udev uevents boot step takes about twice as long.  No kernel panics yet.

Edit: And rebuilding udev 165 with the panic.patch from the Arch bug report (https://bugs.archlinux.org/task/22343) makes the identify packet device error at boot go away.

Last edited by azleifel (2011-01-15 21:51:48)

Offline

#122 2011-01-15 09:59:51

silent
Member
Registered: 2008-08-05
Posts: 57

Re: Latest udev causes kernel panics (something about libata)

I just had a kernel panic at boot also with udev-164-3, but I realized that I have forgotten to rebuild kernel initcpio images after downgrading udev.  I have 1 SATA + 2 PATA HDD's + 1 SATA ODD.

Last edited by silent (2011-01-15 10:20:29)

Offline

#123 2011-01-15 10:18:35

Wilco
Member
Registered: 2008-11-09
Posts: 440

Re: Latest udev causes kernel panics (something about libata)

pdork3 wrote:

i'm reading this thread for some days now. it seems that no one really knows whats the problem, yet.
on my machine i'm having the same issues as described. kernel panics at boot, sometimes 5 times in a row.
panics occur at different boot states. sometimes very early, sometimes later (when daemons loading).
i have a fresh installed arch with all updates. no patches, no nothing.
my system has pata hard disc and pata optical.
mounting cd/dvd also gives kernel panic sometimes. see picture!

http://img156.imagevenue.com/img.php?im … _504lo.jpg

i think its a pata problem. anyone with sata drives having problems?

I have system lockups with a SATA only system. Don't know if that's the same problem because I don't get a kernel panic, but just a hard freeze; I can only hold the power button, no flashing leds and no logs.

Offline

#124 2011-01-15 10:32:40

fast_rizwaan
Member
Registered: 2010-04-01
Posts: 65

Re: Latest udev causes kernel panics (something about libata)

I also get 1 or 2 panik attacks before the system really boots  ;-)
sometime 2nd time or 3rd time arch boots.

I installed arch 2 days, ago, nothing custom, only the kde and openoffice with build-essentials.

uname -a
Linux myhost 2.6.36-ARCH #1 SMP PREEMPT Sat Jan 8 13:16:43 UTC 2011 i686 Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz GenuineIntel GNU/Linux

dmesg

Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.36-ARCH (tobias@T-POWA-LX) (gcc version 4.5.2 (GCC) ) #1 SMP PREEMPT Sat Jan 8 13:16:43 UTC 2011
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007f2a7000 (usable)
BIOS-e820: 000000007f2a7000 - 000000007f2ea000 (ACPI NVS)
BIOS-e820: 000000007f2ea000 - 000000007f3c1000 (reserved)
BIOS-e820: 000000007f3c1000 - 000000007f3d1000 (ACPI NVS)
BIOS-e820: 000000007f3d1000 - 000000007f44e000 (reserved)
BIOS-e820: 000000007f44e000 - 000000007f454000 (ACPI data)
BIOS-e820: 000000007f454000 - 000000007f455000 (ACPI NVS)
BIOS-e820: 000000007f455000 - 000000007f457000 (ACPI data)
BIOS-e820: 000000007f457000 - 000000007f459000 (ACPI NVS)
BIOS-e820: 000000007f459000 - 000000007f45a000 (reserved)
BIOS-e820: 000000007f45a000 - 000000007f45e000 (ACPI NVS)
BIOS-e820: 000000007f45e000 - 000000007f46d000 (reserved)
BIOS-e820: 000000007f46d000 - 000000007f600000 (usable)
BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
BIOS-e820: 00000000ffa00000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
DMI 2.4 present.
e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
last_pfn = 0x7f600 max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-E7FFF uncachable
  E8000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000 mask F80000000 write-back
  1 base 07F600000 mask FFFE00000 uncachable
  2 base 07F800000 mask FFF800000 uncachable
  3 disabled
  4 disabled
  5 disabled
  6 disabled
  7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
e820 update range: 0000000000002000 - 0000000000010000 (usable) ==> (reserved)
Scanning 1 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000001000 (reserved)
modified: 0000000000001000 - 0000000000002000 (usable)
modified: 0000000000002000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009fc00 (usable)
modified: 000000000009fc00 - 00000000000a0000 (reserved)
modified: 00000000000e0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 000000007f2a7000 (usable)
modified: 000000007f2a7000 - 000000007f2ea000 (ACPI NVS)
modified: 000000007f2ea000 - 000000007f3c1000 (reserved)
modified: 000000007f3c1000 - 000000007f3d1000 (ACPI NVS)
modified: 000000007f3d1000 - 000000007f44e000 (reserved)
modified: 000000007f44e000 - 000000007f454000 (ACPI data)
modified: 000000007f454000 - 000000007f455000 (ACPI NVS)
modified: 000000007f455000 - 000000007f457000 (ACPI data)
modified: 000000007f457000 - 000000007f459000 (ACPI NVS)
modified: 000000007f459000 - 000000007f45a000 (reserved)
modified: 000000007f45a000 - 000000007f45e000 (ACPI NVS)
modified: 000000007f45e000 - 000000007f46d000 (reserved)
modified: 000000007f46d000 - 000000007f600000 (usable)
modified: 00000000fed1c000 - 00000000fed20000 (reserved)
modified: 00000000ffa00000 - 00000000ffc00000 (reserved)
modified: 00000000ffe00000 - 0000000100000000 (reserved)
initial memory mapped : 0 - 01800000
found SMP MP-table at [c00fc600] fc600
init_memory_mapping: 0000000000000000-00000000377fe000
0000000000 - 0000400000 page 4k
0000400000 - 0037400000 page 2M
0037400000 - 00377fe000 page 4k
kernel direct mapping tables up to 377fe000 @ 15000-1a000
RAMDISK: 7f0dc000 - 7f297000
Allocated new RAMDISK: 00100000 - 002ba0b5
Move RAMDISK from 000000007f0dc000 - 000000007f2960b4 to 00100000 - 002ba0b4
ACPI: RSDP 000f03f0 00024 (v02  INTEL)
ACPI: XSDT 7f455f10 00044 (v01  INTEL   DG31PR 06222004 MSFT 00010013)
ACPI: FACP 7f453d90 000F4 (v04  INTEL   DG31PR 06222004 MSFT 00010013)
ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20100702/tbfadt-369)
ACPI Warning: 32/64X FACS address mismatch in FADT - 0x7F458F40/0x000000007F454F40, using 32 (20100702/tbfadt-486)
ACPI: DSDT 7f44e010 04BE9 (v01  INTEL   DG31PR 00000000 INTL 20051117)
ACPI: FACS 7f458f40 00040
ACPI: APIC 7f453f10 0006C (v02  INTEL   DG31PR 06222004 MSFT 00010013)
ACPI: HPET 7f45cd10 00038 (v01  INTEL ICH7HPET 06222004 AMI. 00000001)
ACPI: MCFG 7f45cc10 0003C (v01 INTEL  DG31PR   06222004 MSFT 00000097)
ACPI: Local APIC address 0xfee00000
1150MB HIGHMEM available.
887MB LOWMEM available.
  mapped low ram: 0 - 377fe000
  low ram: 0 - 377fe000
Zone PFN ranges:
  DMA      0x00000001 -> 0x00001000
  Normal   0x00001000 -> 0x000377fe
  HighMem  0x000377fe -> 0x0007f600
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
    0: 0x00000001 -> 0x00000002
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0007f2a7
    0: 0x0007f46d -> 0x0007f600
On node 0 totalpages: 521162
free_area_init_node: node 0, pgdat c142d600, node_mem_map c1598020
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 3952 pages, LIFO batch:0
  Normal zone: 1744 pages used for memmap
  Normal zone: 221486 pages, LIFO batch:31
  HighMem zone: 2301 pages used for memmap
  HighMem zone: 291647 pages, LIFO batch:31
Using APIC driver default
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
SMP: Allowing 4 CPUs, 2 hotplug CPUs
nr_irqs_gsi: 40
early_res array is doubled to 64 at [16000 - 167ff]
PM: Registered nosave memory: 0000000000002000 - 0000000000010000
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
Allocating PCI resources starting at 7f600000 (gap: 7f600000:7f71c000)
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 13 pages/cpu @c2800000 s31488 r0 d21760 u1048576
early_res array is doubled to 128 at [16800 - 177ff]
pcpu-alloc: s31488 r0 d21760 u1048576 alloc=1*4194304
pcpu-alloc: [0] 0 1 2 3
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 517085
Kernel command line: root=/dev/sda2 ro
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
allocated 10434540 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
Subtract (61 early reservations)
  #1 [0000001000 - 0000002000]   EX TRAMPOLINE
  #2 [0001000000 - 000158fe8c]   TEXT DATA BSS
  #3 [0001590000 - 00015960e8]             BRK
  #4 [00000fc610 - 0000100000]   BIOS reserved
  #5 [00000fc600 - 00000fc610]    MP-table mpf
  #6 [000009fc00 - 00000fc380]   BIOS reserved
  #7 [00000fc57c - 00000fc600]   BIOS reserved
  #8 [00000fc380 - 00000fc57c]    MP-table mpc
  #9 [0000010000 - 0000011000]      TRAMPOLINE
  #10 [0000011000 - 0000015000]     ACPI WAKEUP
  #11 [0000015000 - 0000016000]         PGTABLE
  #12 [0000100000 - 00002bb000]     NEW RAMDISK
  #13 [0001597000 - 0001598000]         BOOTMEM
  #14 [0001598000 - 0002588000]         BOOTMEM
  #15 [000158fec0 - 000158fec4]         BOOTMEM
  #16 [000158ff00 - 000158ffc0]         BOOTMEM
  #17 [0001596100 - 0001596154]         BOOTMEM
  #18 [0002588000 - 000258b000]         BOOTMEM
  #19 [0001596180 - 00015961ec]         BOOTMEM
  #20 [000258b000 - 0002591000]         BOOTMEM
  #21 [000158ffc0 - 000158ffe5]         BOOTMEM
  #22 [0001596200 - 0001596227]         BOOTMEM
  #23 [0001596240 - 00015964a8]         BOOTMEM
  #24 [00015964c0 - 0001596500]         BOOTMEM
  #25 [0001596500 - 0001596540]         BOOTMEM
  #26 [0001596540 - 0001596580]         BOOTMEM
  #27 [0001596580 - 00015965c0]         BOOTMEM
  #28 [00015965c0 - 0001596600]         BOOTMEM
  #29 [0001596600 - 0001596640]         BOOTMEM
  #30 [0001596640 - 0001596680]         BOOTMEM
  #31 [0001596680 - 00015966c0]         BOOTMEM
  #32 [00015966c0 - 0001596700]         BOOTMEM
  #33 [0001596700 - 0001596740]         BOOTMEM
  #34 [0001596740 - 0001596780]         BOOTMEM
  #35 [0001596780 - 00015967c0]         BOOTMEM
  #36 [00015967c0 - 0001596800]         BOOTMEM
  #37 [0001596800 - 0001596840]         BOOTMEM
  #38 [0001596840 - 0001596880]         BOOTMEM
  #39 [0001596880 - 00015968c0]         BOOTMEM
  #40 [00015968c0 - 0001596900]         BOOTMEM
  #41 [0001596900 - 0001596940]         BOOTMEM
  #42 [0001596940 - 0001596980]         BOOTMEM
  #43 [0001596980 - 0001596990]         BOOTMEM
  #44 [00015969c0 - 00015969d0]         BOOTMEM
  #45 [0001596a00 - 0001596a12]         BOOTMEM
  #46 [0001596a40 - 0001596a52]         BOOTMEM
  #47 [0002800000 - 000280d000]         BOOTMEM
  #48 [0002900000 - 000290d000]         BOOTMEM
  #49 [0002a00000 - 0002a0d000]         BOOTMEM
  #50 [0002b00000 - 0002b0d000]         BOOTMEM
  #51 [0001596a80 - 0001596a84]         BOOTMEM
  #52 [0001596ac0 - 0001596ac4]         BOOTMEM
  #53 [0001596b00 - 0001596b10]         BOOTMEM
  #54 [0001596b40 - 0001596b50]         BOOTMEM
  #55 [0001596b80 - 0001596c20]         BOOTMEM
  #56 [0001596c40 - 0001596c88]         BOOTMEM
  #57 [0002591000 - 0002595000]         BOOTMEM
  #58 [0002595000 - 0002615000]         BOOTMEM
  #59 [0002615000 - 0002655000]         BOOTMEM
  #60 [0002b0d000 - 00035007ec]         BOOTMEM
Initializing HighMem for node 0 (000377fe:0007f600)
Memory: 2049580k/2086912k available (3104k kernel code, 35068k reserved, 1205k data, 428k init, 1175792k highmem)
virtual kernel memory layout:
    fixmap  : 0xfff16000 - 0xfffff000   ( 932 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
    lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
      .init : 0xc1436000 - 0xc14a1000   ( 428 kB)
      .data : 0xc1308226 - 0xc1435820   (1205 kB)
      .text : 0xc1000000 - 0xc1308226   (3104 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Hierarchical RCU implementation.
    RCU-based detection of stalled CPUs is disabled.
    Verbose stalled-CPUs detection is disabled.
NR_IRQS:512
Extended CMOS year: 2000
Console: colour VGA+ 80x25
console [tty0] enabled
hpet clockevent registered
Fast TSC calibration using PIT
Detected 2533.081 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 5068.25 BogoMIPS (lpj=8443603)
pid_max: default: 32768 minimum: 301
Security Framework initialized
TOMOYO Linux initialized
AppArmor: AppArmor disabled by boot time parameter
Mount-cache hash table entries: 512
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 6 MCE banks
CPU0: Thermal monitoring enabled (TM2)
using mwait in idle threads.
Performance Events: PEBS fmt0+, Core2 events, Intel PMU driver.
... version:                2
... bit width:              40
... generic registers:      2
... value mask:             000000ffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             0000000700000003
ACPI: Core revision 20100702
Enabling APIC mode:  Flat.  Using 1 I/O APICs
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM)2 Duo CPU     E7200  @ 2.53GHz stepping 06
NMI watchdog enabled, takes one hw-pmu counter.
Booting Node   0, Processors  #1
Initializing CPU#1
NMI watchdog enabled, takes one hw-pmu counter.
Brought up 2 CPUs
Total of 2 processors activated (10136.92 BogoMIPS).
devtmpfs: initialized
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-40] at [mem 0xe0000000-0xe40fffff] (base 0xe0000000)
PCI: not using MMCONFIG
PCI: Using configuration type 1 for base access
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: SSDT 7f458c10 002CC (v01    AMI      IST 00000001 MSFT 03000001)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 002CC (v01    AMI      IST 00000001 MSFT 03000001)
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MMCONFIG for domain 0000 [bus 00-40] at [mem 0xe0000000-0xe40fffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xe40fffff] reserved in ACPI motherboard resources
PCI: MMCONFIG for 0000 [bus00-1f] at [mem 0xe0000000-0xe1ffffff] (base 0xe0000000) (size reduced!)
PCI: Using MMCONFIG for extended config space
ACPI: BIOS _OSI(Linux) query ignored
ACPI: No dock devices found.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
pci_root PNP0A08:00: host bridge window [io  0x0000-0x0cf7]
pci_root PNP0A08:00: host bridge window [io  0x0d00-0xffff]
pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
pci_root PNP0A08:00: host bridge window [mem 0x80000000-0xffffffff]
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:02.0: reg 10: [mem 0xff900000-0xff97ffff]
pci 0000:00:02.0: reg 14: [io  0xf140-0xf147]
pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff pref]
pci 0000:00:02.0: reg 1c: [mem 0xff700000-0xff7fffff]
pci 0000:00:1b.0: reg 10: [mem 0xff980000-0xff983fff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1d.0: reg 20: [io  0xf080-0xf09f]
pci 0000:00:1d.1: reg 20: [io  0xf060-0xf07f]
pci 0000:00:1d.2: reg 20: [io  0xf040-0xf05f]
pci 0000:00:1d.3: reg 20: [io  0xf020-0xf03f]
pci 0000:00:1d.7: reg 10: [mem 0xff984000-0xff9843ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: quirk: [io  0x0400-0x047f] claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: [io  0x0500-0x053f] claimed by ICH6 GPIO
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0290 (mask 00ff)
pci 0000:00:1f.1: reg 10: [io  0xf130-0xf137]
pci 0000:00:1f.1: reg 14: [io  0xf120-0xf123]
pci 0000:00:1f.1: reg 18: [io  0xf110-0xf117]
pci 0000:00:1f.1: reg 1c: [io  0xf100-0xf103]
pci 0000:00:1f.1: reg 20: [io  0xf0f0-0xf0ff]
pci 0000:00:1f.2: reg 10: [io  0xf0e0-0xf0e7]
pci 0000:00:1f.2: reg 14: [io  0xf0d0-0xf0d3]
pci 0000:00:1f.2: reg 18: [io  0xf0c0-0xf0c7]
pci 0000:00:1f.2: reg 1c: [io  0xf0b0-0xf0b3]
pci 0000:00:1f.2: reg 20: [io  0xf0a0-0xf0af]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 20: [io  0xf000-0xf01f]
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0:   bridge window [io  0xf000-0x0000] (disabled)
pci 0000:00:01.0:   bridge window [mem 0xfff00000-0x000fffff] (disabled)
pci 0000:00:01.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0:   bridge window [io  0xf000-0x0000] (disabled)
pci 0000:00:1c.0:   bridge window [mem 0xfff00000-0x000fffff] (disabled)
pci 0000:00:1c.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:03:00.0: reg 10: [io  0xe000-0xe0ff]
pci 0000:03:00.0: reg 18: [mem 0xff820000-0xff820fff 64bit]
pci 0000:03:00.0: reg 30: [mem 0xff800000-0xff81ffff pref]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:03:00.0: PME# disabled
pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1:   bridge window [io  0xe000-0xefff]
pci 0000:00:1c.1:   bridge window [mem 0xff800000-0xff8fffff]
pci 0000:00:1c.1:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:00:1e.0: PCI bridge to [bus 04-04] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0xf000-0x0000] (disabled)
pci 0000:00:1e.0:   bridge window [mem 0xfff00000-0x000fffff] (disabled)
pci 0000:00:1e.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
pci 0000:00:1e.0:   bridge window [io  0x0000-0x0cf7] (subtractive decode)
pci 0000:00:1e.0:   bridge window [io  0x0d00-0xffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
pci 0000:00:1e.0:   bridge window [mem 0x80000000-0xffffffff] (subtractive decode)
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15)
HEST: Table is not found!
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
reserve RAM buffer: 0000000000002000 - 000000000000ffff
reserve RAM buffer: 000000000009fc00 - 000000000009ffff
reserve RAM buffer: 000000007f2a7000 - 000000007fffffff
reserve RAM buffer: 000000007f600000 - 000000007fffffff
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
HPET: 3 timers in total, 0 timers will be used for per-cpu timer
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 comparators, 64-bit 14.318180 MHz counter
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: [mem 0xfed14000-0xfed19fff] has been reserved
system 00:01: [mem 0xe0000000-0xe3ffffff] has been reserved
system 00:02: [io  0x0400-0x047f] has been reserved
system 00:02: [io  0x1180-0x119f] has been reserved
system 00:02: [io  0x0500-0x053f] has been reserved
system 00:02: [mem 0xfec00000-0xfecfffff] could not be reserved
system 00:02: [mem 0xfee00000-0xfee0ffff] has been reserved
system 00:02: [mem 0xfed1c000-0xfed1ffff] has been reserved
system 00:02: [mem 0xffb00000-0xffcfffff] could not be reserved
system 00:02: [mem 0xfc800000-0xfc800fff] has been reserved
system 00:02: [mem 0xfed20000-0xfed7ffff] has been reserved
system 00:02: [mem 0xffe00000-0xffffffff] has been reserved
system 00:03: [io  0x0290-0x029f] has been reserved
system 00:0b: [io  0x04d0-0x04d1] has been reserved
pci 0000:00:1c.0: BAR 14: assigned [mem 0x80000000-0x801fffff]
pci 0000:00:1c.0: BAR 15: assigned [mem 0x80200000-0x803fffff 64bit pref]
pci 0000:00:1c.1: BAR 15: assigned [mem 0x80400000-0x805fffff 64bit pref]
pci 0000:00:1c.0: BAR 13: assigned [io  0x2000-0x2fff]
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0:   bridge window [io  disabled]
pci 0000:00:01.0:   bridge window [mem disabled]
pci 0000:00:01.0:   bridge window [mem pref disabled]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
pci 0000:00:1c.0:   bridge window [mem 0x80000000-0x801fffff]
pci 0000:00:1c.0:   bridge window [mem 0x80200000-0x803fffff 64bit pref]
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1:   bridge window [io  0xe000-0xefff]
pci 0000:00:1c.1:   bridge window [mem 0xff800000-0xff8fffff]
pci 0000:00:1c.1:   bridge window [mem 0x80400000-0x805fffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 04-04]
pci 0000:00:1e.0:   bridge window [io  disabled]
pci 0000:00:1e.0:   bridge window [mem disabled]
pci 0000:00:1e.0:   bridge window [mem pref disabled]
pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:01.0: setting latency timer to 64
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
pci_bus 0000:00: resource 5 [io  0x0d00-0xffff]
pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 7 [mem 0x80000000-0xffffffff]
pci_bus 0000:02: resource 0 [io  0x2000-0x2fff]
pci_bus 0000:02: resource 1 [mem 0x80000000-0x801fffff]
pci_bus 0000:02: resource 2 [mem 0x80200000-0x803fffff 64bit pref]
pci_bus 0000:03: resource 0 [io  0xe000-0xefff]
pci_bus 0000:03: resource 1 [mem 0xff800000-0xff8fffff]
pci_bus 0000:03: resource 2 [mem 0x80400000-0x805fffff 64bit pref]
pci_bus 0000:04: resource 4 [io  0x0000-0x0cf7]
pci_bus 0000:04: resource 5 [io  0x0d00-0xffff]
pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:04: resource 7 [mem 0x80000000-0xffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
pci 0000:00:02.0: Boot video device
pci 0000:00:1d.7: EHCI: BIOS handoff failed (BIOS bug?) 01010001
PCI: CLS 64 bytes, default 64
Unpacking initramfs...
Freeing initrd memory: 1772k freed
apm: BIOS not found.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1295105825.613:1): initialized
highmem bounce pool size: 64 pages
HugeTLB registered 4 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1710
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:01.0: ACPI _OSC control granted for 0x1d
pcieport 0000:00:01.0: setting latency timer to 64
pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
pcieport 0000:00:1c.0: ACPI _OSC control granted for 0x1d
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
pcieport 0000:00:1c.1: ACPI _OSC control granted for 0x1d
pcieport 0000:00:1c.1: setting latency timer to 64
pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
intel_idle: MWAIT substates: 0x22220
intel_idle: does not run on family 6 model 23
ERST: Table is not found!
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03: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
mice: PS/2 mouse device common for all mice
rtc_cmos 00:09: RTC can wake from S4
rtc_cmos 00:09: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
Using IPI No-Shortcut mode
PM: Resume from disk failed.
registered taskstats version 1
rtc_cmos 00:09: setting system clock to 2011-01-15 15:37:06 UTC (1295105826)
Initalizing network drop monitor service
Freeing unused kernel memory: 428k freed
udev[38]: starting version 165
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
SCSI subsystem initialized
libata version 3.00 loaded.
pata_acpi 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
pata_acpi 0000:00:1f.1: setting latency timer to 64
pata_acpi 0000:00:1f.1: PCI INT A disabled
pata_acpi 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
pata_acpi 0000:00:1f.2: setting latency timer to 64
pata_acpi 0000:00:1f.2: PCI INT B disabled
ata_piix 0000:00:1f.1: version 2.13
ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
ata_piix 0000:00:1f.1: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf0f0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf0f8 irq 15
ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi2 : ata_piix
ata2: port disabled. ignoring.
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0xf0e0 ctl 0xf0d0 bmdma 0xf0a0 irq 19
ata4: SATA max UDMA/133 cmd 0xf0c0 ctl 0xf0b0 bmdma 0xf0a8 irq 19
FDC 0 is a post-1991 82077
ata4.01: NODEV after polling detection
ata4.00: ATAPI: MOSER BAER DH-20A6S, 7M73, max UDMA/100
ata3.00: ATA-8: WDC WD10EARS-00Y5B1, 80.00A80, max UDMA/133
ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access     ATA      WDC WD10EARS-00Y 80.0 PQ: 0 ANSI: 5
ata4.00: configured for UDMA/100
scsi 3:0:0:0: CD-ROM            MOSER    BAER DH-20A6S    7M73 PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 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 < sda5 >
sd 2:0:0:0: [sda] Attached SCSI disk
sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 3:0:0:0: Attached scsi CD-ROM sr0
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Not activating Mandatory Access Control now since /sbin/tomoyo-init doesn't exist.
udev[645]: starting version 165
input: PC Speaker as /devices/platform/pcspkr/input/input1
intel_rng: Firmware space is locked read-only. If you can't or
intel_rng: don't want to disable this in firmware setup, and if
intel_rng: you are certain that your system has a functional
intel_rng: RNG, try using the 'no_fwh_detect' option.
Linux agpgart interface v0.103
iTCO_vendor_support: vendor-support=0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
ACPI: Sleep Button [SLPB]
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
ACPI: Power Button [PWRF]
sd 2:0:0:0: Attached scsi generic sg0 type 0
sr 3:0:0:0: Attached scsi generic sg1 type 5
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: using broken periodic workaround
ehci_hcd 0000:00:1d.7: debug port 1
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xff984000
ACPI: acpi_idle registered with cpuidle
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8169 0000:03:00.0: setting latency timer to 64
r8169 0000:03:00.0: irq 43 for MSI/MSI-X
r8169 0000:03:00.0: eth0: RTL8168b/8111b at 0xf87b2000, 00:1c:c0:62:86:49, XID 98500000 IRQ 43
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
agpgart-intel 0000:00:00.0: Intel G33 Chipset
agpgart-intel 0000:00:00.0: detected 7676K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000f080
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000f060
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000f040
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.3: setting latency timer to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000f020
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
leds_ss4200: no LED devices found
psmouse serio1: ID: 10 00 64
[drm] Initialized drm 1.1.0 20060810
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
i915 0000:00:02.0: irq 44 for MSI/MSI-X
[drm] set up 7M of stolen space
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5
[drm] initialized overlay support
Console: switching to colour frame buffer device 180x56
fb0: inteldrmfb frame buffer device
drm: registered panic notifier
ACPI Exception: AE_NOT_FOUND, Evaluating _DOD (20100702/video-1964)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
ACPI: Video Device [GFX0] (multi-head: no  rom: yes  post: no)
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
HDA Intel 0000:00:1b.0: irq 45 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
usb 2-1: new full speed USB device using uhci_hcd and address 2
hda_codec: ALC888: SKU not ready 0x411111f0
hda_codec: ALC888: BIOS auto-probing.
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input7
EXT4-fs (sda2): re-mounted. Opts: (null)
EXT4-fs (sda2): re-mounted. Opts: (null)
fuse init (API version 7.15)
r8169 0000:03:00.0: eth0: link up
r8169 0000:03:00.0: eth0: link up
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
Bluetooth: L2CAP ver 2.15
Bluetooth: L2CAP socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
loop: module loaded
scsi4 : vhba
scsi 4:0:0:0: CD-ROM            CDEmu    Virt. CD/DVD-ROM 1.10 PQ: 0 ANSI: 0
sr1: scsi3-mmc drive: 40x/40x cd/rw xa/form2 cdda tray
sr 4:0:0:0: Attached scsi CD-ROM sr1
sr 4:0:0:0: Attached scsi generic sg2 type 5
Adding 2097148k swap on /var/swapfile.  Priority:-1 extents:6 across:2260992k
start_kdeinit (1753): /proc/1753/oom_adj is deprecated, please use /proc/1753/oom_score_adj instead.
EXT4-fs (sda2): re-mounted. Opts: commit=0
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth0: no IPv6 routers present

Offline

#125 2011-01-15 14:44:27

soylent_green_is_hamster
Member
Registered: 2006-11-15
Posts: 109

Re: Latest udev causes kernel panics (something about libata)

Wilco wrote:
pdork3 wrote:

i'm reading this thread for some days now. it seems that no one really knows whats the problem, yet.
on my machine i'm having the same issues as described. kernel panics at boot, sometimes 5 times in a row.
panics occur at different boot states. sometimes very early, sometimes later (when daemons loading).
i have a fresh installed arch with all updates. no patches, no nothing.
my system has pata hard disc and pata optical.
mounting cd/dvd also gives kernel panic sometimes. see picture!

http://img156.imagevenue.com/img.php?im … _504lo.jpg

i think its a pata problem. anyone with sata drives having problems?

I have system lockups with a SATA only system. Don't know if that's the same problem because I don't get a kernel panic, but just a hard freeze; I can only hold the power button, no flashing leds and no logs.

I have a SATA system too. It boots OK, but I get the same random hard freeze occasionally on mounting or unmounting dvds. Nothing in the logs either!

Offline

Board footer

Powered by FluxBB