Mailing List Archive: Linux: Kernel

2.6.13-rc3-mm3

1 2 3 4

View All

Index | Next | Previous | View Threaded

akpm at osdl

Jul 29, 2005, 2:27 AM

Post #26 of 90 (868 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Matthias Urlichs <smurf [at] smurf> wrote:
>
> Hi, Rafael J. Wysocki wrote:
>
> > start a binary search
>
> Note that if you work from my git import, git has a nice tree bisection
> option.

Is that documented anywhere?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

smurf at smurf

Jul 29, 2005, 5:01 AM

Post #27 of 90 (868 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Hi,

Andrew Morton:
> Matthias Urlichs <smurf [at] smurf> wrote:
> > Note that if you work from my git import, git has a nice tree bisection
> > option.
>
> Is that documented anywhere?

*checking* Apparently not, not unless you count the git list's archive.
(It's git-rev-list.)

I'll fix that.

--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf [at] smurf
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
The makers may make
and the users may use,
but the fixers must fix
with but minimal clues

Attachments:

signature.asc (0.18 KB)

mbligh at mbligh

Jul 29, 2005, 8:21 AM

Post #28 of 90 (865 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

>> > - There's a pretty large x86_64 update here which naughty maintainer wants
>> > in 2.6.13. Extra testing, please.
>>
>> Is still regressed as of 2.6.12 for me, at least. Crashes in TSC sync.
>> Talked to Andi about it at OLS, but then drank too much to remember the
>> conclusion ... however, it's still broken ;-)
>>
>> Matrix is here (see left hand column).
>>
>> http://test.kernel.org/
>>
>> Example boot log is here:
>>
>> http://test.kernel.org/9447/debug/console.log
>
> Does Eric's recent fix fix it?
>
>
> From: Eric W. Biederman <ebiederm [at] xmission>
>
> sync_tsc was using smp_call_function to ask the boot processor to report
> it's tsc value. smp_call_function performs an IPI_send_allbutself which is
> a broadcast ipi. There is a window during processor startup during which
> the target cpu has started and before it has initialized it's interrupt
> vectors so it can properly process an interrupt. Receveing an interrupt
> during that window will triple fault the cpu and do other nasty things.

Wheeeeeeee! that does indeed seem to work. Nice job.

> I believe this patch suffers from apicid versus logical cpu number
> confusion. I copied the basic logic from smp_send_reschedule and I can't
> find where that translates from the logical cpuid to apicid. So it isn't
> quite correct yet. It should be close enough that it shouldn't be too hard
> to finish it up.
>
> More bug fixes after I have slept but I figured I needed to get this
> one out for review.

Eric, when you have a final version, throw it over to me, and I'll give
that one a spin-test too ...

Thanks!

M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

tk-shockwave at web

Jul 29, 2005, 8:48 AM

Post #29 of 90 (890 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Andrew Morton schrieb:
> Michael Thonke <iogl64nx [at] gmail> wrote:
>> here again I have two problems. With 2.6.13-rc3-mm3 I have problems
>> using my SATA drives on Intel ICH6.
>> The kernel can't route there IRQs or can't discover them. the option
>> irqpoll got them to work now.
>> The problem is new because 2.6.13-rc3[-mm1,mm2] work without any problems.
>
> OK. Please generate the full dmesg output for -mm2 and for -mm3 and run
> `diff -u dmesg.mm2 dmesg.mm3' and send it? And keep those files because we
> may end up needing to add them to an acpi bugzilla entry ;)

Well I did a little mistake..it only worked correctly up to
2.6.13-rc3-mm1 but this dmesg output I have.

Well as I save mm[2,3] are unable to setup the correct IRQs for the
devices..and please note that 2.6.13-rc3-mm3 only booted with irqpoll so
its in the dmesg output "dmesg.mm3"
Normaly the IRQ routed to something about 1xx now they are 1-21?! Caused
by irqpoll?

>
>> The SATA drives are Samsung HD160JJ SATAII. The mainboard I use is a
>> ASUS P4GPL-X.
>>
>> Second one is about Intel HD-Codec (snd-hda-intel) on modprobe when
>> loading the module it gives me
>>
>> ---> snip
>> hda_codec: Unknown model for ALC880, trying auto-probe from BIOS...
>
> Does -mm2 print that `unknown model' message?

Yes and mm1 it's a wide problem as I found many posts on ALSA Forums
But the big problem behind is...after it oops
My Linux Raid (md) goes bad then..at reboot it gives me more oops and
all changes on FS (reiser4) lost..and if I wouldn't use snd-hda-intel as
modul the hole system hung at boot.

>
>> Unable to handle kernel NULL pointer dereference at virtual address 00000000
>> printing eip:
>> f88713f4
>> *pde = 00000000
>> Oops: 0002 [#1]
>> PREEMPT
>> last sysfs file:
>> Modules linked in: snd_hda_intel snd_hda_codec nvidia
>> CPU: 0
>> EIP: 0060:[<f88713f4>] Tainted: P VLI
>
> Please verify that it happens without the nvidia module loaded.
>
>> EFLAGS: 00010293 (2.6.13-rc3-mm3pm)
>> eax: fffffffe ebx: f3b33548 ecx: 00000000 edx: 00000000
>> esi: f3b33400 edi: 00000000 ebp: 00000006 esp: f0371ddc
>> ds: 007b es: 007b ss: 0068
>> Process modprobe (pid: 7398, threadinfo=f0370000 task=f4183560)
>> Stack: 00000000 00000000 00000000 00000000 f3b33400 f3b33548 f0f1d000
>> f8871933
>> f3b33400 f0f1d000 f8871bbd f8875478 f88748f6 00000001 f886d77e
>> 00000f00
>> 00000005 00000000 f0f1d000 f54d04c0 00000000 f886d984 00000f00
>> 00000002
>> Call Trace:
>> [<f8871933>]
>> [<f8871bbd>]
>
> Odd trace. Do you have CONFIG_KALLSYMS enabled? If not, please turn it on.

Mh I tried but my system freezes on boot then. And screen leaves blank.
>

Thank you Andrew and the other for the great help up to here.

Greets

Best regards
Michael

Attachments:

dmesg-mm1-mm3.diif (13.5 KB)

dmesg.mm1 (14.2 KB)

dmesg.mm3 (15.3 KB)

dmesg.oops_mm1 (15.3 KB)

ebiederm at xmission

Jul 29, 2005, 9:15 AM

Post #30 of 90 (868 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

"Martin J. Bligh" <mbligh [at] mbligh> writes:

>> From: Eric W. Biederman <ebiederm [at] xmission>
>>
>> sync_tsc was using smp_call_function to ask the boot processor to report
>> it's tsc value. smp_call_function performs an IPI_send_allbutself which is
>> a broadcast ipi. There is a window during processor startup during which
>> the target cpu has started and before it has initialized it's interrupt
>> vectors so it can properly process an interrupt. Receveing an interrupt
>> during that window will triple fault the cpu and do other nasty things.
>
> Wheeeeeeee! that does indeed seem to work. Nice job.

Welcome. I hadn't how many people were tracking this.

>> I believe this patch suffers from apicid versus logical cpu number
>> confusion. I copied the basic logic from smp_send_reschedule and I can't
>> find where that translates from the logical cpuid to apicid. So it isn't
>> quite correct yet. It should be close enough that it shouldn't be too hard
>> to finish it up.
>>
>> More bug fixes after I have slept but I figured I needed to get this
>> one out for review.
>
> Eric, when you have a final version, throw it over to me, and I'll give
> that one a spin-test too ...

With respect to the fix that is final. The rest of the bug
fixes in my queue are for other problems.

Mostly my concerns are with respect to apicid vs logical cpu
numbers that I'm not certain are handled properly in the code.
genapic_flat doesn't seem to do any translation. And I don't
recall if boot_cpu_id is an apic_id or a logical cpu number.
On most hardware it is 0 in either case so it doesn't matter.

Eric

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

akpm at osdl

Jul 29, 2005, 12:33 PM

Post #31 of 90 (894 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Michael Thonke <tk-shockwave [at] web> wrote:
>
> Andrew Morton schrieb:
> > Michael Thonke <iogl64nx [at] gmail> wrote:
> >> here again I have two problems. With 2.6.13-rc3-mm3 I have problems
> >> using my SATA drives on Intel ICH6.
> >> The kernel can't route there IRQs or can't discover them. the option
> >> irqpoll got them to work now.
> >> The problem is new because 2.6.13-rc3[-mm1,mm2] work without any problems.
> >
> > OK. Please generate the full dmesg output for -mm2 and for -mm3 and run
> > `diff -u dmesg.mm2 dmesg.mm3' and send it? And keep those files because we
> > may end up needing to add them to an acpi bugzilla entry ;)
>
> Well I did a little mistake..it only worked correctly up to
> 2.6.13-rc3-mm1 but this dmesg output I have.
>
> Well as I save mm[2,3] are unable to setup the correct IRQs for the
> devices..and please note that 2.6.13-rc3-mm3 only booted with irqpoll so
> its in the dmesg output "dmesg.mm3"
> Normaly the IRQ routed to something about 1xx now they are 1-21?! Caused
> by irqpoll?
>

Are these problems only present in -mm kernels? Does 2.6.13-rc4 work OK?

> > Odd trace. Do you have CONFIG_KALLSYMS enabled? If not, please turn it on.
>
> Mh I tried but my system freezes on boot then. And screen leaves blank.
> >

Oh geeze.

@@ -53,10 +23,18 @@
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
+ ACPI-0287: *** Error: Region SystemMemory(0) has no handler
+ ACPI-0127: *** Error: acpi_load_tables: Could not load namespace: AE_NOT_EXIST
+ ACPI-0136: *** Error: acpi_load_tables: Could not load tables: AE_NOT_EXIST
+ACPI: Unable to load the System Description Tables
ENABLING IO-APIC IRQs
-..TIMER: vector=0x31 pin1=2 pin2=0
+..TIMER: vector=0x31 pin1=2 pin2=-1
NET: Registered protocol family 16
PCI: Using configuration type 1
+ACPI: Subsystem revision 20050708
+ACPI: Interpreter disabled.

Well it looks like ACPI committed suicide, so there's probably not much
point looking at the other things until that gets addressed.

Would you have time to raise a kernel bugzilla entry for this? Raise it
against the ACPI AML interpreter, version 20050708 and mention the above
failure. The output of acpidump (from
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20050727.tar.gz)
will probably be asked for.

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

khalid_aziz at hp

Jul 29, 2005, 4:05 PM

Post #32 of 90 (898 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Serial console is broken on ia64 on an HP rx2600 machine on
2.6.13-rc3-mm3. When kernel is booted up with "console=ttyS,...", no
output ever appears on the console and system is hung. So I booted the
kernel with "console=uart,mmio,0xff5e0000" to enable early console and
here is how far the kernel got before hanging:

-------
Linux version 2.6.13-rc3-mm3 (root [at] mar) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #4 SMP Fri Jul 29 16:30:41 MDT 2005
EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
booting generic kernel on platform hpzx1
PCDP: v0 at 0x3fb2c000
Explicit "console="; ignoring PCDP
Early serial console at MMIO 0xff5e0000 (options '115200')
efi.trim_top: ignoring 4KB of memory at 0x0 due to granule hole at 0x0
efi.trim_top: ignoring 636KB of memory at 0x1000 due to granule hole at 0x0
efi.trim_bottom: ignoring 15360KB of memory at 0x100000 due to granule hole at 0x0
SAL 3.1: HP version 2.31
SAL Platform features: None
SAL: AP wakeup using external interrupt vector 0xff
No logical to physical processor mapping available
ACPI: Local APIC address c0000000fee00000
GSI 36 (level, low) -> CPU 0 (0x0000) vector 48
2 CPUs available, 2 CPUs total
MCA related initialization done
Virtual mem_map starts at 0xa0007fffc7200000
Built 1 zonelists
Kernel command line: BOOT_IMAGE=scsi1:/EFI/debian/boot/vmlinuz-2.6.13-rc3-mm3 root=/dev/sdb2 console=uart,mmio,0xff5e0000 ro
PID hash table entries: 4096 (order: 12, 131072 bytes)
Console: colour VGA+ 80x25
Memory: 12439136k/12542128k available (7051k code, 116240k reserved, 3406k data, 352k init)
Leaving McKinley Errata 9 workaround enabled
Dentry cache hash table entries: 2097152 (order: 10, 16777216 bytes)
Inode-cache hash table entries: 1048576 (order: 9, 8388608 bytes)
Mount-cache hash table entries: 1024
Boot processor id 0x0/0x0
CPU 1: synchronized ITC with CPU 0 (last diff -5 cycles, maxerr 433 cycles)
Brought up 2 CPUs
Total of 2 processors activated (2695.16 BogoMIPS).
-> [0][1][ 786432] 0.5 [ 0.5] (0): ( 500513 250256)
-> [0][1][ 827823] 0.5 [ 0.5] (0): ( 529015 139379)
-> [0][1][ 871392] 0.5 [ 0.5] (0): ( 557119 83741)
-> [0][1][ 917254] 0.5 [ 0.5] (0): ( 585481 56051)
-> [0][1][ 965530] 0.6 [ 0.6] (0): ( 615654 43112)
-> [0][1][1016347] 0.6 [ 0.6] (0): ( 653296 40377)
-> [0][1][1069838] 0.6 [ 0.6] (0): ( 681359 34220)
-> [0][1][1126145] 0.7 [ 0.7] (0): ( 706209 29535)
-> [0][1][1185415] 0.7 [ 0.7] (0): ( 754788 39057)
-> [0][1][1247805] 0.7 [ 0.7] (0): ( 788675 36472)
-> [0][1][1313478] 0.8 [ 0.8] (0): ( 840102 43949)
-> [0][1][1382608] 0.7 [ 0.8] (0): ( 742042 71004)
-> [0][1][1455376] 0.6 [ 0.8] (0): ( 653934 79556)
-> [0][1][1531974] 0.7 [ 0.8] (0): ( 766991 96306)
-> [0][1][1612604] 0.7 [ 0.8] (0): ( 779253 54284)
-> [0][1][1697477] 0.5 [ 0.8] (0): ( 534912 149312)
-> [0][1][1786817] 0.5 [ 0.8] (0): ( 503106 90559)
-> found max.
[0][1] working set size found: 1313478, cost: 840102
---------------------
| migration cost matrix (max_cache_size: 1572864, cpu: -1 MHz):
---------------------
[00] [01]
[00]: - 1.6(0)
[01]: 1.6(0) -
--------------------------------
| cacheflush times [1]: 1.6 (1680204)
| calibration delay: 1 seconds
--------------------------------
NET: Registered protocol family 16
ACPI: bus type pci registered
ACPI: Subsystem revision 20050708
ACPI-0509: *** Error: Method execution failed [\PARS.GFIT] (Node e0000002ffff8a00), AE_BAD_PARAMETER
ACPI-0509: *** Error: Method execution failed [\_SB_.SBA0._INI] (Node e0000002ffffa780), AE_BAD_PARAMETER
ACPI: Interpreter enabled
ACPI: Using IOSAPIC for interrupt routing
SCSI subsystem initialized
perfmon: version 2.0 IRQ 238
perfmon: Itanium 2 PMU detected, 16 PMCs, 18 PMDs, 4 counters (47 bits)
PAL Information Facility v0.5
perfmon: added sampling format default_format
perfmon_default_smpl: default_format v2.0 registered
Total HugeTLB memory allocated, 0
SGI XFS with large block/inode numbers, no debug enabled
Initializing Cryptographic API
EFI Time Services Driver v0.4
i8042.c: No controller found.
Serial: 8250/16550 driver $Revision: 1.90 $ 6 ports, IRQ sharing enabled
mice: PS/2 mouse device common for all mice
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Intel(R) PRO/1000 Network Driver - version 6.0.60-k2
Copyright (c) 1999-2005 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.4.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
netconsole: not configured, aborting
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
Fusion MPT base driver 3.03.02
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.03.02
EFI Variables Facility v0.08 2004-May-17
NET: Registered protocol family 2
IP route cache hash table entries: 2097152 (order: 10, 16777216 bytes)
TCP established hash table entries: 8388608 (order: 13, 134217728 bytes)
TCP bind hash table entries: 65536 (order: 6, 1048576 bytes)
TCP: Hash tables configured (established 8388608 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
No ttyS device at MMIO 0xff5e0000 for console
-------

Serial driver failed to find any serial ports. I am using defconfig. A
2.6.13-rc3 kernel (no mm3 patch) compiled with defconfig boots up fine
and finds all serial ports.

--
Khalid

On Thu, 2005-07-28 at 02:58 -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm3/
>
> - Added the anonymous pagefault scalability enhancement patches.
>
> I remain fairly dubious about this - it seems a fairly specific and
> complex piece of work to speed up one extremely specific part of one type of
> computer's one type of workload. Surely there's a better way :(
>
> The patches at present spit warnings or don't compile on lots of
> architectures. x86, x86_64, ppc64 and ia64 are OK.
>
> - There's a pretty large x86_64 update here which naughty maintainer wants
> in 2.6.13. Extra testing, please.
>
> - Dropped git-net.patch (davem's net devel tree). I'm seeing weird TCP
> hangs. I'm fairly sure they're present in mainline, but was unable to
> reproduce it without git-net.patch when I was actually trying.
>
>
>
> Changes since 2.6.13-rc3-mm2:
>
>
> linus.patch
> git-acpi.patch
> git-cryptodev.patch
> git-drm.patch
> git-audit.patch
> git-input.patch
> git-kbuild.patch
> git-libata-adma-mwi.patch
> git-libata-chs-support.patch
> git-libata-passthru.patch
> git-libata-promise-sata-pata.patch
> git-netdev-chelsio.patch
> git-netdev-e100.patch
> git-netdev-smc91x-eeprom.patch
> git-netdev-ieee80211-wifi.patch
> git-ocfs2.patch
> git-serial.patch
> git-scsi-block.patch
> git-scsi-misc-drivers-scsi-chc-remove-devfs-stuff.patch
>
> Subsystem trees
>
> -i2c-mpc-restore-code-removed.patch
> -really-__nocast-annotate-kmalloc_node.patch
> -mips-fbdev-kconfig-fix.patch
> -md-when-resizing-an-array-we-need-to-update-resync_max_sectors-as-well-as-size.patch
> -uml-readd-missing-define-to-arch-um-makefile-i386.patch
> -uml-add-dependency-to-arch-um-makefile-for-parallel-builds.patch
> -uml-add-skas0-command-line-option.patch
> -uml-update-module-interface.patch
> -uml-fix-misdeclared-function.patch
> -x86_64-fix-smp-boot-lockup-on-some-machines.patch
> -try_to_freeze-call-fixes.patch
> -add-missing-tvaudio-try_to_freeze.patch
> -fix-missing-refrigerator-invocation-in-jffs2.patch
> -as-ioched-tunable-encoding-fix.patch
> -reiserfs-fix-deadlock-in-inode-creation-failure-path-w-default-acl.patch
> -ext2-drop-quota-reference-before-releasing-inode.patch
> -ext3-drop-quota-references-before-releasing-inode.patch
> -pnp-build-fix.patch
> -address-bug-using-smp_processor_id-in-preemptible.patch
> -watchdog-add-missing-0x-in-alim1535_wdtc.patch
> -itimer-fixes.patch
> -add-pcibios_bus_to_resource-for-parisc.patch
> -autofs4-fix-infamous-busy-inodes-after-umount-message.patch
> -scsi_scan-check-return-code-from-scsi_sysfs_add_sdev.patch
> -i4l-add-olitec-isdn-pci-card-in-hisax-gazel-driver.patch
> -jsm-use-dynamic-major-number-allocation.patch
> -jsm-warning-fixes.patch
> -undo-mempolicy-shared-policy-rbtree-microoptimization.patch
> -ub-fix-for-blank-cds.patch
> -fix-xip-sparse-file-handling-in-ext2.patch
> -check_user_page_readable-deadlock-fix.patch
> -mpt-fusion-free-irq-in-suspend.patch
> -eurotechwdt-build-fix.patch
> -softdog-build-fix.patch
> -x86_64-fsnotify-build-fix.patch
> -fix-warning-in-powernow-k8c.patch
> -speakup-build-fix.patch
> -drm-via-fix-sparse-warnings.patch
> -netfilter-build-fix.patch
> -ipv6_netfilter_init-warning-fix.patch
> -consolidate-config_watchdog_nowayout-handling.patch
> -madvise-does-not-always-return-ebadf-on-non-file.patch
> -remove-bogus-warning-in-page_allocc.patch
> -ppc-ppc64-use-kconfighz.patch
> -ppc32-update-defconfigs.patch
> -ppc32-add-proper-prototype-for-cpm2_reset.patch
> -ppc32-make-the-uarts-on-mpc824x-individual-platform-devices.patch
> -ppc32-8xx-update-datatlbmiss-exception-comment.patch
> -ppc-fix-compilation-error-with-config_pq2fads.patch
> -ppc32-fix-typo-in-setup-of-2nd-pci-bus-on-85xx.patch
> -ppc32-fix-building-of-prpmc750.patch
> -ppc32-fix-building-of-radstone_ppc7d.patch
> -ppc32-fix-dma_map_page-to-use-page_to_bus.patch
> -ppc32-fix-440sp-mal-channels-count.patch
> -ppc32-fix-building-of-tqm8260-board.patch
> -ppc64-update-defconfigs.patch
> -ppc64-hide-config_adb.patch
> -ppc64-genrtc-build-fix.patch
> -make-a-few-functions-static-in-pmac_setupc.patch
> -ppc64-dynamically-allocate-segment-tables.patch
> -ppc64-remove-another-fixed-address-constraint.patch
> -mips-remove-obsolete-giu-driver-for-vr41xx.patch
> -i386-add-missing-kconfig-help-text.patch
> -m32r-add-missing-kconfig-help-text.patch
> -cris-update-1-17-arch-split.patch
> -cris-update-2-17-configuration-and-build.patch
> -cris-update-3-17-console.patch
> -cris-update-4-17-debug.patch
> -cris-update-5-17-drivers.patch
> -cris-update-6-17-i-o-and-dma-allocator.patch
> -cris-update-7-17-irq.patch
> -cris-update-8-17-misc-patches.patch
> -cris-update-9-17-mm.patch
> -cris-update-10-17-pci.patch
> -cris-update-11-17-profiler.patch
> -cris-update-12-17-serial-port-driver.patch # rmk said no
> -cris-update-13-17-smp.patch
> -cris-update-14-17-synchronous-serial-port-driver.patch
> -cris-update-15-17-updates-for-2612.patch
> -cris-update-17-17-new-subarchitecture-v32.patch
> -cris-update-17-17-new-subarchitecture-v32-swapped-kmalloc-args.patch
> -cris-ide-driver.patch
> -v850-define-pfn_valid.patch
> -v850-const-qualify-first-parameter-of-find_next_zero_bit.patch
> -v850-add-defconfigs.patch
> -v850-update-ioremap-return-type-and-add-ioread-iowrite-functions.patch
> -v850-add-pte_file.patch
> -v850-update-pci-support.patch
> -v850-define-l1_cache_shift-and-l1_cache_shift_max.patch
> -s390-spin-lock-retry.patch
> -s390-find_next_zero_bit-fixes.patch
> -s390-atomic64-inline-functions.patch
> -s390-external-call-performance.patch
> -s390-debug-data-for-ifcc-ccc.patch
> -s390-resource-accessibility-event-handling.patch
> -s390-fba-dasd-i-o-errors.patch
> -s390-free-dasd-slab-cache.patch
> -s390-channel-tape-fixes.patch
> -s390-31-bit-memory-size-limit.patch
> -s390-cpu-timer-reset-in-machine-check-handler.patch
> -s390-use-__cpcmd-in-vmcp_write.patch
> -fortuna-random-driver-fix.patch
> -stale-posix-lock-handling.patch
> -cciss-per-disk-queue.patch
> -kernel-capabilityc-add-kerneldoc.patch
> -kernel-cpusetc-add-kerneldoc-fix-typos.patch
> -kernel-crash_dumpc-add-kerneldoc.patch
> -tpm-support-for-infineon-tpm.patch
> -ppc64-tpm_infineon-build-fix.patch
> -mbcache-remove-unused-mb_cache_shrink-parameter.patch
> -documentation-changes-document-the-required-udev-version.patch
> -reiserfs-doesnt-use-mbcache.patch
> -ia64-halt-hangup-fix.patch
> -turn-many-if-undefined_string-into-ifdef-undefined_string.patch
> -riva-wundef-fix.patch
> -sys_get_thread_area-does-not-clear-the-returned-argument.patch
> -serial_core-whitespace-fix.patch
> -add-text-for-dealing-with-dot-releases-to-readme.patch
> -ib-update-fmr-functions.patch
> -ib-update-mad-client-api.patch
> -ib-add-mad-helper-functions.patch
> -ib-combine-some-mad-routines.patch
> -ib-change-saving-of-users-send-wr_id-in-mad.patch
> -ib-change-ib_mad_send_wr_private-struct.patch
> -ib-fix-timeout-cancelled-mad-handling.patch
> -ib-minor-cleanup-during-mad-startup-and-shutdown.patch
> -ib-add-ib_coalesce_recv_mad-to-mad.patch
> -ib-add-automatic-retries-to-mad-layer.patch
> -ib-simplify-calling-of-list_del-in-mad.patch
> -ib-eliminate-mad-cache-leak-associated-with-local.patch
> -ib-add-ib_modify_mad-api-to-mad.patch
> -ib-optimize-canceling-a-mad.patch
> -ib-fix-a-couple-of-mad-code-paths.patch
> -ib-add-ib_create_ah_from_wc-to-ib-verbs.patch
> -ib-a-couple-of-ib-core-bug-fixes.patch
> -ib-introduce-rmpp-apis.patch
> -ib-add-rmpp-implementation.patch
> -ib-add-service-record-support-to-sa-client.patch
> -ib-add-the-header-file-for-kernel-cm-communications.patch
> -ib-add-the-kernel-cm-implementation.patch
> -ib-user-mad-abi-changes-to-support-rmpp.patch
> -ib-implementation-for-rmpp-support-in-user-mad.patch
> -ib-add-the-header-file-for-user-space-cm.patch
> -ib-add-kernel-portion-of-user-cm-implementation.patch
> -ib-add-kernel-portion-of-user-cm-implementation-fix.patch
> -ib-hook-up-userspace-cm-to-the-make-system.patch
> -ib-eliminate-sparse-warnings-in-sa-client.patch
> -ib-add-core-locking-documentation-to-infiniband.patch
> -dvico-fusion-dvb-t1-tuner-lg-z201-fix.patch
> -drivers-media-video-tveepromc-possible-cleanups.patch
> -video_saa7134-must-depend-on-sound.patch
> -v4l-fix-regression-modprobe-bttv-freezes-the-computer.patch
> -dvb-v4l-lgdt3302-isolate-tuner.patch
> -dvb-v4l-rf-input-selection-fix.patch
> -lgdt3302-warning-fix.patch
> -dvb-v4l-cx88-cleanup.patch
> -v4l-hybrid-dvb-fix-warnings-with-wundef.patch
> -v4l-hybrid-dvb-move-defines-to-makefile.patch
> -v4l-hybrid-dvb-rename-cflags-from-config_dvb_xxxx-back.patch
> -v4l-fix-tuning-with-mxb-driver.patch
> -dvb-rename-lgdt3302-frontend-module-to-lgdt330x.patch
> -serial-mri-mri-pcids1-dual-port-serial-card.patch
> -clean-up-the-old-digi-support-and-rescue-it.patch
> -cpm_uart-use-dpram-for-early-console.patch
> -fbmon-horizontal-frequency-rounding-fix.patch
> -fbmem-use-unregister_chrdev-on-unload.patch
> -radeonfb-clean-up-edid-sysfs-attribute.patch
> -fbdev-colormap-fixes.patch
> -dont-repaint-the-cursor-when-it-is-disabled.patch
> -fbdev-update-info-cmap-when-setting-cmap-from-user-kernelspace.patch
> -clean-up-inline-static-vs-static-inline.patch
> -update-credits-entry-and-listings-in-source-files-for-jesper.patch
>
> Merged
>
> +bio_clone-fix.patch
>
> Fix BIO cloning bug - might be the cause of data corruption on some MD
> setups.
>
> +x86_64-always-ack-ipis-even-on-errors.patch
> +x86_64-update-defconfig.patch
> +x86_64-use-for_each_cpu_mask-for-clustered-ipi-flush.patch
> +x86_64-i386-x86_64-remove-prototypes-for-not-existing.patch
> +x86_64-move-cpu_present-possible_map-parsing-earlier.patch
> +x86_64-minor-clean-up-to-cpu-setup-use-smp_processor_id-instead-of-custom-hack.patch
> +x86_64-clarify-booting-processor-message.patch
> +x86_64-some-cleanup-in-setup64c.patch
> +x86_64-remove-unused-variable-in-delayc.patch
> +x86_64-improve-config_gart_iommu-description-and-make-it-default-y.patch
> +x86_64-some-updates-for-boot-optionstxt.patch
> +x86_64-fix-some-comments-in-tlbflushh.patch
> +x86_64-remove-obsolete-eat_key-prototype.patch
> +x86_64-fix-some-typos-in-systemh-comments.patch
> +x86_64-fix-incorrectly-defined-msr_k8_syscfg.patch
> +x86_64-fix-overflow-in-numa-hash-function-setup.patch
> +x86_64-print-a-boot-message-for-hotplug-memory-zones.patch
> +x86_64-create-per-cpu-machine-check-sysfs-directories.patch
> +x86_64-remove-ia32_-build-tools-in-makefile.patch
> +x86_64-remove-the-broadcast-options-that-were-added-for.patch
> +x86_64-support-more-than-8-cores-on-amd-systems.patch
> +x86_64-icecream-has-no-way-of-detecting-assembler-level.patch
> +x86_64-turn-bug-data-into-valid-instruction.patch
> +x86_64-when-running-cpuid4-need-to-run-on-the-correct.patch
> +x86_64-remove-unnecessary-include-in-faultc.patch
> +x86_64-small-assembly-improvements.patch
> +x86_64-switch-to-the-interrupt-stack-when-running-a.patch
> +x86_64-fix-srat-handling-on-non-dual-core-systems.patch
> +x86_64-fix-gcc-4-warning-in-sched_find_first_bit.patch
> +x86_64-use-msleep-in-smpbootc.patch
> +x86_64-remove-unused-variable-in-k8-busc.patch
> +x86_64-fix-cpu_to_node-setup-for-sparse-apic_ids.patch
>
> x86_64 update
>
> +cs89x0-collect-tx_bytes-statistics.patch
>
> net driver stats fix
>
> +ppc32-inotify-syscalls.patch
> +ppc64-inotify-syscalls.patch
>
> ppc32/ppc64 syscall table updates
>
> +selinux-default-labeling-of-mls-field.patch
>
> SELinux multilevel security feature work
>
> +pcdp-if-pcdp-contains-parity-information-use-it.patch
>
> pcdp driver fix
>
> +qla2xxx-mark-dependency-on-fw_loader.patch
>
> qlogic Kconfig fix
>
> +alpha-fix-statement-with-no-effect-warnings.patch
>
> Alpha warning fixes
>
> +mm-ensure-proper-alignment-for-node_remap_start_pfn.patch
>
> memory management initialisation fix
>
> -move-truncate_inode_pages-into-delete_inode.patch
>
> This is in git-ocfs2.patch
>
> +mpt-fusion-free-irq-in-suspend.patch
>
> mpt-fusion power management fix
>
> +gregkh-driver-stable_api_nonsense.txt-fixes.patch
> +gregkh-driver-speakup-kconfig-fix.patch
> +gregkh-driver-speakup-kconfig-fix-2.patch
> +gregkh-driver-speakup-build-fix.patch
>
> Greg's driver core tree
>
> +drivers-char-drm-drm_pcic-fix-warnings.patch
>
> Warning fixes
>
> +gregkh-i2c-w1-netlink-callbacks.patch
>
> Greg's i2c tree
>
> +git-net-gregkh-i2c-w1-netlink-callbacks-fix.patch
>
> Fix incompatibility between git-net and Greg's i2c tree
>
> +include-net-ieee80211h-must-include-linux-wirelessh.patch
>
> net build fix
>
> +gregkh-pci-pci-restore-bar-values.patch
>
> Greg's PCI tree
>
> -revert-gregkh-pci-pci-assign-unassigned-resources.patch
>
> Hopefully no longer needed
>
> +mpt-fusion-dv-fixes.patch
>
> Try to fix some mpt-fusion domain validation problems (doesn't seem to work)
>
> +gregkh-usb-usb-ftdi_sio-new-devices.patch
> +gregkh-usb-usb-ftdi_sio-rts-dtr.patch
> +gregkh-usb-usb-ftdi_sio-timeout-fix.patch
> +gregkh-usb-usb-usbfs-dont-leak-data.patch
> +gregkh-usb-usb-usbnet-remove-unused-vars.patch
> +gregkh-usb-usb-dont-delete-unregistered-interfaces.patch
> +gregkh-usb-usb-usbserial-remove-unneeded-casts.patch
>
> Greg's USB tree
>
> -proc-pid-numa_maps-to-show-on-which-nodes-pages-reside-tidy.patch
>
> Folded into proc-pid-numa_maps-to-show-on-which-nodes-pages-reside.patch
>
> +vm-add-capabilites-check-to-set_zone_reclaim.patch
>
> Make sys_set_zone_reclaim() privileged
>
> +page-fault-patches-introduce-pte_xchg-and-pte_cmpxchg.patch
> +page-fault-patches-introduce-pte_xchg-and-pte_cmpxchg-fix.patch
> +page-fault-patches-optional-page_lock-acquisition-in.patch
> +page-fault-patches-optional-page_lock-acquisition-in-tidy.patch
> +page-fault-patches-no-pagetable-lock-in-do_anon_page.patch
>
> anonymous pagefault scalability enhancements.
>
> -net-add-driver-for-the-nic-on-cell-blades-kconfig-fix.patch
>
> Folded into net-add-driver-for-the-nic-on-cell-blades.patch
>
> -sk98lin-basic-suspend-resume-support-fix.patch
>
> Folded into sk98lin-basic-suspend-resume-support.patch
>
> +ppc32-mark-boards-that-dont-build-as-broken.patch
> +ppc32-add-440ep-support.patch
> +ppc32-add-bamboo-platform.patch
> +ppc32-add-bamboo-defconfig.patch
> +ppc32-remove-board-support-for-adir.patch
> +ppc32-remove-board-support-for-ash.patch
> +ppc32-remove-board-support-for-beech.patch
> +ppc32-remove-defconfig-for-cedar.patch
> +ppc32-remove-board-support-for-k2.patch
> +ppc32-remove-board-support-for-mcpn765.patch
> +ppc32-remove-board-support-for-menf1.patch
> +ppc32-remove-board-support-for-oak.patch
> +ppc32-remove-board-support-for-rainier.patch
> +ppc32-remove-board-support-for-redwood.patch
> +ppc32-remove-board-support-for-sm850.patch
> +ppc32-remove-board-support-for-spd823ts.patch
> +ppc32-remove-board-support-for-ep405.patch
> +ppc32-remove-board-support-for-pcore.patch
>
> ppc32 work
>
> +ppc64-remove-nested-feature-sections.patch
>
> ppc64 cleanup
>
> +ptrace-i386-fix-syscall-audit-interaction-with-singlestep.patch
> +uml-support-ptrace-adds-the-host-sysemu-support-for-uml-and-general-usage.patch
> +uml-support-reorganize-ptrace_sysemu-support.patch
> +uml-support-add-ptrace_sysemu_singlestep-option-to-i386.patch
> +sysemu-fix-sysaudit--singlestep-interaction.patch
>
> UML feature work
>
> -areca-raid-linux-scsi-driver-fix.patch
>
> Folded into areca-raid-linux-scsi-driver.patch (will be dropped from next -mm)
>
> -relayfs-cancel-work-on-close-reset.patch
> -relayfs-add-private-data-to-channel-struct.patch
> -relayfs-function-docfix.patch
> -relayfs-add-relayfs-website-to-documentation.patch
> -avoid-lookup_hash-usage-in-relayfs.patch
>
> Folded into relayfs.patch
>
> -add-skip_hangcheck_timer.patch
>
> Dropped, but will come back.
>
> -yealink-updates.patch
> -yealink-updates-0701.patch
>
> Folded into new-driver-for-yealink-usb-p1k-phone.patch
>
> +support-powering-sharp-zaurus-sl-5500-lcd-up-and-down.patch
>
> Make Pavel's Zausus happier
>
> +radix_tag_get-differentiate-between-no-present-node-and-tag-unset-cases.patch
> +radix_tag_get-differentiate-between-no-present-node-and-tag-unset-cases-fix.patch
>
> radix_tree_tag_get() API enhancement.
>
> +aio-fix-races-in-callback-path.patch
>
> AIO race fix
>
> +auxiliary-vector-cleanups.patch
>
> SHuffle the AT_* auxiliary vector defines around
>
> +pnp-consolidate-kmalloc-wrappers.patch
>
> PNP cleanup
>
> -fix-race-in-do_get_write_access-warning-fix.patch
>
> Folded into fix-race-in-do_get_write_access.patch
>
> -kprobes-prevent-possible-race-conditions-generic-fixes.patch
>
> Folded into kprobes-prevent-possible-race-conditions-generic.patch
>
> -kprobes-prevent-possible-race-conditions-ia64-changes-fixes.patch
>
> Folded into kprobes-prevent-possible-race-conditions-ia64-changes.patch
>
> -connector-exit-notifier-fix.patch
> -connector-exit-notifier-remove-the-union-declaration.patch
> -connector-exit-notifier-fix-missing-dependencies-in.patch
>
> Folded into connector-exit-notifier.patch
>
> -connector-add-a-fork-connector-use-after-free-fix.patch
> -connector-add-a-fork-connector-remove-the-union-declaration-fork.patch
> -connector-fork-notifier-fix-missing-dependencies-in.patch
>
> Folded into connector-add-a-fork-connector.patch
>
> -jbd-split-checkpoint-lists-tweaks.patch
>
> Folded into jbd-split-checkpoint-lists.patch
>
> -spinlock-consolidation-m32r-fix.patch
> -spinlock-consolidation-up-spinlocks-gcc-29x-fix.patch
> -page_uptodate-locking-scalability-fix.patch
> -spinlock-consolidation-s390-fix.patch
>
> Folded into spinlock-consolidation.patch
>
> -revert-fix-broken-kmalloc_node-in-rc1-rc2.patch
> -numa-aware-slab-allocator-v5-fix.patch
> -numa-slab-allocator-cleanups.patch
>
> Folded into numa-aware-slab-allocator-v5.patch
>
> -iteraid-remove-ite_ioc_get_driver_version.patch
>
> Folded into iteraid.patch (will be dropped from next -mm)
>
> -page-owner-tracking-leak-detector-tidy.patch
>
> Folded into page-owner-tracking-leak-detector.patch
>
> -perfctr-handle-non-of-ppc32-platforms.patch
> -perfctr-syscall-numbering-fixups.patch
>
> Folded into perfctr.patch
>
> +split-general-cache-manager-from-cachefs-fs-fscache-cleanups.patch
>
> clean up split-general-cache-manager-from-cachefs.patch
>
> -files-break-up-files-struct-warning-fix.patch
>
> Folded into files-break-up-files-struct.patch
>
> -asfs-filesystem-driver-fixes.patch
>
> Folded into asfs-filesystem-driver.patch
>
> -v9fs-documentation-makefiles-configuration-resend-take-2.patch
>
> Folded into v9fs-documentation-makefiles-configuration.patch
>
> -v9fs-vfs-file-dentry-and-directory-operations-fix-fsf-postal-address-in-source-headers.patch
> -v9fs-vfs-file-dentry-and-directory-operations-resend-take-2.patch
>
> Folded into v9fs-vfs-file-dentry-and-directory-operations.patch
>
> -v9fs-vfs-inode-operations-fix-fsf-postal-address-in-source-headers.patch
> -v9fs-vfs-inode-operations-resend-take-2.patch
>
> Folded into v9fs-vfs-inode-operations.patch
>
> -v9fs-vfs-superblock-operations-and-glue-fix-fsf-postal-address-in-source-headers.patch
> -v9fs-vfs-superblock-operations-and-glue-resend-take-2.patch
> -v9fs-vfs-superblock-operations-and-glue-replace-v9fs_block_bits-with-fls.patch
>
> Folded into v9fs-vfs-superblock-operations-and-glue.patch
>
> -v9fs-9p-protocol-implementation-fix-fsf-postal-address-in-source-headers.patch
> -v9fs-9p-protocol-implementation-resend-take-2.patch
>
> Folded into v9fs-9p-protocol-implementation.patch
>
> -v9fs-transport-modules-fix-fsf-postal-address-in-source-headers.patch
> -v9fs-transport-modules-fix-timeout-segfault-corner-case.patch
> -v9fs-transport-modules-resend-take-2.patch
>
> Folded into v9fs-transport-modules.patch
>
> -v9fs-debug-and-support-routines-fix.patch
> -v9fs-debug-and-support-routines-fix-fsf-postal-address-in-source-headers.patch
> -v9fs-debug-and-support-routines-resend-take-2.patch
>
> Folded into v9fs-debug-and-support-routines.patch
>
> -v9fs-clean-up-vfs_inode-and-setattr-functions-2.patch
>
> Folded into v9fs-clean-up-vfs_inode-and-setattr-functions.patch
>
> +serial-add-mmio-support-to-8250_pnp.patch
>
> Add MMIO support to the UART driver
>
> -device-mapper-fix-deadlocks-in-core-prep-fix.patch
>
> Folded into device-mapper-fix-deadlocks-in-core-prep.patch
>
> -timer-initialization-cleanup-define_timer-pluto-fix.patch
>
> Folded into timer-initialization-cleanup-define_timer.patch
>
>
>
> All 633 patches:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm3/patch-list
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo [at] vger
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--

====================================================================
Khalid Aziz Open Source and Linux Organization
(970)898-9214 Hewlett-Packard
khalid.aziz [at] hp Fort Collins, CO

"The Linux kernel is subject to relentless development"
- Alessandro Rubini

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

akpm at osdl

Jul 29, 2005, 4:17 PM

Post #33 of 90 (891 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Khalid Aziz <khalid_aziz [at] hp> wrote:
>
> Serial console is broken on ia64 on an HP rx2600 machine on
> 2.6.13-rc3-mm3. When kernel is booted up with "console=ttyS,...", no
> output ever appears on the console and system is hung. So I booted the
> kernel with "console=uart,mmio,0xff5e0000" to enable early console and
> here is how far the kernel got before hanging:

(cc the ia64 and acpi lists)

OK, thanks. There have been a few serial driver changes recently, but
there's also a tremendous ACPI patch in -mm. I'm wondering about those
ACPI error messages:

> -------
> Linux version 2.6.13-rc3-mm3 (root [at] mar) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #4 SMP Fri Jul 29 16:30:41 MDT 2005
> EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
> booting generic kernel on platform hpzx1
> PCDP: v0 at 0x3fb2c000
> Explicit "console="; ignoring PCDP
> Early serial console at MMIO 0xff5e0000 (options '115200')
> efi.trim_top: ignoring 4KB of memory at 0x0 due to granule hole at 0x0
> efi.trim_top: ignoring 636KB of memory at 0x1000 due to granule hole at 0x0
> efi.trim_bottom: ignoring 15360KB of memory at 0x100000 due to granule hole at 0x0
> SAL 3.1: HP version 2.31
> SAL Platform features: None
> SAL: AP wakeup using external interrupt vector 0xff
> No logical to physical processor mapping available
> ACPI: Local APIC address c0000000fee00000
> GSI 36 (level, low) -> CPU 0 (0x0000) vector 48
> 2 CPUs available, 2 CPUs total
> MCA related initialization done
> Virtual mem_map starts at 0xa0007fffc7200000
> Built 1 zonelists
> Kernel command line: BOOT_IMAGE=scsi1:/EFI/debian/boot/vmlinuz-2.6.13-rc3-mm3 root=/dev/sdb2 console=uart,mmio,0xff5e0000 ro
> PID hash table entries: 4096 (order: 12, 131072 bytes)
> Console: colour VGA+ 80x25
> Memory: 12439136k/12542128k available (7051k code, 116240k reserved, 3406k data, 352k init)
> Leaving McKinley Errata 9 workaround enabled
> Dentry cache hash table entries: 2097152 (order: 10, 16777216 bytes)
> Inode-cache hash table entries: 1048576 (order: 9, 8388608 bytes)
> Mount-cache hash table entries: 1024
> Boot processor id 0x0/0x0
> CPU 1: synchronized ITC with CPU 0 (last diff -5 cycles, maxerr 433 cycles)
> Brought up 2 CPUs
> Total of 2 processors activated (2695.16 BogoMIPS).
> -> [0][1][ 786432] 0.5 [ 0.5] (0): ( 500513 250256)
> -> [0][1][ 827823] 0.5 [ 0.5] (0): ( 529015 139379)
> -> [0][1][ 871392] 0.5 [ 0.5] (0): ( 557119 83741)
> -> [0][1][ 917254] 0.5 [ 0.5] (0): ( 585481 56051)
> -> [0][1][ 965530] 0.6 [ 0.6] (0): ( 615654 43112)
> -> [0][1][1016347] 0.6 [ 0.6] (0): ( 653296 40377)
> -> [0][1][1069838] 0.6 [ 0.6] (0): ( 681359 34220)
> -> [0][1][1126145] 0.7 [ 0.7] (0): ( 706209 29535)
> -> [0][1][1185415] 0.7 [ 0.7] (0): ( 754788 39057)
> -> [0][1][1247805] 0.7 [ 0.7] (0): ( 788675 36472)
> -> [0][1][1313478] 0.8 [ 0.8] (0): ( 840102 43949)
> -> [0][1][1382608] 0.7 [ 0.8] (0): ( 742042 71004)
> -> [0][1][1455376] 0.6 [ 0.8] (0): ( 653934 79556)
> -> [0][1][1531974] 0.7 [ 0.8] (0): ( 766991 96306)
> -> [0][1][1612604] 0.7 [ 0.8] (0): ( 779253 54284)
> -> [0][1][1697477] 0.5 [ 0.8] (0): ( 534912 149312)
> -> [0][1][1786817] 0.5 [ 0.8] (0): ( 503106 90559)
> -> found max.
> [0][1] working set size found: 1313478, cost: 840102
> ---------------------
> | migration cost matrix (max_cache_size: 1572864, cpu: -1 MHz):
> ---------------------
> [00] [01]
> [00]: - 1.6(0)
> [01]: 1.6(0) -
> --------------------------------
> | cacheflush times [1]: 1.6 (1680204)
> | calibration delay: 1 seconds
> --------------------------------
> NET: Registered protocol family 16
> ACPI: bus type pci registered
> ACPI: Subsystem revision 20050708
> ACPI-0509: *** Error: Method execution failed [\PARS.GFIT] (Node e0000002ffff8a00), AE_BAD_PARAMETER
> ACPI-0509: *** Error: Method execution failed [\_SB_.SBA0._INI] (Node e0000002ffffa780), AE_BAD_PARAMETER
> ACPI: Interpreter enabled
> ACPI: Using IOSAPIC for interrupt routing

Does the above happen on 2.6.13-rc3 or 2.6.13-rc4?

> SCSI subsystem initialized
> perfmon: version 2.0 IRQ 238
> perfmon: Itanium 2 PMU detected, 16 PMCs, 18 PMDs, 4 counters (47 bits)
> PAL Information Facility v0.5
> perfmon: added sampling format default_format
> perfmon_default_smpl: default_format v2.0 registered
> Total HugeTLB memory allocated, 0
> SGI XFS with large block/inode numbers, no debug enabled
> Initializing Cryptographic API
> EFI Time Services Driver v0.4
> i8042.c: No controller found.
> Serial: 8250/16550 driver $Revision: 1.90 $ 6 ports, IRQ sharing enabled
> mice: PS/2 mouse device common for all mice
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Intel(R) PRO/1000 Network Driver - version 6.0.60-k2
> Copyright (c) 1999-2005 Intel Corporation.
> e100: Intel(R) PRO/100 Network Driver, 3.4.10-k2-NAPI
> e100: Copyright(c) 1999-2005 Intel Corporation
> netconsole: not configured, aborting
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
> ide-floppy driver 0.99.newide
> Fusion MPT base driver 3.03.02
> Copyright (c) 1999-2005 LSI Logic Corporation
> Fusion MPT SPI Host driver 3.03.02
> EFI Variables Facility v0.08 2004-May-17
> NET: Registered protocol family 2
> IP route cache hash table entries: 2097152 (order: 10, 16777216 bytes)
> TCP established hash table entries: 8388608 (order: 13, 134217728 bytes)
> TCP bind hash table entries: 65536 (order: 6, 1048576 bytes)
> TCP: Hash tables configured (established 8388608 bind 65536)
> TCP reno registered
> TCP bic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> No ttyS device at MMIO 0xff5e0000 for console
> -------
>
> Serial driver failed to find any serial ports. I am using defconfig. A
> 2.6.13-rc3 kernel (no mm3 patch) compiled with defconfig boots up fine
> and finds all serial ports.

Well it did claim to find an 8250 controller.

If you have time, it would be useful if you could obtain the 2.6.13-rc3 dmesg
output and do

diff -u dmesg-2.6.13-rc3 dmesg-2.6.13-rc3-mm3

and send it, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

iogl64nx at gmail

Jul 29, 2005, 4:20 PM

Post #34 of 90 (882 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Andrew Morton schrieb:

>Michael Thonke <tk-shockwave [at] web> wrote:
>
>
>>Andrew Morton schrieb:
>>
>>
>>>Michael Thonke <iogl64nx [at] gmail> wrote:
>>>
>>>
>>>>here again I have two problems. With 2.6.13-rc3-mm3 I have problems
>>>> using my SATA drives on Intel ICH6.
>>>> The kernel can't route there IRQs or can't discover them. the option
>>>> irqpoll got them to work now.
>>>> The problem is new because 2.6.13-rc3[-mm1,mm2] work without any problems.
>>>>
>>>>
>>>OK. Please generate the full dmesg output for -mm2 and for -mm3 and run
>>>`diff -u dmesg.mm2 dmesg.mm3' and send it? And keep those files because we
>>>may end up needing to add them to an acpi bugzilla entry ;)
>>>
>>>
>>Well I did a little mistake..it only worked correctly up to
>>2.6.13-rc3-mm1 but this dmesg output I have.
>>
>>Well as I save mm[2,3] are unable to setup the correct IRQs for the
>>devices..and please note that 2.6.13-rc3-mm3 only booted with irqpoll so
>>its in the dmesg output "dmesg.mm3"
>>Normaly the IRQ routed to something about 1xx now they are 1-21?! Caused
>>by irqpoll?
>>
>>
>>
>
>Are these problems only present in -mm kernels? Does 2.6.13-rc4 work OK?
>
>
I'm sorry to say that, Yes.

I finially compiled a fresh 2.6.13-rc4-git1 kernel with ck-patch and
Gregh-kh patches.

With this kernel non of the problems I had with mm-kernel are present.
Here is everthing just perfect..now
I attached a dmesg output for review :-)

