* 2.6.30-rc8 Oops whilst booting @ 2009-06-06 18:59 Chris Clayton 2009-06-06 21:15 ` Chris Clayton 0 siblings, 1 reply; 38+ messages in thread From: Chris Clayton @ 2009-06-06 18:59 UTC (permalink / raw) To: LKML Hi, After a git pull earlier today, I've had oopsen whilst booting the system twice today: A photo of the oops message can be viewed at: http://img231.imageshack.us/img231/8931/dscn0610.jpg I haven't used the 2.6.30-rc kernels very much, so I don't have a clue when the problem was introduced. I have no problems at all with 2.6.29.4. Happy to help solve this - just let me know what else I can do. Thanks -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-06 18:59 2.6.30-rc8 Oops whilst booting Chris Clayton @ 2009-06-06 21:15 ` Chris Clayton 2009-06-07 13:25 ` Jaswinder Singh Rajput 0 siblings, 1 reply; 38+ messages in thread From: Chris Clayton @ 2009-06-06 21:15 UTC (permalink / raw) To: LKML Sorry, I've just realised what a poor report my earlier email was. I should also have said that the kernel has booted succesfully. At the time of reporting I had had two panics. I've just done another git pull, so the kernel is bang up to date with kernel.org, but after building and installing, a reboot resulted in another panic. The system then booted OK after switch off and on again. Please cc me to any reply, I'm not subscribed. On Saturday 06 June 2009, Chris Clayton wrote: > Hi, > > After a git pull earlier today, I've had oopsen whilst booting the system > twice today: A photo of the oops message can be viewed at: > > http://img231.imageshack.us/img231/8931/dscn0610.jpg > > I haven't used the 2.6.30-rc kernels very much, so I don't have a clue when > the problem was introduced. I have no problems at all with 2.6.29.4. > > Happy to help solve this - just let me know what else I can do. > > Thanks -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-06 21:15 ` Chris Clayton @ 2009-06-07 13:25 ` Jaswinder Singh Rajput 2009-06-07 18:38 ` Chris Clayton 0 siblings, 1 reply; 38+ messages in thread From: Jaswinder Singh Rajput @ 2009-06-07 13:25 UTC (permalink / raw) To: chris2553; +Cc: LKML Hello Chris, On Sat, 2009-06-06 at 22:15 +0100, Chris Clayton wrote: > Sorry, I've just realised what a poor report my earlier email was. I should also have said that the > kernel has booted succesfully. At the time of reporting I had had two panics. I've just done > another git pull, so the kernel is bang up to date with kernel.org, but after building and > installing, a reboot resulted in another panic. The system then booted OK after switch off and on > again. > > Please cc me to any reply, I'm not subscribed. > > > On Saturday 06 June 2009, Chris Clayton wrote: > > Hi, > > > > After a git pull earlier today, I've had oopsen whilst booting the system > > twice today: A photo of the oops message can be viewed at: > > > > http://img231.imageshack.us/img231/8931/dscn0610.jpg > > > > I haven't used the 2.6.30-rc kernels very much, so I don't have a clue when > > the problem was introduced. I have no problems at all with 2.6.29.4. > > Can you provide your .config and dmesg of working and non-working kernel. Thanks, -- JSR ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-07 13:25 ` Jaswinder Singh Rajput @ 2009-06-07 18:38 ` Chris Clayton 2009-06-07 22:31 ` Jaswinder Singh Rajput 0 siblings, 1 reply; 38+ messages in thread From: Chris Clayton @ 2009-06-07 18:38 UTC (permalink / raw) To: Jaswinder Singh Rajput, linux-kernel [-- Attachment #1: Type: text/plain, Size: 2343 bytes --] 2009/6/7 Jaswinder Singh Rajput <jaswinder@kernel.org>: > Hello Chris, > Hello Jaswinder and thanks for the reply. > On Sat, 2009-06-06 at 22:15 +0100, Chris Clayton wrote: >> Sorry, I've just realised what a poor report my earlier email was. I should also have said that the >> kernel has booted succesfully. At the time of reporting I had had two panics. I've just done >> another git pull, so the kernel is bang up to date with kernel.org, but after building and >> installing, a reboot resulted in another panic. The system then booted OK after switch off and on >> again. >> >> Please cc me to any reply, I'm not subscribed. >> >> >> On Saturday 06 June 2009, Chris Clayton wrote: >> > Hi, >> > >> > After a git pull earlier today, I've had oopsen whilst booting the system >> > twice today: A photo of the oops message can be viewed at: >> > >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> > >> > I haven't used the 2.6.30-rc kernels very much, so I don't have a clue when >> > the problem was introduced. I have no problems at all with 2.6.29.4. >> > > > Can you provide your .config and dmesg of working and non-working > kernel. > > Thanks, > -- > JSR > > Sorry for delay in replying - I've been bisecting but ended up with: commit 60a0cd528d761c50d3a0a49e8fbaf6a87e64254a Merge: e25e092 8e35961 Author: Linus Torvalds <torvalds@linux-foundation.org> Commit: Linus Torvalds <torvalds@linux-foundation.org> Merge branch 'merge' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc * 'merge' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc: powerpc/mm: Fix broken MMU PID stealing on !SMP which seems wrong given I have and x86 machine. I guess I didn't try enough reboots before reporting a kernel as good. However, I did get two bad boots. The dmesg for a good boot and config are attached. As I don't get to user space on a bad boot, I can't provide a dmesg, but a photograph of the panic can be viewed at http://img99.imageshack.us/my.php?image=dscn0617b.jpg I'll start bisecting again, but allow may more reboots before deciding a kernel is good. Let me know if I can provide any additional information. Thanks -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson [-- Attachment #2: dmesg.good --] [-- Type: application/octet-stream, Size: 31613 bytes --] Linux version 2.6.30-rc7 (chris@upstairs) (gcc version 4.3.4 20090531 (prerelease) (GCC) ) #215 SMP PREEMPT Sun Jun 7 15:51:33 BST 2009 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD NSC Geode by NSC Cyrix CyrixInstead Centaur CentaurHauls Transmeta GenuineTMx86 Transmeta TransmetaCPU UMC UMC UMC UMC BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000bffb0000 (usable) BIOS-e820: 00000000bffb0000 - 00000000bffc0000 (ACPI data) BIOS-e820: 00000000bffc0000 - 00000000bfff0000 (ACPI NVS) BIOS-e820: 00000000bfff0000 - 00000000c0000000 (reserved) BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved) DMI 2.3 present. AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) last_pfn = 0xbffb0 max_arch_pfn = 0x100000 MTRR default type: uncachable MTRR fixed ranges enabled: 00000-9FFFF write-back A0000-DFFFF uncachable E0000-EFFFF write-through F0000-FFFFF write-protect MTRR variable ranges enabled: 0 base 000000000 mask F80000000 write-back 1 base 080000000 mask FC0000000 write-back 2 disabled 3 disabled 4 disabled 5 disabled 6 disabled 7 disabled x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 init_memory_mapping: 0000000000000000-00000000377fe000 0000000000 - 0000400000 page 4k 0000400000 - 0037400000 page 2M 0037400000 - 00377fe000 page 4k kernel direct mapping tables up to 377fe000 @ 10000-15000 ACPI: RSDP 000faf50 00021 (v02 ACPIAM) ACPI: XSDT bffb0100 0003C (v01 A M I OEMXSDT 06000626 MSFT 00000097) ACPI: FACP bffb0290 000F4 (v03 A M I OEMFACP 06000626 MSFT 00000097) ACPI: DSDT bffb0400 03552 (v01 A0495 A0495036 00000036 INTL 02002026) ACPI: FACS bffc0000 00040 ACPI: APIC bffb0390 0006C (v01 A M I OEMAPIC 06000626 MSFT 00000097) ACPI: OEMB bffc0040 0003F (v01 A M I OEMBIOS 06000626 MSFT 00000097) ACPI: Local APIC address 0xfee00000 2183MB HIGHMEM available. 887MB LOWMEM available. mapped low ram: 0 - 377fe000 low ram: 0 - 377fe000 node 0 low ram: 00000000 - 377fe000 node 0 bootmap 00011000 - 00017f00 (8 early reservations) ==> bootmem [0000000000 - 00377fe000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000] #3 [0000100000 - 00004bef84] TEXT DATA BSS ==> [0000100000 - 00004bef84] #4 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000] #5 [00004bf000 - 00004c1218] BRK ==> [00004bf000 - 00004c1218] #6 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000] #7 [0000011000 - 0000018000] BOOTMAP ==> [0000011000 - 0000018000] found SMP MP-table at [c00ff780] ff780 Zone PFN ranges: DMA 0x00000010 -> 0x00001000 Normal 0x00001000 -> 0x000377fe HighMem 0x000377fe -> 0x000bffb0 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x00000010 -> 0x0000009f 0: 0x00000100 -> 0x000bffb0 On node 0 totalpages: 786239 free_area_init_node: node 0, pgdat c0428b80, node_mem_map c1000200 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 3951 pages, LIFO batch:0 Normal zone: 1744 pages used for memmap Normal zone: 221486 pages, LIFO batch:31 HighMem zone: 4368 pages used for memmap HighMem zone: 554658 pages, LIFO batch:31 Using APIC driver default ACPI: PM-Timer IO Port: 0x808 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[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, 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. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information 4 Processors exceeds NR_CPUS limit of 2 SMP: Allowing 2 CPUs, 0 hotplug CPUs nr_irqs_gsi: 24 Allocating PCI resources starting at c4000000 (gap: c0000000:3fb80000) NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1 PERCPU: Embedded 13 pages at c2810000, static data 30748 bytes Built 1 zonelists in Zone order, mobility grouping on. Total pages: 780095 Kernel command line: root=/dev/sdb6 ro usbcore.old_scheme_first=1 Unknown boot option `usbcore.old_scheme_first=1': ignoring Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 NR_IRQS:320 CPU 0 irqstacks, hard=c2810000 soft=c2811000 PID hash table entries: 4096 (order: 12, 16384 bytes) Fast TSC calibration using PIT Detected 3194.092 MHz processor. Console: colour VGA+ 80x25 console [tty0] enabled Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Initializing HighMem for node 0 (000377fe:000bffb0) Memory: 3114748k/3145408k available (2332k kernel code, 29396k reserved, 978k data, 276k init, 2236104k highmem) virtual kernel memory layout: fixmap : 0xfff9d000 - 0xfffff000 ( 392 kB) pkmap : 0xff800000 - 0xffc00000 (4096 kB) vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB) lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB) .init : 0xc0440000 - 0xc0485000 ( 276 kB) .data : 0xc0347103 - 0xc043bbc8 ( 978 kB) .text : 0xc0100000 - 0xc0347103 (2332 kB) Checking if this processor honours the WP bit even in supervisor mode...Ok. SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 Calibrating delay loop (skipped), value calculated using timer frequency.. 6388.18 BogoMIPS (lpj=3194092) Security Framework initialized Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (24) available using mwait in idle threads. Checking 'hlt' instruction... OK. ACPI: Core revision 20090320 ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 CPU0: Intel(R) Pentium(R) D CPU 3.20GHz stepping 02 APIC calibration not consistent with PM-Timer: 1701ms instead of 100ms APIC delta adjusted to PM-Timer: 1247690 (21232485) CPU 1 irqstacks, hard=c2820000 soft=c2821000 Booting processor 1 APIC 0x1 ip 0x6000 Initializing CPU#1 Calibrating delay using timer specific routine.. 6387.86 BogoMIPS (lpj=3193931) CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#1. CPU1: Intel P4/Xeon Extended MCE MSRs (24) available x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106 CPU1: Intel(R) Pentium(R) D CPU 3.20GHz stepping 02 checking TSC synchronization [CPU#0 -> CPU#1]: passed. Brought up 2 CPUs Total of 2 processors activated (12776.04 BogoMIPS). net_namespace: 732 bytes NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2 PCI: Using configuration type 1 for base access bio: create slab <bio-0> at 0 ACPI: EC: Look up EC in DSDT ACPI: Interpreter enabled ACPI: (supports S0 S5) ACPI: Using IOAPIC for interrupt routing ACPI Warning (tbutils-0246): Incorrect checksum in table [OEMB] - 7D, should be 70 [20090320] ACPI: No dock devices found. ACPI: PCI Root Bridge [PCI0] (0000:00) pci 0000:00:00.0: reg 10 32bit mmio: [0xd8000000-0xdfffffff] pci 0000:00:1d.0: reg 20 io port: [0xa800-0xa81f] pci 0000:00:1d.1: reg 20 io port: [0xb000-0xb01f] pci 0000:00:1d.2: reg 20 io port: [0xb400-0xb41f] pci 0000:00:1d.3: reg 20 io port: [0xb800-0xb81f] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf9fffc00-0xf9ffffff] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold pci 0000:00:1d.7: PME# disabled pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO pci 0000:00:1f.0: quirk: region 0480-04bf claimed by ICH4 GPIO pci 0000:00:1f.1: reg 10 io port: [0x00-0x07] pci 0000:00:1f.1: reg 14 io port: [0x00-0x03] pci 0000:00:1f.1: reg 18 io port: [0x00-0x07] pci 0000:00:1f.1: reg 1c io port: [0x00-0x03] pci 0000:00:1f.1: reg 20 io port: [0xfc00-0xfc0f] pci 0000:00:1f.1: reg 24 32bit mmio: [0x000000-0x0003ff] pci 0000:00:1f.2: reg 10 io port: [0x9800-0x9807] pci 0000:00:1f.2: reg 14 io port: [0x9400-0x9403] pci 0000:00:1f.2: reg 18 io port: [0x9000-0x9007] pci 0000:00:1f.2: reg 1c io port: [0x8800-0x8803] pci 0000:00:1f.2: reg 20 io port: [0x8400-0x840f] pci 0000:00:1f.5: reg 10 io port: [0xa400-0xa4ff] pci 0000:00:1f.5: reg 14 io port: [0xa000-0xa03f] pci 0000:00:1f.5: reg 18 32bit mmio: [0xf9fff800-0xf9fff9ff] pci 0000:00:1f.5: reg 1c 32bit mmio: [0xf9fff400-0xf9fff4ff] pci 0000:00:1f.5: PME# supported from D0 D3hot D3cold pci 0000:00:1f.5: PME# disabled pci 0000:01:00.0: reg 10 32bit mmio: [0xfa000000-0xfaffffff] pci 0000:01:00.0: reg 14 32bit mmio: [0xe0000000-0xefffffff] pci 0000:01:00.0: reg 30 32bit mmio: [0xfbee0000-0xfbefffff] pci 0000:00:01.0: bridge io port: [0xc000-0xcfff] pci 0000:00:01.0: bridge 32bit mmio: [0xfa000000-0xfbefffff] pci 0000:00:01.0: bridge 32bit mmio pref: [0xe0000000-0xf8ffffff] pci 0000:02:09.0: reg 20 io port: [0xe400-0xe41f] pci 0000:02:09.0: supports D1 D2 pci 0000:02:09.0: PME# supported from D0 D1 D2 D3hot pci 0000:02:09.0: PME# disabled pci 0000:02:09.1: reg 20 io port: [0xe800-0xe81f] pci 0000:02:09.1: supports D1 D2 pci 0000:02:09.1: PME# supported from D0 D1 D2 D3hot pci 0000:02:09.1: PME# disabled pci 0000:02:09.2: reg 10 32bit mmio: [0xfbfffc00-0xfbfffcff] pci 0000:02:09.2: supports D1 D2 pci 0000:02:09.2: PME# supported from D0 D1 D2 D3hot pci 0000:02:09.2: PME# disabled pci 0000:02:0a.0: reg 10 32bit mmio: [0xfbffd000-0xfbffdfff] pci 0000:02:0a.0: supports D1 D2 pci 0000:02:0a.0: PME# supported from D0 D1 D2 D3hot pci 0000:02:0a.0: PME# disabled pci 0000:02:0a.1: reg 10 32bit mmio: [0xfbffe000-0xfbffefff] pci 0000:02:0a.1: supports D1 D2 pci 0000:02:0a.1: PME# supported from D0 D1 D2 D3hot pci 0000:02:0a.1: PME# disabled pci 0000:02:0a.2: reg 10 32bit mmio: [0xfbfff800-0xfbfff8ff] pci 0000:02:0a.2: supports D1 D2 pci 0000:02:0a.2: PME# supported from D0 D1 D2 D3hot pci 0000:02:0a.2: PME# disabled pci 0000:02:0b.0: reg 10 32bit mmio: [0xfbfff000-0xfbfff7ff] pci 0000:02:0b.0: reg 14 io port: [0xe000-0xe07f] pci 0000:02:0b.0: supports D2 pci 0000:02:0b.0: PME# supported from D2 D3hot D3cold pci 0000:02:0b.0: PME# disabled pci 0000:02:0d.0: reg 10 io port: [0xd800-0xd8ff] pci 0000:02:0d.0: reg 14 32bit mmio: [0xfbffcc00-0xfbffccff] pci 0000:02:0d.0: supports D1 D2 pci 0000:02:0d.0: PME# supported from D1 D2 D3hot D3cold pci 0000:02:0d.0: PME# disabled pci 0000:00:1e.0: transparent bridge pci 0000:00:1e.0: bridge io port: [0xd000-0xefff] pci 0000:00:1e.0: bridge 32bit mmio: [0xfbf00000-0xfbffffff] pci_bus 0000:00: on NUMA node 0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._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 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) SCSI subsystem initialized libata version 3.00 loaded. PCI: Using ACPI for IRQ routing pnp: PnP ACPI init ACPI: bus type pnp registered pnp: PnP ACPI: found 13 devices ACPI: ACPI bus type pnp unregistered system 00:07: ioport range 0x290-0x297 has been reserved system 00:08: ioport range 0x4d0-0x4d1 has been reserved system 00:08: ioport range 0x800-0x87f has been reserved system 00:08: ioport range 0x400-0x41f has been reserved system 00:08: ioport range 0x480-0x4bf has been reserved system 00:08: iomem range 0xfed20000-0xfed8ffff has been reserved system 00:08: iomem range 0xffb00000-0xffbfffff could not be reserved system 00:09: iomem range 0xfec00000-0xfec00fff has been reserved system 00:09: iomem range 0xfee00000-0xfee00fff has been reserved system 00:0c: iomem range 0x0-0x9ffff could not be reserved system 00:0c: iomem range 0xc0000-0xdffff could not be reserved system 00:0c: iomem range 0xe0000-0xfffff could not be reserved system 00:0c: iomem range 0x100000-0xbffeffff could not be reserved system 00:0c: iomem range 0xfff00000-0xffffffff has been reserved pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 pci 0000:00:01.0: IO window: 0xc000-0xcfff pci 0000:00:01.0: MEM window: 0xfa000000-0xfbefffff pci 0000:00:01.0: PREFETCH window: 0x000000e0000000-0x000000f8ffffff pci 0000:00:1e.0: PCI bridge, secondary bus 0000:02 pci 0000:00:1e.0: IO window: 0xd000-0xefff pci 0000:00:1e.0: MEM window: 0xfbf00000-0xfbffffff pci 0000:00:1e.0: PREFETCH window: disabled pci 0000:00:1e.0: setting latency timer to 64 pci_bus 0000:00: resource 0 io: [0x00-0xffff] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff] pci_bus 0000:01: resource 0 io: [0xc000-0xcfff] pci_bus 0000:01: resource 1 mem: [0xfa000000-0xfbefffff] pci_bus 0000:01: resource 2 pref mem [0xe0000000-0xf8ffffff] pci_bus 0000:02: resource 0 io: [0xd000-0xefff] pci_bus 0000:02: resource 1 mem: [0xfbf00000-0xfbffffff] pci_bus 0000:02: resource 3 io: [0x00-0xffff] pci_bus 0000:02: resource 4 mem: [0x000000-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 NET: Registered protocol family 1 highmem bounce pool size: 64 pages msgmni has been set to 1717 alg: No test for stdrng (krng) io scheduler noop registered io scheduler cfq registered (default) pci 0000:01:00.0: Boot video device input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 ACPI: Power Button [PWRF] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1 ACPI: Power Button [PWRB] processor ACPI_CPU:00: registered as cooling_device0 ACPI: Processor [CPU1] (supports 8 throttling states) processor ACPI_CPU:01: registered as cooling_device1 Real Time Clock Driver v1.12b Linux agpgart interface v0.103 agpgart-intel 0000:00:00.0: Intel 865 Chipset agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xd8000000 Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods ata_piix 0000:00:1f.1: version 2.13 ata_piix 0000:00:1f.1: enabling device (0005 -> 0007) 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 0xfc00 irq 14 ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15 ata_piix 0000:00:1f.2: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ] ata_piix 0000:00:1f.2: setting latency timer to 64 scsi2 : ata_piix scsi3 : ata_piix ata3: SATA max UDMA/133 cmd 0x9800 ctl 0x9400 bmdma 0x8400 irq 18 ata4: SATA max UDMA/133 cmd 0x9000 ctl 0x8800 bmdma 0x8408 irq 18 8139too Fast Ethernet driver 0.9.28 8139too 0000:02:0d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 eth0: RealTek RTL8139 at 0xf8006c00, 00:17:31:a9:1d:48, IRQ 23 eth0: Identified 8139 chip type 'RTL-8100B/8139D' PNP: PS/2 Controller [PNP0f03:PS2M] at 0x60,0x64 irq 12 PNP: PS/2 controller doesn't have KBD irq; using default 1 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 cpuidle: using governor ladder cpuidle: using governor menu Advanced Linux Sound Architecture Driver Version 1.0.20. Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17 Intel ICH 0000:00:1f.5: setting latency timer to 64 ata3.00: ATA-7: Hitachi HDS721616PLA380, P22OA70A, max UDMA/133 ata3.00: 321672960 sectors, multi 16: LBA48 NCQ (depth 0/32) ata3.00: configured for UDMA/133 ata2.00: ATAPI: SONY DVD RW DW-G120A, MYS2, max UDMA/66 ata2.01: ATAPI: PHILIPS DVDR1628P1, Q2.2, max UDMA/33 ata2.00: configured for UDMA/66 ata1.00: ATA-7: MAXTOR STM3250820A, 3.AAE, max UDMA/100 ata1.00: 488397168 sectors, multi 16: LBA48 ata1.01: ATA-7: Maxtor 6L160P0, BAJ41G20, max UDMA/133 ata1.01: 320173056 sectors, multi 16: LBA48 ata2.01: configured for UDMA/33 ata1.00: configured for UDMA/100 ata1.01: configured for UDMA/100 scsi 0:0:0:0: Direct-Access ATA MAXTOR STM325082 3.AA PQ: 0 ANSI: 5 scsi 0:0:1:0: Direct-Access ATA Maxtor 6L160P0 BAJ4 PQ: 0 ANSI: 5 scsi 2:0:0:0: Direct-Access ATA Hitachi HDS72161 P22O PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors: (250 GB/232 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:1:0: [sdb] 320173056 512-byte hardware sectors: (163 GB/152 GiB) sd 0:0:1:0: [sdb] Write Protect is off sda:<7>sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 scsi 1:0:0:0: CD-ROM SONY DVD RW DW-G120A MYS2 PQ: 0 ANSI: 5 sd 2:0:0:0: [sdc] 321672960 512-byte hardware sectors: (164 GB/153 GiB) sd 2:0:0:0: [sdc] Write Protect is off sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc:sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 1:0:0:0: Attached scsi CD-ROM sr0 scsi 1:0:1:0: CD-ROM PHILIPS DVDR1628P1 Q2.2 PQ: 0 ANSI: 5 sdc1 sdc2 sdc3 sd 2:0:0:0: [sdc] Attached SCSI disk sr1: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray sr 1:0:1:0: Attached scsi CD-ROM sr1 intel8x0_measure_ac97_clock: measured 50858 usecs (2451 samples) intel8x0: clocking to 48000 ALSA device list: #0: Intel ICH5 with ALC655 at irq 17 TCP cubic registered NET: Registered protocol family 15 Using IPI No-Shortcut mode sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sda1 sda2 sda3 sda4 < sdb1 sdb2 sdb3 sdb4 < sda5 sdb5 sda6 sdb6 > sd 0:0:1:0: [sdb] Attached SCSI disk sda7 > sd 0:0:0:0: [sda] Attached SCSI disk Switched to NOHz mode on CPU #1 Switched to NOHz mode on CPU #0 input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input2 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with writeback data mode. VFS: Mounted root (ext3 filesystem) readonly on device 8:22. Freeing unused kernel memory: 276k freed EXT3 FS on sdb6, internal journal Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 ohci1394 0000:02:0b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb uhci_hcd: USB Universal Host Controller Interface driver uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 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 1 uhci_hcd 0000:00:1d.0: irq 16, io base 0x0000a800 usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: UHCI Host Controller usb usb1: Manufacturer: Linux 2.6.30-rc7 uhci_hcd usb usb1: SerialNumber: 0000:00:1d.0 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-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 2 uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000b000 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: UHCI Host Controller usb usb2: Manufacturer: Linux 2.6.30-rc7 uhci_hcd usb usb2: SerialNumber: 0000:00:1d.1 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-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 3 uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000b400 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: UHCI Host Controller usb usb3: Manufacturer: Linux 2.6.30-rc7 uhci_hcd usb usb3: SerialNumber: 0000:00:1d.2 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected uhci_hcd 0000:00:1d.3: PCI INT A -> 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 4 uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000b800 usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb4: Product: UHCI Host Controller usb usb4: Manufacturer: Linux 2.6.30-rc7 uhci_hcd usb usb4: SerialNumber: 0000:00:1d.3 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[22] MMIO=[fbfff000-fbfff7ff] Max Packet=[2048] IR/IT contexts=[4/8] uhci_hcd 0000:02:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 uhci_hcd 0000:02:09.0: UHCI Host Controller uhci_hcd 0000:02:09.0: new USB bus registered, assigned bus number 5 uhci_hcd 0000:02:09.0: irq 17, io base 0x0000e400 usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb5: Product: UHCI Host Controller usb usb5: Manufacturer: Linux 2.6.30-rc7 uhci_hcd usb usb5: SerialNumber: 0000:02:09.0 usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 2 ports detected uhci_hcd 0000:02:09.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18 uhci_hcd 0000:02:09.1: UHCI Host Controller uhci_hcd 0000:02:09.1: new USB bus registered, assigned bus number 6 uhci_hcd 0000:02:09.1: irq 18, io base 0x0000e800 usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb6: Product: UHCI Host Controller usb usb6: Manufacturer: Linux 2.6.30-rc7 uhci_hcd usb usb6: SerialNumber: 0000:02:09.1 usb usb6: configuration #1 chosen from 1 choice hub 6-0:1.0: USB hub found hub 6-0:1.0: 2 ports detected ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ohci_hcd 0000:02:0a.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 ohci_hcd 0000:02:0a.0: OHCI Host Controller ohci_hcd 0000:02:0a.0: new USB bus registered, assigned bus number 7 ohci_hcd 0000:02:0a.0: irq 21, io mem 0xfbffd000 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after ehci_hcd 0000:00:1d.7: PCI INT D -> 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 8 ehci_hcd 0000:00:1d.7: debug port 1 ehci_hcd 0000:00:1d.7: cache line size of 128 is not supported ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf9fffc00 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 usb usb8: New USB device found, idVendor=1d6b, idProduct=0002 usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb8: Product: EHCI Host Controller usb usb8: Manufacturer: Linux 2.6.30-rc7 ehci_hcd usb usb8: SerialNumber: 0000:00:1d.7 usb usb8: configuration #1 chosen from 1 choice hub 8-0:1.0: USB hub found hub 8-0:1.0: 8 ports detected usb 5-1: new full speed USB device using uhci_hcd and address 2 parport_pc 00:06: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP(,...)] usb 5-1: not running at top speed; connect to a high speed hub usb 5-1: New USB device found, idVendor=2040, idProduct=9950 usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 5-1: Product: WinTV Nova-DT usb 5-1: Manufacturer: Hauppauge usb 5-1: SerialNumber: 4030248054 usb 5-1: configuration #1 chosen from 1 choice usb usb7: New USB device found, idVendor=1d6b, idProduct=0001 usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb7: Product: OHCI Host Controller usb usb7: Manufacturer: Linux 2.6.30-rc7 ohci_hcd usb usb7: SerialNumber: 0000:02:0a.0 usb usb7: configuration #1 chosen from 1 choice hub 7-0:1.0: USB hub found hub 7-0:1.0: 3 ports detected ehci_hcd 0000:02:09.2: PCI INT C -> GSI 19 (level, low) -> IRQ 19 ehci_hcd 0000:02:09.2: EHCI Host Controller ehci_hcd 0000:02:09.2: new USB bus registered, assigned bus number 9 ehci_hcd 0000:02:09.2: irq 19, io mem 0xfbfffc00 ehci_hcd 0000:02:09.2: USB 2.0 started, EHCI 1.00 usb usb9: New USB device found, idVendor=1d6b, idProduct=0002 usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb9: Product: EHCI Host Controller usb usb9: Manufacturer: Linux 2.6.30-rc7 ehci_hcd usb usb9: SerialNumber: 0000:02:09.2 usb usb9: configuration #1 chosen from 1 choice hub 9-0:1.0: USB hub found hub 9-0:1.0: 4 ports detected ohci_hcd 0000:02:0a.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22 ohci_hcd 0000:02:0a.1: OHCI Host Controller ohci_hcd 0000:02:0a.1: new USB bus registered, assigned bus number 10 ohci_hcd 0000:02:0a.1: irq 22, io mem 0xfbffe000 usb 8-8: new high speed USB device using ehci_hcd and address 4 usb 8-8: New USB device found, idVendor=0409, idProduct=0059 usb 8-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0 usb 8-8: configuration #1 chosen from 1 choice hub 8-8:1.0: USB hub found hub 8-8:1.0: 4 ports detected dib0700: loaded with support for 9 different device-types dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware usb 5-1: firmware: requesting dvb-usb-dib0700-1.20.fw dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' dib0700: firmware download failed at 7 with -71 usbcore: registered new interface driver dvb_usb_dib0700 usb 1-2: new full speed USB device using uhci_hcd and address 2 usb 1-2: New USB device found, idVendor=06bd, idProduct=2061 usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-2: Product: SNAPSCAN usb 1-2: Manufacturer: AGFA usb 1-2: configuration #1 chosen from 1 choice ieee1394: Host added: ID:BUS[0-00:1023] GUID[00110666000013cc] usb usb10: New USB device found, idVendor=1d6b, idProduct=0001 usb usb10: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb10: Product: OHCI Host Controller usb usb10: Manufacturer: Linux 2.6.30-rc7 ohci_hcd usb usb10: SerialNumber: 0000:02:0a.1 usb usb10: configuration #1 chosen from 1 choice hub 10-0:1.0: USB hub found hub 10-0:1.0: 2 ports detected ehci_hcd 0000:02:0a.2: PCI INT C -> GSI 23 (level, low) -> IRQ 23 ehci_hcd 0000:02:0a.2: EHCI Host Controller ehci_hcd 0000:02:0a.2: new USB bus registered, assigned bus number 11 ehci_hcd 0000:02:0a.2: irq 23, io mem 0xfbfff800 usb 2-2: new low speed USB device using uhci_hcd and address 2 ehci_hcd 0000:02:0a.2: USB 2.0 started, EHCI 0.95 usb usb11: New USB device found, idVendor=1d6b, idProduct=0002 usb usb11: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb11: Product: EHCI Host Controller usb usb11: Manufacturer: Linux 2.6.30-rc7 ehci_hcd usb usb11: SerialNumber: 0000:02:0a.2 usb usb11: configuration #1 chosen from 1 choice hub 11-0:1.0: USB hub found hub 11-0:1.0: 5 ports detected usb 2-2: New USB device found, idVendor=045e, idProduct=00f1 usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-2: Product: Microsoft Wireless Desktop Receiver 3.1A usb 2-2: Manufacturer: Microsft usb 2-2: configuration #1 chosen from 1 choice usb 5-1: USB disconnect, address 2 input: Microsft Microsoft Wireless Desktop Receiver 3.1A as /devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/input/input3 generic-usb 0003:045E:00F1.0001: input: USB HID v1.11 Keyboard [Microsft Microsoft Wireless Desktop Receiver 3.1A] on usb-0000:00:1d.1-2/input0 platform microcode: firmware: requesting intel-ucode/0f-06-02 platform microcode: firmware: requesting intel-ucode/0f-06-02 Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba usb 9-1: new high speed USB device using ehci_hcd and address 2 usb 9-1: New USB device found, idVendor=2040, idProduct=9950 usb 9-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 9-1: Product: WinTV Nova-DT usb 9-1: Manufacturer: Hauppauge usb 9-1: SerialNumber: 4030248054 usb 9-1: configuration #1 chosen from 1 choice dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware usb 9-1: firmware: requesting dvb-usb-dib0700-1.20.fw dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' input: Microsft Microsoft Wireless Desktop Receiver 3.1A as /devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.1/input/input4 generic-usb 0003:045E:00F1.0002: input: USB HID v1.11 Mouse [Microsft Microsoft Wireless Desktop Receiver 3.1A] on usb-0000:00:1d.1-2/input1 usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Microcode Update Driver: v2.00 removed. Adding 4096532k swap on /dev/sda5. Priority:-1 extents:1 across:4096532k dib0700: firmware started successfully. eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) DVB: registering adapter 0 frontend 0 (DiBcom 3000MC/P)... MT2060: successfully identified (IF1 = 1230) dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) DVB: registering adapter 1 frontend 0 (DiBcom 3000MC/P)... MT2060: successfully identified (IF1 = 1234) input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1e.0/0000:02:09.2/usb9/9-1/input/input5 dvb-usb: schedule remote query interval to 50 msecs. dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. parport_pc 00:06: disabled ieee1394: Node removed: ID:BUS[0-00:1023] GUID[00110666000013cc] [-- Attachment #3: .config --] [-- Type: application/octet-stream, Size: 54024 bytes --] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.30-rc3 # Sun Jun 7 13:44:45 2009 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_FAST_CMPXCHG_LOCAL=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_HAVE_DYNAMIC_PER_CPU_AREA=y # CONFIG_HAVE_CPUMASK_OF_CPU_MAP is not set CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_X86_32_SMP=y CONFIG_X86_HT=y CONFIG_X86_TRAMPOLINE=y CONFIG_X86_32_LAZY_GS=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y # CONFIG_POSIX_MQUEUE is not set CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set # # RCU Subsystem # CONFIG_CLASSIC_RCU=y # CONFIG_TREE_RCU is not set # CONFIG_PREEMPT_RCU is not set # CONFIG_TREE_RCU_TRACE is not set # CONFIG_PREEMPT_RCU_TRACE is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=16 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y # CONFIG_GROUP_SCHED is not set # CONFIG_CGROUPS is not set # CONFIG_SYSFS_DEPRECATED_V2 is not set # CONFIG_RELAY is not set CONFIG_NAMESPACES=y # CONFIG_UTS_NS is not set # CONFIG_IPC_NS is not set # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set # CONFIG_NET_NS is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set # CONFIG_STRIP_ASM_SYMS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_SLUB_DEBUG=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set # CONFIG_PROFILING is not set # CONFIG_MARKERS is not set CONFIG_HAVE_OPROFILE=y # CONFIG_KPROBES is not set CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_API_DEBUG=y # CONFIG_SLOW_WORK is not set CONFIG_HAVE_GENERIC_DMA_COHERENT=y CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_BSG is not set # CONFIG_BLK_DEV_INTEGRITY is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=m CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_PREEMPT_NOTIFIERS=y # CONFIG_FREEZER is not set # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y # CONFIG_HIGH_RES_TIMERS is not set CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y # CONFIG_SPARSE_IRQ is not set CONFIG_X86_MPPARSE=y # CONFIG_X86_BIGSMP is not set # CONFIG_X86_EXTENDED_PLATFORM is not set CONFIG_SCHED_OMIT_FRAME_POINTER=y # CONFIG_PARAVIRT_GUEST is not set # CONFIG_MEMTEST is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_GENERIC_CPU is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CPU=y CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_INTERNODE_CACHE_BYTES=64 CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_XADD=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=4 CONFIG_X86_DEBUGCTLMSR=y CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_CYRIX_32=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=y CONFIG_CPU_SUP_TRANSMETA_32=y CONFIG_CPU_SUP_UMC_32=y # CONFIG_X86_DS is not set # CONFIG_HPET_TIMER is not set CONFIG_DMI=y # CONFIG_IOMMU_HELPER is not set # CONFIG_IOMMU_API is not set CONFIG_NR_CPUS=2 # CONFIG_SCHED_SMT is not set CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set # CONFIG_X86_MCE_P4THERMAL is not set CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set CONFIG_MICROCODE=m CONFIG_MICROCODE_INTEL=y # CONFIG_MICROCODE_AMD is not set CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # CONFIG_X86_CPU_DEBUG is not set # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_HIGHMEM=y # CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_PHYS_ADDR_T_64BIT is not set CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_UNEVICTABLE_LRU=y CONFIG_HAVE_MLOCK=y CONFIG_HAVE_MLOCKED_PAGE_BIT=y CONFIG_MMU_NOTIFIER=y # CONFIG_HIGHPTE is not set # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set CONFIG_X86_RESERVE_LOW_64K=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_MTRR_SANITIZER is not set CONFIG_X86_PAT=y # CONFIG_EFI is not set CONFIG_SECCOMP=y # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set CONFIG_HZ_1000=y CONFIG_HZ=1000 # CONFIG_SCHED_HRTICK is not set CONFIG_KEXEC=y # CONFIG_CRASH_DUMP is not set CONFIG_PHYSICAL_START=0x100000 # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_ALIGN=0x100000 CONFIG_HOTPLUG_CPU=y # CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y # # Power management and ACPI options # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SUSPEND is not set # CONFIG_HIBERNATION is not set CONFIG_ACPI=y # CONFIG_ACPI_PROCFS is not set # CONFIG_ACPI_PROCFS_POWER is not set CONFIG_ACPI_SYSFS_POWER=y # CONFIG_ACPI_PROC_EVENT is not set # CONFIG_ACPI_AC is not set # CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=y CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set # CONFIG_ACPI_PCI_SLOT is not set CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=y # CONFIG_ACPI_SBS is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # # Bus options (PCI etc.) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set # CONFIG_PCI_GOOLPC is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_DOMAINS=y # CONFIG_PCIEPORTBUS is not set CONFIG_ARCH_SUPPORTS_MSI=y # CONFIG_PCI_MSI is not set # CONFIG_PCI_LEGACY is not set # CONFIG_PCI_STUB is not set CONFIG_HT_IRQ=y # CONFIG_PCI_IOV is not set CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # CONFIG_OLPC is not set # CONFIG_PCCARD is not set # CONFIG_HOTPLUG_PCI is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set CONFIG_HAVE_AOUT=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=m CONFIG_HAVE_ATOMIC_IOMAP=y CONFIG_NET=y # # Networking options # CONFIG_PACKET=m # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=m # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set # CONFIG_XFRM_STATISTICS is not set CONFIG_XFRM_IPCOMP=y CONFIG_NET_KEY=y # CONFIG_NET_KEY_MIGRATE is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y # CONFIG_IP_PNP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m # CONFIG_NET_IPGRE_BROADCAST is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set CONFIG_INET_AH=y CONFIG_INET_ESP=y CONFIG_INET_IPCOMP=y CONFIG_INET_XFRM_TUNNEL=y CONFIG_INET_TUNNEL=y CONFIG_INET_XFRM_MODE_TRANSPORT=m CONFIG_INET_XFRM_MODE_TUNNEL=m # CONFIG_INET_XFRM_MODE_BEET is not set # CONFIG_INET_LRO is not set # CONFIG_INET_DIAG is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_CUBIC=y CONFIG_DEFAULT_TCP_CONG="cubic" # CONFIG_TCP_MD5SIG is not set # CONFIG_IPV6 is not set # CONFIG_NETLABEL is not set # CONFIG_NETWORK_SECMARK is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y # CONFIG_BRIDGE_NETFILTER is not set # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=m # CONFIG_NETFILTER_NETLINK_QUEUE is not set CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_NF_CONNTRACK=m # CONFIG_NF_CT_ACCT is not set # CONFIG_NF_CONNTRACK_MARK is not set # CONFIG_NF_CONNTRACK_EVENTS is not set # CONFIG_NF_CT_PROTO_DCCP is not set # CONFIG_NF_CT_PROTO_SCTP is not set # CONFIG_NF_CT_PROTO_UDPLITE is not set # CONFIG_NF_CONNTRACK_AMANDA is not set CONFIG_NF_CONNTRACK_FTP=m CONFIG_NF_CONNTRACK_H323=m CONFIG_NF_CONNTRACK_IRC=m CONFIG_NF_CONNTRACK_NETBIOS_NS=m # CONFIG_NF_CONNTRACK_PPTP is not set # CONFIG_NF_CONNTRACK_SANE is not set CONFIG_NF_CONNTRACK_SIP=m CONFIG_NF_CONNTRACK_TFTP=m # CONFIG_NF_CT_NETLINK is not set CONFIG_NETFILTER_XTABLES=m # CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set # CONFIG_NETFILTER_XT_TARGET_CONNMARK is not set # CONFIG_NETFILTER_XT_TARGET_MARK is not set CONFIG_NETFILTER_XT_TARGET_NFLOG=m # CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set # CONFIG_NETFILTER_XT_TARGET_RATEEST is not set # CONFIG_NETFILTER_XT_TARGET_TCPMSS is not set # CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set # CONFIG_NETFILTER_XT_MATCH_COMMENT is not set # CONFIG_NETFILTER_XT_MATCH_CONNBYTES is not set # CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is not set # CONFIG_NETFILTER_XT_MATCH_CONNMARK is not set CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m # CONFIG_NETFILTER_XT_MATCH_DCCP is not set # CONFIG_NETFILTER_XT_MATCH_DSCP is not set # CONFIG_NETFILTER_XT_MATCH_ESP is not set # CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set CONFIG_NETFILTER_XT_MATCH_HELPER=m # CONFIG_NETFILTER_XT_MATCH_HL is not set # CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set # CONFIG_NETFILTER_XT_MATCH_LENGTH is not set # CONFIG_NETFILTER_XT_MATCH_LIMIT is not set # CONFIG_NETFILTER_XT_MATCH_MAC is not set # CONFIG_NETFILTER_XT_MATCH_MARK is not set CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m # CONFIG_NETFILTER_XT_MATCH_OWNER is not set # CONFIG_NETFILTER_XT_MATCH_POLICY is not set # CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set # CONFIG_NETFILTER_XT_MATCH_QUOTA is not set # CONFIG_NETFILTER_XT_MATCH_RATEEST is not set # CONFIG_NETFILTER_XT_MATCH_REALM is not set # CONFIG_NETFILTER_XT_MATCH_RECENT is not set # CONFIG_NETFILTER_XT_MATCH_SCTP is not set CONFIG_NETFILTER_XT_MATCH_STATE=m # CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set # CONFIG_NETFILTER_XT_MATCH_STRING is not set # CONFIG_NETFILTER_XT_MATCH_TCPMSS is not set # CONFIG_NETFILTER_XT_MATCH_TIME is not set # CONFIG_NETFILTER_XT_MATCH_U32 is not set # CONFIG_IP_VS is not set # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=m CONFIG_NF_CONNTRACK_IPV4=m CONFIG_NF_CONNTRACK_PROC_COMPAT=y # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=m # CONFIG_IP_NF_MATCH_ADDRTYPE is not set # CONFIG_IP_NF_MATCH_AH is not set # CONFIG_IP_NF_MATCH_ECN is not set # CONFIG_IP_NF_MATCH_TTL is not set CONFIG_IP_NF_FILTER=m # CONFIG_IP_NF_TARGET_REJECT is not set CONFIG_IP_NF_TARGET_LOG=m # CONFIG_IP_NF_TARGET_ULOG is not set CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m # CONFIG_IP_NF_TARGET_NETMAP is not set # CONFIG_IP_NF_TARGET_REDIRECT is not set # CONFIG_NF_NAT_SNMP_BASIC is not set CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_TFTP=m # CONFIG_NF_NAT_AMANDA is not set # CONFIG_NF_NAT_PPTP is not set CONFIG_NF_NAT_H323=m CONFIG_NF_NAT_SIP=m # CONFIG_IP_NF_MANGLE is not set # CONFIG_IP_NF_TARGET_TTL is not set # CONFIG_IP_NF_RAW is not set # CONFIG_IP_NF_SECURITY is not set # CONFIG_IP_NF_ARPTABLES is not set # CONFIG_IP_DCCP is not set # CONFIG_IP_SCTP is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set CONFIG_STP=m CONFIG_BRIDGE=m # CONFIG_NET_DSA is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set CONFIG_LLC=m # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_PHONET is not set # CONFIG_NET_SCHED is not set # CONFIG_DCB is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set CONFIG_IRDA=m # # IrDA protocols # # CONFIG_IRLAN is not set # CONFIG_IRCOMM is not set # CONFIG_IRDA_ULTRA is not set # # IrDA options # # CONFIG_IRDA_CACHE_LAST_LSAP is not set # CONFIG_IRDA_FAST_RR is not set # CONFIG_IRDA_DEBUG is not set # # Infrared-port device drivers # # # SIR device drivers # CONFIG_IRTTY_SIR=m # # Dongle support # # CONFIG_DONGLE is not set # CONFIG_KINGSUN_DONGLE is not set # CONFIG_KSDAZZLE_DONGLE is not set # CONFIG_KS959_DONGLE is not set # # FIR device drivers # # CONFIG_USB_IRDA is not set CONFIG_SIGMATEL_FIR=m # CONFIG_NSC_FIR is not set # CONFIG_WINBOND_FIR is not set # CONFIG_TOSHIBA_FIR is not set # CONFIG_SMC_IRCC_FIR is not set # CONFIG_ALI_FIR is not set # CONFIG_VLSI_FIR is not set # CONFIG_VIA_FIR is not set # CONFIG_MCS_FIR is not set CONFIG_BT=m CONFIG_BT_L2CAP=m # CONFIG_BT_SCO is not set CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y # CONFIG_BT_BNEP is not set CONFIG_BT_HIDP=m # # Bluetooth device drivers # CONFIG_BT_HCIBTUSB=m CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_BCSP=y # CONFIG_BT_HCIUART_LL is not set # CONFIG_BT_HCIBCM203X is not set # CONFIG_BT_HCIBPA10X is not set # CONFIG_BT_HCIBFUSB is not set # CONFIG_BT_HCIVHCI is not set # CONFIG_AF_RXRPC is not set # CONFIG_WIRELESS is not set # CONFIG_WIMAX is not set # CONFIG_RFKILL is not set # CONFIG_NET_9P is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="" CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y # CONFIG_FIRMWARE_IN_KERNEL is not set CONFIG_EXTRA_FIRMWARE="" # CONFIG_SYS_HYPERVISOR is not set # CONFIG_CONNECTOR is not set # CONFIG_MTD is not set CONFIG_PARPORT=m CONFIG_PARPORT_PC=m # CONFIG_PARPORT_SERIAL is not set CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_GSC is not set # CONFIG_PARPORT_AX88796 is not set # CONFIG_PARPORT_1284 is not set CONFIG_PNP=y CONFIG_PNP_DEBUG_MESSAGES=y # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y CONFIG_BLK_DEV_FD=m # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=m # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_UB is not set # CONFIG_BLK_DEV_RAM is not set CONFIG_CDROM_PKTCDVD=m CONFIG_CDROM_PKTCDVD_BUFFERS=8 CONFIG_CDROM_PKTCDVD_WCACHE=y # CONFIG_ATA_OVER_ETH is not set # CONFIG_BLK_DEV_HD is not set # CONFIG_MISC_DEVICES is not set CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # # CONFIG_RAID_ATTRS is not set CONFIG_SCSI=y CONFIG_SCSI_DMA=y # CONFIG_SCSI_TGT is not set # CONFIG_SCSI_NETLINK is not set CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set # CONFIG_CHR_DEV_SG is not set # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # CONFIG_SCSI_SCAN_ASYNC is not set CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # CONFIG_SCSI_SRP_ATTRS is not set # CONFIG_SCSI_LOWLEVEL is not set # CONFIG_SCSI_DH is not set # CONFIG_SCSI_OSD_INITIATOR is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y # CONFIG_SATA_PMP is not set # CONFIG_SATA_AHCI is not set # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # CONFIG_SATA_SVW is not set CONFIG_ATA_PIIX=y # CONFIG_SATA_MV is not set # CONFIG_SATA_NV is not set # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set # CONFIG_PATA_ACPI is not set # CONFIG_PATA_ALI is not set # CONFIG_PATA_AMD is not set # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD640_PCI is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CS5535 is not set # CONFIG_PATA_CS5536 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_ATA_GENERIC is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NINJA32 is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_NS87415 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set # CONFIG_PATA_SCH is not set # CONFIG_MD is not set # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # # Enable only one of the two stacks, unless you know what you are doing # # CONFIG_FIREWIRE is not set CONFIG_IEEE1394=m CONFIG_IEEE1394_OHCI1394=m # CONFIG_IEEE1394_PCILYNX is not set CONFIG_IEEE1394_SBP2=m # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set # CONFIG_IEEE1394_ETH1394_ROM_ENTRY is not set # CONFIG_IEEE1394_ETH1394 is not set CONFIG_IEEE1394_RAWIO=m CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_DV1394=m # CONFIG_IEEE1394_VERBOSEDEBUG is not set # CONFIG_I2O is not set # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y CONFIG_COMPAT_NET_DEV_OPS=y CONFIG_DUMMY=m # CONFIG_BONDING is not set # CONFIG_MACVLAN is not set # CONFIG_EQUALIZER is not set CONFIG_TUN=m # CONFIG_VETH is not set # CONFIG_NET_SB1000 is not set # CONFIG_ARCNET is not set # CONFIG_PHYLIB is not set CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set # CONFIG_CASSINI is not set # CONFIG_NET_VENDOR_3COM is not set # CONFIG_ETHOC is not set # CONFIG_DNET is not set # CONFIG_NET_TULIP is not set # CONFIG_HP100 is not set # CONFIG_IBM_NEW_EMAC_ZMII is not set # CONFIG_IBM_NEW_EMAC_RGMII is not set # CONFIG_IBM_NEW_EMAC_TAH is not set # CONFIG_IBM_NEW_EMAC_EMAC4 is not set # CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set CONFIG_NET_PCI=y # CONFIG_PCNET32 is not set # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_B44 is not set # CONFIG_FORCEDETH is not set # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set # CONFIG_NE2K_PCI is not set # CONFIG_8139CP is not set CONFIG_8139TOO=y # CONFIG_8139TOO_PIO is not set # CONFIG_8139TOO_TUNE_TWISTER is not set # CONFIG_8139TOO_8129 is not set # CONFIG_8139_OLD_RX_RESET is not set # CONFIG_R6040 is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SMSC9420 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_SC92031 is not set # CONFIG_NET_POCKET is not set # CONFIG_ATL2 is not set # CONFIG_NETDEV_1000 is not set # CONFIG_NETDEV_10000 is not set # CONFIG_TR is not set # # Wireless LAN # # CONFIG_WLAN_PRE80211 is not set # CONFIG_WLAN_80211 is not set # # Enable WiMAX (Networking options) to see the WiMAX drivers # # # USB Network Adapters # # CONFIG_USB_CATC is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set # CONFIG_USB_USBNET is not set # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PLIP is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_NET_FC is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_ISDN is not set # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y CONFIG_INPUT_FF_MEMLESS=m # CONFIG_INPUT_POLLDEV is not set # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=m # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set # CONFIG_KEYBOARD_STOWAWAY is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y # CONFIG_MOUSE_PS2_ELANTECH is not set # CONFIG_MOUSE_PS2_TOUCHKIT is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_APPLETOUCH is not set # CONFIG_MOUSE_BCM5974 is not set # CONFIG_MOUSE_VSXXXAA is not set CONFIG_INPUT_JOYSTICK=y # CONFIG_JOYSTICK_ANALOG is not set # CONFIG_JOYSTICK_A3D is not set # CONFIG_JOYSTICK_ADI is not set # CONFIG_JOYSTICK_COBRA is not set # CONFIG_JOYSTICK_GF2K is not set # CONFIG_JOYSTICK_GRIP is not set # CONFIG_JOYSTICK_GRIP_MP is not set # CONFIG_JOYSTICK_GUILLEMOT is not set # CONFIG_JOYSTICK_INTERACT is not set CONFIG_JOYSTICK_SIDEWINDER=m # CONFIG_JOYSTICK_TMDC is not set # CONFIG_JOYSTICK_IFORCE is not set # CONFIG_JOYSTICK_WARRIOR is not set # CONFIG_JOYSTICK_MAGELLAN is not set # CONFIG_JOYSTICK_SPACEORB is not set # CONFIG_JOYSTICK_SPACEBALL is not set # CONFIG_JOYSTICK_STINGER is not set # CONFIG_JOYSTICK_TWIDJOY is not set # CONFIG_JOYSTICK_ZHENHUA is not set # CONFIG_JOYSTICK_DB9 is not set # CONFIG_JOYSTICK_GAMECON is not set # CONFIG_JOYSTICK_TURBOGRAFX is not set # CONFIG_JOYSTICK_JOYDUMP is not set # CONFIG_JOYSTICK_XPAD is not set # CONFIG_INPUT_TABLET is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=m # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PARKBD is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set CONFIG_GAMEPORT=m CONFIG_GAMEPORT_NS558=m # CONFIG_GAMEPORT_L4 is not set # CONFIG_GAMEPORT_EMU10K1 is not set # CONFIG_GAMEPORT_FM801 is not set # # Character devices # CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_VT_HW_CONSOLE_BINDING is not set # CONFIG_DEVKMEM is not set # CONFIG_SERIAL_NONSTANDARD is not set # CONFIG_NOZOMI is not set # # Serial drivers # CONFIG_SERIAL_8250=y # CONFIG_SERIAL_8250_CONSOLE is not set CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y # CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=128 CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set # CONFIG_PPDEV is not set # CONFIG_IPMI_HANDLER is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set CONFIG_RTC=y # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_NSC_GPIO is not set # CONFIG_CS5535_GPIO is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HPET is not set # CONFIG_HANGCHECK_TIMER is not set # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set CONFIG_DEVPORT=y CONFIG_I2C=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_CHARDEV=m CONFIG_I2C_HELPER_AUTO=y # # I2C Hardware Bus support # # # PC SMBus host controller drivers # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set CONFIG_I2C_I801=m # CONFIG_I2C_ISCH is not set CONFIG_I2C_PIIX4=m # CONFIG_I2C_NFORCE2 is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_VIA is not set # CONFIG_I2C_VIAPRO is not set # # I2C system bus drivers (mostly embedded / system-on-chip) # # CONFIG_I2C_OCORES is not set # CONFIG_I2C_SIMTEC is not set # # External I2C/SMBus adapter drivers # # CONFIG_I2C_PARPORT is not set # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_TAOS_EVM is not set # CONFIG_I2C_TINY_USB is not set # # Graphics adapter I2C/DDC channel drivers # # CONFIG_I2C_VOODOO3 is not set # # Other I2C/SMBus bus drivers # # CONFIG_I2C_PCA_PLATFORM is not set # CONFIG_I2C_STUB is not set # CONFIG_SCx200_ACB is not set # # Miscellaneous I2C Chip support # # CONFIG_DS1682 is not set # CONFIG_SENSORS_PCF8574 is not set # CONFIG_PCF8575 is not set # CONFIG_SENSORS_PCA9539 is not set # CONFIG_SENSORS_MAX6875 is not set # CONFIG_SENSORS_TSL2550 is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # CONFIG_SPI is not set CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y # CONFIG_GPIOLIB is not set # CONFIG_W1 is not set CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PDA_POWER is not set # CONFIG_BATTERY_DS2760 is not set # CONFIG_BATTERY_BQ27x00 is not set CONFIG_HWMON=y CONFIG_HWMON_VID=m # CONFIG_SENSORS_ABITUGURU is not set # CONFIG_SENSORS_ABITUGURU3 is not set # CONFIG_SENSORS_AD7414 is not set # CONFIG_SENSORS_AD7418 is not set # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1029 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ADT7462 is not set # CONFIG_SENSORS_ADT7470 is not set # CONFIG_SENSORS_ADT7473 is not set # CONFIG_SENSORS_ADT7475 is not set # CONFIG_SENSORS_K8TEMP is not set # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATK0110 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_I5K_AMB is not set # CONFIG_SENSORS_F71805F is not set # CONFIG_SENSORS_F71882FG is not set # CONFIG_SENSORS_F75375S is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_FSCPOS is not set # CONFIG_SENSORS_FSCHMD is not set # CONFIG_SENSORS_G760A is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_CORETEMP is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_LM93 is not set # CONFIG_SENSORS_LTC4215 is not set # CONFIG_SENSORS_LTC4245 is not set # CONFIG_SENSORS_LM95241 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_MAX6650 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_PC87427 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_DME1737 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47M192 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_ADS7828 is not set # CONFIG_SENSORS_THMC50 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_VT1211 is not set # CONFIG_SENSORS_VT8231 is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83791D is not set # CONFIG_SENSORS_W83792D is not set # CONFIG_SENSORS_W83793 is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83L786NG is not set # CONFIG_SENSORS_W83627HF is not set CONFIG_SENSORS_W83627EHF=m # CONFIG_SENSORS_HDAPS is not set # CONFIG_SENSORS_LIS3LV02D is not set # CONFIG_SENSORS_APPLESMC is not set # CONFIG_HWMON_DEBUG_CHIP is not set CONFIG_THERMAL=y # CONFIG_THERMAL_HWMON is not set # CONFIG_WATCHDOG is not set CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # # CONFIG_SSB is not set # # Multifunction device drivers # # CONFIG_MFD_CORE is not set # CONFIG_MFD_SM501 is not set # CONFIG_HTC_PASIC3 is not set # CONFIG_TWL4030_CORE is not set # CONFIG_MFD_TMIO is not set # CONFIG_PMIC_DA903X is not set # CONFIG_MFD_WM8400 is not set # CONFIG_MFD_WM8350_I2C is not set # CONFIG_MFD_PCF50633 is not set # CONFIG_REGULATOR is not set # # Multimedia devices # # # Multimedia core support # CONFIG_VIDEO_DEV=m CONFIG_VIDEO_V4L2_COMMON=m # CONFIG_VIDEO_ALLOW_V4L1 is not set CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_DVB_CORE=m CONFIG_VIDEO_MEDIA=m # # Multimedia drivers # CONFIG_MEDIA_ATTACH=y CONFIG_MEDIA_TUNER=m # CONFIG_MEDIA_TUNER_CUSTOMISE is not set CONFIG_MEDIA_TUNER_SIMPLE=m CONFIG_MEDIA_TUNER_TDA8290=m CONFIG_MEDIA_TUNER_TDA9887=m CONFIG_MEDIA_TUNER_TEA5761=m CONFIG_MEDIA_TUNER_TEA5767=m CONFIG_MEDIA_TUNER_MT20XX=m CONFIG_MEDIA_TUNER_MT2060=m CONFIG_MEDIA_TUNER_MT2266=m CONFIG_MEDIA_TUNER_XC2028=m CONFIG_MEDIA_TUNER_XC5000=m CONFIG_MEDIA_TUNER_MXL5007T=m CONFIG_MEDIA_TUNER_MC44S803=m CONFIG_VIDEO_V4L2=m CONFIG_VIDEO_CAPTURE_DRIVERS=y # CONFIG_VIDEO_ADV_DEBUG is not set # CONFIG_VIDEO_FIXED_MINOR_RANGES is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y # CONFIG_VIDEO_VIVI is not set # CONFIG_VIDEO_BT848 is not set # CONFIG_VIDEO_SAA5246A is not set # CONFIG_VIDEO_SAA5249 is not set # CONFIG_VIDEO_SAA7134 is not set # CONFIG_VIDEO_HEXIUM_ORION is not set # CONFIG_VIDEO_HEXIUM_GEMINI is not set # CONFIG_VIDEO_CX88 is not set # CONFIG_VIDEO_CX23885 is not set # CONFIG_VIDEO_AU0828 is not set # CONFIG_VIDEO_IVTV is not set # CONFIG_VIDEO_CX18 is not set # CONFIG_VIDEO_CAFE_CCIC is not set # CONFIG_SOC_CAMERA is not set CONFIG_V4L_USB_DRIVERS=y # CONFIG_USB_VIDEO_CLASS is not set CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_GSPCA=m # CONFIG_USB_M5602 is not set # CONFIG_USB_STV06XX is not set # CONFIG_USB_GSPCA_CONEX is not set # CONFIG_USB_GSPCA_ETOMS is not set # CONFIG_USB_GSPCA_FINEPIX is not set # CONFIG_USB_GSPCA_MARS is not set # CONFIG_USB_GSPCA_MR97310A is not set # CONFIG_USB_GSPCA_OV519 is not set # CONFIG_USB_GSPCA_OV534 is not set # CONFIG_USB_GSPCA_PAC207 is not set # CONFIG_USB_GSPCA_PAC7311 is not set # CONFIG_USB_GSPCA_SONIXB is not set # CONFIG_USB_GSPCA_SONIXJ is not set # CONFIG_USB_GSPCA_SPCA500 is not set # CONFIG_USB_GSPCA_SPCA501 is not set # CONFIG_USB_GSPCA_SPCA505 is not set # CONFIG_USB_GSPCA_SPCA506 is not set # CONFIG_USB_GSPCA_SPCA508 is not set # CONFIG_USB_GSPCA_SPCA561 is not set # CONFIG_USB_GSPCA_SQ905 is not set # CONFIG_USB_GSPCA_SQ905C is not set # CONFIG_USB_GSPCA_STK014 is not set # CONFIG_USB_GSPCA_SUNPLUS is not set # CONFIG_USB_GSPCA_T613 is not set # CONFIG_USB_GSPCA_TV8532 is not set # CONFIG_USB_GSPCA_VC032X is not set CONFIG_USB_GSPCA_ZC3XX=m # CONFIG_VIDEO_PVRUSB2 is not set # CONFIG_VIDEO_HDPVR is not set # CONFIG_VIDEO_EM28XX is not set # CONFIG_VIDEO_CX231XX is not set # CONFIG_VIDEO_USBVISION is not set # CONFIG_USB_ET61X251 is not set # CONFIG_USB_SN9C102 is not set # CONFIG_USB_ZC0301 is not set CONFIG_USB_PWC_INPUT_EVDEV=y # CONFIG_USB_ZR364XX is not set # CONFIG_USB_STKWEBCAM is not set # CONFIG_USB_S2255 is not set # CONFIG_RADIO_ADAPTERS is not set # CONFIG_DVB_DYNAMIC_MINORS is not set CONFIG_DVB_CAPTURE_DRIVERS=y # # Supported SAA7146 based PCI Adapters # # CONFIG_TTPCI_EEPROM is not set # CONFIG_DVB_AV7110 is not set # CONFIG_DVB_BUDGET_CORE is not set # # Supported USB Adapters # CONFIG_DVB_USB=m # CONFIG_DVB_USB_DEBUG is not set # CONFIG_DVB_USB_A800 is not set # CONFIG_DVB_USB_DIBUSB_MB is not set # CONFIG_DVB_USB_DIBUSB_MC is not set CONFIG_DVB_USB_DIB0700=m # CONFIG_DVB_USB_UMT_010 is not set # CONFIG_DVB_USB_CXUSB is not set # CONFIG_DVB_USB_M920X is not set # CONFIG_DVB_USB_GL861 is not set # CONFIG_DVB_USB_AU6610 is not set # CONFIG_DVB_USB_DIGITV is not set # CONFIG_DVB_USB_VP7045 is not set # CONFIG_DVB_USB_VP702X is not set # CONFIG_DVB_USB_GP8PSK is not set # CONFIG_DVB_USB_NOVA_T_USB2 is not set # CONFIG_DVB_USB_TTUSB2 is not set CONFIG_DVB_USB_DTT200U=m # CONFIG_DVB_USB_OPERA1 is not set # CONFIG_DVB_USB_AF9005 is not set # CONFIG_DVB_USB_DW2102 is not set # CONFIG_DVB_USB_CINERGY_T2 is not set # CONFIG_DVB_USB_ANYSEE is not set # CONFIG_DVB_USB_DTV5100 is not set # CONFIG_DVB_USB_AF9015 is not set # CONFIG_DVB_USB_CE6230 is not set # CONFIG_DVB_TTUSB_BUDGET is not set # CONFIG_DVB_TTUSB_DEC is not set # CONFIG_DVB_SIANO_SMS1XXX is not set # # Supported FlexCopII (B2C2) Adapters # # CONFIG_DVB_B2C2_FLEXCOP is not set # # Supported BT878 Adapters # # # Supported Pluto2 Adapters # # CONFIG_DVB_PLUTO2 is not set # # Supported SDMC DM1105 Adapters # # CONFIG_DVB_DM1105 is not set # # Supported FireWire (IEEE 1394) Adapters # # CONFIG_DVB_FIREDTV is not set # # Supported DVB Frontends # # CONFIG_DVB_FE_CUSTOMISE is not set CONFIG_DVB_DIB3000MC=m CONFIG_DVB_DIB7000M=m CONFIG_DVB_DIB7000P=m CONFIG_DVB_LGDT3305=m CONFIG_DVB_S5H1411=m CONFIG_DVB_TUNER_DIB0070=m # CONFIG_DAB is not set # # Graphics support # CONFIG_AGP=y # CONFIG_AGP_ALI is not set # CONFIG_AGP_ATI is not set # CONFIG_AGP_AMD is not set # CONFIG_AGP_AMD64 is not set CONFIG_AGP_INTEL=y # CONFIG_AGP_NVIDIA is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_SWORKS is not set # CONFIG_AGP_VIA is not set # CONFIG_AGP_EFFICEON is not set # CONFIG_DRM is not set # CONFIG_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set # CONFIG_FB is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_VGACON_SOFT_SCROLLBACK is not set CONFIG_DUMMY_CONSOLE=y CONFIG_SOUND=y CONFIG_SOUND_OSS_CORE=y CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=y # CONFIG_SND_SEQ_DUMMY is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_RTCTIMER=y CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y # CONFIG_SND_DYNAMIC_MINORS is not set # CONFIG_SND_SUPPORT_OLD_API is not set # CONFIG_SND_VERBOSE_PROCFS is not set # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_VMASTER=y CONFIG_SND_MPU401_UART=m CONFIG_SND_AC97_CODEC=y CONFIG_SND_DRIVERS=y # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_MTS64 is not set # CONFIG_SND_SERIAL_U16550 is not set CONFIG_SND_MPU401=m # CONFIG_SND_PORTMAN2X4 is not set # CONFIG_SND_AC97_POWER_SAVE is not set CONFIG_SND_PCI=y # CONFIG_SND_AD1889 is not set # CONFIG_SND_ALS300 is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_ALI5451 is not set # CONFIG_SND_ATIIXP is not set # CONFIG_SND_ATIIXP_MODEM is not set # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AW2 is not set # CONFIG_SND_AZT3328 is not set # CONFIG_SND_BT87X is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_OXYGEN is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS5530 is not set # CONFIG_SND_CS5535AUDIO is not set # CONFIG_SND_DARLA20 is not set # CONFIG_SND_GINA20 is not set # CONFIG_SND_LAYLA20 is not set # CONFIG_SND_DARLA24 is not set # CONFIG_SND_GINA24 is not set # CONFIG_SND_LAYLA24 is not set # CONFIG_SND_MONA is not set # CONFIG_SND_MIA is not set # CONFIG_SND_ECHO3G is not set # CONFIG_SND_INDIGO is not set # CONFIG_SND_INDIGOIO is not set # CONFIG_SND_INDIGODJ is not set # CONFIG_SND_INDIGOIOX is not set # CONFIG_SND_INDIGODJX is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_EMU10K1X is not set # CONFIG_SND_ENS1370 is not set # CONFIG_SND_ENS1371 is not set # CONFIG_SND_ES1938 is not set # CONFIG_SND_ES1968 is not set # CONFIG_SND_FM801 is not set # CONFIG_SND_HDA_INTEL is not set # CONFIG_SND_HDSP is not set # CONFIG_SND_HDSPM is not set # CONFIG_SND_HIFIER is not set # CONFIG_SND_ICE1712 is not set # CONFIG_SND_ICE1724 is not set CONFIG_SND_INTEL8X0=y # CONFIG_SND_INTEL8X0M is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_PCXHR is not set # CONFIG_SND_RIPTIDE is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set # CONFIG_SND_RME9652 is not set # CONFIG_SND_SIS7019 is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VIRTUOSO is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_YMFPCI is not set # CONFIG_SND_USB is not set # CONFIG_SND_SOC is not set # CONFIG_SOUND_PRIME is not set CONFIG_AC97_BUS=y CONFIG_HID_SUPPORT=y CONFIG_HID=y # CONFIG_HID_DEBUG is not set # CONFIG_HIDRAW is not set # # USB Input Devices # CONFIG_USB_HID=m # CONFIG_HID_PID is not set # CONFIG_USB_HIDDEV is not set # # Special HID drivers # CONFIG_HID_A4TECH=m CONFIG_HID_APPLE=m CONFIG_HID_BELKIN=m CONFIG_HID_CHERRY=m CONFIG_HID_CHICONY=m CONFIG_HID_CYPRESS=m # CONFIG_DRAGONRISE_FF is not set CONFIG_HID_EZKEY=m CONFIG_HID_KYE=m CONFIG_HID_GYRATION=m CONFIG_HID_KENSINGTON=m CONFIG_HID_LOGITECH=m # CONFIG_LOGITECH_FF is not set # CONFIG_LOGIRUMBLEPAD2_FF is not set CONFIG_HID_MICROSOFT=m CONFIG_HID_MONTEREY=m CONFIG_HID_NTRIG=m CONFIG_HID_PANTHERLORD=m # CONFIG_PANTHERLORD_FF is not set CONFIG_HID_PETALYNX=m CONFIG_HID_SAMSUNG=m CONFIG_HID_SONY=m CONFIG_HID_SUNPLUS=m # CONFIG_GREENASIA_FF is not set CONFIG_HID_TOPSEED=m # CONFIG_THRUSTMASTER_FF is not set # CONFIG_ZEROPLUS_FF is not set CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=m # CONFIG_USB_DEBUG is not set CONFIG_USB_ANNOUNCE_NEW_DEVICES=y # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_SUSPEND is not set # CONFIG_USB_OTG is not set # CONFIG_USB_MON is not set # CONFIG_USB_WUSB is not set # CONFIG_USB_WUSB_CBAF is not set # # USB Host Controller Drivers # # CONFIG_USB_C67X00_HCD is not set CONFIG_USB_EHCI_HCD=m # CONFIG_USB_EHCI_ROOT_HUB_TT is not set # CONFIG_USB_EHCI_TT_NEWSCHED is not set # CONFIG_USB_OXU210HP_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_ISP1760_HCD is not set CONFIG_USB_OHCI_HCD=m # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=m # CONFIG_USB_SL811_HCD is not set # CONFIG_USB_R8A66597_HCD is not set # CONFIG_USB_WHCI_HCD is not set # CONFIG_USB_HWA_HCD is not set # # Enable Host or Gadget support to see Inventra options # # # USB Device Class drivers # # CONFIG_USB_ACM is not set CONFIG_USB_PRINTER=m # CONFIG_USB_WDM is not set # CONFIG_USB_TMC is not set # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_STORAGE_ALAUDA is not set # CONFIG_USB_STORAGE_ONETOUCH is not set # CONFIG_USB_STORAGE_KARMA is not set # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # # USB port drivers # # CONFIG_USB_USS720 is not set # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_ADUTUX is not set # CONFIG_USB_SEVSEG is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_BERRY_CHARGE is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYPRESS_CY7C63 is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_FTDI_ELAN is not set # CONFIG_USB_APPLEDISPLAY is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TRANCEVIBRATOR is not set # CONFIG_USB_IOWARRIOR is not set # CONFIG_USB_TEST is not set # CONFIG_USB_ISIGHTFW is not set # CONFIG_USB_VST is not set # CONFIG_USB_GADGET is not set # # OTG and related infrastructure # # CONFIG_NOP_USB_XCEIV is not set # CONFIG_UWB is not set # CONFIG_MMC is not set # CONFIG_MEMSTICK is not set # CONFIG_NEW_LEDS is not set # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set # CONFIG_EDAC is not set # CONFIG_RTC_CLASS is not set # CONFIG_DMADEVICES is not set # CONFIG_AUXDISPLAY is not set # CONFIG_UIO is not set # CONFIG_STAGING is not set # CONFIG_X86_PLATFORM_DEVICES is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_FIRMWARE_MEMMAP=y # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set # CONFIG_DMIID is not set # CONFIG_ISCSI_IBFT_FIND is not set # # File systems # CONFIG_EXT2_FS=m # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_EXT4_FS=m # CONFIG_EXT4DEV_COMPAT is not set # CONFIG_EXT4_FS_XATTR is not set CONFIG_JBD=y CONFIG_JBD2=m CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=m # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_REISERFS_FS_XATTR is not set # CONFIG_JFS_FS is not set # CONFIG_FS_POSIX_ACL is not set CONFIG_FILE_LOCKING=y CONFIG_XFS_FS=m # CONFIG_XFS_QUOTA is not set # CONFIG_XFS_POSIX_ACL is not set # CONFIG_XFS_RT is not set # CONFIG_XFS_DEBUG is not set # CONFIG_OCFS2_FS is not set # CONFIG_BTRFS_FS is not set CONFIG_DNOTIFY=y CONFIG_INOTIFY=y # CONFIG_INOTIFY_USER is not set # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set CONFIG_FUSE_FS=m # # Caches # # CONFIG_FSCACHE is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=m CONFIG_JOLIET=y # CONFIG_ZISOFS is not set CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set # CONFIG_CONFIGFS_FS is not set # CONFIG_MISC_FILESYSTEMS is not set CONFIG_NETWORK_FILESYSTEMS=y # CONFIG_NFS_FS is not set # CONFIG_NFSD is not set CONFIG_EXPORTFS=m CONFIG_SMB_FS=m # CONFIG_SMB_NLS_DEFAULT is not set CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set # CONFIG_CIFS_WEAK_PW_HASH is not set # CONFIG_CIFS_XATTR is not set # CONFIG_CIFS_DEBUG2 is not set # CONFIG_CIFS_EXPERIMENTAL is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_KARMA_PARTITION is not set # CONFIG_EFI_PARTITION is not set # CONFIG_SYSV68_PARTITION is not set CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set CONFIG_NLS_CODEPAGE_850=m # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set CONFIG_NLS_ISO8859_1=y # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set CONFIG_NLS_ISO8859_15=m # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set CONFIG_NLS_UTF8=m # CONFIG_DLM is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set CONFIG_ENABLE_WARN_DEPRECATED=y CONFIG_ENABLE_MUST_CHECK=y CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y CONFIG_UNUSED_SYMBOLS=y # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set # CONFIG_DEBUG_KERNEL is not set # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_SLUB_STATS is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_MEMORY_INIT=y CONFIG_ARCH_WANT_FRAME_POINTERS=y # CONFIG_FRAME_POINTER is not set # CONFIG_RCU_CPU_STALL_DETECTOR is not set # CONFIG_LATENCYTOP is not set CONFIG_SYSCTL_SYSCALL_CHECK=y CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_FTRACE_SYSCALLS=y CONFIG_TRACING_SUPPORT=y # # Tracers # # CONFIG_FUNCTION_TRACER is not set # CONFIG_IRQSOFF_TRACER is not set # CONFIG_PREEMPT_TRACER is not set # CONFIG_SYSPROF_TRACER is not set # CONFIG_SCHED_TRACER is not set # CONFIG_CONTEXT_SWITCH_TRACER is not set # CONFIG_EVENT_TRACER is not set # CONFIG_FTRACE_SYSCALLS is not set # CONFIG_BOOT_TRACER is not set # CONFIG_TRACE_BRANCH_PROFILING is not set # CONFIG_POWER_TRACER is not set # CONFIG_STACK_TRACER is not set # CONFIG_KMEMTRACE is not set # CONFIG_WORKQUEUE_TRACER is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_MMIOTRACE is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y CONFIG_STRICT_DEVMEM=y CONFIG_X86_VERBOSE_BOOTUP=y CONFIG_EARLY_PRINTK=y # CONFIG_EARLY_PRINTK_DBGP is not set CONFIG_4KSTACKS=y CONFIG_DOUBLEFAULT=y CONFIG_HAVE_MMIOTRACE_SUPPORT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 # CONFIG_OPTIMIZE_INLINING is not set # # Security options # # CONFIG_KEYS is not set CONFIG_SECURITY=y # CONFIG_SECURITYFS is not set # CONFIG_SECURITY_NETWORK is not set # CONFIG_SECURITY_PATH is not set # CONFIG_SECURITY_FILE_CAPABILITIES is not set CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0 # CONFIG_SECURITY_TOMOYO is not set # CONFIG_IMA is not set CONFIG_CRYPTO=y # # Crypto core or helper # # CONFIG_CRYPTO_FIPS is not set CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=y CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y # CONFIG_CRYPTO_GF128MUL is not set # CONFIG_CRYPTO_NULL is not set CONFIG_CRYPTO_WORKQUEUE=y # CONFIG_CRYPTO_CRYPTD is not set CONFIG_CRYPTO_AUTHENC=y # CONFIG_CRYPTO_TEST is not set # # Authenticated Encryption with Associated Data # # CONFIG_CRYPTO_CCM is not set # CONFIG_CRYPTO_GCM is not set # CONFIG_CRYPTO_SEQIV is not set # # Block modes # CONFIG_CRYPTO_CBC=y # CONFIG_CRYPTO_CTR is not set # CONFIG_CRYPTO_CTS is not set CONFIG_CRYPTO_ECB=m # CONFIG_CRYPTO_LRW is not set CONFIG_CRYPTO_PCBC=m # CONFIG_CRYPTO_XTS is not set # # Hash modes # CONFIG_CRYPTO_HMAC=y # CONFIG_CRYPTO_XCBC is not set # # Digest # # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_CRC32C_INTEL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_RMD128 is not set # CONFIG_CRYPTO_RMD160 is not set # CONFIG_CRYPTO_RMD256 is not set # CONFIG_CRYPTO_RMD320 is not set CONFIG_CRYPTO_SHA1=y # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_TGR192 is not set # CONFIG_CRYPTO_WP512 is not set # # Ciphers # CONFIG_CRYPTO_AES=m # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_ANUBIS is not set CONFIG_CRYPTO_ARC4=m # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_CAMELLIA is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_FCRYPT is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_SALSA20 is not set # CONFIG_CRYPTO_SALSA20_586 is not set # CONFIG_CRYPTO_SEED is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_586 is not set # # Compression # CONFIG_CRYPTO_DEFLATE=y # CONFIG_CRYPTO_ZLIB is not set # CONFIG_CRYPTO_LZO is not set # # Random Number Generation # # CONFIG_CRYPTO_ANSI_CPRNG is not set # CONFIG_CRYPTO_HW is not set CONFIG_HAVE_KVM=y CONFIG_HAVE_KVM_IRQCHIP=y CONFIG_VIRTUALIZATION=y CONFIG_KVM=m CONFIG_KVM_INTEL=m # CONFIG_KVM_AMD is not set # CONFIG_KVM_TRACE is not set # CONFIG_LGUEST is not set # CONFIG_VIRTIO_PCI is not set # CONFIG_VIRTIO_BALLOON is not set # CONFIG_BINARY_PRINTF is not set # # Library routines # CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_LAST_BIT=y CONFIG_CRC_CCITT=m CONFIG_CRC16=m CONFIG_CRC_T10DIF=y CONFIG_CRC_ITU_T=m CONFIG_CRC32=y # CONFIG_CRC7 is not set # CONFIG_LIBCRC32C is not set CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_NLATTR=y ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-07 18:38 ` Chris Clayton @ 2009-06-07 22:31 ` Jaswinder Singh Rajput 2009-06-07 22:55 ` NeilBrown 0 siblings, 1 reply; 38+ messages in thread From: Jaswinder Singh Rajput @ 2009-06-07 22:31 UTC (permalink / raw) To: Chris Clayton; +Cc: linux-kernel, James Bottomley, scsi, NeilBrown, Tejun Heo On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: > 2009/6/7 Jaswinder Singh Rajput <jaswinder@kernel.org>: > > Hello Chris, > > > > Hello Jaswinder > > and thanks for the reply. > > > On Sat, 2009-06-06 at 22:15 +0100, Chris Clayton wrote: > >> Sorry, I've just realised what a poor report my earlier email was. I should also have said that the > >> kernel has booted succesfully. At the time of reporting I had had two panics. I've just done > >> another git pull, so the kernel is bang up to date with kernel.org, but after building and > >> installing, a reboot resulted in another panic. The system then booted OK after switch off and on > >> again. > >> > >> Please cc me to any reply, I'm not subscribed. > >> > >> > >> On Saturday 06 June 2009, Chris Clayton wrote: > >> > Hi, > >> > > >> > After a git pull earlier today, I've had oopsen whilst booting the system > >> > twice today: A photo of the oops message can be viewed at: > >> > > >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg > >> > > >> > I haven't used the 2.6.30-rc kernels very much, so I don't have a clue when > >> > the problem was introduced. I have no problems at all with 2.6.29.4. > >> > > > > > Can you provide your .config and dmesg of working and non-working > > kernel. > > > > Thanks, > > -- > > JSR > > > > > > Sorry for delay in replying - I've been bisecting but ended up with: > > commit 60a0cd528d761c50d3a0a49e8fbaf6a87e64254a > Merge: e25e092 8e35961 > Author: Linus Torvalds <torvalds@linux-foundation.org> > Commit: Linus Torvalds <torvalds@linux-foundation.org> > > Merge branch 'merge' of > git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc > > * 'merge' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc: > powerpc/mm: Fix broken MMU PID stealing on !SMP > Based on this I added some CCs. > which seems wrong given I have and x86 machine. I guess I didn't try > enough reboots before reporting a kernel as good. > > However, I did get two bad boots. The dmesg for a good boot and config > are attached. As I don't get to user space on a bad boot, I can't > provide a dmesg, but a photograph of the panic can be viewed at > http://img99.imageshack.us/my.php?image=dscn0617b.jpg > Error message will be in previous screen, can you do some page up and capture the output. And .config is same for Good and Bad. -- JSR ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-07 22:31 ` Jaswinder Singh Rajput @ 2009-06-07 22:55 ` NeilBrown 2009-06-08 8:08 ` Chris Clayton 0 siblings, 1 reply; 38+ messages in thread From: NeilBrown @ 2009-06-07 22:55 UTC (permalink / raw) To: Jaswinder Singh Rajput Cc: Chris Clayton, linux-kernel, James Bottomley, scsi, Tejun Heo On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: > On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >> 2009/6/7 Jaswinder Singh Ra >> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg This message says that it found a vfat filesystem on 8:3x (I cannot see what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even sdc6 or sdc7. However the vfat filesystem didn't have /sbin/init. >> http://img99.imageshack.us/my.php?image=dscn0617b.jpg This one says it couldn't find anything at 8,22, which I think should be sdb6. It also shows that you have and sdc6, but sdb only goes up to sdb3. So it seems that your disk drives have changed name - not a wholely unexpected event these days. We now need answers to questions like: - what device do you expect the root filesystem to be on - how is the kernel being told this? Maybe it is hard coded into your initrd. Knowing which distro and what /etc/fstab says might help (though it wouldn't help me, I'm just about out of my depth at this point) Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. Good luck, NeilBrown ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-07 22:55 ` NeilBrown @ 2009-06-08 8:08 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 8:08 UTC (permalink / raw) To: NeilBrown Cc: Jaswinder Singh Rajput, linux-kernel, James Bottomley, scsi, Tejun Heo Hi Neil, Thanks for the reply. 2009/6/7 NeilBrown <neilb@suse.de>: > On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >>> 2009/6/7 Jaswinder Singh Ra >>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg > > This message says that it found a vfat filesystem on 8:3x (I cannot see > what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even > sdc6 or sdc7. > However the vfat filesystem didn't have /sbin/init. > >>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg > > This one says it couldn't find anything at 8,22, which I think > should be sdb6. > It also shows that you have and sdc6, but sdb only goes up to sdb3. > > So it seems that your disk drives have changed name - not a wholely > unexpected event these days. > > We now need answers to questions like: > - what device do you expect the root filesystem to be on > - how is the kernel being told this? Maybe it is hard coded > into your initrd. Knowing which distro and what /etc/fstab > says might help (though it wouldn't help me, I'm just about out > of my depth at this point) > Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding > e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. > Yes, I've just been looking at the photographs of the panics again and I've noticed that two of my discs are being detected in the "wrong order". There are three HDDS. The first, /dev/sda, is the master on the first IDE port and contains sda1..sda7. The second, normally /dev/sdb, is the slave on that port and contains sdb1..sdb6. The third, normally /dev/sdc, is attached to the first SATA port and contains sdc1..sdc3. The second photograph I posted shows that sdb and sdc have been reversed. The first partition on the disc that is normally /dev/sdb does indeed have a FAT32 filesystem in the first partition. By the way, I should have said that in between the panics that the two photographs show, I copied contents of /dev/sdc1, which I normally boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the reboot festival that bisecting would involve. I also, of course, changed the name of the root partition that is passed to the kernel by GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions shown in the photographs seem inconsistent. Sorry I forgot to mention that - I really shouldn't do these things late at night :-). As I indicate above, when booting the partition I have set up to do this bisecting, I expect the root filesystem to be on /dev/hdb6. As I also indicate, this information is passed to the kernel through GRUB's /boot/grub/menu.lst. The kernel is configured specifically for my system and the drivers needed to boot the system are built in to the kernel, so I don't use an initrd. IIRC, that's the way Slackware is installed today, except, of course, it's a big fat kernel with all drivers needed to boot any system built in. I could be wrong on that though, it's a while since I installed As to the distro, it used to be (the now defunct) Peanut Linux, which was derived from Slackware. However, it's years since I installed it and I have upgraded just about everything in user space and added many other things (udev, dbus...). I don't think that makes any difference here, though, because we don't get as far as user space. On a successful boot, the system is stable and runs trouble-free for several hours a day, every day. Hope this helps. I'm a good way through bisecting again and this time the system has to boot without a panic 100 times before I mark a kernel as good. I'll post the result later. Thanks > Good luck, > NeilBrown > > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 8:08 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 8:08 UTC (permalink / raw) To: NeilBrown Cc: Jaswinder Singh Rajput, linux-kernel, James Bottomley, scsi, Tejun Heo Hi Neil, Thanks for the reply. 2009/6/7 NeilBrown <neilb@suse.de>: > On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >>> 2009/6/7 Jaswinder Singh Ra >>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg > > This message says that it found a vfat filesystem on 8:3x (I cannot see > what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even > sdc6 or sdc7. > However the vfat filesystem didn't have /sbin/init. > >>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg > > This one says it couldn't find anything at 8,22, which I think > should be sdb6. > It also shows that you have and sdc6, but sdb only goes up to sdb3. > > So it seems that your disk drives have changed name - not a wholely > unexpected event these days. > > We now need answers to questions like: > - what device do you expect the root filesystem to be on > - how is the kernel being told this? Maybe it is hard coded > into your initrd. Knowing which distro and what /etc/fstab > says might help (though it wouldn't help me, I'm just about out > of my depth at this point) > Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding > e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. > Yes, I've just been looking at the photographs of the panics again and I've noticed that two of my discs are being detected in the "wrong order". There are three HDDS. The first, /dev/sda, is the master on the first IDE port and contains sda1..sda7. The second, normally /dev/sdb, is the slave on that port and contains sdb1..sdb6. The third, normally /dev/sdc, is attached to the first SATA port and contains sdc1..sdc3. The second photograph I posted shows that sdb and sdc have been reversed. The first partition on the disc that is normally /dev/sdb does indeed have a FAT32 filesystem in the first partition. By the way, I should have said that in between the panics that the two photographs show, I copied contents of /dev/sdc1, which I normally boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the reboot festival that bisecting would involve. I also, of course, changed the name of the root partition that is passed to the kernel by GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions shown in the photographs seem inconsistent. Sorry I forgot to mention that - I really shouldn't do these things late at night :-). As I indicate above, when booting the partition I have set up to do this bisecting, I expect the root filesystem to be on /dev/hdb6. As I also indicate, this information is passed to the kernel through GRUB's /boot/grub/menu.lst. The kernel is configured specifically for my system and the drivers needed to boot the system are built in to the kernel, so I don't use an initrd. IIRC, that's the way Slackware is installed today, except, of course, it's a big fat kernel with all drivers needed to boot any system built in. I could be wrong on that though, it's a while since I installed As to the distro, it used to be (the now defunct) Peanut Linux, which was derived from Slackware. However, it's years since I installed it and I have upgraded just about everything in user space and added many other things (udev, dbus...). I don't think that makes any difference here, though, because we don't get as far as user space. On a successful boot, the system is stable and runs trouble-free for several hours a day, every day. Hope this helps. I'm a good way through bisecting again and this time the system has to boot without a panic 100 times before I mark a kernel as good. I'll post the result later. Thanks > Good luck, > NeilBrown > > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 8:08 ` Chris Clayton @ 2009-06-08 10:58 ` Chris Clayton -1 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 10:58 UTC (permalink / raw) To: NeilBrown Cc: Jaswinder Singh Rajput, linux-kernel, James Bottomley, scsi, Tejun Heo 2009/6/8 Chris Clayton <chris2553@googlemail.com>: > Hi Neil, > > Thanks for the reply. > > 2009/6/7 NeilBrown <neilb@suse.de>: >> On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >>> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >>>> 2009/6/7 Jaswinder Singh Ra >>>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> >> This message says that it found a vfat filesystem on 8:3x (I cannot see >> what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even >> sdc6 or sdc7. >> However the vfat filesystem didn't have /sbin/init. >> > >>>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg >> >> This one says it couldn't find anything at 8,22, which I think >> should be sdb6. >> It also shows that you have and sdc6, but sdb only goes up to sdb3. >> >> So it seems that your disk drives have changed name - not a wholely >> unexpected event these days. >> >> We now need answers to questions like: >> - what device do you expect the root filesystem to be on >> - how is the kernel being told this? Maybe it is hard coded >> into your initrd. Knowing which distro and what /etc/fstab >> says might help (though it wouldn't help me, I'm just about out >> of my depth at this point) >> Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding >> e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. >> > > Yes, I've just been looking at the photographs of the panics again and > I've noticed that two of my discs are being detected in the "wrong > order". There are three HDDS. The first, /dev/sda, is the master on > the first IDE port and contains sda1..sda7. The second, normally > /dev/sdb, is the slave on that port and contains sdb1..sdb6. The > third, normally /dev/sdc, is attached to the first SATA port and > contains sdc1..sdc3. The second photograph I posted shows that sdb and > sdc have been reversed. The first partition on the disc that is > normally /dev/sdb does indeed have a FAT32 filesystem in the first > partition. > > By the way, I should have said that in between the panics that the two > photographs show, I copied contents of /dev/sdc1, which I normally > boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the > reboot festival that bisecting would involve. I also, of course, > changed the name of the root partition that is passed to the kernel by > GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions > shown in the photographs seem inconsistent. Sorry I forgot to mention > that - I really shouldn't do these things late at night :-). > > As I indicate above, when booting the partition I have set up to do > this bisecting, I expect the root filesystem to be on /dev/hdb6. As I > also indicate, this information is passed to the kernel through GRUB's > /boot/grub/menu.lst. The kernel is configured specifically for my > system and the drivers needed to boot the system are built in to the > kernel, so I don't use an initrd. IIRC, that's the way Slackware is > installed today, except, of course, it's a big fat kernel with all > drivers needed to boot any system built in. I could be wrong on that > though, it's a while since I installed > > As to the distro, it used to be (the now defunct) Peanut Linux, which > was derived from Slackware. However, it's years since I installed it > and I have upgraded just about everything in user space and added many > other things (udev, dbus...). I don't think that makes any difference > here, though, because we don't get as far as user space. On a > successful boot, the system is stable and runs trouble-free for > several hours a day, every day. > > Hope this helps. > > I'm a good way through bisecting again and this time the system has to > boot without a panic 100 times before I mark a kernel as good. I'll > post the result later. > Finally got to the end of the bisection/reboot festival. I ended up here: [chris:~/kernel/linux-2.6]$ git bisect good d5a877e8dd409d8c702986d06485c374b705d340 is first bad commit commit d5a877e8dd409d8c702986d06485c374b705d340 Author: James Bottomley <James.Bottomley@HansenPartnership.com> Date: Sun May 24 13:03:43 2009 -0700 async: make sure independent async domains can't accidentally entangle The problem occurs when async_synchronize_full_domain() is called when the async_pending list is not empty. This will cause lowest_running() to return the cookie of the first entry on the async_pending list, which might be nothing at all to do with the domain being asked for and thus cause the domain synchronization to wait for an unrelated domain. This can cause a deadlock if domain synchronization is used from one domain to wait for another. Fix by running over the async_pending list to see if any pending items actually belong to our domain (and return their cookies if they do). Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> :040000 040000 fab1e0c06572605a7015061db4a7e0a77c04fa91 34252dbb7fed3942f5952c25639564bbd77357da M kernel I can't claim to know what the change actually means, but the change seems to be a much better candidate than my previous bisection outcome where I required only 20 "panicless" boots to regard the kernel as good. As I said earlier today, this time I required 100 such boots. I'll revert that change, give the new kernel the reboot treatment :-) and report back later. Chris > Thanks > > >> Good luck, >> NeilBrown >> >> > > > > -- > No, Sir; there is nothing which has yet been contrived by man, by which > so much happiness is produced as by a good tavern or inn - Doctor Samuel > Johnson > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 10:58 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 10:58 UTC (permalink / raw) To: NeilBrown Cc: Jaswinder Singh Rajput, linux-kernel, James Bottomley, scsi, Tejun Heo 2009/6/8 Chris Clayton <chris2553@googlemail.com>: > Hi Neil, > > Thanks for the reply. > > 2009/6/7 NeilBrown <neilb@suse.de>: >> On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >>> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >>>> 2009/6/7 Jaswinder Singh Ra >>>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> >> This message says that it found a vfat filesystem on 8:3x (I cannot see >> what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even >> sdc6 or sdc7. >> However the vfat filesystem didn't have /sbin/init. >> > >>>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg >> >> This one says it couldn't find anything at 8,22, which I think >> should be sdb6. >> It also shows that you have and sdc6, but sdb only goes up to sdb3. >> >> So it seems that your disk drives have changed name - not a wholely >> unexpected event these days. >> >> We now need answers to questions like: >> - what device do you expect the root filesystem to be on >> - how is the kernel being told this? Maybe it is hard coded >> into your initrd. Knowing which distro and what /etc/fstab >> says might help (though it wouldn't help me, I'm just about out >> of my depth at this point) >> Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding >> e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. >> > > Yes, I've just been looking at the photographs of the panics again and > I've noticed that two of my discs are being detected in the "wrong > order". There are three HDDS. The first, /dev/sda, is the master on > the first IDE port and contains sda1..sda7. The second, normally > /dev/sdb, is the slave on that port and contains sdb1..sdb6. The > third, normally /dev/sdc, is attached to the first SATA port and > contains sdc1..sdc3. The second photograph I posted shows that sdb and > sdc have been reversed. The first partition on the disc that is > normally /dev/sdb does indeed have a FAT32 filesystem in the first > partition. > > By the way, I should have said that in between the panics that the two > photographs show, I copied contents of /dev/sdc1, which I normally > boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the > reboot festival that bisecting would involve. I also, of course, > changed the name of the root partition that is passed to the kernel by > GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions > shown in the photographs seem inconsistent. Sorry I forgot to mention > that - I really shouldn't do these things late at night :-). > > As I indicate above, when booting the partition I have set up to do > this bisecting, I expect the root filesystem to be on /dev/hdb6. As I > also indicate, this information is passed to the kernel through GRUB's > /boot/grub/menu.lst. The kernel is configured specifically for my > system and the drivers needed to boot the system are built in to the > kernel, so I don't use an initrd. IIRC, that's the way Slackware is > installed today, except, of course, it's a big fat kernel with all > drivers needed to boot any system built in. I could be wrong on that > though, it's a while since I installed > > As to the distro, it used to be (the now defunct) Peanut Linux, which > was derived from Slackware. However, it's years since I installed it > and I have upgraded just about everything in user space and added many > other things (udev, dbus...). I don't think that makes any difference > here, though, because we don't get as far as user space. On a > successful boot, the system is stable and runs trouble-free for > several hours a day, every day. > > Hope this helps. > > I'm a good way through bisecting again and this time the system has to > boot without a panic 100 times before I mark a kernel as good. I'll > post the result later. > Finally got to the end of the bisection/reboot festival. I ended up here: [chris:~/kernel/linux-2.6]$ git bisect good d5a877e8dd409d8c702986d06485c374b705d340 is first bad commit commit d5a877e8dd409d8c702986d06485c374b705d340 Author: James Bottomley <James.Bottomley@HansenPartnership.com> Date: Sun May 24 13:03:43 2009 -0700 async: make sure independent async domains can't accidentally entangle The problem occurs when async_synchronize_full_domain() is called when the async_pending list is not empty. This will cause lowest_running() to return the cookie of the first entry on the async_pending list, which might be nothing at all to do with the domain being asked for and thus cause the domain synchronization to wait for an unrelated domain. This can cause a deadlock if domain synchronization is used from one domain to wait for another. Fix by running over the async_pending list to see if any pending items actually belong to our domain (and return their cookies if they do). Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> :040000 040000 fab1e0c06572605a7015061db4a7e0a77c04fa91 34252dbb7fed3942f5952c25639564bbd77357da M kernel I can't claim to know what the change actually means, but the change seems to be a much better candidate than my previous bisection outcome where I required only 20 "panicless" boots to regard the kernel as good. As I said earlier today, this time I required 100 such boots. I'll revert that change, give the new kernel the reboot treatment :-) and report back later. Chris > Thanks > > >> Good luck, >> NeilBrown >> >> > > > > -- > No, Sir; there is nothing which has yet been contrived by man, by which > so much happiness is produced as by a good tavern or inn - Doctor Samuel > Johnson > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 10:58 ` Chris Clayton (?) @ 2009-06-08 11:34 ` Jaswinder Singh Rajput 2009-06-08 12:53 ` Chris Clayton -1 siblings, 1 reply; 38+ messages in thread From: Jaswinder Singh Rajput @ 2009-06-08 11:34 UTC (permalink / raw) To: Chris Clayton Cc: NeilBrown, linux-kernel, James Bottomley, scsi, Tejun Heo, Arjan van de Ven, Linus Torvalds Hello Chris, On Mon, 2009-06-08 at 11:58 +0100, Chris Clayton wrote: > 2009/6/8 Chris Clayton <chris2553@googlemail.com>: > > Hi Neil, > > > > Thanks for the reply. > > > > 2009/6/7 NeilBrown <neilb@suse.de>: > >> On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: > >>> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: > >>>> 2009/6/7 Jaswinder Singh Ra > >>>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg > >> > >> This message says that it found a vfat filesystem on 8:3x (I cannot see > >> what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even > >> sdc6 or sdc7. > >> However the vfat filesystem didn't have /sbin/init. > >> > > > >>>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg > >> > >> This one says it couldn't find anything at 8,22, which I think > >> should be sdb6. > >> It also shows that you have and sdc6, but sdb only goes up to sdb3. > >> > >> So it seems that your disk drives have changed name - not a wholely > >> unexpected event these days. > >> > >> We now need answers to questions like: > >> - what device do you expect the root filesystem to be on > >> - how is the kernel being told this? Maybe it is hard coded > >> into your initrd. Knowing which distro and what /etc/fstab > >> says might help (though it wouldn't help me, I'm just about out > >> of my depth at this point) > >> Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding > >> e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. > >> > > > > Yes, I've just been looking at the photographs of the panics again and > > I've noticed that two of my discs are being detected in the "wrong > > order". There are three HDDS. The first, /dev/sda, is the master on > > the first IDE port and contains sda1..sda7. The second, normally > > /dev/sdb, is the slave on that port and contains sdb1..sdb6. The > > third, normally /dev/sdc, is attached to the first SATA port and > > contains sdc1..sdc3. The second photograph I posted shows that sdb and > > sdc have been reversed. The first partition on the disc that is > > normally /dev/sdb does indeed have a FAT32 filesystem in the first > > partition. > > > > By the way, I should have said that in between the panics that the two > > photographs show, I copied contents of /dev/sdc1, which I normally > > boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the > > reboot festival that bisecting would involve. I also, of course, > > changed the name of the root partition that is passed to the kernel by > > GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions > > shown in the photographs seem inconsistent. Sorry I forgot to mention > > that - I really shouldn't do these things late at night :-). > > > > As I indicate above, when booting the partition I have set up to do > > this bisecting, I expect the root filesystem to be on /dev/hdb6. As I > > also indicate, this information is passed to the kernel through GRUB's > > /boot/grub/menu.lst. The kernel is configured specifically for my > > system and the drivers needed to boot the system are built in to the > > kernel, so I don't use an initrd. IIRC, that's the way Slackware is > > installed today, except, of course, it's a big fat kernel with all > > drivers needed to boot any system built in. I could be wrong on that > > though, it's a while since I installed > > > > As to the distro, it used to be (the now defunct) Peanut Linux, which > > was derived from Slackware. However, it's years since I installed it > > and I have upgraded just about everything in user space and added many > > other things (udev, dbus...). I don't think that makes any difference > > here, though, because we don't get as far as user space. On a > > successful boot, the system is stable and runs trouble-free for > > several hours a day, every day. > > > > Hope this helps. > > > > I'm a good way through bisecting again and this time the system has to > > boot without a panic 100 times before I mark a kernel as good. I'll > > post the result later. > > > > Finally got to the end of the bisection/reboot festival. I ended up here: > > [chris:~/kernel/linux-2.6]$ git bisect good > d5a877e8dd409d8c702986d06485c374b705d340 is first bad commit > commit d5a877e8dd409d8c702986d06485c374b705d340 > Author: James Bottomley <James.Bottomley@HansenPartnership.com> > Date: Sun May 24 13:03:43 2009 -0700 > > async: make sure independent async domains can't accidentally entangle > > The problem occurs when async_synchronize_full_domain() is called when > the async_pending list is not empty. This will cause lowest_running() > to return the cookie of the first entry on the async_pending list, which > might be nothing at all to do with the domain being asked for and thus > cause the domain synchronization to wait for an unrelated domain. This > can cause a deadlock if domain synchronization is used from one domain > to wait for another. > > Fix by running over the async_pending list to see if any pending items > actually belong to our domain (and return their cookies if they do). > > Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> > Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> > Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> > > :040000 040000 fab1e0c06572605a7015061db4a7e0a77c04fa91 > 34252dbb7fed3942f5952c25639564bbd77357da M kernel > > I can't claim to know what the change actually means, but the change > seems to be a much better candidate than my previous bisection outcome > where I required only 20 "panicless" boots to regard the kernel as > good. As I said earlier today, this time I required 100 such boots. > > I'll revert that change, give the new kernel the reboot treatment :-) > and report back later. > Good work. Please also share this info with other signed-off members, So adding CC. Thanks, -- JSR ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 11:34 ` Jaswinder Singh Rajput @ 2009-06-08 12:53 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 12:53 UTC (permalink / raw) To: Jaswinder Singh Rajput Cc: NeilBrown, linux-kernel, James Bottomley, scsi, Tejun Heo, Arjan van de Ven, Linus Torvalds 2009/6/8 Jaswinder Singh Rajput <jaswinder@kernel.org>: > Hello Chris, > > On Mon, 2009-06-08 at 11:58 +0100, Chris Clayton wrote: >> 2009/6/8 Chris Clayton <chris2553@googlemail.com>: >> > Hi Neil, >> > >> > Thanks for the reply. >> > >> > 2009/6/7 NeilBrown <neilb@suse.de>: >> >> On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >> >>> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >> >>>> 2009/6/7 Jaswinder Singh Ra >> >>>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> >> >> >> This message says that it found a vfat filesystem on 8:3x (I cannot see >> >> what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even >> >> sdc6 or sdc7. >> >> However the vfat filesystem didn't have /sbin/init. >> >> >> > >> >>>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg >> >> >> >> This one says it couldn't find anything at 8,22, which I think >> >> should be sdb6. >> >> It also shows that you have and sdc6, but sdb only goes up to sdb3. >> >> >> >> So it seems that your disk drives have changed name - not a wholely >> >> unexpected event these days. >> >> >> >> We now need answers to questions like: >> >> - what device do you expect the root filesystem to be on >> >> - how is the kernel being told this? Maybe it is hard coded >> >> into your initrd. Knowing which distro and what /etc/fstab >> >> says might help (though it wouldn't help me, I'm just about out >> >> of my depth at this point) >> >> Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding >> >> e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. >> >> >> > >> > Yes, I've just been looking at the photographs of the panics again and >> > I've noticed that two of my discs are being detected in the "wrong >> > order". There are three HDDS. The first, /dev/sda, is the master on >> > the first IDE port and contains sda1..sda7. The second, normally >> > /dev/sdb, is the slave on that port and contains sdb1..sdb6. The >> > third, normally /dev/sdc, is attached to the first SATA port and >> > contains sdc1..sdc3. The second photograph I posted shows that sdb and >> > sdc have been reversed. The first partition on the disc that is >> > normally /dev/sdb does indeed have a FAT32 filesystem in the first >> > partition. >> > >> > By the way, I should have said that in between the panics that the two >> > photographs show, I copied contents of /dev/sdc1, which I normally >> > boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the >> > reboot festival that bisecting would involve. I also, of course, >> > changed the name of the root partition that is passed to the kernel by >> > GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions >> > shown in the photographs seem inconsistent. Sorry I forgot to mention >> > that - I really shouldn't do these things late at night :-). >> > >> > As I indicate above, when booting the partition I have set up to do >> > this bisecting, I expect the root filesystem to be on /dev/hdb6. As I >> > also indicate, this information is passed to the kernel through GRUB's >> > /boot/grub/menu.lst. The kernel is configured specifically for my >> > system and the drivers needed to boot the system are built in to the >> > kernel, so I don't use an initrd. IIRC, that's the way Slackware is >> > installed today, except, of course, it's a big fat kernel with all >> > drivers needed to boot any system built in. I could be wrong on that >> > though, it's a while since I installed >> > >> > As to the distro, it used to be (the now defunct) Peanut Linux, which >> > was derived from Slackware. However, it's years since I installed it >> > and I have upgraded just about everything in user space and added many >> > other things (udev, dbus...). I don't think that makes any difference >> > here, though, because we don't get as far as user space. On a >> > successful boot, the system is stable and runs trouble-free for >> > several hours a day, every day. >> > >> > Hope this helps. >> > >> > I'm a good way through bisecting again and this time the system has to >> > boot without a panic 100 times before I mark a kernel as good. I'll >> > post the result later. >> > >> >> Finally got to the end of the bisection/reboot festival. I ended up here: >> >> [chris:~/kernel/linux-2.6]$ git bisect good >> d5a877e8dd409d8c702986d06485c374b705d340 is first bad commit >> commit d5a877e8dd409d8c702986d06485c374b705d340 >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> >> Date: Sun May 24 13:03:43 2009 -0700 >> >> async: make sure independent async domains can't accidentally entangle >> >> The problem occurs when async_synchronize_full_domain() is called when >> the async_pending list is not empty. This will cause lowest_running() >> to return the cookie of the first entry on the async_pending list, which >> might be nothing at all to do with the domain being asked for and thus >> cause the domain synchronization to wait for an unrelated domain. This >> can cause a deadlock if domain synchronization is used from one domain >> to wait for another. >> >> Fix by running over the async_pending list to see if any pending items >> actually belong to our domain (and return their cookies if they do). >> >> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> >> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> >> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> >> >> :040000 040000 fab1e0c06572605a7015061db4a7e0a77c04fa91 >> 34252dbb7fed3942f5952c25639564bbd77357da M kernel >> >> I can't claim to know what the change actually means, but the change >> seems to be a much better candidate than my previous bisection outcome >> where I required only 20 "panicless" boots to regard the kernel as >> good. As I said earlier today, this time I required 100 such boots. >> >> I'll revert that change, give the new kernel the reboot treatment :-) >> and report back later. >> > > Good work. Please also share this info with other signed-off members, So > adding CC. > OK. I reversed that change and built and installed the kernel. It has withstood 100 reboots without a panic. Additionally, I pulled the latest changes (that will be rc8-git5, I think) from kernel.org, reversed the change to that kernel and built and installed it. That too withstood 100 reboots without a panic. Let me know if there's anything else I can do to help fix this. Chris > Thanks, > -- > JSR > > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 12:53 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 12:53 UTC (permalink / raw) To: Jaswinder Singh Rajput Cc: NeilBrown, linux-kernel, James Bottomley, scsi, Tejun Heo, Arjan van de Ven, Linus Torvalds 2009/6/8 Jaswinder Singh Rajput <jaswinder@kernel.org>: > Hello Chris, > > On Mon, 2009-06-08 at 11:58 +0100, Chris Clayton wrote: >> 2009/6/8 Chris Clayton <chris2553@googlemail.com>: >> > Hi Neil, >> > >> > Thanks for the reply. >> > >> > 2009/6/7 NeilBrown <neilb@suse.de>: >> >> On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >> >>> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >> >>>> 2009/6/7 Jaswinder Singh Ra >> >>>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> >> >> >> This message says that it found a vfat filesystem on 8:3x (I cannot see >> >> what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even >> >> sdc6 or sdc7. >> >> However the vfat filesystem didn't have /sbin/init. >> >> >> > >> >>>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg >> >> >> >> This one says it couldn't find anything at 8,22, which I think >> >> should be sdb6. >> >> It also shows that you have and sdc6, but sdb only goes up to sdb3. >> >> >> >> So it seems that your disk drives have changed name - not a wholely >> >> unexpected event these days. >> >> >> >> We now need answers to questions like: >> >> - what device do you expect the root filesystem to be on >> >> - how is the kernel being told this? Maybe it is hard coded >> >> into your initrd. Knowing which distro and what /etc/fstab >> >> says might help (though it wouldn't help me, I'm just about out >> >> of my depth at this point) >> >> Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding >> >> e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. >> >> >> > >> > Yes, I've just been looking at the photographs of the panics again and >> > I've noticed that two of my discs are being detected in the "wrong >> > order". There are three HDDS. The first, /dev/sda, is the master on >> > the first IDE port and contains sda1..sda7. The second, normally >> > /dev/sdb, is the slave on that port and contains sdb1..sdb6. The >> > third, normally /dev/sdc, is attached to the first SATA port and >> > contains sdc1..sdc3. The second photograph I posted shows that sdb and >> > sdc have been reversed. The first partition on the disc that is >> > normally /dev/sdb does indeed have a FAT32 filesystem in the first >> > partition. >> > >> > By the way, I should have said that in between the panics that the two >> > photographs show, I copied contents of /dev/sdc1, which I normally >> > boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the >> > reboot festival that bisecting would involve. I also, of course, >> > changed the name of the root partition that is passed to the kernel by >> > GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions >> > shown in the photographs seem inconsistent. Sorry I forgot to mention >> > that - I really shouldn't do these things late at night :-). >> > >> > As I indicate above, when booting the partition I have set up to do >> > this bisecting, I expect the root filesystem to be on /dev/hdb6. As I >> > also indicate, this information is passed to the kernel through GRUB's >> > /boot/grub/menu.lst. The kernel is configured specifically for my >> > system and the drivers needed to boot the system are built in to the >> > kernel, so I don't use an initrd. IIRC, that's the way Slackware is >> > installed today, except, of course, it's a big fat kernel with all >> > drivers needed to boot any system built in. I could be wrong on that >> > though, it's a while since I installed >> > >> > As to the distro, it used to be (the now defunct) Peanut Linux, which >> > was derived from Slackware. However, it's years since I installed it >> > and I have upgraded just about everything in user space and added many >> > other things (udev, dbus...). I don't think that makes any difference >> > here, though, because we don't get as far as user space. On a >> > successful boot, the system is stable and runs trouble-free for >> > several hours a day, every day. >> > >> > Hope this helps. >> > >> > I'm a good way through bisecting again and this time the system has to >> > boot without a panic 100 times before I mark a kernel as good. I'll >> > post the result later. >> > >> >> Finally got to the end of the bisection/reboot festival. I ended up here: >> >> [chris:~/kernel/linux-2.6]$ git bisect good >> d5a877e8dd409d8c702986d06485c374b705d340 is first bad commit >> commit d5a877e8dd409d8c702986d06485c374b705d340 >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> >> Date: Sun May 24 13:03:43 2009 -0700 >> >> async: make sure independent async domains can't accidentally entangle >> >> The problem occurs when async_synchronize_full_domain() is called when >> the async_pending list is not empty. This will cause lowest_running() >> to return the cookie of the first entry on the async_pending list, which >> might be nothing at all to do with the domain being asked for and thus >> cause the domain synchronization to wait for an unrelated domain. This >> can cause a deadlock if domain synchronization is used from one domain >> to wait for another. >> >> Fix by running over the async_pending list to see if any pending items >> actually belong to our domain (and return their cookies if they do). >> >> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> >> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> >> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> >> >> :040000 040000 fab1e0c06572605a7015061db4a7e0a77c04fa91 >> 34252dbb7fed3942f5952c25639564bbd77357da M kernel >> >> I can't claim to know what the change actually means, but the change >> seems to be a much better candidate than my previous bisection outcome >> where I required only 20 "panicless" boots to regard the kernel as >> good. As I said earlier today, this time I required 100 such boots. >> >> I'll revert that change, give the new kernel the reboot treatment :-) >> and report back later. >> > > Good work. Please also share this info with other signed-off members, So > adding CC. > OK. I reversed that change and built and installed the kernel. It has withstood 100 reboots without a panic. Additionally, I pulled the latest changes (that will be rc8-git5, I think) from kernel.org, reversed the change to that kernel and built and installed it. That too withstood 100 reboots without a panic. Let me know if there's anything else I can do to help fix this. Chris > Thanks, > -- > JSR > > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 12:53 ` Chris Clayton @ 2009-06-08 16:21 ` Linus Torvalds -1 siblings, 0 replies; 38+ messages in thread From: Linus Torvalds @ 2009-06-08 16:21 UTC (permalink / raw) To: Chris Clayton Cc: Jaswinder Singh Rajput, NeilBrown, linux-kernel, James Bottomley, scsi, Tejun Heo, Arjan van de Ven On Mon, 8 Jun 2009, Chris Clayton wrote: > > OK. I reversed that change and built and installed the kernel. It has > withstood 100 reboots without a panic. Additionally, I pulled the > latest changes (that will be rc8-git5, I think) from kernel.org, > reversed the change to that kernel and built and installed it. That > too withstood 100 reboots without a panic. > > Let me know if there's anything else I can do to help fix this. That's already pretty convincing. James, Arjan? The original oops message is here (a jpg screen capture, unable to open initial console): http://lkml.org/lkml/2009/6/6/142 and it's this bug entry: Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474 Subject : Oops whilst booting Submitter : Chris Clayton <chris2553@googlemail.com> Date : 2009-06-06 18:59 (2 days old) References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4 and now bisected down to >> commit d5a877e8dd409d8c702986d06485c374b705d340 >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> >> Date: Sun May 24 13:03:43 2009 -0700 >> >> async: make sure independent async domains can't accidentally entangle please advice. Otherwise I'll have to revert. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 16:21 ` Linus Torvalds 0 siblings, 0 replies; 38+ messages in thread From: Linus Torvalds @ 2009-06-08 16:21 UTC (permalink / raw) To: Chris Clayton Cc: Jaswinder Singh Rajput, NeilBrown, linux-kernel, James Bottomley, scsi, Tejun Heo, Arjan van de Ven On Mon, 8 Jun 2009, Chris Clayton wrote: > > OK. I reversed that change and built and installed the kernel. It has > withstood 100 reboots without a panic. Additionally, I pulled the > latest changes (that will be rc8-git5, I think) from kernel.org, > reversed the change to that kernel and built and installed it. That > too withstood 100 reboots without a panic. > > Let me know if there's anything else I can do to help fix this. That's already pretty convincing. James, Arjan? The original oops message is here (a jpg screen capture, unable to open initial console): http://lkml.org/lkml/2009/6/6/142 and it's this bug entry: Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474 Subject : Oops whilst booting Submitter : Chris Clayton <chris2553@googlemail.com> Date : 2009-06-06 18:59 (2 days old) References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4 and now bisected down to >> commit d5a877e8dd409d8c702986d06485c374b705d340 >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> >> Date: Sun May 24 13:03:43 2009 -0700 >> >> async: make sure independent async domains can't accidentally entangle please advice. Otherwise I'll have to revert. Linus ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 16:21 ` Linus Torvalds (?) @ 2009-06-08 16:51 ` James Bottomley 2009-06-08 17:06 ` Jaswinder Singh Rajput 2009-06-08 17:21 ` Linus Torvalds -1 siblings, 2 replies; 38+ messages in thread From: James Bottomley @ 2009-06-08 16:51 UTC (permalink / raw) To: Linus Torvalds Cc: Chris Clayton, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 2009-06-08 at 09:21 -0700, Linus Torvalds wrote: > > On Mon, 8 Jun 2009, Chris Clayton wrote: > > > > OK. I reversed that change and built and installed the kernel. It has > > withstood 100 reboots without a panic. Additionally, I pulled the > > latest changes (that will be rc8-git5, I think) from kernel.org, > > reversed the change to that kernel and built and installed it. That > > too withstood 100 reboots without a panic. > > > > Let me know if there's anything else I can do to help fix this. > > That's already pretty convincing. > > James, Arjan? The original oops message is here (a jpg screen capture, > unable to open initial console): > > http://lkml.org/lkml/2009/6/6/142 > > and it's this bug entry: > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474 > Subject : Oops whilst booting > Submitter : Chris Clayton <chris2553@googlemail.com> > Date : 2009-06-06 18:59 (2 days old) > References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4 > > and now bisected down to > > >> commit d5a877e8dd409d8c702986d06485c374b705d340 > >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> > >> Date: Sun May 24 13:03:43 2009 -0700 > >> > >> async: make sure independent async domains can't accidentally entangle > > please advice. Otherwise I'll have to revert. The root cause is a reordering of the devices caused by the async code. I suspect it's a bug in async that was obscured by the old behaviour of async_synchronize.. (or it's a bug in the new code) ... how long do I have to find out which? James ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 16:51 ` James Bottomley @ 2009-06-08 17:06 ` Jaswinder Singh Rajput 2009-06-08 17:45 ` Chris Clayton 2009-06-08 17:21 ` Linus Torvalds 1 sibling, 1 reply; 38+ messages in thread From: Jaswinder Singh Rajput @ 2009-06-08 17:06 UTC (permalink / raw) To: James Bottomley Cc: Linus Torvalds, Chris Clayton, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 2009-06-08 at 16:51 +0000, James Bottomley wrote: > On Mon, 2009-06-08 at 09:21 -0700, Linus Torvalds wrote: > > > > On Mon, 8 Jun 2009, Chris Clayton wrote: > > > > > > OK. I reversed that change and built and installed the kernel. It has > > > withstood 100 reboots without a panic. Additionally, I pulled the > > > latest changes (that will be rc8-git5, I think) from kernel.org, > > > reversed the change to that kernel and built and installed it. That > > > too withstood 100 reboots without a panic. > > > > > > Let me know if there's anything else I can do to help fix this. > > > > That's already pretty convincing. > > > > James, Arjan? The original oops message is here (a jpg screen capture, > > unable to open initial console): > > > > http://lkml.org/lkml/2009/6/6/142 > > > > and it's this bug entry: > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474 > > Subject : Oops whilst booting > > Submitter : Chris Clayton <chris2553@googlemail.com> > > Date : 2009-06-06 18:59 (2 days old) > > References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4 > > > > and now bisected down to > > > > >> commit d5a877e8dd409d8c702986d06485c374b705d340 > > >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> > > >> Date: Sun May 24 13:03:43 2009 -0700 > > >> > > >> async: make sure independent async domains can't accidentally entangle > > > > please advice. Otherwise I'll have to revert. > > The root cause is a reordering of the devices caused by the async code. > > I suspect it's a bug in async that was obscured by the old behaviour of > async_synchronize.. (or it's a bug in the new code) ... how long do I > have to find out which? > But reverting your patch Or if we return like this also fix chris problem : diff --git a/kernel/async.c b/kernel/async.c index 94dd36f..3b492cb 100644 --- a/kernel/async.c +++ b/kernel/async.c @@ -96,15 +96,13 @@ static async_cookie_t __lowest_in_progress(struct list_head *running) if (!list_empty(running)) { entry = list_first_entry(running, struct async_entry, list); - ret = entry->cookie; + return entry->cookie; } if (!list_empty(&async_pending)) { list_for_each_entry(entry, &async_pending, list) - if (entry->running == running) { - ret = entry->cookie; - break; - } + if (entry->running == running) + return entry->cookie; } return ret; ^ permalink raw reply related [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 17:06 ` Jaswinder Singh Rajput @ 2009-06-08 17:45 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 17:45 UTC (permalink / raw) To: Jaswinder Singh Rajput Cc: James Bottomley, Linus Torvalds, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven 2009/6/8 Jaswinder Singh Rajput <jaswinder@kernel.org>: > But reverting your patch Or if we return like this also fix chris > problem : > > diff --git a/kernel/async.c b/kernel/async.c > index 94dd36f..3b492cb 100644 > --- a/kernel/async.c > +++ b/kernel/async.c > @@ -96,15 +96,13 @@ static async_cookie_t __lowest_in_progress(struct list_head *running) > if (!list_empty(running)) { > entry = list_first_entry(running, > struct async_entry, list); > - ret = entry->cookie; > + return entry->cookie; > } > > if (!list_empty(&async_pending)) { > list_for_each_entry(entry, &async_pending, list) > - if (entry->running == running) { > - ret = entry->cookie; > - break; > - } > + if (entry->running == running) > + return entry->cookie; > } > > return ret; > > > I can confirm that a kernel built with Jaswinder's patch applied survived 200 boots without a panic. Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 17:45 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 17:45 UTC (permalink / raw) To: Jaswinder Singh Rajput Cc: James Bottomley, Linus Torvalds, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven 2009/6/8 Jaswinder Singh Rajput <jaswinder@kernel.org>: > But reverting your patch Or if we return like this also fix chris > problem : > > diff --git a/kernel/async.c b/kernel/async.c > index 94dd36f..3b492cb 100644 > --- a/kernel/async.c > +++ b/kernel/async.c > @@ -96,15 +96,13 @@ static async_cookie_t __lowest_in_progress(struct list_head *running) > if (!list_empty(running)) { > entry = list_first_entry(running, > struct async_entry, list); > - ret = entry->cookie; > + return entry->cookie; > } > > if (!list_empty(&async_pending)) { > list_for_each_entry(entry, &async_pending, list) > - if (entry->running == running) { > - ret = entry->cookie; > - break; > - } > + if (entry->running == running) > + return entry->cookie; > } > > return ret; > > > I can confirm that a kernel built with Jaswinder's patch applied survived 200 boots without a panic. Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 17:45 ` Chris Clayton (?) @ 2009-06-08 18:21 ` Linus Torvalds 2009-06-08 19:17 ` Chris Clayton -1 siblings, 1 reply; 38+ messages in thread From: Linus Torvalds @ 2009-06-08 18:21 UTC (permalink / raw) To: Chris Clayton Cc: Jaswinder Singh Rajput, James Bottomley, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 8 Jun 2009, Chris Clayton wrote: > > I can confirm that a kernel built with Jaswinder's patch applied > survived 200 boots without a panic. Ok, goodie. Can you confirm that the further cleanup (removing the pointless 'ret' variable and the useless empty checking around 'for_each_entry') also works for you? Linus --- kernel/async.c | 15 +++++---------- 1 files changed, 5 insertions(+), 10 deletions(-) diff --git a/kernel/async.c b/kernel/async.c index 5054030..27235f5 100644 --- a/kernel/async.c +++ b/kernel/async.c @@ -92,23 +92,18 @@ extern int initcall_debug; static async_cookie_t __lowest_in_progress(struct list_head *running) { struct async_entry *entry; - async_cookie_t ret = next_cookie; /* begin with "infinity" value */ if (!list_empty(running)) { entry = list_first_entry(running, struct async_entry, list); - ret = entry->cookie; + return entry->cookie; } - if (!list_empty(&async_pending)) { - list_for_each_entry(entry, &async_pending, list) - if (entry->running == running) { - ret = entry->cookie; - break; - } - } + list_for_each_entry(entry, &async_pending, list) + if (entry->running == running) + return entry->cookie; - return ret; + return next_cookie; /* "infinity" value */ } static async_cookie_t lowest_in_progress(struct list_head *running) ^ permalink raw reply related [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 18:21 ` Linus Torvalds @ 2009-06-08 19:17 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 19:17 UTC (permalink / raw) To: Linus Torvalds Cc: Jaswinder Singh Rajput, James Bottomley, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven Linus, 2009/6/8 Linus Torvalds <torvalds@linux-foundation.org>: > > > On Mon, 8 Jun 2009, Chris Clayton wrote: >> >> I can confirm that a kernel built with Jaswinder's patch applied >> survived 200 boots without a panic. > > Ok, goodie. > > Can you confirm that the further cleanup (removing the pointless 'ret' > variable and the useless empty checking around 'for_each_entry') also > works for you? > > Linus > > --- > kernel/async.c | 15 +++++---------- > 1 files changed, 5 insertions(+), 10 deletions(-) > > diff --git a/kernel/async.c b/kernel/async.c > index 5054030..27235f5 100644 > --- a/kernel/async.c > +++ b/kernel/async.c > @@ -92,23 +92,18 @@ extern int initcall_debug; > static async_cookie_t __lowest_in_progress(struct list_head *running) > { > struct async_entry *entry; > - async_cookie_t ret = next_cookie; /* begin with "infinity" value */ > > if (!list_empty(running)) { > entry = list_first_entry(running, > struct async_entry, list); > - ret = entry->cookie; > + return entry->cookie; > } > > - if (!list_empty(&async_pending)) { > - list_for_each_entry(entry, &async_pending, list) > - if (entry->running == running) { > - ret = entry->cookie; > - break; > - } > - } > + list_for_each_entry(entry, &async_pending, list) > + if (entry->running == running) > + return entry->cookie; > > - return ret; > + return next_cookie; /* "infinity" value */ > } > > static async_cookie_t lowest_in_progress(struct list_head *running) > Yes, rc8-git5 with your patch applied has booted 100 times without a panic. May I add that the people who thought of, designed and implemented kexec should have a large and shiny medals pinned to their chests. Well over 1000 kernel boots have been executed on my PC today and, if I hadn't been able to do that automatically with a few lines of script at the head of /etc/rc.d/rc.local, I would have been bleary-eyed before noon :-) Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 19:17 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 19:17 UTC (permalink / raw) To: Linus Torvalds Cc: Jaswinder Singh Rajput, James Bottomley, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven Linus, 2009/6/8 Linus Torvalds <torvalds@linux-foundation.org>: > > > On Mon, 8 Jun 2009, Chris Clayton wrote: >> >> I can confirm that a kernel built with Jaswinder's patch applied >> survived 200 boots without a panic. > > Ok, goodie. > > Can you confirm that the further cleanup (removing the pointless 'ret' > variable and the useless empty checking around 'for_each_entry') also > works for you? > > Linus > > --- > kernel/async.c | 15 +++++---------- > 1 files changed, 5 insertions(+), 10 deletions(-) > > diff --git a/kernel/async.c b/kernel/async.c > index 5054030..27235f5 100644 > --- a/kernel/async.c > +++ b/kernel/async.c > @@ -92,23 +92,18 @@ extern int initcall_debug; > static async_cookie_t __lowest_in_progress(struct list_head *running) > { > struct async_entry *entry; > - async_cookie_t ret = next_cookie; /* begin with "infinity" value */ > > if (!list_empty(running)) { > entry = list_first_entry(running, > struct async_entry, list); > - ret = entry->cookie; > + return entry->cookie; > } > > - if (!list_empty(&async_pending)) { > - list_for_each_entry(entry, &async_pending, list) > - if (entry->running == running) { > - ret = entry->cookie; > - break; > - } > - } > + list_for_each_entry(entry, &async_pending, list) > + if (entry->running == running) > + return entry->cookie; > > - return ret; > + return next_cookie; /* "infinity" value */ > } > > static async_cookie_t lowest_in_progress(struct list_head *running) > Yes, rc8-git5 with your patch applied has booted 100 times without a panic. May I add that the people who thought of, designed and implemented kexec should have a large and shiny medals pinned to their chests. Well over 1000 kernel boots have been executed on my PC today and, if I hadn't been able to do that automatically with a few lines of script at the head of /etc/rc.d/rc.local, I would have been bleary-eyed before noon :-) Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 19:17 ` Chris Clayton @ 2009-06-08 20:03 ` Chris Clayton -1 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 20:03 UTC (permalink / raw) To: Linus Torvalds Cc: Jaswinder Singh Rajput, James Bottomley, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Monday 08 June 2009, Chris Clayton wrote: > Linus, > > 2009/6/8 Linus Torvalds <torvalds@linux-foundation.org>: > > On Mon, 8 Jun 2009, Chris Clayton wrote: > >> I can confirm that a kernel built with Jaswinder's patch applied > >> survived 200 boots without a panic. > > > > Ok, goodie. > > > > Can you confirm that the further cleanup (removing the pointless 'ret' > > variable and the useless empty checking around 'for_each_entry') also > > works for you? > > > > Linus > > > > --- > > kernel/async.c | 15 +++++---------- > > 1 files changed, 5 insertions(+), 10 deletions(-) > > > > diff --git a/kernel/async.c b/kernel/async.c > > index 5054030..27235f5 100644 > > --- a/kernel/async.c > > +++ b/kernel/async.c > > @@ -92,23 +92,18 @@ extern int initcall_debug; > > static async_cookie_t __lowest_in_progress(struct list_head *running) > > { > > struct async_entry *entry; > > - async_cookie_t ret = next_cookie; /* begin with "infinity" value > > */ > > > > if (!list_empty(running)) { > > entry = list_first_entry(running, > > struct async_entry, list); > > - ret = entry->cookie; > > + return entry->cookie; > > } > > > > - if (!list_empty(&async_pending)) { > > - list_for_each_entry(entry, &async_pending, list) > > - if (entry->running == running) { > > - ret = entry->cookie; > > - break; > > - } > > - } > > + list_for_each_entry(entry, &async_pending, list) > > + if (entry->running == running) > > + return entry->cookie; > > > > - return ret; > > + return next_cookie; /* "infinity" value */ > > } > > > > static async_cookie_t lowest_in_progress(struct list_head *running) > > Yes, rc8-git5 with your patch applied has booted 100 times without a panic. > ...so I should have added: Tested-by: Chris Clayton <chris2553@googlemail.com> > May I add that the people who thought of, designed and implemented > kexec should have a large and shiny medals pinned to their chests. > Well over 1000 kernel boots have been executed on my PC today and, if > I hadn't been able to do that automatically with a few lines of script > at the head of /etc/rc.d/rc.local, I would have been bleary-eyed > before noon :-) > > Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 20:03 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 20:03 UTC (permalink / raw) To: Linus Torvalds Cc: Jaswinder Singh Rajput, James Bottomley, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Monday 08 June 2009, Chris Clayton wrote: > Linus, > > 2009/6/8 Linus Torvalds <torvalds@linux-foundation.org>: > > On Mon, 8 Jun 2009, Chris Clayton wrote: > >> I can confirm that a kernel built with Jaswinder's patch applied > >> survived 200 boots without a panic. > > > > Ok, goodie. > > > > Can you confirm that the further cleanup (removing the pointless 'ret' > > variable and the useless empty checking around 'for_each_entry') also > > works for you? > > > > Linus > > > > --- > > kernel/async.c | 15 +++++---------- > > 1 files changed, 5 insertions(+), 10 deletions(-) > > > > diff --git a/kernel/async.c b/kernel/async.c > > index 5054030..27235f5 100644 > > --- a/kernel/async.c > > +++ b/kernel/async.c > > @@ -92,23 +92,18 @@ extern int initcall_debug; > > static async_cookie_t __lowest_in_progress(struct list_head *running) > > { > > struct async_entry *entry; > > - async_cookie_t ret = next_cookie; /* begin with "infinity" value > > */ > > > > if (!list_empty(running)) { > > entry = list_first_entry(running, > > struct async_entry, list); > > - ret = entry->cookie; > > + return entry->cookie; > > } > > > > - if (!list_empty(&async_pending)) { > > - list_for_each_entry(entry, &async_pending, list) > > - if (entry->running == running) { > > - ret = entry->cookie; > > - break; > > - } > > - } > > + list_for_each_entry(entry, &async_pending, list) > > + if (entry->running == running) > > + return entry->cookie; > > > > - return ret; > > + return next_cookie; /* "infinity" value */ > > } > > > > static async_cookie_t lowest_in_progress(struct list_head *running) > > Yes, rc8-git5 with your patch applied has booted 100 times without a panic. > ...so I should have added: Tested-by: Chris Clayton <chris2553@googlemail.com> > May I add that the people who thought of, designed and implemented > kexec should have a large and shiny medals pinned to their chests. > Well over 1000 kernel boots have been executed on my PC today and, if > I hadn't been able to do that automatically with a few lines of script > at the head of /etc/rc.d/rc.local, I would have been bleary-eyed > before noon :-) > > Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 16:51 ` James Bottomley 2009-06-08 17:06 ` Jaswinder Singh Rajput @ 2009-06-08 17:21 ` Linus Torvalds 2009-06-08 17:37 ` Arjan van de Ven 2009-06-08 17:38 ` James Bottomley 1 sibling, 2 replies; 38+ messages in thread From: Linus Torvalds @ 2009-06-08 17:21 UTC (permalink / raw) To: James Bottomley Cc: Chris Clayton, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 8 Jun 2009, James Bottomley wrote: > > The root cause is a reordering of the devices caused by the async code. That's NULL information. OF COURSE the root cause is the async code. We know that. We're looking for the specifics. In particular, before that commit, at most you will wait for too _much_. In other words, it's a "good" wait. Your commit caused it to wait for less, and that then showed a bug. Not all that surprising - it's now not waiting enough. You tried to avoid a deadlock situation of waiting for too much, but you avoided the deadlock by now waiting for too little. I also think that your code is simply buggy. As far as I can tell, int he case of having both running and pending events, you'll always pick the pending cookie. But it's the _running_ cookie that has the lower event number, isn't it? I dunno. It all looks very fishy to me. Linus ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 17:21 ` Linus Torvalds @ 2009-06-08 17:37 ` Arjan van de Ven 2009-06-08 17:38 ` James Bottomley 1 sibling, 0 replies; 38+ messages in thread From: Arjan van de Ven @ 2009-06-08 17:37 UTC (permalink / raw) To: Linus Torvalds Cc: James Bottomley, Chris Clayton, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo Linus Torvalds wrote: > > On Mon, 8 Jun 2009, James Bottomley wrote: >> The root cause is a reordering of the devices caused by the async code. > > That's NULL information. > > OF COURSE the root cause is the async code. We know that. We're looking > for the specifics. > > In particular, before that commit, at most you will wait for too _much_. > In other words, it's a "good" wait. > > Your commit caused it to wait for less, and that then showed a bug. Not > all that surprising - it's now not waiting enough. > > You tried to avoid a deadlock situation of waiting for too much, but you > avoided the deadlock by now waiting for too little. > > I also think that your code is simply buggy. As far as I can tell, int he > case of having both running and pending events, you'll always pick the > pending cookie. But it's the _running_ cookie that has the lower event > number, isn't it? > > I dunno. It all looks very fishy to me. > that's likely my screwup, not james' the patch looks ok to me, it indeed should fix the problem. (and is simpler than the idea I had around using min() ) ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 17:21 ` Linus Torvalds 2009-06-08 17:37 ` Arjan van de Ven @ 2009-06-08 17:38 ` James Bottomley 1 sibling, 0 replies; 38+ messages in thread From: James Bottomley @ 2009-06-08 17:38 UTC (permalink / raw) To: Linus Torvalds Cc: Chris Clayton, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 2009-06-08 at 10:21 -0700, Linus Torvalds wrote: > > On Mon, 8 Jun 2009, James Bottomley wrote: > > > > The root cause is a reordering of the devices caused by the async code. > > That's NULL information. > > OF COURSE the root cause is the async code. We know that. We're looking > for the specifics. > > In particular, before that commit, at most you will wait for too _much_. > In other words, it's a "good" wait. > > Your commit caused it to wait for less, and that then showed a bug. Not > all that surprising - it's now not waiting enough. right ... my question was whether this exposed an existing bug that was hidden by the waiting too much. Actually, I audited all the async code and that's impossible: we don't actually have any async domains at all (except for the spurious superblock s_async_list, which never gets anything added to its runqueue), so it must be a bug in the code. > You tried to avoid a deadlock situation of waiting for too much, but you > avoided the deadlock by now waiting for too little. > > I also think that your code is simply buggy. As far as I can tell, int he > case of having both running and pending events, you'll always pick the > pending cookie. But it's the _running_ cookie that has the lower event > number, isn't it? Yes, see later fix. Assuming we get confirmation from the reporter, we should be good to go. > I dunno. It all looks very fishy to me. Well, the other option is to revert the fix ... since there is no other separated domain, there's nothing really to fix ... the original code that showed the problem was a SCSI feature tree conversion of our current async scanning code to the async infrastructure which used a separate domain. James ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 16:21 ` Linus Torvalds (?) (?) @ 2009-06-08 17:06 ` James Bottomley 2009-06-08 17:42 ` Linus Torvalds 2009-06-08 18:33 ` Chris Clayton -1 siblings, 2 replies; 38+ messages in thread From: James Bottomley @ 2009-06-08 17:06 UTC (permalink / raw) To: Linus Torvalds Cc: Chris Clayton, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 2009-06-08 at 09:21 -0700, Linus Torvalds wrote: > > On Mon, 8 Jun 2009, Chris Clayton wrote: > > > > OK. I reversed that change and built and installed the kernel. It has > > withstood 100 reboots without a panic. Additionally, I pulled the > > latest changes (that will be rc8-git5, I think) from kernel.org, > > reversed the change to that kernel and built and installed it. That > > too withstood 100 reboots without a panic. > > > > Let me know if there's anything else I can do to help fix this. > > That's already pretty convincing. > > James, Arjan? The original oops message is here (a jpg screen capture, > unable to open initial console): > > http://lkml.org/lkml/2009/6/6/142 > > and it's this bug entry: > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474 > Subject : Oops whilst booting > Submitter : Chris Clayton <chris2553@googlemail.com> > Date : 2009-06-06 18:59 (2 days old) > References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4 > > and now bisected down to > > >> commit d5a877e8dd409d8c702986d06485c374b705d340 > >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> > >> Date: Sun May 24 13:03:43 2009 -0700 > >> > >> async: make sure independent async domains can't accidentally entangle > > please advice. Otherwise I'll have to revert. I think it's a bug in the async code. It's providing cookies too high because it doesn't stop after it finds a running entry. Can we try this as the fix? James --- diff --git a/kernel/async.c b/kernel/async.c index 5054030..e4909ee 100644 --- a/kernel/async.c +++ b/kernel/async.c @@ -97,7 +97,7 @@ static async_cookie_t __lowest_in_progress(struct list_head *running) if (!list_empty(running)) { entry = list_first_entry(running, struct async_entry, list); - ret = entry->cookie; + return entry->cookie; } if (!list_empty(&async_pending)) { ^ permalink raw reply related [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 17:06 ` James Bottomley @ 2009-06-08 17:42 ` Linus Torvalds 2009-06-08 17:49 ` James Bottomley 2009-06-08 18:33 ` Chris Clayton 1 sibling, 1 reply; 38+ messages in thread From: Linus Torvalds @ 2009-06-08 17:42 UTC (permalink / raw) To: James Bottomley Cc: Chris Clayton, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 8 Jun 2009, James Bottomley wrote: > > I think it's a bug in the async code. It's providing cookies too high > because it doesn't stop after it finds a running entry. > > Can we try this as the fix? Ok, this looks likely. That said, why doesn't that function look like this? Linus --- kernel/async.c | 15 +++++---------- 1 files changed, 5 insertions(+), 10 deletions(-) diff --git a/kernel/async.c b/kernel/async.c index 5054030..27235f5 100644 --- a/kernel/async.c +++ b/kernel/async.c @@ -92,23 +92,18 @@ extern int initcall_debug; static async_cookie_t __lowest_in_progress(struct list_head *running) { struct async_entry *entry; - async_cookie_t ret = next_cookie; /* begin with "infinity" value */ if (!list_empty(running)) { entry = list_first_entry(running, struct async_entry, list); - ret = entry->cookie; + return entry->cookie; } - if (!list_empty(&async_pending)) { - list_for_each_entry(entry, &async_pending, list) - if (entry->running == running) { - ret = entry->cookie; - break; - } - } + list_for_each_entry(entry, &async_pending, list) + if (entry->running == running) + return entry->cookie; - return ret; + return next_cookie; /* "infinity" value */ } static async_cookie_t lowest_in_progress(struct list_head *running) ^ permalink raw reply related [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 17:42 ` Linus Torvalds @ 2009-06-08 17:49 ` James Bottomley 0 siblings, 0 replies; 38+ messages in thread From: James Bottomley @ 2009-06-08 17:49 UTC (permalink / raw) To: Linus Torvalds Cc: Chris Clayton, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 2009-06-08 at 10:42 -0700, Linus Torvalds wrote: > > On Mon, 8 Jun 2009, James Bottomley wrote: > > > > I think it's a bug in the async code. It's providing cookies too high > > because it doesn't stop after it finds a running entry. > > > > Can we try this as the fix? > > Ok, this looks likely. > > That said, why doesn't that function look like this? That's probably a better style ... or simply put an if ... else if to make it exclusive. James ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 17:06 ` James Bottomley @ 2009-06-08 18:33 ` Chris Clayton 2009-06-08 18:33 ` Chris Clayton 1 sibling, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 18:33 UTC (permalink / raw) To: James Bottomley Cc: Linus Torvalds, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven 2009/6/8 James Bottomley <James.Bottomley@hansenpartnership.com>: > On Mon, 2009-06-08 at 09:21 -0700, Linus Torvalds wrote: >> >> On Mon, 8 Jun 2009, Chris Clayton wrote: >> > >> > OK. I reversed that change and built and installed the kernel. It has >> > withstood 100 reboots without a panic. Additionally, I pulled the >> > latest changes (that will be rc8-git5, I think) from kernel.org, >> > reversed the change to that kernel and built and installed it. That >> > too withstood 100 reboots without a panic. >> > >> > Let me know if there's anything else I can do to help fix this. >> >> That's already pretty convincing. >> >> James, Arjan? The original oops message is here (a jpg screen capture, >> unable to open initial console): >> >> http://lkml.org/lkml/2009/6/6/142 >> >> and it's this bug entry: >> >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474 >> Subject : Oops whilst booting >> Submitter : Chris Clayton <chris2553@googlemail.com> >> Date : 2009-06-06 18:59 (2 days old) >> References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4 >> >> and now bisected down to >> >> >> commit d5a877e8dd409d8c702986d06485c374b705d340 >> >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> >> >> Date: Sun May 24 13:03:43 2009 -0700 >> >> >> >> async: make sure independent async domains can't accidentally entangle >> >> please advice. Otherwise I'll have to revert. > > I think it's a bug in the async code. It's providing cookies too high > because it doesn't stop after it finds a running entry. > > Can we try this as the fix? > > James > > --- > > diff --git a/kernel/async.c b/kernel/async.c > index 5054030..e4909ee 100644 > --- a/kernel/async.c > +++ b/kernel/async.c > @@ -97,7 +97,7 @@ static async_cookie_t __lowest_in_progress(struct list_head *running) > if (!list_empty(running)) { > entry = list_first_entry(running, > struct async_entry, list); > - ret = entry->cookie; > + return entry->cookie; > } > > if (!list_empty(&async_pending)) { > I can also confirm that a kernel with this patch applied has withstood the 100-boot torture. I'll try Linus's version now and report back asap. Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 18:33 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 18:33 UTC (permalink / raw) To: James Bottomley Cc: Linus Torvalds, Jaswinder Singh Rajput, NeilBrown, linux-kernel, scsi, Tejun Heo, Arjan van de Ven 2009/6/8 James Bottomley <James.Bottomley@hansenpartnership.com>: > On Mon, 2009-06-08 at 09:21 -0700, Linus Torvalds wrote: >> >> On Mon, 8 Jun 2009, Chris Clayton wrote: >> > >> > OK. I reversed that change and built and installed the kernel. It has >> > withstood 100 reboots without a panic. Additionally, I pulled the >> > latest changes (that will be rc8-git5, I think) from kernel.org, >> > reversed the change to that kernel and built and installed it. That >> > too withstood 100 reboots without a panic. >> > >> > Let me know if there's anything else I can do to help fix this. >> >> That's already pretty convincing. >> >> James, Arjan? The original oops message is here (a jpg screen capture, >> unable to open initial console): >> >> http://lkml.org/lkml/2009/6/6/142 >> >> and it's this bug entry: >> >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13474 >> Subject : Oops whilst booting >> Submitter : Chris Clayton <chris2553@googlemail.com> >> Date : 2009-06-06 18:59 (2 days old) >> References : http://marc.info/?l=linux-kernel&m=124431487924254&w=4 >> >> and now bisected down to >> >> >> commit d5a877e8dd409d8c702986d06485c374b705d340 >> >> Author: James Bottomley <James.Bottomley@HansenPartnership.com> >> >> Date: Sun May 24 13:03:43 2009 -0700 >> >> >> >> async: make sure independent async domains can't accidentally entangle >> >> please advice. Otherwise I'll have to revert. > > I think it's a bug in the async code. It's providing cookies too high > because it doesn't stop after it finds a running entry. > > Can we try this as the fix? > > James > > --- > > diff --git a/kernel/async.c b/kernel/async.c > index 5054030..e4909ee 100644 > --- a/kernel/async.c > +++ b/kernel/async.c > @@ -97,7 +97,7 @@ static async_cookie_t __lowest_in_progress(struct list_head *running) > if (!list_empty(running)) { > entry = list_first_entry(running, > struct async_entry, list); > - ret = entry->cookie; > + return entry->cookie; > } > > if (!list_empty(&async_pending)) { > I can also confirm that a kernel with this patch applied has withstood the 100-boot torture. I'll try Linus's version now and report back asap. Chris -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 8:08 ` Chris Clayton (?) (?) @ 2009-06-08 14:23 ` James Bottomley 2009-06-08 15:04 ` Chris Clayton 2009-06-08 15:17 ` Chris Clayton -1 siblings, 2 replies; 38+ messages in thread From: James Bottomley @ 2009-06-08 14:23 UTC (permalink / raw) To: Chris Clayton Cc: NeilBrown, Jaswinder Singh Rajput, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 2009-06-08 at 09:08 +0100, Chris Clayton wrote: > Hi Neil, > > Thanks for the reply. > > 2009/6/7 NeilBrown <neilb@suse.de>: > > On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: > >> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: > >>> 2009/6/7 Jaswinder Singh Ra > >>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg > > > > This message says that it found a vfat filesystem on 8:3x (I cannot see > > what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even > > sdc6 or sdc7. > > However the vfat filesystem didn't have /sbin/init. > > > > >>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg > > > > This one says it couldn't find anything at 8,22, which I think > > should be sdb6. > > It also shows that you have and sdc6, but sdb only goes up to sdb3. > > > > So it seems that your disk drives have changed name - not a wholely > > unexpected event these days. > > > > We now need answers to questions like: > > - what device do you expect the root filesystem to be on > > - how is the kernel being told this? Maybe it is hard coded > > into your initrd. Knowing which distro and what /etc/fstab > > says might help (though it wouldn't help me, I'm just about out > > of my depth at this point) > > Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding > > e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. > > > > Yes, I've just been looking at the photographs of the panics again and > I've noticed that two of my discs are being detected in the "wrong > order". There are three HDDS. The first, /dev/sda, is the master on > the first IDE port and contains sda1..sda7. The second, normally > /dev/sdb, is the slave on that port and contains sdb1..sdb6. The > third, normally /dev/sdc, is attached to the first SATA port and > contains sdc1..sdc3. The second photograph I posted shows that sdb and > sdc have been reversed. The first partition on the disc that is > normally /dev/sdb does indeed have a FAT32 filesystem in the first > partition. > > By the way, I should have said that in between the panics that the two > photographs show, I copied contents of /dev/sdc1, which I normally > boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the > reboot festival that bisecting would involve. I also, of course, > changed the name of the root partition that is passed to the kernel by > GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions > shown in the photographs seem inconsistent. Sorry I forgot to mention > that - I really shouldn't do these things late at night :-). Actually, you can save yourself a lot of pain by mounting by label instead ... that way both grub and fstab will find your root disc even if it has swapped order. > As I indicate above, when booting the partition I have set up to do > this bisecting, I expect the root filesystem to be on /dev/hdb6. As I > also indicate, this information is passed to the kernel through GRUB's > /boot/grub/menu.lst. The kernel is configured specifically for my > system and the drivers needed to boot the system are built in to the > kernel, so I don't use an initrd. IIRC, that's the way Slackware is > installed today, except, of course, it's a big fat kernel with all > drivers needed to boot any system built in. I could be wrong on that > though, it's a while since I installed The fact that a slave on the first channel is detected after the SATA indicates a problem with async probing. What are the two drivers for these? James ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 14:23 ` James Bottomley @ 2009-06-08 15:04 ` Chris Clayton 2009-06-08 15:17 ` Chris Clayton 1 sibling, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 15:04 UTC (permalink / raw) To: James Bottomley Cc: NeilBrown, Jaswinder Singh Rajput, linux-kernel, scsi, Tejun Heo, Arjan van de Ven, Linus Torvalds Hi James, 2009/6/8 James Bottomley <James.Bottomley@hansenpartnership.com>: > On Mon, 2009-06-08 at 09:08 +0100, Chris Clayton wrote: >> Hi Neil, >> >> Thanks for the reply. >> >> 2009/6/7 NeilBrown <neilb@suse.de>: >> > On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >> >> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >> >>> 2009/6/7 Jaswinder Singh Ra >> >>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> > >> > This message says that it found a vfat filesystem on 8:3x (I cannot see >> > what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even >> > sdc6 or sdc7. >> > However the vfat filesystem didn't have /sbin/init. >> > >> >> >>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg >> > >> > This one says it couldn't find anything at 8,22, which I think >> > should be sdb6. >> > It also shows that you have and sdc6, but sdb only goes up to sdb3. >> > >> > So it seems that your disk drives have changed name - not a wholely >> > unexpected event these days. >> > >> > We now need answers to questions like: >> > - what device do you expect the root filesystem to be on >> > - how is the kernel being told this? Maybe it is hard coded >> > into your initrd. Knowing which distro and what /etc/fstab >> > says might help (though it wouldn't help me, I'm just about out >> > of my depth at this point) >> > Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding >> > e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. >> > >> >> Yes, I've just been looking at the photographs of the panics again and >> I've noticed that two of my discs are being detected in the "wrong >> order". There are three HDDS. The first, /dev/sda, is the master on >> the first IDE port and contains sda1..sda7. The second, normally >> /dev/sdb, is the slave on that port and contains sdb1..sdb6. The >> third, normally /dev/sdc, is attached to the first SATA port and >> contains sdc1..sdc3. The second photograph I posted shows that sdb and >> sdc have been reversed. The first partition on the disc that is >> normally /dev/sdb does indeed have a FAT32 filesystem in the first >> partition. >> >> By the way, I should have said that in between the panics that the two >> photographs show, I copied contents of /dev/sdc1, which I normally >> boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the >> reboot festival that bisecting would involve. I also, of course, >> changed the name of the root partition that is passed to the kernel by >> GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions >> shown in the photographs seem inconsistent. Sorry I forgot to mention >> that - I really shouldn't do these things late at night :-). > > Actually, you can save yourself a lot of pain by mounting by label > instead ... that way both grub and fstab will find your root disc even > if it has swapped order. > >> As I indicate above, when booting the partition I have set up to do >> this bisecting, I expect the root filesystem to be on /dev/hdb6. As I >> also indicate, this information is passed to the kernel through GRUB's >> /boot/grub/menu.lst. The kernel is configured specifically for my >> system and the drivers needed to boot the system are built in to the >> kernel, so I don't use an initrd. IIRC, that's the way Slackware is >> installed today, except, of course, it's a big fat kernel with all >> drivers needed to boot any system built in. I could be wrong on that >> though, it's a while since I installed > > The fact that a slave on the first channel is detected after the SATA > indicates a problem with async probing. What are the two drivers for > these? > I think this is the relevant part of my .config: CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y # CONFIG_SATA_PMP is not set # CONFIG_SATA_AHCI is not set # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # CONFIG_SATA_SVW is not set CONFIG_ATA_PIIX=y <<<<================= # CONFIG_SATA_MV is not set # CONFIG_SATA_NV is not set # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set The ATA/(E)IDE driver is disabled. Chris > James > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 15:04 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 15:04 UTC (permalink / raw) To: James Bottomley Cc: NeilBrown, Jaswinder Singh Rajput, linux-kernel, scsi, Tejun Heo, Arjan van de Ven, Linus Torvalds Hi James, 2009/6/8 James Bottomley <James.Bottomley@hansenpartnership.com>: > On Mon, 2009-06-08 at 09:08 +0100, Chris Clayton wrote: >> Hi Neil, >> >> Thanks for the reply. >> >> 2009/6/7 NeilBrown <neilb@suse.de>: >> > On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >> >> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >> >>> 2009/6/7 Jaswinder Singh Ra >> >>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> > >> > This message says that it found a vfat filesystem on 8:3x (I cannot see >> > what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even >> > sdc6 or sdc7. >> > However the vfat filesystem didn't have /sbin/init. >> > >> >> >>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg >> > >> > This one says it couldn't find anything at 8,22, which I think >> > should be sdb6. >> > It also shows that you have and sdc6, but sdb only goes up to sdb3. >> > >> > So it seems that your disk drives have changed name - not a wholely >> > unexpected event these days. >> > >> > We now need answers to questions like: >> > - what device do you expect the root filesystem to be on >> > - how is the kernel being told this? Maybe it is hard coded >> > into your initrd. Knowing which distro and what /etc/fstab >> > says might help (though it wouldn't help me, I'm just about out >> > of my depth at this point) >> > Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding >> > e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. >> > >> >> Yes, I've just been looking at the photographs of the panics again and >> I've noticed that two of my discs are being detected in the "wrong >> order". There are three HDDS. The first, /dev/sda, is the master on >> the first IDE port and contains sda1..sda7. The second, normally >> /dev/sdb, is the slave on that port and contains sdb1..sdb6. The >> third, normally /dev/sdc, is attached to the first SATA port and >> contains sdc1..sdc3. The second photograph I posted shows that sdb and >> sdc have been reversed. The first partition on the disc that is >> normally /dev/sdb does indeed have a FAT32 filesystem in the first >> partition. >> >> By the way, I should have said that in between the panics that the two >> photographs show, I copied contents of /dev/sdc1, which I normally >> boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the >> reboot festival that bisecting would involve. I also, of course, >> changed the name of the root partition that is passed to the kernel by >> GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions >> shown in the photographs seem inconsistent. Sorry I forgot to mention >> that - I really shouldn't do these things late at night :-). > > Actually, you can save yourself a lot of pain by mounting by label > instead ... that way both grub and fstab will find your root disc even > if it has swapped order. > >> As I indicate above, when booting the partition I have set up to do >> this bisecting, I expect the root filesystem to be on /dev/hdb6. As I >> also indicate, this information is passed to the kernel through GRUB's >> /boot/grub/menu.lst. The kernel is configured specifically for my >> system and the drivers needed to boot the system are built in to the >> kernel, so I don't use an initrd. IIRC, that's the way Slackware is >> installed today, except, of course, it's a big fat kernel with all >> drivers needed to boot any system built in. I could be wrong on that >> though, it's a while since I installed > > The fact that a slave on the first channel is detected after the SATA > indicates a problem with async probing. What are the two drivers for > these? > I think this is the relevant part of my .config: CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_ACPI=y # CONFIG_SATA_PMP is not set # CONFIG_SATA_AHCI is not set # CONFIG_SATA_SIL24 is not set CONFIG_ATA_SFF=y # CONFIG_SATA_SVW is not set CONFIG_ATA_PIIX=y <<<<================= # CONFIG_SATA_MV is not set # CONFIG_SATA_NV is not set # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set The ATA/(E)IDE driver is disabled. Chris > James > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 14:23 ` James Bottomley @ 2009-06-08 15:17 ` Chris Clayton 2009-06-08 15:17 ` Chris Clayton 1 sibling, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 15:17 UTC (permalink / raw) To: James Bottomley Cc: NeilBrown, Jaswinder Singh Rajput, linux-kernel, scsi, Tejun Heo, Arjan van de Ven Sorry James, I forgot to ask... 2009/6/8 James Bottomley <James.Bottomley@hansenpartnership.com>: > On Mon, 2009-06-08 at 09:08 +0100, Chris Clayton wrote: >> Hi Neil, >> >> Thanks for the reply. >> >> 2009/6/7 NeilBrown <neilb@suse.de>: >> > On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >> >> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >> >>> 2009/6/7 Jaswinder Singh Ra >> >>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> > >> > This message says that it found a vfat filesystem on 8:3x (I cannot see >> > what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even >> > sdc6 or sdc7. >> > However the vfat filesystem didn't have /sbin/init. >> > >> >> >>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg >> > >> > This one says it couldn't find anything at 8,22, which I think >> > should be sdb6. >> > It also shows that you have and sdc6, but sdb only goes up to sdb3. >> > >> > So it seems that your disk drives have changed name - not a wholely >> > unexpected event these days. >> > >> > We now need answers to questions like: >> > - what device do you expect the root filesystem to be on >> > - how is the kernel being told this? Maybe it is hard coded >> > into your initrd. Knowing which distro and what /etc/fstab >> > says might help (though it wouldn't help me, I'm just about out >> > of my depth at this point) >> > Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding >> > e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. >> > >> >> Yes, I've just been looking at the photographs of the panics again and >> I've noticed that two of my discs are being detected in the "wrong >> order". There are three HDDS. The first, /dev/sda, is the master on >> the first IDE port and contains sda1..sda7. The second, normally >> /dev/sdb, is the slave on that port and contains sdb1..sdb6. The >> third, normally /dev/sdc, is attached to the first SATA port and >> contains sdc1..sdc3. The second photograph I posted shows that sdb and >> sdc have been reversed. The first partition on the disc that is >> normally /dev/sdb does indeed have a FAT32 filesystem in the first >> partition. >> >> By the way, I should have said that in between the panics that the two >> photographs show, I copied contents of /dev/sdc1, which I normally >> boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the >> reboot festival that bisecting would involve. I also, of course, >> changed the name of the root partition that is passed to the kernel by >> GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions >> shown in the photographs seem inconsistent. Sorry I forgot to mention >> that - I really shouldn't do these things late at night :-). > > Actually, you can save yourself a lot of pain by mounting by label > instead ... that way both grub and fstab will find your root disc even > if it has swapped order. > Would I be right in assuming from this that "out-of-order" detection is expected behaviour? If so, I'll fix up my system and shut up :-) I suspect I may not be the only person on the planet who specifies the root filesystem in this way, though. Thanks >> As I indicate above, when booting the partition I have set up to do >> this bisecting, I expect the root filesystem to be on /dev/hdb6. As I >> also indicate, this information is passed to the kernel through GRUB's >> /boot/grub/menu.lst. The kernel is configured specifically for my >> system and the drivers needed to boot the system are built in to the >> kernel, so I don't use an initrd. IIRC, that's the way Slackware is >> installed today, except, of course, it's a big fat kernel with all >> drivers needed to boot any system built in. I could be wrong on that >> though, it's a while since I installed > > The fact that a slave on the first channel is detected after the SATA > indicates a problem with async probing. What are the two drivers for > these? > > James > > > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting @ 2009-06-08 15:17 ` Chris Clayton 0 siblings, 0 replies; 38+ messages in thread From: Chris Clayton @ 2009-06-08 15:17 UTC (permalink / raw) To: James Bottomley Cc: NeilBrown, Jaswinder Singh Rajput, linux-kernel, scsi, Tejun Heo, Arjan van de Ven Sorry James, I forgot to ask... 2009/6/8 James Bottomley <James.Bottomley@hansenpartnership.com>: > On Mon, 2009-06-08 at 09:08 +0100, Chris Clayton wrote: >> Hi Neil, >> >> Thanks for the reply. >> >> 2009/6/7 NeilBrown <neilb@suse.de>: >> > On Mon, June 8, 2009 8:31 am, Jaswinder Singh Rajput wrote: >> >> On Sun, 2009-06-07 at 19:38 +0100, Chris Clayton wrote: >> >>> 2009/6/7 Jaswinder Singh Ra >> >>> >> > http://img231.imageshack.us/img231/8931/dscn0610.jpg >> > >> > This message says that it found a vfat filesystem on 8:3x (I cannot see >> > what digit should be 'x'). That is probably sdc1 or sdc2. Maybe even >> > sdc6 or sdc7. >> > However the vfat filesystem didn't have /sbin/init. >> > >> >> >>> http://img99.imageshack.us/my.php?image=dscn0617b.jpg >> > >> > This one says it couldn't find anything at 8,22, which I think >> > should be sdb6. >> > It also shows that you have and sdc6, but sdb only goes up to sdb3. >> > >> > So it seems that your disk drives have changed name - not a wholely >> > unexpected event these days. >> > >> > We now need answers to questions like: >> > - what device do you expect the root filesystem to be on >> > - how is the kernel being told this? Maybe it is hard coded >> > into your initrd. Knowing which distro and what /etc/fstab >> > says might help (though it wouldn't help me, I'm just about out >> > of my depth at this point) >> > Maybe if you changed /etc/fstab to mount by uuid instead of hardcoding >> > e.g. /etc/sdb3, and then run "mkinitramfs" or whatever, it might work. >> > >> >> Yes, I've just been looking at the photographs of the panics again and >> I've noticed that two of my discs are being detected in the "wrong >> order". There are three HDDS. The first, /dev/sda, is the master on >> the first IDE port and contains sda1..sda7. The second, normally >> /dev/sdb, is the slave on that port and contains sdb1..sdb6. The >> third, normally /dev/sdc, is attached to the first SATA port and >> contains sdc1..sdc3. The second photograph I posted shows that sdb and >> sdc have been reversed. The first partition on the disc that is >> normally /dev/sdb does indeed have a FAT32 filesystem in the first >> partition. >> >> By the way, I should have said that in between the panics that the two >> photographs show, I copied contents of /dev/sdc1, which I normally >> boot from, to /dev/sdb6, so that I minimised the risk to sdc1 in the >> reboot festival that bisecting would involve. I also, of course, >> changed the name of the root partition that is passed to the kernel by >> GRUB and amended /etc/fstab on /dev/sdb6. That's why the partitions >> shown in the photographs seem inconsistent. Sorry I forgot to mention >> that - I really shouldn't do these things late at night :-). > > Actually, you can save yourself a lot of pain by mounting by label > instead ... that way both grub and fstab will find your root disc even > if it has swapped order. > Would I be right in assuming from this that "out-of-order" detection is expected behaviour? If so, I'll fix up my system and shut up :-) I suspect I may not be the only person on the planet who specifies the root filesystem in this way, though. Thanks >> As I indicate above, when booting the partition I have set up to do >> this bisecting, I expect the root filesystem to be on /dev/hdb6. As I >> also indicate, this information is passed to the kernel through GRUB's >> /boot/grub/menu.lst. The kernel is configured specifically for my >> system and the drivers needed to boot the system are built in to the >> kernel, so I don't use an initrd. IIRC, that's the way Slackware is >> installed today, except, of course, it's a big fat kernel with all >> drivers needed to boot any system built in. I could be wrong on that >> though, it's a while since I installed > > The fact that a slave on the first channel is detected after the SATA > indicates a problem with async probing. What are the two drivers for > these? > > James > > > -- No, Sir; there is nothing which has yet been contrived by man, by which so much happiness is produced as by a good tavern or inn - Doctor Samuel Johnson ^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: 2.6.30-rc8 Oops whilst booting 2009-06-08 15:17 ` Chris Clayton (?) @ 2009-06-08 15:32 ` James Bottomley -1 siblings, 0 replies; 38+ messages in thread From: James Bottomley @ 2009-06-08 15:32 UTC (permalink / raw) To: Chris Clayton Cc: NeilBrown, Jaswinder Singh Rajput, linux-kernel, scsi, Tejun Heo, Arjan van de Ven On Mon, 2009-06-08 at 16:17 +0100, Chris Clayton wrote: > > Actually, you can save yourself a lot of pain by mounting by label > > instead ... that way both grub and fstab will find your root disc even > > if it has swapped order. > > > > Would I be right in assuming from this that "out-of-order" detection > is expected behaviour? If so, I'll fix up my system and shut up :-) I > suspect I may not be the only person on the planet who specifies the > root filesystem in this way, though. Yes and no ... yes generally because parallel asynchronous probing does relax the ordering rules, so if you have multiple devices the ordering can easily change. No in your particular case because you have a single ata_piix and even with async enabled it should probe PATA first (master and slave) followed by SATA. The fact that the PATA and SATA probes didn't synchronise is a bug somewhere, but I'm not sure where. Could you fix your system to do the label mounting and post the full boot log where it's out of sequence? I have a nasty feeling we might have got the ata probe order correct only to be thrown out of order by sd driver attachment. James ^ permalink raw reply [flat|nested] 38+ messages in thread
end of thread, other threads:[~2009-06-08 20:05 UTC | newest] Thread overview: 38+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-06-06 18:59 2.6.30-rc8 Oops whilst booting Chris Clayton 2009-06-06 21:15 ` Chris Clayton 2009-06-07 13:25 ` Jaswinder Singh Rajput 2009-06-07 18:38 ` Chris Clayton 2009-06-07 22:31 ` Jaswinder Singh Rajput 2009-06-07 22:55 ` NeilBrown 2009-06-08 8:08 ` Chris Clayton 2009-06-08 8:08 ` Chris Clayton 2009-06-08 10:58 ` Chris Clayton 2009-06-08 10:58 ` Chris Clayton 2009-06-08 11:34 ` Jaswinder Singh Rajput 2009-06-08 12:53 ` Chris Clayton 2009-06-08 12:53 ` Chris Clayton 2009-06-08 16:21 ` Linus Torvalds 2009-06-08 16:21 ` Linus Torvalds 2009-06-08 16:51 ` James Bottomley 2009-06-08 17:06 ` Jaswinder Singh Rajput 2009-06-08 17:45 ` Chris Clayton 2009-06-08 17:45 ` Chris Clayton 2009-06-08 18:21 ` Linus Torvalds 2009-06-08 19:17 ` Chris Clayton 2009-06-08 19:17 ` Chris Clayton 2009-06-08 20:03 ` Chris Clayton 2009-06-08 20:03 ` Chris Clayton 2009-06-08 17:21 ` Linus Torvalds 2009-06-08 17:37 ` Arjan van de Ven 2009-06-08 17:38 ` James Bottomley 2009-06-08 17:06 ` James Bottomley 2009-06-08 17:42 ` Linus Torvalds 2009-06-08 17:49 ` James Bottomley 2009-06-08 18:33 ` Chris Clayton 2009-06-08 18:33 ` Chris Clayton 2009-06-08 14:23 ` James Bottomley 2009-06-08 15:04 ` Chris Clayton 2009-06-08 15:04 ` Chris Clayton 2009-06-08 15:17 ` Chris Clayton 2009-06-08 15:17 ` Chris Clayton 2009-06-08 15:32 ` James Bottomley
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.