The Oops on probing snd-hda-intel gone. It works now ... Mozart rocks :-)
I look at the CVS tree of Alsa later.

I finialy converted my reiser4 root to reiser 3.6.

Where I can get acpidumb or what it is called?

>
>
>>>Odd trace. Do you have CONFIG_KALLSYMS enabled? If not, please turn it on.
>>>
>>>
Okay, i will do so ... what else we need to back that out.

>>Mh I tried but my system freezes on boot then. And screen leaves blank.
>>
>>
>
>Oh geeze.
>
>
Like oh my god? ;-)

>@@ -53,10 +23,18 @@
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
>+ ACPI-0287: *** Error: Region SystemMemory(0) has no handler
>+ ACPI-0127: *** Error: acpi_load_tables: Could not load namespace: AE_NOT_EXIST
>+ ACPI-0136: *** Error: acpi_load_tables: Could not load tables: AE_NOT_EXIST
>+ACPI: Unable to load the System Description Tables
> ENABLING IO-APIC IRQs
>-..TIMER: vector=0x31 pin1=2 pin2=0
>+..TIMER: vector=0x31 pin1=2 pin2=-1
>
>
The pin2=-1 is wrong I think, right?

> NET: Registered protocol family 16
> PCI: Using configuration type 1
>+ACPI: Subsystem revision 20050708
>+ACPI: Interpreter disabled.
>
>Well it looks like ACPI committed suicide, so there's probably not much
>point looking at the other things until that gets addressed.
>
>Would you have time to raise a kernel bugzilla entry for this? Raise it
>against the ACPI AML interpreter, version 20050708 and mention the above
>failure. The output of acpidump (from
>ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20050727.tar.gz)
>will probably be asked for.
>
>Thanks.
>
>
>
Sorry for my different mail accounts, gmail have some problems.
Let me say, Thanks again for the help Andrew and all others.

Attachments:

dmesg.2613rc4git1 (15.0 KB)

rpurdie at rpsys

Jul 30, 2005, 3:27 AM

Post #35 of 90 (887 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

On Thu, 2005-07-28 at 02:58 -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm3/
>
> - There's a pretty large x86_64 update here which naughty maintainer wants
> in 2.6.13. Extra testing, please.
>
> +x86_64-switch-to-the-interrupt-stack-when-running-a.patch

The above patch causes the BUG below on the Zaurus (arm pxa255 with
preempt enabled). This can only be due to the suspicious looking changes
to kernel/softirq.c in that patch...

Richard

kernel BUG at kernel/sched.c:2988!
kernel BUG at kernel/sched.c:2988!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 8f5 [#1]
Modules linked in:
CPU: 0
PC is at __bug+0x40/0x54
LR is at 0x60000013
pc : [<c0021290>] lr : [<60000013>] Not tainted
sp : c3c0dc6c ip : 00000001 fp : c3c0dc7c
r10: fffff920 r9 : c3c0c000 r8 : 00000000
r7 : 00000000 r6 : c0271a00 r5 : f2d00000 r4 : 00000000
r3 : 00000000 r2 : 00000000 r1 : 00000026 r0 : 00000001
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: 397F Table: A0004000 DAC: 00000017
Process khelper (pid: 94, stack limit = 0xc3c0c194)
Backtrace:
[<c0021250>] (__bug+0x0/0x54) from [<c01f01a8>] (preempt_schedule_irq+0x84/0x8c)
r4 = C3C0C000
[<c01f0124>] (preempt_schedule_irq+0x0/0x8c) from [<c001ba3c>] (svc_preempt+0x28/0x4c)
r4 = FFFFFFFF
[<c0037618>] (release_console_sem+0x0/0x27c) from [<c0037a48>] (vprintk+0x1b4/0x344)
[<c0037894>] (vprintk+0x0/0x344) from [<c0037bf4>] (printk+0x1c/0x20)
[<c0037bd8>] (printk+0x0/0x20) from [<c002128c>] (__bug+0x3c/0x54)
r3 = C022716C r2 = 00000000 r1 = 00000000 r0 = C02043C8
[<c0021250>] (__bug+0x0/0x54) from [<c01f01a8>] (preempt_schedule_irq+0x84/0x8c)
r4 = C3C0C000
[<c01f0124>] (preempt_schedule_irq+0x0/0x8c) from [<c001ba3c>] (svc_preempt+0x28/0x4c)
r4 = FFFFFFFF
[<c0098ee8>] (dput+0x0/0x308) from [<c008e9ec>] (__link_path_walk+0xc00/0x1280)
r6 = 00000000 r5 = C022EA7E r4 = FFFFFFFE
[<c008ddec>] (__link_path_walk+0x0/0x1280) from [<c008f118>] (link_path_walk+0xac/0x1dc)
[<c008f06c>] (link_path_walk+0x0/0x1dc) from [<c008f334>] (path_lookup+0xec/0x260)
r7 = 00000000 r6 = C3C0DEEC r5 = C3C0C000 r4 = C03327FC
[<c008f248>] (path_lookup+0x0/0x260) from [<c0089f24>] (open_exec+0x2c/0xe0)
r8 = C034FE78 r7 = 00000001 r6 = C3C0DEEC r5 = C3C0AA20
r4 = C022EA78
[<c0089ef8>] (open_exec+0x0/0xe0) from [<c008b224>] (do_execve+0x48/0x1f4)
r7 = FFFFFFF4 r6 = C3C08E00 r5 = C3C0AA20 r4 = C022EA78
[<c008b1dc>] (do_execve+0x0/0x1f4) from [<c0020bfc>] (execve+0x40/0x88)
[<c0020bbc>] (execve+0x0/0x88) from [<c004938c>] (____call_usermodehelper+0xa8/0xb4)
r7 = 00000000 r6 = 00000000 r5 = C034FE14 r4 = C3C0C000
[<c00492e4>] (____call_usermodehelper+0x0/0xb4) from [<c0039604>] (do_exit+0x0/0xd90)
r6 = 00000000 r5 = 00000000 r4 = 00000000
Code: 1b005a54 e59f0014 eb005a52 e3a03000 (e5833000)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

khalid.aziz at hp

Jul 30, 2005, 8:33 AM

Post #36 of 90 (876 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

On Fri, 2005-07-29 at 16:17 -0700, Andrew Morton wrote:
> Khalid Aziz <khalid_aziz [at] hp> wrote:
> >
> > Serial console is broken on ia64 on an HP rx2600 machine on
> > 2.6.13-rc3-mm3. When kernel is booted up with "console=ttyS,...", no
> > output ever appears on the console and system is hung. So I booted the
> > kernel with "console=uart,mmio,0xff5e0000" to enable early console and
> > here is how far the kernel got before hanging:
>
> (cc the ia64 and acpi lists)
>
> OK, thanks. There have been a few serial driver changes recently, but
> there's also a tremendous ACPI patch in -mm. I'm wondering about those
> ACPI error messages:
>
> > -------
> > Linux version 2.6.13-rc3-mm3 (root [at] mar) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #4 SMP Fri Jul 29 16:30:41 MDT 2005
> > EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
> > booting generic kernel on platform hpzx1
> > PCDP: v0 at 0x3fb2c000
> > Explicit "console="; ignoring PCDP
> ..............
> > NET: Registered protocol family 16
> > ACPI: bus type pci registered
> > ACPI: Subsystem revision 20050708
> > ACPI-0509: *** Error: Method execution failed [\PARS.GFIT] (Node e0000002ffff8a00), AE_BAD_PARAMETER
> > ACPI-0509: *** Error: Method execution failed [\_SB_.SBA0._INI] (Node e0000002ffffa780), AE_BAD_PARAMETER
> > ACPI: Interpreter enabled
> > ACPI: Using IOSAPIC for interrupt routing
>
> Does the above happen on 2.6.13-rc3 or 2.6.13-rc4?

No, I do not see this on 2.6.13-rc3. It does seem ACPI is busted on
2.6.13-rc3-mm3 which is leading to kernel not being able to scan PCI bus
and set up IRQ routing.

> Well it did claim to find an 8250 controller.
>
> If you have time, it would be useful if you could obtain the 2.6.13-rc3 dmesg
> output and do
> diff -u dmesg-2.6.13-rc3 dmesg-2.6.13-rc3-mm3
>
> and send it, thanks.

Here is the diff:

1c1
< Linux version 2.6.13-rc3 (root [at] mar) (gcc version 3.3.5 (Debian
1:3.3.5-12)) #
3 SMP Fri Jul 29 16:07:24 MDT 2005
---
> Linux version 2.6.13-rc3-mm3 (root [at] mar) (gcc version 3.3.5 (Debian
1:3.3.5-12
)) #4 SMP Fri Jul 29 16:30:41 MDT 2005
5a6
> Early serial console at MMIO 0xff5e0000 (options '115200')
19c20
< Kernel command line:
BOOT_IMAGE=scsi1:/EFI/debian/boot/vmlinuz-2.6.13-rc3 root
=/dev/sdb2 console=ttyS0,115200n8 ro
---
> Kernel command line:
BOOT_IMAGE=scsi1:/EFI/debian/boot/vmlinuz-2.6.13-rc3-mm3
root=/dev/sdb2 console=uart,mmio,0xff5e0000 ro
22c23
< Memory: 12438928k/12541920k available (6951k code, 116448k reserved,
3697k dat
a, 288k init)
---
> Memory: 12439136k/12542128k available (7051k code, 116240k reserved,
3406k dat
a, 352k init)
28c29
< CPU 1: synchronized ITC with CPU 0 (last diff 0 cycles, maxerr 433
cycles)
---
> CPU 1: synchronized ITC with CPU 0 (last diff -5 cycles, maxerr 433
cycles)
30a32,60
> -> [0][1][ 786432] 0.5 [ 0.5] (0): ( 500513 250256)
> -> [0][1][ 827823] 0.5 [ 0.5] (0): ( 529015 139379)
> -> [0][1][ 871392] 0.5 [ 0.5] (0): ( 557119 83741)
> -> [0][1][ 917254] 0.5 [ 0.5] (0): ( 585481 56051)
> -> [0][1][ 965530] 0.6 [ 0.6] (0): ( 615654 43112)
> -> [0][1][1016347] 0.6 [ 0.6] (0): ( 653296 40377)
> -> [0][1][1069838] 0.6 [ 0.6] (0): ( 681359 34220)
> -> [0][1][1126145] 0.7 [ 0.7] (0): ( 706209 29535)
> -> [0][1][1185415] 0.7 [ 0.7] (0): ( 754788 39057)
> -> [0][1][1247805] 0.7 [ 0.7] (0): ( 788675 36472)
> -> [0][1][1313478] 0.8 [ 0.8] (0): ( 840102 43949)
> -> [0][1][1382608] 0.7 [ 0.8] (0): ( 742042 71004)
> -> [0][1][1455376] 0.6 [ 0.8] (0): ( 653934 79556)
> -> [0][1][1531974] 0.7 [ 0.8] (0): ( 766991 96306)
> -> [0][1][1612604] 0.7 [ 0.8] (0): ( 779253 54284)
> -> [0][1][1697477] 0.5 [ 0.8] (0): ( 534912 149312)
> -> [0][1][1786817] 0.5 [ 0.8] (0): ( 503106 90559)
> -> found max.
> [0][1] working set size found: 1313478, cost: 840102
> ---------------------
> | migration cost matrix (max_cache_size: 1572864, cpu: -1 MHz):
> ---------------------
> [00] [01]
> [00]: - 1.6(0)
> [01]: 1.6(0) -
> --------------------------------
> | cacheflush times [1]: 1.6 (1680204)
> | calibration delay: 1 seconds
> --------------------------------
33c63,65
< ACPI: Subsystem revision 20050408
---
> ACPI: Subsystem revision 20050708
> ACPI-0509: *** Error: Method execution failed [\PARS.GFIT] (Node
e0000002f
fff8a00), AE_BAD_PARAMETER
> ACPI-0509: *** Error: Method execution failed [\_SB_.SBA0._INI]
(Node e000
0002ffffa780), AE_BAD_PARAMETER
36,91d67
< ACPI: PCI Root Bridge [PCI0] (0000:00)
< ACPI: Assume root bridge [\_SB_.SBA0.PCI0] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI1] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI2] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI3] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI4] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI6] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI7] segment is 0
< ACPI: PCI Root Bridge [PCI1] (0000:20)
< ACPI: Assume root bridge [\_SB_.SBA0.PCI0] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI1] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI2] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI3] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI4] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI6] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI7] segment is 0
< ACPI: PCI Root Bridge [PCI2] (0000:40)
< ACPI: Assume root bridge [\_SB_.SBA0.PCI0] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI1] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI2] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI3] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI4] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI6] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI7] segment is 0
< ACPI: PCI Root Bridge [PCI3] (0000:60)
< ACPI: Assume root bridge [\_SB_.SBA0.PCI0] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI1] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI2] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI3] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI4] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI6] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI7] segment is 0
< ACPI: PCI Root Bridge [PCI4] (0000:80)
< ACPI: Assume root bridge [\_SB_.SBA0.PCI0] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI1] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI2] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI3] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI4] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI6] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI7] segment is 0
< ACPI: PCI Root Bridge [PCI6] (0000:c0)
< ACPI: Assume root bridge [\_SB_.SBA0.PCI0] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI1] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI2] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI3] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI4] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI6] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI7] segment is 0
< ACPI: PCI Root Bridge [PCI7] (0000:e0)
< ACPI: Assume root bridge [\_SB_.SBA0.PCI0] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI1] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI2] segment is 0
ACPI: Assume root bridge [\_SB_.SBA0.PCI3] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI4] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI6] segment is 0
< ACPI: Assume root bridge [\_SB_.SBA0.PCI7] segment is 0
93d68
< IOC: zx1 2.2 HPA 0xfed01000 IOVA space 1024Mb at 0x40000000
100d74
< inotify syscall
106,116c80
< GSI 34 (edge, high) -> CPU 0 (0x0000) vector 49
< ttyS0 at MMIO 0xff5e0000 (irq = 49) is a 16550A
< GSI 35 (edge, high) -> CPU 1 (0x0100) vector 50
< ttyS1 at MMIO 0xff5e2000 (irq = 50) is a 16550A
< GSI 82 (level, low) -> CPU 0 (0x0000) vector 51
< ACPI: PCI Interrupt 0000:e0:01.0[A] -> GSI 82 (level, low) -> IRQ 51
< ttyS2 at MMIO 0xf8031000 (irq = 51) is a 16450
< ACPI: PCI Interrupt 0000:e0:01.1[A] -> GSI 82 (level, low) -> IRQ 51
< ttyS3 at MMIO 0xf8030000 (irq = 51) is a 16550A
< ttyS4 at MMIO 0xf8030010 (irq = 51) is a 16550A
< ttyS5 at MMIO 0xf8030038 (irq = 51) is a 16550A
---
> mice: PS/2 mouse device common for all mice
124c88
< e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI
---
> e100: Intel(R) PRO/100 Network Driver, 3.4.10-k2-NAPI
126,134d89
< GSI 20 (level, low) -> CPU 1 (0x0100) vector 52
< ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 20 (level, low) -> IRQ 52
< e100: eth0: e100_probe: addr 0x80020000, irq 52, MAC addr
00:30:6E:39:C6:60
< tg3.c:v3.33 (July 5, 2005)
< GSI 29 (level, low) -> CPU 0 (0x0000) vector 53
< ACPI: PCI Interrupt 0000:20:02.0[A] -> GSI 29 (level, low) -> IRQ 53
< eth1: Tigon3 [partno(BCM95700A6) rev 0105 PHY(5701)]
(PCI:66MHz:64-bit) 10/100
/1000BaseT Ethernet 00:30:6e:39:16:c0
< eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[0]

< eth1: dma_rwctrl[76ff2d0f]
137,148c92
< ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
< CMD649: IDE controller at PCI slot 0000:00:02.0
< GSI 21 (level, low) -> CPU 1 (0x0100) vector 54
< ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 21 (level, low) -> IRQ 54
< CMD649: chipset revision 2
< CMD649: 100% native mode on irq 54
< ide0: BM-DMA at 0x0d40-0x0d47, BIOS settings: hda:pio, hdb:pio
< ide1: BM-DMA at 0x0d48-0x0d4f, BIOS settings: hdc:pio, hdd:pio
< hda: DW-28E, ATAPI CD/DVD-ROM drive
< ide0 at 0xd58-0xd5f,0xd66 on irq 54
< hda: ATAPI 24X DVD-ROM CD-R/RW drive, 1698kB Cache, UDMA(33)
< Uniform CD-ROM driver Revision: 3.20
---
> ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
150,167d93
< GSI 38 (level, low) -> CPU 0 (0x0000) vector 55
< ACPI: PCI Interrupt 0000:40:01.0[A] -> GSI 38 (level, low) -> IRQ 55
< sym0: <1010-66> rev 0x1 at pci 0000:40:01.0 irq 55
< sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking
< sym0: open drain IRQ line driver, using on-chip SRAM
< sym0: using LOAD/STORE-based firmware.
< sym0: handling phase mismatch from SCRIPTS.
< sym0: SCSI BUS has been reset.
< scsi0 : sym-2.2.1
< GSI 39 (level, low) -> CPU 1 (0x0100) vector 56
< ACPI: PCI Interrupt 0000:40:01.1[B] -> GSI 39 (level, low) -> IRQ 56
< sym1: <1010-66> rev 0x1 at pci 0000:40:01.1 irq 56
< sym1: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking
< sym1: open drain IRQ line driver, using on-chip SRAM
< sym1: using LOAD/STORE-based firmware.
< sym1: handling phase mismatch from SCRIPTS.
< sym1: SCSI BUS has been reset.
< scsi1 : sym-2.2.1
171,205d96
< GSI 27 (level, low) -> CPU 0 (0x0000) vector 57
< ACPI: PCI Interrupt 0000:20:01.0[A] -> GSI 27 (level, low) -> IRQ 57
< mptbase: Initiating ioc0 bringup
< ioc0: 53C1030: Capabilities={Initiator,Target}
< scsi2 : ioc0: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=57
< Vendor: HP 36.4G Model: ST336706LC Rev: HP05
< Type: Direct-Access ANSI SCSI revision: 02
< SCSI device sda: 71132960 512-byte hdwr sectors (36420 MB)
< SCSI device sda: drive cache: write through
< SCSI device sda: 71132960 512-byte hdwr sectors (36420 MB)
< SCSI device sda: drive cache: write through
< sda: sda1 sda2 sda3
< Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
< Vendor: HP 36.4G Model: ST336706LC Rev: HP05
< Type: Direct-Access ANSI SCSI revision: 02
< SCSI device sdb: 71132960 512-byte hdwr sectors (36420 MB)
< SCSI device sdb: drive cache: write through
< SCSI device sdb: 71132960 512-byte hdwr sectors (36420 MB)
< SCSI device sdb: drive cache: write through
< sdb: sdb1 sdb2 sdb3 sdb4
< Attached scsi disk sdb at scsi2, channel 0, id 1, lun 0
< GSI 28 (level, low) -> CPU 1 (0x0100) vector 58
< ACPI: PCI Interrupt 0000:20:01.1[B] -> GSI 28 (level, low) -> IRQ 58
< mptbase: Initiating ioc1 bringup
< mptscsih: ioc0: DV: Release failed. id 0<6>ioc1: 53C1030:
Capabilities={Initia
tor,Target}
< scsi3 : ioc1: LSI53C1030, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=58
< Vendor: HP 36.4G Model: ST336706LC Rev: HP04
< Type: Direct-Access ANSI SCSI revision: 02
< SCSI device sdc: 71132960 512-byte hdwr sectors (36420 MB)
< SCSI device sdc: drive cache: write through
< SCSI device sdc: 71132960 512-byte hdwr sectors (36420 MB)
< SCSI device sdc: drive cache: write through
< sdc: sdc1 sdc2 sdc3
< Attached scsi disk sdc at scsi3, channel 0, id 2, lun 0
< mice: PS/2 mouse device common for all mice
216,220c107
< kjournald starting. Commit interval 5 seconds
< EXT3-fs: mounted filesystem with ordered data mode.
< VFS: Mounted root (ext3 filesystem) readonly.
< Freeing unused kernel memory: 288kB freed
< INIT: version 2.86 booting
---
> No ttyS device at MMIO 0xff5e0000 for console

I have also attached the bootup logs for 2.6.13-rc3 and 2.6.13-rc3-mm3.

--
Khalid

Attachments:

rc3_bootup.log (10.8 KB)

rc3-mm3_bootup.log (5.04 KB)

akpm at osdl

Jul 30, 2005, 10:05 AM

Post #37 of 90 (866 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Richard Purdie <rpurdie [at] rpsys> wrote:
>
> On Thu, 2005-07-28 at 02:58 -0700, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm3/
> >
> > - There's a pretty large x86_64 update here which naughty maintainer wants
> > in 2.6.13. Extra testing, please.
> >
> > +x86_64-switch-to-the-interrupt-stack-when-running-a.patch
>
> The above patch causes the BUG below on the Zaurus (arm pxa255 with
> preempt enabled). This can only be due to the suspicious looking changes
> to kernel/softirq.c in that patch...

err, yes. I assume this was some debugging stuff which leaked through. I
hope x86_64 still works after we fix it...

--- devel/kernel/softirq.c~revert-bogus-softirq-changes 2005-07-30 10:03:12.000000000 -0700
+++ devel-akpm/kernel/softirq.c 2005-07-30 10:03:21.000000000 -0700
@@ -86,7 +86,7 @@ restart:
/* Reset the pending bitmask before enabling irqs */
local_softirq_pending() = 0;

- //local_irq_enable();
+ local_irq_enable();

h = softirq_vec;

@@ -99,7 +99,7 @@ restart:
pending >>= 1;
} while (pending);

- //local_irq_disable();
+ local_irq_disable();

pending = local_softirq_pending();
if (pending && --max_restart)
_

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

akpm at osdl

Jul 30, 2005, 11:02 AM

Post #38 of 90 (891 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Khalid Aziz <khalid.aziz [at] hp> wrote:
>
> On Fri, 2005-07-29 at 16:17 -0700, Andrew Morton wrote:
> > Khalid Aziz <khalid_aziz [at] hp> wrote:
> > >
> > > Serial console is broken on ia64 on an HP rx2600 machine on
> > > 2.6.13-rc3-mm3. When kernel is booted up with "console=ttyS,...", no
> > > output ever appears on the console and system is hung. So I booted the
> > > kernel with "console=uart,mmio,0xff5e0000" to enable early console and
> > > here is how far the kernel got before hanging:
> >
> > (cc the ia64 and acpi lists)
> >
> > OK, thanks. There have been a few serial driver changes recently, but
> > there's also a tremendous ACPI patch in -mm. I'm wondering about those
> > ACPI error messages:
> >
> > > -------
> > > Linux version 2.6.13-rc3-mm3 (root [at] mar) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #4 SMP Fri Jul 29 16:30:41 MDT 2005
> > > EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
> > > booting generic kernel on platform hpzx1
> > > PCDP: v0 at 0x3fb2c000
> > > Explicit "console="; ignoring PCDP
> > ..............
> > > NET: Registered protocol family 16
> > > ACPI: bus type pci registered
> > > ACPI: Subsystem revision 20050708
> > > ACPI-0509: *** Error: Method execution failed [\PARS.GFIT] (Node e0000002ffff8a00), AE_BAD_PARAMETER
> > > ACPI-0509: *** Error: Method execution failed [\_SB_.SBA0._INI] (Node e0000002ffffa780), AE_BAD_PARAMETER
> > > ACPI: Interpreter enabled
> > > ACPI: Using IOSAPIC for interrupt routing
> >
> > Does the above happen on 2.6.13-rc3 or 2.6.13-rc4?
>
> No, I do not see this on 2.6.13-rc3. It does seem ACPI is busted on
> 2.6.13-rc3-mm3 which is leading to kernel not being able to scan PCI bus
> and set up IRQ routing.
>

OK, thanks. Could I suggest that you raise a bug against ACPI 20050708 at
bugzilla.kernel.org containing the info we've generated thus far?

And thanks for testing -mm: we really don't want to permit this to leak
into mainline...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

mano at roarinelk

Jul 31, 2005, 2:04 AM

Post #39 of 90 (886 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Hello,

something broke the sonypi driver a bit after -mm2:
I can no longer set bluetooth-power for instance, and it logs these
messages:

sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 605)
sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 607)
sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 594)

setting/getting brightness, getting battery/ac status still work.

The ioports assignments have changed a bit between -mm2 and -mm3:

/proc/ioports on -mm2:
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0376-0376 : ide1
03f6-03f6 : ide0
0400-047f : 0000:00:1f.0
0400-0403 : PM1a_EVT_BLK
0404-0405 : PM1a_CNT_BLK
0408-040b : PM_TMR
0410-0415 : ACPI CPU throttle
0420-0420 : PM2_CNT_BLK
0428-042f : GPE0_BLK
0500-053f : 0000:00:1f.0
0500-053f : pnp 00:08
0540-055f : 0000:00:1f.3
0540-054f : i801-smbus
0cf8-0cff : PCI conf1
1080-109f : Sony Programable I/O Device
c000-cfff : PCI Bus #01
c800-c8ff : 0000:01:00.0
c800-c8ff : radeonfb
d000-dfff : PCI Bus #02
d000-d1ff : PCI CardBus #03
d400-d5ff : PCI CardBus #03
dc00-dc3f : 0000:02:03.0
dc00-dc3f : e1000
e000-e03f : 0000:00:1f.5
e000-e03f : Intel 82801DB-ICH4
e080-e0ff : 0000:00:1f.6
e400-e4ff : 0000:00:1f.6
e800-e81f : 0000:00:1d.0
e800-e81f : uhci_hcd
e880-e89f : 0000:00:1d.1
e880-e89f : uhci_hcd
ec00-ec1f : 0000:00:1d.2
ec00-ec1f : uhci_hcd
ee00-eeff : 0000:00:1f.5
ee00-eeff : Intel 82801DB-ICH4
fe00-fe01 : motherboard
ffa0-ffaf : 0000:00:1f.1
ffa0-ffa7 : ide0
ffa8-ffaf : ide1

/proc/ioports on -mm3:
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0376-0376 : ide1
03f6-03f6 : ide0
0400-047f : 0000:00:1f.0
0400-0403 : PM1a_EVT_BLK
0404-0405 : PM1a_CNT_BLK
0408-040b : PM_TMR
0410-0415 : ACPI CPU throttle
0420-0420 : PM2_CNT_BLK
0428-042f : GPE0_BLK
0500-053f : 0000:00:1f.0
0500-053f : pnp 00:08
0540-055f : 0000:00:1f.3
0540-054f : i801-smbus
0cf8-0cff : PCI conf1
1000-1fff : PCI CardBus #03
1080-109f : Sony Programable I/O Device
2000-2fff : PCI CardBus #03
c000-cfff : PCI Bus #01
c800-c8ff : 0000:01:00.0
c800-c8ff : radeonfb
d000-dfff : PCI Bus #02
dc00-dc3f : 0000:02:03.0
dc00-dc3f : e1000
e000-e03f : 0000:00:1f.5
e000-e03f : Intel 82801DB-ICH4
e080-e0ff : 0000:00:1f.6
e400-e4ff : 0000:00:1f.6
e800-e81f : 0000:00:1d.0
e800-e81f : uhci_hcd
e880-e89f : 0000:00:1d.1
e880-e89f : uhci_hcd
ec00-ec1f : 0000:00:1d.2
ec00-ec1f : uhci_hcd
ee00-eeff : 0000:00:1f.5
ee00-eeff : Intel 82801DB-ICH4
fe00-fe01 : motherboard
ffa0-ffaf : 0000:00:1f.1
ffa0-ffa7 : ide0
ffa8-ffaf : ide1

I'd appreciate any hints

Thanks,

--
Manuel Lauss
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

akpm at osdl

Jul 31, 2005, 2:16 AM

Post #40 of 90 (880 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Manuel Lauss <mano [at] roarinelk> wrote:
>
> something broke the sonypi driver a bit after -mm2:
> I can no longer set bluetooth-power for instance, and it logs these
> messages:
>
> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 605)
> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 607)
> sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 594)
>
> setting/getting brightness, getting battery/ac status still work.
>

Can you do a `patch -p1 -R' of the below, see if it fixes it? It probably
won't.

Also please test 2.6.13-rc4-mm1 which is missing the acpi tree...

Thanks.

From: Dmitry Torokhov <dtor_core [at] ameritech>

Make sure that input_work is not running when unloading the module;
submit/retrieve key release data into/from input_fifo in one shot.

Signed-off-by: Dmitry Torokhov <dtor [at] mail>
Cc: Stelian Pop <stelian [at] popies>
Signed-off-by: Andrew Morton <akpm [at] osdl>
---

drivers/char/sonypi.c | 122 +++++++++++++++++++++++++-------------------------
1 files changed, 63 insertions(+), 59 deletions(-)

diff -puN drivers/char/sonypi.c~sonypi-make-sure-that-input_work-is-not-running-when-unloading drivers/char/sonypi.c
--- 25/drivers/char/sonypi.c~sonypi-make-sure-that-input_work-is-not-running-when-unloading 2005-06-03 02:13:08.000000000 -0700
+++ 25-akpm/drivers/char/sonypi.c 2005-06-03 02:13:08.000000000 -0700
@@ -439,6 +439,11 @@ static struct {
{ 0, 0 },
};

+struct sonypi_keypress {
+ struct input_dev *dev;
+ int key;
+};
+
static struct sonypi_device {
struct pci_dev *dev;
struct platform_device *pdev;
@@ -710,22 +715,61 @@ static void sonypi_setbluetoothpower(u8

static void input_keyrelease(void *data)
{
- struct input_dev *input_dev;
- int key;
-
- while (1) {
- if (kfifo_get(sonypi_device.input_fifo,
- (unsigned char *)&input_dev,
- sizeof(input_dev)) != sizeof(input_dev))
- return;
- if (kfifo_get(sonypi_device.input_fifo,
- (unsigned char *)&key,
- sizeof(key)) != sizeof(key))
- return;
+ struct sonypi_keypress kp;

+ while (kfifo_get(sonypi_device.input_fifo, (unsigned char *)&kp,
+ sizeof(kp)) == sizeof(kp)) {
msleep(10);
- input_report_key(input_dev, key, 0);
- input_sync(input_dev);
+ input_report_key(kp.dev, kp.key, 0);
+ input_sync(kp.dev);
+ }
+}
+
+static void sonypi_report_input_event(u8 event)
+{
+ struct input_dev *jog_dev = &sonypi_device.input_jog_dev;
+ struct input_dev *key_dev = &sonypi_device.input_key_dev;
+ struct sonypi_keypress kp = { NULL };
+ int i;
+
+ switch (event) {
+ case SONYPI_EVENT_JOGDIAL_UP:
+ case SONYPI_EVENT_JOGDIAL_UP_PRESSED:
+ input_report_rel(jog_dev, REL_WHEEL, 1);
+ input_sync(jog_dev);
+ break;
+
+ case SONYPI_EVENT_JOGDIAL_DOWN:
+ case SONYPI_EVENT_JOGDIAL_DOWN_PRESSED:
+ input_report_rel(jog_dev, REL_WHEEL, -1);
+ input_sync(jog_dev);
+ break;
+
+ case SONYPI_EVENT_JOGDIAL_PRESSED:
+ kp.key = BTN_MIDDLE;
+ kp.dev = jog_dev;
+ break;
+
+ case SONYPI_EVENT_FNKEY_RELEASED:
+ /* Nothing, not all VAIOs generate this event */
+ break;
+
+ default:
+ for (i = 0; sonypi_inputkeys[i].sonypiev; i++)
+ if (event == sonypi_inputkeys[i].sonypiev) {
+ kp.dev = key_dev;
+ kp.key = sonypi_inputkeys[i].inputev;
+ break;
+ }
+ break;
+ }
+
+ if (kp.dev) {
+ input_report_key(kp.dev, kp.key, 1);
+ input_sync(kp.dev);
+ kfifo_put(sonypi_device.input_fifo,
+ (unsigned char *)&kp, sizeof(kp));
+ schedule_work(&sonypi_device.input_work);
}
}

@@ -768,51 +812,8 @@ found:
printk(KERN_INFO
"sonypi: event port1=0x%02x,port2=0x%02x\n", v1, v2);

- if (useinput) {
- struct input_dev *input_jog_dev = &sonypi_device.input_jog_dev;
- struct input_dev *input_key_dev = &sonypi_device.input_key_dev;
- switch (event) {
- case SONYPI_EVENT_JOGDIAL_UP:
- case SONYPI_EVENT_JOGDIAL_UP_PRESSED:
- input_report_rel(input_jog_dev, REL_WHEEL, 1);
- break;
- case SONYPI_EVENT_JOGDIAL_DOWN:
- case SONYPI_EVENT_JOGDIAL_DOWN_PRESSED:
- input_report_rel(input_jog_dev, REL_WHEEL, -1);
- break;
- case SONYPI_EVENT_JOGDIAL_PRESSED: {
- int key = BTN_MIDDLE;
- input_report_key(input_jog_dev, key, 1);
- kfifo_put(sonypi_device.input_fifo,
- (unsigned char *)&input_jog_dev,
- sizeof(input_jog_dev));
- kfifo_put(sonypi_device.input_fifo,
- (unsigned char *)&key, sizeof(key));
- break;
- }
- case SONYPI_EVENT_FNKEY_RELEASED:
- /* Nothing, not all VAIOs generate this event */
- break;
- }
- input_sync(input_jog_dev);
-
- for (i = 0; sonypi_inputkeys[i].sonypiev; i++) {
- int key;
-
- if (event != sonypi_inputkeys[i].sonypiev)
- continue;
-
- key = sonypi_inputkeys[i].inputev;
- input_report_key(input_key_dev, key, 1);
- kfifo_put(sonypi_device.input_fifo,
- (unsigned char *)&input_key_dev,
- sizeof(input_key_dev));
- kfifo_put(sonypi_device.input_fifo,
- (unsigned char *)&key, sizeof(key));
- }
- input_sync(input_key_dev);
- schedule_work(&sonypi_device.input_work);
- }
+ if (useinput)
+ sonypi_report_input_event(event);

kfifo_put(sonypi_device.fifo, (unsigned char *)&event, sizeof(event));
kill_fasync(&sonypi_device.fifo_async, SIGIO, POLL_IN);
@@ -1337,6 +1338,9 @@ static void __devexit sonypi_remove(void
{
sonypi_disable();

+ synchronize_sched(); /* Allow sonypi interrupt to complete. */
+ flush_scheduled_work();
+
platform_device_unregister(sonypi_device.pdev);

if (useinput) {
_

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

mano at roarinelk

Jul 31, 2005, 4:12 AM

Post #41 of 90 (868 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Andrew Morton wrote:
> Manuel Lauss <mano [at] roarinelk> wrote:
>
>>something broke the sonypi driver a bit after -mm2:
>> I can no longer set bluetooth-power for instance, and it logs these
>> messages:
>>
>> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 605)
>> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 607)
>> sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 594)
>>
>> setting/getting brightness, getting battery/ac status still work.
>>
>
>
> Can you do a `patch -p1 -R' of the below, see if it fixes it? It probably
> won't.
>
> Also please test 2.6.13-rc4-mm1 which is missing the acpi tree...
>
> Thanks.

Didn't help, and -rc4-mm1 has the same problem.
Also tried with CONFIG_ACPI=n and with cardbus disabled, no change.
Added a few debug lines to the module:

sonypi_call1(82) enter
sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 595)
sonypi_call1() leave
sonypi_call2(81, ff) enter
sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 608)
sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 610)
sonypi_call2() leave
sonypi_call1(82) enter
sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 595)
sonypi_call1() leave
sonypi: Sony Programmable I/O Controller Driverv1.26.
sonypi: detected type2 model, verbose = 1, fnkeyinit = off, camera = off, compat = off, mask = 0xffffffff, useinput = off, acpi = on
sonypi: enabled at irq=11, port1=0x1080, port2=0x1084
sonypi: device allocated minor is 63
sonypi: setbluetoothpower enter
sonypi_call2(96, 00) enter
sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 608)
sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 610)
sonypi_call2() leave
sonypi_call1(82) enter
sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 595)
sonypi_call1() leave
sonypi: setbluetoothpower leave

brightness for instance does not use the sonypi_callX() functions, and it works.
cat /dev/sonypi produces no more output either, and interrupt count for sonypi does
no longer increase when I press a hotkey or close the lid.

Thanks,

--
Manuel Lauss
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

mano at roarinelk

Jul 31, 2005, 5:46 AM

Post #42 of 90 (886 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

akpm at osdl

Jul 31, 2005, 10:35 AM

Post #43 of 90 (868 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Manuel Lauss <mano [at] roarinelk> wrote:
>
> Andrew Morton wrote:
> > Manuel Lauss <mano [at] roarinelk> wrote:
> >
> >>something broke the sonypi driver a bit after -mm2:
> >> I can no longer set bluetooth-power for instance, and it logs these
> >> messages:
> >>
> >> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 605)
> >> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 607)
> >> sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 594)
> >>
> >> setting/getting brightness, getting battery/ac status still work.
> >>
> >
> >
> > Can you do a `patch -p1 -R' of the below, see if it fixes it? It probably
> > won't.
> >
> > Also please test 2.6.13-rc4-mm1 which is missing the acpi tree...
> >
> > Thanks.
>
>
> Found the cause:

Wonderful, thanks. So does that mean that 2.6.13-rc4 doesn't work?

> > -revert-gregkh-pci-pci-assign-unassigned-resources.patch
> >
> > Hopefully no longer needed
>
> Applying this dropped patch to -rc3-mm3 and -rc4-mm1 fixes
> it.

OK, I'll bring it back again.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

mano at roarinelk

Jul 31, 2005, 11:21 AM

Post #44 of 90 (876 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

On Sun, Jul 31, 2005 at 10:35:28AM -0700, Andrew Morton wrote:
> Manuel Lauss <mano [at] roarinelk> wrote:
> >
> > Andrew Morton wrote:
> > > Manuel Lauss <mano [at] roarinelk> wrote:
> > >
> > >>something broke the sonypi driver a bit after -mm2:
> > >> I can no longer set bluetooth-power for instance, and it logs these
> > >> messages:
> > >>
> > >> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 605)
> > >> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 607)
> > >> sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 594)
> > >>
> > >> setting/getting brightness, getting battery/ac status still work.
> > >>
> > >
> > >
> > > Can you do a `patch -p1 -R' of the below, see if it fixes it? It probably
> > > won't.
> > >
> > > Also please test 2.6.13-rc4-mm1 which is missing the acpi tree...
> > >
> > > Thanks.
> >
> >
> > Found the cause:
>
> Wonderful, thanks. So does that mean that 2.6.13-rc4 doesn't work?

Yes, sonypi is busted in -rc4 also.

--
Manuel Lauss
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

torvalds at osdl

Jul 31, 2005, 11:25 AM

Post #45 of 90 (896 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

On Sun, 31 Jul 2005, Manuel Lauss wrote:
>
> something broke the sonypi driver a bit after -mm2:
> I can no longer set bluetooth-power for instance, and it logs these
> messages:
>
> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 605)
> sonypi command failed at drivers/char/sonypi.c : sonypi_call2 (line 607)
> sonypi command failed at drivers/char/sonypi.c : sonypi_call1 (line 594)
>
> setting/getting brightness, getting battery/ac status still work.
>
>
> The ioports assignments have changed a bit between -mm2 and -mm3:

The diff shows:

-/proc/ioports on -mm2:
+/proc/ioports on -mm3:
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
@@ -25,13 +25,13 @@
0540-055f : 0000:00:1f.3
0540-054f : i801-smbus
0cf8-0cff : PCI conf1
-1080-109f : Sony Programable I/O Device
+1000-1fff : PCI CardBus #03
+ 1080-109f : Sony Programable I/O Device
+2000-2fff : PCI CardBus #03
c000-cfff : PCI Bus #01
c800-c8ff : 0000:01:00.0
c800-c8ff : radeonfb
d000-dfff : PCI Bus #02
- d000-d1ff : PCI CardBus #03
- d400-d5ff : PCI CardBus #03
dc00-dc3f : 0000:02:03.0
dc00-dc3f : e1000
e000-e03f : 0000:00:1f.5

ie the difference is that the PCI cardbus resources have been moved from
inside PCI Bus #2 to outside of it, and as a side effect the sonypi
device just happened to be allocated inside the Cardbus IO space.

Now, this is really unlucky. There are two issues here:

- the -mm2 iomap just _looks_ better. I can't tell what the exact
difference is, but it looks like one of the PCI resource allocation
patches got reverted or re-applied.

However, I'm almost positive that this is the Intel transparent bridge
thing, and it doesn't really matter where the CardBus resources got
allocated. So the _real_ breakage is probably due to a totally
unrelated issue:

- The SonyPI driver just allocates IO regions in random areas. It's got a
list of places to try allocating in, and the 1080 area just happens to
be the first on the list, and since it's not used by anything else, it
succeeds (never mind that it's on totally the wrong bus).

and I think the real bug here is the SonyPI driver.

It should either use an IO port in the legacy motherboard resource area
(ie allocate itself somewhere in IO ports 0x100-0x3ff), _or_ it should
play well as a PCI device, and actually try to work with the PCI IO port
allocation layer.

So instead of just saying "I want port 1080" (which may be on some other
bus entirely), it _could_ (and should) do something like

/*
* Use "device resource 6" for this: it's traditionally
* the PCI ROM resource, but we don't have a ROM, so we take it
* over for our special IO region.
*/
struct resource *res = dev->resource + 6;
int ret;

res->flags = IORESOURCE_IO;
ret = pci_bus_alloc_resource(dev->bus, /* bus */
res, /* resource */
SONYPI_TYPE2_REGION_SIZE, /* size */,
SONYPI_TYPE2_REGION_SIZE, /* alignment */,
PCIBIOS_MIN_IO, /* Min starting pos */
IORESOURCE_IO, /* IO type */
pcibios_align_resource, /* Standard alignment */
dev);
if (ret < 0)
return -ENODEV;

.. use port "res->start" ..

which should do the right thing.

Stelian? The above is untested, but it should give roughly the right
behaviour - you might need to tweak it a bit, but I think it should be a
lot better than just picking random IO ports out of your hat and seeing if
they are already used by something else...

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

mano at roarinelk

Jul 31, 2005, 11:41 AM

Post #46 of 90 (865 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Linus Torvalds wrote:

>
> - The SonyPI driver just allocates IO regions in random areas. It's got a
> list of places to try allocating in, and the 1080 area just happens to
> be the first on the list, and since it's not used by anything else, it
> succeeds (never mind that it's on totally the wrong bus).

On three different intel-vaios, I've seen the sonypi device always
located at ioport 0x1080. Even the windows driver on these models
always allocates the 0x1080-0x109f io-range for it.

--
Manuel Lauss

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

torvalds at osdl

Jul 31, 2005, 11:59 AM

Post #47 of 90 (910 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

On Sun, 31 Jul 2005, Manuel Lauss wrote:
>
> Linus Torvalds wrote:
>
> >
> > - The SonyPI driver just allocates IO regions in random areas. It's got a
> > list of places to try allocating in, and the 1080 area just happens to
> > be the first on the list, and since it's not used by anything else, it
> > succeeds (never mind that it's on totally the wrong bus).
>
> On three different intel-vaios, I've seen the sonypi device always
> located at ioport 0x1080. Even the windows driver on these models
> always allocates the 0x1080-0x109f io-range for it.

I think that's how the Linux driver IO list was gathered - looking at
where it tends to sit by default.

And the thing is, that would actually be ok too (as I sent in a separate
email to Stelian later) - if the BIOS actually sets it up at 1080, we
could easily just make a PCI quirk that marks that region _early_ in the
bootup sequence as being reserved for SonyPI. That would make any later
PCI allocation requests know to avoid it.

The problem with the current setup is that the SonyPI driver is a
perfectly regular driver, and thus obviously loads _after_ a number of
other drivers, and the PCI setup code in particular. So what has happened
is that we've set up other PCI IO regious without knowing - or caring -
about the SonyPI driver, and then the SonyPI driver comes along and says
"oh, btw, I want that region".

And _that_ cannot work reliably. If you have a specific pre-allocated
region that you want (or must have - some regions are fixed because of
things like ACPI tables or SMM etc that depend on them), then you need to
tell the world about it _before_ it starts allocating anything else,
because otherwise the allocation routines obviously cannot know about that
fixed thing.

So what the sonypi driver does now is wrong, but there are two choices to
do it right: tell the PCI subsystem early (traditionally done as a PCI
quirk in drivers/pci/quirks.c, but you could possibly also make it as a
driver-specific "subsys_initcall()" - but only if your driver is always
compiled in, which sonypi isn't), or then allocate it nicely later.

It's the combination of the two that is bad: "just tell somebody later"
doesn't work. They may say that it's easier to get forgiveness than ask
for permission, but that's not true in kernels. Because if you do
something wrong, the device simply won't _work_, which is exactly what
happened here ;).

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

stelian at popies

Jul 31, 2005, 2:35 PM

Post #48 of 90 (867 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

Le dimanche 31 juillet 2005 � 11:25 -0700, Linus Torvalds a �crit :

> - The SonyPI driver just allocates IO regions in random areas.

Those are not really random, the list of IO regions available is given
in the ACPI SPIC device specification. The list is hardcoded here
because the driver does not (yet ?) use the ACPI services for
initializing the device, and experience has shown that the list does not
vary with different models.

> and I think the real bug here is the SonyPI driver.
>
> It should either use an IO port in the legacy motherboard resource area
> (ie allocate itself somewhere in IO ports 0x100-0x3ff),

this cannot be done, because the regions are already defined, and are
not in the legacy area.

> _or_ it should
> play well as a PCI device, and actually try to work with the PCI IO port
> allocation layer.

sure, but the SPIC device is not really tied to a specific PCI device
(it is for the 'type1' models, but not for the 'type2' ones). That's why
the sonypi driver is not a PCI driver but relies on a DMI ident to
detect each and every Vaio laptop out there.

Stelian.
--
Stelian Pop <stelian [at] popies>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

rpurdie at rpsys

Jul 31, 2005, 6:43 PM

Post #49 of 90 (867 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

On Thu, 2005-07-28 at 02:58 -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm3/

I'm seeing a problem on ARM with -rc3-mm3 and -rc4-mm1. -rc3-mm2 and
-rc4 are fine and looking for the problem reveals the problems start
after these patches are applied:

> +page-fault-patches-optional-page_lock-acquisition-in.patch
> +page-fault-patches-optional-page_lock-acquisition-in-tidy.patch

The system appears to be ok and boots happily to a console but if you
load any graphical UI, the screen will blank and the process stops
working (tested with opie and and xserver+GPE). You can kill -9 the
process but you can't regain the console without a suspend/resume cycle
which performs enough of a reset to get it back. chvt and the console
switching keys don't respond.

I tried the patch mentioned in http://lkml.org/lkml/2005/7/28/304 but it
makes no difference.

Richard

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

stelian at popies

Aug 1, 2005, 7:37 AM

Post #50 of 90 (869 views)
Permalink

Re: 2.6.13-rc3-mm3 [In reply to]

[.Sorry all for the duplicate, LKML slipped somehow from the CC: line so I'm sending this again]

Le dimanche 31 juillet 2005 à 16:22 -0700, Linus Torvalds a écrit :

> Also, it looks like sonypi really is pretty nasty to probe for, so it's
> not enough to just say "oh, it's a sony VAIO, let's reserve that region".
> Otherwise I'd just suggest adding a "dmi_check_system()" table to
> arch/i386/pci/i386.c, at the top of "pcibios_assign_resources()", and
> then you could just allocate things based on DMI information.

Since every Vaio laptop out there seems indeed to use only the first IO
port range in the list, we can de-nastyify the probe. And if we don't
even bother to check for Type1 vs. Type2 devices and we reserve both,
then it may be acceptable to do the above.

See the attached patch below which does just that. This has NOT been
tested (only compile-tested), and moreover it has a high breakage
probability in case some Vaios cannot live with the fixed ioport choice.

Note that this patch will conflict with the recent Eric's one (added in
CC:), he may want to rediff his Type3 changes in case this patch gets
in.

Stelian.

Mark some IO regions reserved on Sony Vaio laptops because the sonypi
driver will need them later, and we don't want another driver to reserve
them before the sonypi driver starts.

Signed-off-by: Stelian Pop <stelian [at] popies>

arch/i386/pci/i386.c | 42 +++++++++++++++++++++++++++++++++++
drivers/char/sonypi.c | 60 ++++++++------------------------------------------
2 files changed, 52 insertions(+), 50 deletions(-)

Index: linux-2.6.git/arch/i386/pci/i386.c
===================================================================
--- linux-2.6.git.orig/arch/i386/pci/i386.c 2005-07-08 14:08:10.000000000 +0200
+++ linux-2.6.git/arch/i386/pci/i386.c 2005-08-01 15:46:06.000000000 +0200
@@ -30,6 +30,7 @@
#include <linux/init.h>
#include <linux/ioport.h>
#include <linux/errno.h>
+#include <linux/dmi.h>

#include "pci.h"

@@ -167,12 +168,53 @@
}
}

+/*
+ * Reserve IO ports used later by the sonypi driver, or they may got used
+ * by other devices.
+ */
+static int __init sonyvaio_reserve_ioports(struct dmi_system_id *d)
+{
+ /* IO ports for 'type1' device */
+ if (!request_region(0x10c0, 0x08, "Sony Programable I/O Type1 Device"))
+ printk(KERN_ERR "Sony Vaio: cannot reserve Type1 IO region\n");
+
+ /* IO ports for 'type2' device */
+ if (!request_region(0x1080, 0x20, "Sony Programable I/O Type2 Device"))
+ printk(KERN_ERR "Sony Vaio: cannot reserve Type2 IO region\n");
+
+ printk(KERN_INFO "Sony Vaio: pre-reserved IO ports\n");
+
+ return 0;
+}
+
+static struct dmi_system_id __initdata sonyvaioio_dmi_table[] = {
+ {
+ .callback = sonyvaio_reserve_ioports,
+ .ident = "Sony Vaio Laptop",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Sony Corporation"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "PCG-"),
+ },
+ },
+ {
+ .callback = sonyvaio_reserve_ioports,
+ .ident = "Sony Vaio Laptop",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Sony Corporation"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "VGN-"),
+ },
+ },
+ { }
+};
+
static int __init pcibios_assign_resources(void)
{
struct pci_dev *dev = NULL;
int idx;
struct resource *r;

+ dmi_check_system(sonyvaioio_dmi_table);
+
for_each_pci_dev(dev) {
int class = dev->class >> 8;

Index: linux-2.6.git/drivers/char/sonypi.c
===================================================================
--- linux-2.6.git.orig/drivers/char/sonypi.c 2005-08-01 11:06:47.000000000 +0200
+++ linux-2.6.git/drivers/char/sonypi.c 2005-08-01 15:45:27.000000000 +0200
@@ -104,14 +104,18 @@
#define SONYPI_IRQ_SHIFT 22
#define SONYPI_BASE 0x50
#define SONYPI_G10A (SONYPI_BASE+0x14)
-#define SONYPI_TYPE1_REGION_SIZE 0x08
+/* those ports are reserved in arch/i386/pci/i386.c */
+#define SONYPI_TYPE1_IOPORT1 0x10c0
+#define SONYPI_TYPE1_IOPORT2 0x10c4
#define SONYPI_TYPE1_EVTYPE_OFFSET 0x04

/* type2 series specifics */
#define SONYPI_SIRQ 0x9b
#define SONYPI_SLOB 0x9c
#define SONYPI_SHIB 0x9d
-#define SONYPI_TYPE2_REGION_SIZE 0x20
+/* those ports are reserved in arch/i386/pci/i386.c */
+#define SONYPI_TYPE2_IOPORT1 0x1080
+#define SONYPI_TYPE2_IOPORT2 0x1084
#define SONYPI_TYPE2_EVTYPE_OFFSET 0x12

/* battery / brightness addresses */
@@ -136,29 +140,6 @@
#define SONYPI_DATA_IOPORT 0x62
#define SONYPI_CST_IOPORT 0x66

-/* The set of possible ioports */
-struct sonypi_ioport_list {
- u16 port1;
- u16 port2;
-};
-
-static struct sonypi_ioport_list sonypi_type1_ioport_list[] = {
- { 0x10c0, 0x10c4 }, /* looks like the default on C1Vx */
- { 0x1080, 0x1084 },
- { 0x1090, 0x1094 },
- { 0x10a0, 0x10a4 },
- { 0x10b0, 0x10b4 },
- { 0x0, 0x0 }
-};
-
-static struct sonypi_ioport_list sonypi_type2_ioport_list[] = {
- { 0x1080, 0x1084 },
- { 0x10a0, 0x10a4 },
- { 0x10c0, 0x10c4 },
- { 0x10e0, 0x10e4 },
- { 0x0, 0x0 }
-};
-
/* The set of possible interrupts */
struct sonypi_irq_list {
u16 irq;
@@ -451,7 +432,6 @@
u16 bits;
u16 ioport1;
u16 ioport2;
- u16 region_size;
u16 evtype_offset;
int camera_power;
int bluetooth_power;
@@ -1139,7 +1119,6 @@
static int __devinit sonypi_probe(void)
{
int i, ret;
- struct sonypi_ioport_list *ioport_list;
struct sonypi_irq_list *irq_list;
struct pci_dev *pcidev;

@@ -1177,33 +1156,17 @@
}

if (sonypi_device.model == SONYPI_DEVICE_MODEL_TYPE2) {
- ioport_list = sonypi_type2_ioport_list;
- sonypi_device.region_size = SONYPI_TYPE2_REGION_SIZE;
+ sonypi_device.ioport1 = SONYPI_TYPE2_IOPORT1;
+ sonypi_device.ioport2 = SONYPI_TYPE2_IOPORT2;
sonypi_device.evtype_offset = SONYPI_TYPE2_EVTYPE_OFFSET;
irq_list = sonypi_type2_irq_list;
} else {
- ioport_list = sonypi_type1_ioport_list;
- sonypi_device.region_size = SONYPI_TYPE1_REGION_SIZE;
+ sonypi_device.ioport1 = SONYPI_TYPE1_IOPORT1;
+ sonypi_device.ioport2 = SONYPI_TYPE1_IOPORT2;
sonypi_device.evtype_offset = SONYPI_TYPE1_EVTYPE_OFFSET;
irq_list = sonypi_type1_irq_list;
}

- for (i = 0; ioport_list[i].port1; i++) {
- if (request_region(ioport_list[i].port1,
- sonypi_device.region_size,
- "Sony Programable I/O Device")) {
- /* get the ioport */
- sonypi_device.ioport1 = ioport_list[i].port1;
- sonypi_device.ioport2 = ioport_list[i].port2;
- break;
- }
- }
- if (!sonypi_device.ioport1) {
- printk(KERN_ERR "sonypi: request_region failed\n");
- ret = -ENODEV;
- goto out_reqreg;
- }
-
for (i = 0; irq_list[i].irq; i++) {

sonypi_device.irq = irq_list[i].irq;
@@ -1303,8 +1266,6 @@
input_unregister_device(&sonypi_device.input_jog_dev);
free_irq(sonypi_device.irq, sonypi_irq);
out_reqirq:
- release_region(sonypi_device.ioport1, sonypi_device.region_size);
-out_reqreg:
misc_deregister(&sonypi_misc_device);
out_miscreg:
if (pcidev)
@@ -1332,7 +1293,6 @@
}

free_irq(sonypi_device.irq, sonypi_irq);
- release_region(sonypi_device.ioport1, sonypi_device.region_size);
misc_deregister(&sonypi_misc_device);
if (sonypi_device.dev)
pci_disable_device(sonypi_device.dev);

--
Stelian Pop <stelian [at] popies>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

1 2 3 4

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads