* [U-Boot-Users] Using a second I2C interface
From: Ben Warren @ 2006-05-12 14:36 UTC (permalink / raw)
To: u-boot
Hello,
The CPU I'm using (MPC8349) has two hardware I2C interfaces, and I'd
like to access the second one in U-boot. Implementing this looks easy
to me, but I don't want to reinvent the wheel if it's already been done
elsewhere. Has anyone done this? If not, I'll follow up with a
proposal.
regards,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060512/a8a75115/attachment.htm
^ permalink raw reply
* Re: [Qemu-devel] PATCH: Support for multi-file raw images
From: Troy Benjegerdes @ 2006-05-12 14:35 UTC (permalink / raw)
To: qemu-devel
In-Reply-To: <1147329045.17542.15.camel@moonpix.desrt.ca>
On Thu, May 11, 2006 at 02:30:45AM -0400, Ryan Lortie wrote:
> Hello.
>
> Attached is a C file (and small patch) to add support for multi-file raw
> images to QEMU. The rationale (for me at least) is as follows:
>
> I use rsync to backup my home directory. The act of starting up QEMU
> changes a 20GB file on my drive. This causes 20GB of extra copying next
> time I do backups. If I could split the drive image into smaller parts
> (maybe 2048 10MB files) then the amount of extra copying is drastically
> reduced (since only a few of these files are modified).
>
> There are definitely other reasons that this may be useful.
Have you tried making a read-only 'base' image and using qcow images
instead? I'm not convinced that splitting things up is going to help a
lot. You might end up writing 1 512 byte block each to 500 files.. in
the qcow image case, that is writing 256K, and with 10mb files, that's
5GB.
> o If the files comprising the device are deleted (for example) while
> QEMU is running then this is quite bad. Currently this will result
> in read/write requests returning -1. Maybe it makes sense to panic
> and cause QEMU to exit.
>
at the very least, the console should print an error. If you can keep
all the files open, deleting the file won't be a problem.
^ permalink raw reply
* Testing status of fully virtualized guests (Intel VT) on 64bit XEN unstable
From: Ed Smith @ 2006-05-12 14:35 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 4648 bytes --]
Test Configuration:
Dell Precision WorkStation 380, Dual Core, 2GB, 3 SATA (Intel VT)
64bit XEN Hypervisor on a RHEL4U2 64bit root (/dev/sda)
32bit fully virtualized (HVM) guest RHEL4U2 256MB (/dev/sdb)
pae=1, acpi=1, apic=1
kernargs clock=pit
64bit fully virtualized (HVM) guest RHEL4U2 256MB (/dev/sdc)
pae=1, acpi=1, apic=1
kernargs clock=pit noapic
Boot Tests:
Boot a fully virtualized (HVM) guest to the login prompt
Results are marked Pass|Fail where (n) points to a failure description
Regression Tests:
851 tests (850 ltp tests and one 30 minute user load test)
Tests are marked #Pass/#Fail where (n) points to a failure description
XEN 64bit 1 CPU Hypervisor (booted nosmp):
----------------------------------------------------------------------
| XEN | Guest Kernel (SMP kernels booted with 1 CPU) |
| Changeset|-----------------------------------------------------------|
| | 32bit UP | 32bit SMP | 64bit UP | 64bit SMP |
| |--------------|--------------|--------------|--------------|
| | Boot | Test | Boot | Test | Boot | Test | Boot | Test |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9972 | Pass | 850/1 | Fail | | Pass | | Pass | 851/0 |
| | (2) | (1) | (7) | | (2) | | (2) | |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9960 | Pass | 850/1 | Fail | | Pass | | Pass | 851/0 |
| | (2) | (1) | (7) | | (2) | | (2) | |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9925 | Pass | 850/1 | Fail | | Pass | | Pass | 851/0 |
| | (2) | (1) | (3) | | (2) | | (2) | |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9920 | Pass | 850/1 | Fail | | Pass | | Pass | 851/0 |
| | (2) | (1) | (3) | | (2) | | (2) | |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9913 | Pass | 851/0 | Fail | | Pass | | Pass | 851/0 |
| | (2) | | (3) | | (2) | | (2) | |
----------------------------------------------------------------------
XEN 64bit 2 CPU Hypervisor (booted smp):
----------------------------------------------------------------------
| XEN | Guest Kernel (SMP kernels booted with 2 CPUs) |
| Changeset|-----------------------------------------------------------|
| | 32bit UP | 32bit SMP | 64bit UP | 64bit SMP |
| |--------------|--------------|--------------|--------------|
| | Boot | Test | Boot | Test | Boot | Test | Boot | Test |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9972 | Pass | | Fail | | Pass | | Pass | Fail |
| | (2) | | (7) | | (2) | | (5,6)| (4) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9960 | Pass | | Fail | | Pass | | Pass | Fail |
| | (2) | | (7) | | (2) | | (5,6)| (4) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9925 | Pass | | Fail | | Pass | | Pass | Fail |
| | (2) | | (3) | | (2) | | (5,6)| (4) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9920 | Pass | | Fail | | Pass | | Pass | Fail |
| | (2) | | (3) | | (2) | | (5,6)| (4) |
|----------|------|-------|------|-------|------|-------|------|-------|
| 9913 | Pass | | Fail | | Pass | | Pass | Fail |
| | (2) | | (3) | | (2) | | (5,6)| (4) |
----------------------------------------------------------------------
Failures:
1. 32bit UP guest fail ltp gettimeofday02:
"Time is going backwards"
2. 32bit and 64bit guests fail first boot attempt after booting XEN:
"(XEN) Failed vm entry, domain_crash_sync called from vmx.c"
3. 32bit SMP guest hangs on boot:
"Uncompressing Linux... Ok, booting the kernel."
4. 64bit SMP guest fails testing:
Guest hangs under load.
5. 64bit SMP guest report these messages the XEN console:
"(XEN) spurious IRQ irq got=-1"
6. 64bit SMP guest report these messages the XEN console during testing:
"(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252"
7. 32bit SMP guest crashes on boot:
"(XEN) __hvm_bug at vmx.c:2286"
[-- Attachment #2: boot.2 --]
[-- Type: text/plain, Size: 4362 bytes --]
File: boot.2
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
Kernel 2.6.16.13-xen on an x86_64
Bridge firewalling registered
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
tst110 login: root
[root@tst110 ~]# xm info
host : tst110
release : 2.6.16.13-xen
version : #1 SMP Fri May 12 01:45:32 EDT 2006
machine : x86_64
nr_cpus : 1
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 1
threads_per_core : 1
cpu_mhz : 2793
hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
total_memory : 1023
free_memory : 209
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
platform_params : virt_start=0xffff800000000000
xen_changeset : Wed May 10 17:30:42 2006 +0100 9972:91c77df11b43
cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)
cc_compile_by : build
cc_compile_domain : katana-technology.com
cc_compile_date : Fri May 12 00:48:20 EDT 2006
(XEN) Failed vm entry
(XEN) domain_crash_sync called from vmx.c:2086
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: 0010:[<0000000000100000>]
(XEN) RFLAGS: 0000000000000002 CONTEXT: hvm
(XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 0000000000000000 rsp: 0000000000000000 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 000000000005003b cr3: 0000000000000000
(XEN) ds: 0008 es: 0008 fs: 0008 gs: 0008 ss: 0008 cs: 0010
(XEN) (GUEST: 2) HVM Loader
(XEN) (GUEST: 2) Loading ROMBIOS ...
(XEN) (GUEST: 2) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 2) Loading ACPI ...
(XEN) (GUEST: 2) Loading VMXAssist ...
(XEN) (GUEST: 2) VMX go ...
(XEN) (GUEST: 2) VMXAssist (May 12 2006)
(XEN) (GUEST: 2) Memory size 256 MB
(XEN) (GUEST: 2) E820 map:
(XEN) (GUEST: 2) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 2) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 2) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 2) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 2) 0000000000100000 - 000000000FFFE000 (RAM)
(XEN) (GUEST: 2) 000000000FFFE000 - 000000000FFFF000 (Type 18)
(XEN) (GUEST: 2) 000000000FFFF000 - 0000000010000000 (Type 17)
(XEN) (GUEST: 2) 0000000010000000 - 0000000010003000 (ACPI NVS)
(XEN) (GUEST: 2) 0000000010003000 - 000000001000D000 (ACPI Data)
(XEN) (GUEST: 2) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Start BIOS ...
(XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 2) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 2) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 2) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 2) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
(XEN) (GUEST: 2) HVMAssist BIOS, 8 cpus, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) (GUEST: 2) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (10757 MBytes)
(XEN) (GUEST: 2) ata0 slave: Unknown device
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Booting from Hard Disk...
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) KBD: unsupported int 16h function 03
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=E980, BX=E6F5 not yet supported!
(XEN) (GUEST: 2) int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
[-- Attachment #3: boot.3 --]
[-- Type: text/plain, Size: 3618 bytes --]
File: boot.3
[root@tst177 ~]# xm info
host : tst177.katana-technology.com
release : 2.6.16-xen
version : #1 SMP Wed Apr 26 01:42:49 EDT 2006
machine : x86_64
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2793
hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
total_memory : 2047
free_memory : 131
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
platform_params : virt_start=0xffff800000000000
xen_changeset : Tue Apr 25 13:22:11 2006 +0100 9744:1ad06bd6832d
cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)
cc_compile_by : build
cc_compile_domain : katana-technology.com
cc_compile_date : Wed Apr 26 00:47:38 EDT 2006
[root@tst177 ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1877 2 r----- 36.5
(XEN) (GUEST: 3) Loading ROMBIOS ...
(XEN) (GUEST: 3) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 3) Loading ACPI ...
(XEN) (GUEST: 3) Loading VMXAssist ...
(XEN) (GUEST: 3) VMX go ...
(XEN) (GUEST: 3) VMXAssist (Apr 26 2006)
(XEN) (GUEST: 3) Memory size 256 MB
(XEN) (GUEST: 3) E820 map:
(XEN) (GUEST: 3) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 3) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 3) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 3) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 3) 0000000000100000 - 000000000FFFE000 (RAM)
(XEN) (GUEST: 3) 000000000FFFE000 - 000000000FFFF000 (Type 18)
(XEN) (GUEST: 3) 000000000FFFF000 - 0000000010000000 (Type 17)
(XEN) (GUEST: 3) 0000000010000000 - 0000000010003000 (ACPI NVS)
(XEN) (GUEST: 3) 0000000010003000 - 000000001000D000 (ACPI Data)
(XEN) (GUEST: 3) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 3)
(XEN) (GUEST: 3) Start BIOS ...
(XEN) (GUEST: 3) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 3) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 3) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 3) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 3) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
(XEN) (GUEST: 3) HVMAssist BIOS, 8 cpus, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 3)
(XEN) (GUEST: 3) ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) (GUEST: 3) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (12997 MBytes)
(XEN) (GUEST: 3) ata0 slave: Unknown device
(XEN) (GUEST: 3)
(XEN) (GUEST: 3) Booting from Hard Disk...
(XEN) (GUEST: 3) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) (GUEST: 3) int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) (GUEST: 3) *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) (GUEST: 3) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 3) KBD: unsupported int 16h function 03
(XEN) (GUEST: 3) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 3) *** int 15h function AX=E980, BX=E6F5 not yet supported!
(XEN) (GUEST: 3) int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) (GUEST: 3) int13_harddisk: function 41, unmapped device for ELDL=81
32bit SMP guest has hung at this point. Last message on the guest console:
Uncompressing Linux... Ok, booting the kernel.
[-- Attachment #4: boot.5 --]
[-- Type: text/plain, Size: 5675 bytes --]
File: boot.5
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
Kernel 2.6.16.13-xen on an x86_64
tst177 login: root
Password:
Last login: Fri May 12 10:16:55 on ttyS0
You have new mail.
[root@tst177 ~]# /etc/init.d/xend start
Bridge firewalling registered
ip_tables: (C) 2000-2006 Netfilter Core Team
[root@tst177 ~]# xm info
host : tst177
release : 2.6.16.13-xen
version : #1 SMP Fri May 12 01:45:32 EDT 2006
machine : x86_64
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2793
hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
total_memory : 2047
free_memory : 131
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
platform_params : virt_start=0xffff800000000000
xen_changeset : Wed May 10 17:30:42 2006 +0100 9972:91c77df11b43
cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)
cc_compile_by : build
cc_compile_domain : katana-technology.com
cc_compile_date : Fri May 12 00:48:20 EDT 2006
[root@tst177 ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1877 2 r----- 35.4
[root@tst177 ~]# ip_tables: (C) 2000-2006 Netfilter Core Team
(XEN) Failed vm entry
(XEN) domain_crash_sync called from vmx.c:2086
(XEN) Domain 1 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 1
(XEN) RIP: 0010:[<0000000000100000>]
(XEN) RFLAGS: 0000000000000002 CONTEXT: hvm
(XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 0000000000000000 rsp: 0000000000000000 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 000000000005003b cr3: 0000000000000000
(XEN) ds: 0008 es: 0008 fs: 0008 gs: 0008 ss: 0008 cs: 0010
(XEN) (GUEST: 2) HVM Loader
(XEN) (GUEST: 2) Loading ROMBIOS ...
(XEN) (GUEST: 2) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 2) Loading ACPI ...
(XEN) (GUEST: 2) Loading VMXAssist ...
(XEN) (GUEST: 2) VMX go ...
(XEN) (GUEST: 2) VMXAssist (May 12 2006)
(XEN) (GUEST: 2) Memory size 256 MB
(XEN) (GUEST: 2) E820 map:
(XEN) (GUEST: 2) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 2) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 2) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 2) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 2) 0000000000100000 - 000000000FFFE000 (RAM)
(XEN) (GUEST: 2) 000000000FFFE000 - 000000000FFFF000 (Type 18)
(XEN) (GUEST: 2) 000000000FFFF000 - 0000000010000000 (Type 17)
(XEN) (GUEST: 2) 0000000010000000 - 0000000010003000 (ACPI NVS)
(XEN) (GUEST: 2) 0000000010003000 - 000000001000D000 (ACPI Data)
(XEN) (GUEST: 2) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Start BIOS ...
(XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 2) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 2) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 2) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 2) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
(XEN) (GUEST: 2) HVMAssist BIOS, 8 cpus, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) (GUEST: 2) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (12997 MBytes)
(XEN) (GUEST: 2) ata0 slave: Unknown device
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Booting from Hard Disk...
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=EC00, BX=0002 not yet supported!
(XEN) (GUEST: 2) KBD: unsupported int 16h function 03
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) Local APIC Write to read-only register
(XEN) This hvm_vlapic is for P4, no work for De-assert init
(XEN) AP 1 bringup suceeded.
(XEN) (GUEST: 2) Start AP 1 from 00006000 ...
(XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=0600:0000
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
[-- Attachment #5: boot.7 --]
[-- Type: text/plain, Size: 6194 bytes --]
File: boot.7
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
Kernel 2.6.16.13-xen on an x86_64
tst177 login: root
Password:
Last login: Fri May 12 09:35:45 from 10.1.2.13
You have new mail.
[root@tst177 ~]# /etc/init.d/xend start
Bridge firewalling registered
ip_tables: (C) 2000-2006 Netfilter Core Team
[root@tst177 ~]# xm info
host : tst177
release : 2.6.16.13-xen
version : #1 SMP Fri May 12 01:45:32 EDT 2006
machine : x86_64
nr_cpus : 1
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 1
threads_per_core : 1
cpu_mhz : 2793
hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
total_memory : 2047
free_memory : 131
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
platform_params : virt_start=0xffff800000000000
xen_changeset : Wed May 10 17:30:42 2006 +0100 9972:91c77df11b43
cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)
cc_compile_by : build
cc_compile_domain : katana-technology.com
cc_compile_date : Fri May 12 00:48:20 EDT 2006
[root@tst177 ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1877 1 r----- 32.6
[root@tst177 ~]# ip_tables: (C) 2000-2006 Netfilter Core Team
(XEN) Failed vm entry
(XEN) domain_crash_sync called from vmx.c:2086
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: 0010:[<0000000000100000>]
(XEN) RFLAGS: 0000000000000002 CONTEXT: hvm
(XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 0000000000000000 rsp: 0000000000000000 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 000000000005003b cr3: 0000000000000000
(XEN) ds: 0008 es: 0008 fs: 0008 gs: 0008 ss: 0008 cs: 0010
(XEN) (GUEST: 2) HVM Loader
(XEN) (GUEST: 2) Loading ROMBIOS ...
(XEN) (GUEST: 2) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 2) Loading ACPI ...
(XEN) (GUEST: 2) Loading VMXAssist ...
(XEN) (GUEST: 2) VMX go ...
(XEN) (GUEST: 2) VMXAssist (May 12 2006)
(XEN) (GUEST: 2) Memory size 256 MB
(XEN) (GUEST: 2) E820 map:
(XEN) (GUEST: 2) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 2) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 2) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 2) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 2) 0000000000100000 - 000000000FFFE000 (RAM)
(XEN) (GUEST: 2) 000000000FFFE000 - 000000000FFFF000 (Type 18)
(XEN) (GUEST: 2) 000000000FFFF000 - 0000000010000000 (Type 17)
(XEN) (GUEST: 2) 0000000010000000 - 0000000010003000 (ACPI NVS)
(XEN) (GUEST: 2) 0000000010003000 - 000000001000D000 (ACPI Data)
(XEN) (GUEST: 2) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Start BIOS ...
(XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 2) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 2) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 2) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 2) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
(XEN) (GUEST: 2) HVMAssist BIOS, 8 cpus, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) (GUEST: 2) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (12997 MBytes)
(XEN) (GUEST: 2) ata0 slave: Unknown device
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Booting from Hard Disk...
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) KBD: unsupported int 16h function 03
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=E980, BX=E6F5 not yet supported!
(XEN) (GUEST: 2) int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) __hvm_bug at vmx.c:2286
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: 0060:[<00000000c0100264>]
(XEN) RFLAGS: 0000000000010006 CONTEXT: hvm
(XEN) rax: 0000000000000671 rbx: 00000000c038fff0 rcx: 0000000000000003
(XEN) rdx: 0000000000000fc0 rsi: 000000000000fffe rdi: 00000000c040736c
(XEN) rbp: 000000000048c007 rsp: 00000000c031c058 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 0000000080050033 cr3: 0000000001775000
(XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 cs: 0060
(XEN) domain_crash_sync called from vmx.c:2286
(XEN) Domain 2 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: 0060:[<00000000c0100264>]
(XEN) RFLAGS: 0000000000010006 CONTEXT: hvm
(XEN) rax: 0000000000000671 rbx: 00000000c038fff0 rcx: 0000000000000003
(XEN) rdx: 0000000000000fc0 rsi: 000000000000fffe rdi: 00000000c040736c
(XEN) rbp: 000000000048c007 rsp: 00000000c031c058 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 0000000080050033 cr3: 0000000001775000
(XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 cs: 0060
[root@tst177 ~]#
[-- Attachment #6: regression.1 --]
[-- Type: text/plain, Size: 1821 bytes --]
File: regression.1
Time Level Message
05:00:50 INFO Reporting status: 'Test Running' for test: ltp_gettimeofday02
05:00:52 INFO Preparing to run test 'ltp_gettimeofday02' using profile: /qa/conductor/profiles/ltp/syscalls/gettimeofday02.xml
05:00:52 INFO Starting test 'ltp_gettimeofday02' using profile: /qa/conductor/profiles/ltp/syscalls/gettimeofday02.xml
05:00:52 INFO Dispatching operation: RemoteShell
05:00:52 FINE Client sequencer got message requesting the start of a new test: ltp_gettimeofday02
05:00:52 FINER Client sequencer sent message of type: 4 with seq num: 1 of size: 289 bytes
05:00:52 FINER Client sequencer handling new operation from control sequencer
05:00:52 FINE Client sequencer looking for class: com.katana.conductor.operations.RemoteShell
05:00:52 INFO Operation RemoteShell running
05:00:52 FINE Client sequencer was told that an operation is now running
05:00:52 INFO RemoteShell: target node(s) = vs177
05:00:52 INFO ssh: /usr/bin/ssh root@vs177 cd /qa/conductor/tests/ltp/testcases/bin; gettimeofday02
05:00:52 FINE ssh: waiting for command to finish
05:00:53 INFO ssh: gettimeofday02 0 INFO : checking if gettimeofday is monotonous, takes 30s
05:00:53 INFO ssh: gettimeofday02 1 FAIL : Time is going backwards (old 1145696453.61428 vs new 1145696453.60660!
05:00:53 FINE executeShellCmd(ssh): exit value is 1
05:00:53 SEVERE RemoteShell: command failed with error = 1
05:00:53 SEVERE Operation RemoteShell failed
05:00:53 SEVERE Reporting status: 'Test Failed' for test: ltp_gettimeofday02
05:00:53 FINE Client sequencer detected operation completed with status of: Fail
05:00:53 FINER Client sequencer sent message of type: 5 with seq num: 2 of size: 429 bytes
05:00:53 SEVERE Crash Collection disabled for queue : RHEL4U2-32b-XEN
05:00:53 INFO Cleaning up after test
[-- Attachment #7: regression.4 --]
[-- Type: text/plain, Size: 16324 bytes --]
File: regression.4
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
Kernel 2.6.16.13-xen on an x86_64
tst177 login: root
Password:
Last login: Fri May 12 10:16:55 on ttyS0
You have new mail.
[root@tst177 ~]# /etc/init.d/xend start
Bridge firewalling registered
ip_tables: (C) 2000-2006 Netfilter Core Team
[root@tst177 ~]# xm info
host : tst177
release : 2.6.16.13-xen
version : #1 SMP Fri May 12 01:45:32 EDT 2006
machine : x86_64
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2793
hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
total_memory : 2047
free_memory : 131
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
platform_params : virt_start=0xffff800000000000
xen_changeset : Wed May 10 17:30:42 2006 +0100 9972:91c77df11b43
cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)
cc_compile_by : build
cc_compile_domain : katana-technology.com
cc_compile_date : Fri May 12 00:48:20 EDT 2006
[root@tst177 ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1877 2 r----- 35.4
[root@tst177 ~]# ip_tables: (C) 2000-2006 Netfilter Core Team
(XEN) Failed vm entry
(XEN) domain_crash_sync called from vmx.c:2086
(XEN) Domain 1 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 1
(XEN) RIP: 0010:[<0000000000100000>]
(XEN) RFLAGS: 0000000000000002 CONTEXT: hvm
(XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 0000000000000000 rsp: 0000000000000000 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 000000000005003b cr3: 0000000000000000
(XEN) ds: 0008 es: 0008 fs: 0008 gs: 0008 ss: 0008 cs: 0010
(XEN) (GUEST: 2) HVM Loader
(XEN) (GUEST: 2) Loading ROMBIOS ...
(XEN) (GUEST: 2) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 2) Loading ACPI ...
(XEN) (GUEST: 2) Loading VMXAssist ...
(XEN) (GUEST: 2) VMX go ...
(XEN) (GUEST: 2) VMXAssist (May 12 2006)
(XEN) (GUEST: 2) Memory size 256 MB
(XEN) (GUEST: 2) E820 map:
(XEN) (GUEST: 2) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 2) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 2) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 2) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 2) 0000000000100000 - 000000000FFFE000 (RAM)
(XEN) (GUEST: 2) 000000000FFFE000 - 000000000FFFF000 (Type 18)
(XEN) (GUEST: 2) 000000000FFFF000 - 0000000010000000 (Type 17)
(XEN) (GUEST: 2) 0000000010000000 - 0000000010003000 (ACPI NVS)
(XEN) (GUEST: 2) 0000000010003000 - 000000001000D000 (ACPI Data)
(XEN) (GUEST: 2) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Start BIOS ...
(XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 2) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 2) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 2) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 2) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
(XEN) (GUEST: 2) HVMAssist BIOS, 8 cpus, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) (GUEST: 2) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (12997 MBytes)
(XEN) (GUEST: 2) ata0 slave: Unknown device
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Booting from Hard Disk...
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=EC00, BX=0002 not yet supported!
(XEN) (GUEST: 2) KBD: unsupported int 16h function 03
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) Local APIC Write to read-only register
(XEN) This hvm_vlapic is for P4, no work for De-assert init
(XEN) AP 1 bringup suceeded.
(XEN) (GUEST: 2) Start AP 1 from 00006000 ...
(XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=0600:0000
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
Guest is hung at this point
[-- Attachment #8: regression.6 --]
[-- Type: text/plain, Size: 5681 bytes --]
File: regression.6
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
Kernel 2.6.16.13-xen on an x86_64
tst177 login: root
Password:
Last login: Fri May 12 10:16:55 on ttyS0
You have new mail.
[root@tst177 ~]# /etc/init.d/xend start
Bridge firewalling registered
ip_tables: (C) 2000-2006 Netfilter Core Team
[root@tst177 ~]# xm info
host : tst177
release : 2.6.16.13-xen
version : #1 SMP Fri May 12 01:45:32 EDT 2006
machine : x86_64
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2793
hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
total_memory : 2047
free_memory : 131
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
platform_params : virt_start=0xffff800000000000
xen_changeset : Wed May 10 17:30:42 2006 +0100 9972:91c77df11b43
cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)
cc_compile_by : build
cc_compile_domain : katana-technology.com
cc_compile_date : Fri May 12 00:48:20 EDT 2006
[root@tst177 ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 1877 2 r----- 35.4
[root@tst177 ~]# ip_tables: (C) 2000-2006 Netfilter Core Team
(XEN) Failed vm entry
(XEN) domain_crash_sync called from vmx.c:2086
(XEN) Domain 1 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 1
(XEN) RIP: 0010:[<0000000000100000>]
(XEN) RFLAGS: 0000000000000002 CONTEXT: hvm
(XEN) rax: 0000000000000000 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 0000000000000000 rsp: 0000000000000000 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 000000000005003b cr3: 0000000000000000
(XEN) ds: 0008 es: 0008 fs: 0008 gs: 0008 ss: 0008 cs: 0010
(XEN) (GUEST: 2) HVM Loader
(XEN) (GUEST: 2) Loading ROMBIOS ...
(XEN) (GUEST: 2) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 2) Loading ACPI ...
(XEN) (GUEST: 2) Loading VMXAssist ...
(XEN) (GUEST: 2) VMX go ...
(XEN) (GUEST: 2) VMXAssist (May 12 2006)
(XEN) (GUEST: 2) Memory size 256 MB
(XEN) (GUEST: 2) E820 map:
(XEN) (GUEST: 2) 0000000000000000 - 000000000009F800 (RAM)
(XEN) (GUEST: 2) 000000000009F800 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 2) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 2) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 2) 0000000000100000 - 000000000FFFE000 (RAM)
(XEN) (GUEST: 2) 000000000FFFE000 - 000000000FFFF000 (Type 18)
(XEN) (GUEST: 2) 000000000FFFF000 - 0000000010000000 (Type 17)
(XEN) (GUEST: 2) 0000000010000000 - 0000000010003000 (ACPI NVS)
(XEN) (GUEST: 2) 0000000010003000 - 000000001000D000 (ACPI Data)
(XEN) (GUEST: 2) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Start BIOS ...
(XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 2) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 2) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 2) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 2) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
(XEN) (GUEST: 2) HVMAssist BIOS, 8 cpus, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
(XEN) (GUEST: 2) ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (12997 MBytes)
(XEN) (GUEST: 2) ata0 slave: Unknown device
(XEN) (GUEST: 2)
(XEN) (GUEST: 2) Booting from Hard Disk...
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) *** int 15h function AX=EC00, BX=0002 not yet supported!
(XEN) (GUEST: 2) KBD: unsupported int 16h function 03
(XEN) (GUEST: 2) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) (GUEST: 2) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) Local APIC Write to read-only register
(XEN) This hvm_vlapic is for P4, no work for De-assert init
(XEN) AP 1 bringup suceeded.
(XEN) (GUEST: 2) Start AP 1 from 00006000 ...
(XEN) (GUEST: 2) Starting emulated 16-bit real-mode: ip=0600:0000
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) spurious IRQ irq got=-1
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
(XEN) <vlapic_accept_irq>level trig mode repeatedly for vector 252
[-- Attachment #9: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply
* Re: Symbios-NCR 6285-3621 + Adaptec 2944W multilun problem
From: Gabriel Gomiz @ 2006-05-12 14:34 UTC (permalink / raw)
To: James Bottomley; +Cc: linux-scsi
In-Reply-To: <1147442986.3769.2.camel@mulgrave.il.steeleye.com>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
James:
First of all I want to salute you and give thanks for the Linux Voyager
Architecture support! Maybe you remember me from that 2.4.19 boot
problem with the NCR 4100!!! We have two 4100 running perfectly with
linux since then. Now with kernel 2.6.x!!! Thanks again for that.
I'm attaching dmesg output. I'm sorry I forgot to attach it in the last
email. The I/O errors occur when the devices are being detected and
whenever I try to access them. For example to do 'fsidk -l /dev/sdc'.
Thanks again
James Bottomley wrote:
> On Fri, 2006-05-12 at 10:29 -0300, Gabriel Gomiz wrote:
>
>>When configuring 2.6.16.13 kernel scsi subsystem with multilun
>>support,
>>I'm trying to access a Symbios 6285-3621 Array via an Adaptec 2944W
>>HBA
>>with aic7xxx module. All scsi "virtual devices" are recognized
>>sdc-sdd-sde-sdf-sdg-sdh-sdi but then when the kernel tries to detect
>>the
>>partition tables it gets a lot of "Buffer I/O errors".
>
>
> Could we get the dmesg output, both of the devices being detected, and
> when the I/O errors occur, please?
>
> James
--
.^. Lic. Gabriel Gomiz - Red Hat Certified Engineer (RHCE)
/V\ Administrador Red/Sistemas - Desarrollo Sistema POSEIDON
// \\ Gerencia de Sistemas - Cooperativa Obrera Ltda.
/( )\ Tel (0291) 456-0084
^^-^^ s/Window[$s]/LINUX!!/g or die;
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 42440 bytes --]
Linux version 2.6.16.13 (root@galadriel.cooperativaobrera.com.ar) (gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)) #2 SMP Thu May 4 18:35:29 ART 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009d800 (usable)
BIOS-e820: 000000000009d800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0400 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000f9efa800 (usable)
BIOS-e820: 00000000f9efa800 - 00000000f9effc00 (ACPI data)
BIOS-e820: 00000000f9effc00 - 00000000f9f00000 (ACPI NVS)
BIOS-e820: 00000000fe300000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000106100000 (usable)
Warning only 4GB will be used.
Use a PAE enabled kernel.
3200MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f6b70
On node 0 totalpages: 1048576
DMA zone: 4096 pages, LIFO batch:0
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 225280 pages, LIFO batch:31
HighMem zone: 819200 pages, LIFO batch:31
DMI 2.1 present.
Using APIC driver default
ACPI: RSDP (v000 PTLTD ) @ 0x000f6b50
ACPI: RSDT (v001 INTEL S450NX01 0x00000000 INTL 0x01000000) @ 0xf9efabdf
ACPI: FADT (v001 Intel S450NX 0x00000002 INT 0x000f4240) @ 0xf9effafe
ACPI: MADT (v001 Intel Custom 0x00000001 INT 0x10000000) @ 0xf9effb72
ACPI: DSDT (v001 INTEL S450NX1 0x00000001 MSFT 0x01000009) @ 0x00000000
ACPI: BIOS age (1999) fails cutoff (2001), acpi=force is required to enable ACPI
ACPI: Disabling ACPI support
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: INTEL Product ID: S450NX APIC at: 0xFEE00000
Processor #3 6:7 APIC version 17
Processor #0 6:7 APIC version 17
Processor #1 6:7 APIC version 17
Processor #2 6:7 APIC version 17
I/O APIC #4 Version 19 at 0xFEC00000.
Enabling APIC mode: Flat. Using 1 I/O APICs
Processors: 4
Allocating PCI resources starting at fa000000 (gap: f9f00000:04400000)
Built 1 zonelists
Kernel command line: ro root=/dev/vol00/root
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0392000 soft=c0372000
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 550.250 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 4046464k/4194304k available (1611k kernel code, 47224k reserved, 678k data, 188k init, 3177448k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1102.51 BogoMIPS (lpj=2205028)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0387fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0387fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU serial number disabled.
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
CPU0: Intel Pentium III (Katmai) stepping 03
Booting processor 1/0 eip 2000
CPU 1 irqstacks, hard=c0393000 soft=c0373000
Initializing CPU#1
Calibrating delay using timer specific routine.. 1100.46 BogoMIPS (lpj=2200921)
CPU: After generic identify, caps: 0387fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0387fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU serial number disabled.
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel Pentium III (Katmai) stepping 03
Booting processor 2/1 eip 2000
CPU 2 irqstacks, hard=c0394000 soft=c0374000
Initializing CPU#2
Calibrating delay using timer specific routine.. 1100.45 BogoMIPS (lpj=2200913)
CPU: After generic identify, caps: 0387fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0387fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU serial number disabled.
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#2.
CPU2: Intel Pentium III (Katmai) stepping 03
Booting processor 3/2 eip 2000
CPU 3 irqstacks, hard=c0395000 soft=c0375000
Initializing CPU#3
Calibrating delay using timer specific routine.. 1100.48 BogoMIPS (lpj=2200965)
CPU: After generic identify, caps: 0387fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0387fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU serial number disabled.
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#3.
CPU3: Intel Pentium III (Katmai) stepping 03
Total of 4 processors activated (4403.91 BogoMIPS).
ExtINT not setup in hardware but reported by MP table
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
checking TSC synchronization across 4 CPUs: passed.
Brought up 4 CPUs
migration_cost=6742
checking if image is initramfs... it is
Freeing initrd memory: 1158k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfdb33, last bus=1
PCI: Using configuration type 1
ACPI: Subsystem revision 20060127
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:00:0a.0
PCI quirk: region 0c00-0c3f claimed by PIIX4 ACPI
PCI quirk: region 0cc0-0ccf claimed by PIIX4 SMB
PIIX4 devres B PIO at 0ca2-0ca3
PIIX4 devres C PIO at 0ca0-0ca1
PCI: Searching for i450NX host bridges on 0000:00:10.0
PCI->APIC IRQ transform: 0000:01:03.0[A] -> IRQ 185
PCI->APIC IRQ transform: 0000:01:03.1[B] -> IRQ 177
PCI->APIC IRQ transform: 0000:01:05.0[A] -> IRQ 161
PCI->APIC IRQ transform: 0000:00:06.0[A] -> IRQ 145
PCI->APIC IRQ transform: 0000:00:07.0[A] -> IRQ 153
PCI->APIC IRQ transform: 0000:00:08.0[A] -> IRQ 193
PCI->APIC IRQ transform: 0000:00:0c.2[D] -> IRQ 169
apm: BIOS not found.
audit: initializing netlink socket (disabled)
audit(1146771827.192:1): initialized
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Real Time Clock Driver v1.12ac
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
Probing IDE interface ide1...
ide-floppy driver 0.99.newide
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
IP route cache hash table entries: 262144 (order: 8, 1048576 bytes)
TCP established hash table entries: 131072 (order: 9, 2621440 bytes)
TCP bind hash table entries: 65536 (order: 8, 1310720 bytes)
input: AT Translated Set 2 keyboard as /class/input/input0
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Freeing unused kernel memory: 188k freed
SCSI subsystem initialized
sym0: <896> rev 0x1 at pci 0000:01:03.0 irq 185
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.2.2
input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
Vendor: SEAGATE Model: ST318203LC Rev: 0002
Type: Direct-Access ANSI SCSI revision: 02
target0:0:0: tagged command queuing enabled, command queue depth 16.
target0:0:0: Beginning Domain Validation
target0:0:0: asynchronous
target0:0:0: wide asynchronous
target0:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 15)
target0:0:0: Domain Validation skipping write tests
target0:0:0: Ending Domain Validation
SCSI device sda: 35566480 512-byte hdwr sectors (18210 MB)
sda: Write Protect is off
sda: Mode Sense: 9f 00 10 08
SCSI device sda: drive cache: write through w/ FUA
SCSI device sda: 35566480 512-byte hdwr sectors (18210 MB)
sda: Write Protect is off
sda: Mode Sense: 9f 00 10 08
SCSI device sda: drive cache: write through w/ FUA
sda: sda1 sda2
sd 0:0:0:0: Attached scsi disk sda
Vendor: SEAGATE Model: ST318405LC Rev: 5063
Type: Direct-Access ANSI SCSI revision: 03
target0:0:1: tagged command queuing enabled, command queue depth 16.
target0:0:1: Beginning Domain Validation
target0:0:1: asynchronous
target0:0:1: wide asynchronous
target0:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
target0:0:1: Domain Validation skipping write tests
target0:0:1: Ending Domain Validation
SCSI device sdb: 35843670 512-byte hdwr sectors (18352 MB)
sdb: Write Protect is off
sdb: Mode Sense: 9f 00 10 08
SCSI device sdb: drive cache: write back w/ FUA
SCSI device sdb: 35843670 512-byte hdwr sectors (18352 MB)
sdb: Write Protect is off
sdb: Mode Sense: 9f 00 10 08
SCSI device sdb: drive cache: write back w/ FUA
sdb: sdb1 sdb2
sd 0:0:1:0: Attached scsi disk sdb
Vendor: ESG-SHV Model: SCA HSBP M6 Rev: 0.61
Type: Processor ANSI SCSI revision: 02
target0:0:6: Beginning Domain Validation
target0:0:6: asynchronous
target0:0:6: Ending Domain Validation
sym1: <896> rev 0x1 at pci 0000:01:03.1 irq 177
sym1: No NVRAM, ID 7, Fast-40, SE, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.2.2
Vendor: TOSHIBA Model: CD-ROM XM-6401TA Rev: 1012
Type: CD-ROM ANSI SCSI revision: 02
target1:0:5: Beginning Domain Validation
target1:0:5: asynchronous
target1:0:5: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 16)
target1:0:5: Domain Validation skipping write tests
target1:0:5: Ending Domain Validation
sym2: <810a> rev 0x23 at pci 0000:00:08.0 irq 193
sym2: No NVRAM, ID 7, Fast-10, SE, parity checking
sym2: SCSI BUS has been reset.
scsi2 : sym-2.2.2
scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 2944 SCSI adapter>
aic7870: Wide Channel A, SCSI Id=6, 16/253 SCBs
Vendor: SYMBIOS Model: INF-01-00 Rev: 0205
Type: Direct-Access ANSI SCSI revision: 02
scsi3:A:1:0: Tagged Queuing enabled. Depth 4
target3:0:1: Beginning Domain Validation
target3:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
target3:0:1: Domain Validation skipping write tests
target3:0:1: Ending Domain Validation
SCSI device sdc: 35484544 512-byte hdwr sectors (18168 MB)
sdc: Write Protect is off
sdc: Mode Sense: 6b 00 10 08
SCSI device sdc: drive cache: write through w/ FUA
SCSI device sdc: 35484544 512-byte hdwr sectors (18168 MB)
sdc: Write Protect is off
sdc: Mode Sense: 6b 00 10 08
SCSI device sdc: drive cache: write through w/ FUA
sdc:end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
unable to read partition table
sd 3:0:1:0: Attached scsi disk sdc
Vendor: SYMBIOS Model: INF-01-00 Rev: 0205
Type: Direct-Access ANSI SCSI revision: 02
target3:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
scsi3:A:1:1: Tagged Queuing enabled. Depth 4
SCSI device sdd: 35484544 512-byte hdwr sectors (18168 MB)
sdd: Write Protect is off
sdd: Mode Sense: 6b 00 10 08
SCSI device sdd: drive cache: write through w/ FUA
SCSI device sdd: 35484544 512-byte hdwr sectors (18168 MB)
sdd: Write Protect is off
sdd: Mode Sense: 6b 00 10 08
SCSI device sdd: drive cache: write through w/ FUA
sdd:end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
end_request: I/O error, dev sdd, sector 0
Buffer I/O error on device sdd, logical block 0
unable to read partition table
sd 3:0:1:1: Attached scsi disk sdd
Vendor: SYMBIOS Model: INF-01-00 Rev: 0205
Type: Direct-Access ANSI SCSI revision: 02
target3:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
scsi3:A:1:2: Tagged Queuing enabled. Depth 4
SCSI device sde: 35484544 512-byte hdwr sectors (18168 MB)
sde: Write Protect is off
sde: Mode Sense: 6b 00 10 08
SCSI device sde: drive cache: write through w/ FUA
SCSI device sde: 35484544 512-byte hdwr sectors (18168 MB)
sde: Write Protect is off
sde: Mode Sense: 6b 00 10 08
SCSI device sde: drive cache: write through w/ FUA
sde:end_request: I/O error, dev sde, sector 0
Buffer I/O error on device sde, logical block 0
end_request: I/O error, dev sde, sector 0
Buffer I/O error on device sde, logical block 0
end_request: I/O error, dev sde, sector 0
Buffer I/O error on device sde, logical block 0
unable to read partition table
sd 3:0:1:2: Attached scsi disk sde
Vendor: SYMBIOS Model: INF-01-00 Rev: 0205
Type: Direct-Access ANSI SCSI revision: 02
target3:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
scsi3:A:1:3: Tagged Queuing enabled. Depth 4
SCSI device sdf: 35484544 512-byte hdwr sectors (18168 MB)
sdf: Write Protect is off
sdf: Mode Sense: 6b 00 10 08
SCSI device sdf: drive cache: write through w/ FUA
SCSI device sdf: 35484544 512-byte hdwr sectors (18168 MB)
sdf: Write Protect is off
sdf: Mode Sense: 6b 00 10 08
SCSI device sdf: drive cache: write through w/ FUA
sdf:end_request: I/O error, dev sdf, sector 0
Buffer I/O error on device sdf, logical block 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 0
unable to read partition table
sd 3:0:1:3: Attached scsi disk sdf
Vendor: SYMBIOS Model: INF-01-00 Rev: 0205
Type: Direct-Access ANSI SCSI revision: 02
target3:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
scsi3:A:1:4: Tagged Queuing enabled. Depth 4
SCSI device sdg: 35484544 512-byte hdwr sectors (18168 MB)
sdg: Write Protect is off
sdg: Mode Sense: 6b 00 10 08
SCSI device sdg: drive cache: write through w/ FUA
SCSI device sdg: 35484544 512-byte hdwr sectors (18168 MB)
sdg: Write Protect is off
sdg: Mode Sense: 6b 00 10 08
SCSI device sdg: drive cache: write through w/ FUA
sdg:end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 0
unable to read partition table
sd 3:0:1:4: Attached scsi disk sdg
Vendor: SYMBIOS Model: INF-01-00 Rev: 0205
Type: Direct-Access ANSI SCSI revision: 02
target3:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
scsi3:A:1:5: Tagged Queuing enabled. Depth 4
SCSI device sdh: 35484544 512-byte hdwr sectors (18168 MB)
sdh: Write Protect is off
sdh: Mode Sense: 6b 00 10 08
SCSI device sdh: drive cache: write through w/ FUA
SCSI device sdh: 35484544 512-byte hdwr sectors (18168 MB)
sdh: Write Protect is off
sdh: Mode Sense: 6b 00 10 08
SCSI device sdh: drive cache: write through w/ FUA
sdh:end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 0
unable to read partition table
sd 3:0:1:5: Attached scsi disk sdh
Vendor: SYMBIOS Model: INF-01-00 Rev: 0205
Type: Direct-Access ANSI SCSI revision: 02
target3:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
scsi3:A:1:6: Tagged Queuing enabled. Depth 4
Vendor: SYMBIOS Model: INF-01-00 Rev: 0205
Type: Direct-Access ANSI SCSI revision: 02
target3:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)
scsi3:A:1:7: Tagged Queuing enabled. Depth 4
SCSI device sdi: 35484544 512-byte hdwr sectors (18168 MB)
sdi: Write Protect is off
sdi: Mode Sense: 6b 00 10 08
SCSI device sdi: drive cache: write through w/ FUA
SCSI device sdi: 35484544 512-byte hdwr sectors (18168 MB)
sdi: Write Protect is off
sdi: Mode Sense: 6b 00 10 08
SCSI device sdi: drive cache: write through w/ FUA
sdi:end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 0
unable to read partition table
sd 3:0:1:7: Attached scsi disk sdi
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
md: raid1 personality registered for level 1
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb2 ...
md: adding sdb2 ...
md: sdb1 has different UUID to sdb2
md: adding sda2 ...
md: sda1 has different UUID to sdb2
md: created md1
md: bind<sda2>
md: bind<sdb2>
md: running: <sdb2><sda2>
raid1: raid set md1 active with 2 out of 2 mirrors
md: considering sdb1 ...
md: adding sdb1 ...
md: adding sda1 ...
md: created md0
md: bind<sda1>
md: bind<sdb1>
md: running: <sdb1><sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 35484416
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 35484416
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sde, sector 35484416
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 35484416
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 35484416
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 35484416
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 35484416
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdi, sector 0
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:1:0: Attached scsi generic sg1 type 0
0:0:6:0: Attached scsi generic sg2 type 3
1:0:5:0: Attached scsi generic sg3 type 5
sd 3:0:1:0: Attached scsi generic sg4 type 0
sd 3:0:1:1: Attached scsi generic sg5 type 0
sd 3:0:1:2: Attached scsi generic sg6 type 0
sd 3:0:1:3: Attached scsi generic sg7 type 0
sd 3:0:1:4: Attached scsi generic sg8 type 0
sd 3:0:1:5: Attached scsi generic sg9 type 0
3:0:1:6: Attached scsi generic sg10 type 0
sd 3:0:1:7: Attached scsi generic sg11 type 0
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.20
sr 1:0:5:0: Attached scsi CD-ROM sr0
PIIX4: IDE controller at PCI slot 0000:00:0c.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x24a0-0x24a7, BIOS settings: hda:pio, hdb:pio
Probing IDE interface ide0...
PIIX4: IDE controller at PCI slot 0000:00:10.0
PIIX4: device not capable of full native PCI mode
PIIX4: device disabled (BIOS)
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth0: e100_probe: addr 0xfa200000, irq 145, MAC addr 00:D0:B7:6C:17:E7
e100: eth1: e100_probe: addr 0xfa201000, irq 153, MAC addr 00:D0:B7:6C:0D:F5
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3 FS on dm-0, internal journal
end_request: I/O error, dev sdc, sector 8
printk: 74 messages suppressed.
Buffer I/O error on device sdc, logical block 1
end_request: I/O error, dev sdc, sector 8
Buffer I/O error on device sdc, logical block 1
end_request: I/O error, dev sdc, sector 35484528
Buffer I/O error on device sdc, logical block 4435566
end_request: I/O error, dev sdc, sector 35484528
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484480
end_request: I/O error, dev sdc, sector 35484480
end_request: I/O error, dev sdc, sector 35484288
end_request: I/O error, dev sdc, sector 35484288
end_request: I/O error, dev sdc, sector 35484288
end_request: I/O error, dev sdc, sector 35484288
end_request: I/O error, dev sdc, sector 35484528
end_request: I/O error, dev sdc, sector 35484528
end_request: I/O error, dev sdc, sector 35484144
end_request: I/O error, dev sdc, sector 35484144
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdd, sector 8
end_request: I/O error, dev sdd, sector 8
end_request: I/O error, dev sdd, sector 35484528
end_request: I/O error, dev sdd, sector 35484528
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484480
end_request: I/O error, dev sdd, sector 35484480
end_request: I/O error, dev sdd, sector 35484288
end_request: I/O error, dev sdd, sector 35484288
end_request: I/O error, dev sdd, sector 35484288
end_request: I/O error, dev sdd, sector 35484288
end_request: I/O error, dev sdd, sector 35484528
end_request: I/O error, dev sdd, sector 35484528
end_request: I/O error, dev sdd, sector 35484144
end_request: I/O error, dev sdd, sector 35484144
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sde, sector 8
end_request: I/O error, dev sde, sector 8
end_request: I/O error, dev sde, sector 35484528
end_request: I/O error, dev sde, sector 35484528
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484480
end_request: I/O error, dev sde, sector 35484480
end_request: I/O error, dev sde, sector 35484288
end_request: I/O error, dev sde, sector 35484288
end_request: I/O error, dev sde, sector 35484288
end_request: I/O error, dev sde, sector 35484288
end_request: I/O error, dev sde, sector 35484528
end_request: I/O error, dev sde, sector 35484528
end_request: I/O error, dev sde, sector 35484144
end_request: I/O error, dev sde, sector 35484144
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sdf, sector 8
end_request: I/O error, dev sdf, sector 8
end_request: I/O error, dev sdf, sector 35484528
end_request: I/O error, dev sdf, sector 35484528
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484480
end_request: I/O error, dev sdf, sector 35484480
end_request: I/O error, dev sdf, sector 35484288
end_request: I/O error, dev sdf, sector 35484288
end_request: I/O error, dev sdf, sector 35484288
end_request: I/O error, dev sdf, sector 35484288
end_request: I/O error, dev sdf, sector 35484528
end_request: I/O error, dev sdf, sector 35484528
end_request: I/O error, dev sdf, sector 35484144
end_request: I/O error, dev sdf, sector 35484144
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdg, sector 8
end_request: I/O error, dev sdg, sector 8
end_request: I/O error, dev sdg, sector 35484528
end_request: I/O error, dev sdg, sector 35484528
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484480
end_request: I/O error, dev sdg, sector 35484480
end_request: I/O error, dev sdg, sector 35484288
end_request: I/O error, dev sdg, sector 35484288
end_request: I/O error, dev sdg, sector 35484288
end_request: I/O error, dev sdg, sector 35484288
end_request: I/O error, dev sdg, sector 35484528
end_request: I/O error, dev sdg, sector 35484528
end_request: I/O error, dev sdg, sector 35484144
end_request: I/O error, dev sdg, sector 35484144
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdh, sector 8
end_request: I/O error, dev sdh, sector 8
end_request: I/O error, dev sdh, sector 35484528
end_request: I/O error, dev sdh, sector 35484528
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484480
end_request: I/O error, dev sdh, sector 35484480
end_request: I/O error, dev sdh, sector 35484288
end_request: I/O error, dev sdh, sector 35484288
end_request: I/O error, dev sdh, sector 35484288
end_request: I/O error, dev sdh, sector 35484288
end_request: I/O error, dev sdh, sector 35484528
end_request: I/O error, dev sdh, sector 35484528
end_request: I/O error, dev sdh, sector 35484144
end_request: I/O error, dev sdh, sector 35484144
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdi, sector 8
end_request: I/O error, dev sdi, sector 8
end_request: I/O error, dev sdi, sector 35484528
end_request: I/O error, dev sdi, sector 35484528
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484480
end_request: I/O error, dev sdi, sector 35484480
end_request: I/O error, dev sdi, sector 35484288
end_request: I/O error, dev sdi, sector 35484288
end_request: I/O error, dev sdi, sector 35484288
end_request: I/O error, dev sdi, sector 35484288
end_request: I/O error, dev sdi, sector 35484528
end_request: I/O error, dev sdi, sector 35484528
end_request: I/O error, dev sdi, sector 35484144
end_request: I/O error, dev sdi, sector 35484144
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 35484416
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 35484416
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sde, sector 35484416
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 35484416
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 35484416
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 35484416
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 35484416
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdc, sector 8
end_request: I/O error, dev sdc, sector 8
end_request: I/O error, dev sdc, sector 35484528
end_request: I/O error, dev sdc, sector 35484528
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484480
end_request: I/O error, dev sdc, sector 35484480
end_request: I/O error, dev sdc, sector 35484288
end_request: I/O error, dev sdc, sector 35484288
end_request: I/O error, dev sdc, sector 35484288
end_request: I/O error, dev sdc, sector 35484288
end_request: I/O error, dev sdc, sector 35484528
end_request: I/O error, dev sdc, sector 35484528
end_request: I/O error, dev sdc, sector 35484144
end_request: I/O error, dev sdc, sector 35484144
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdc, sector 35484536
end_request: I/O error, dev sdd, sector 8
end_request: I/O error, dev sdd, sector 8
end_request: I/O error, dev sdd, sector 35484528
end_request: I/O error, dev sdd, sector 35484528
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484480
end_request: I/O error, dev sdd, sector 35484480
end_request: I/O error, dev sdd, sector 35484288
end_request: I/O error, dev sdd, sector 35484288
end_request: I/O error, dev sdd, sector 35484288
end_request: I/O error, dev sdd, sector 35484288
end_request: I/O error, dev sdd, sector 35484528
end_request: I/O error, dev sdd, sector 35484528
end_request: I/O error, dev sdd, sector 35484144
end_request: I/O error, dev sdd, sector 35484144
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sdd, sector 35484536
end_request: I/O error, dev sde, sector 8
end_request: I/O error, dev sde, sector 8
end_request: I/O error, dev sde, sector 35484528
end_request: I/O error, dev sde, sector 35484528
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484480
end_request: I/O error, dev sde, sector 35484480
end_request: I/O error, dev sde, sector 35484288
end_request: I/O error, dev sde, sector 35484288
end_request: I/O error, dev sde, sector 35484288
end_request: I/O error, dev sde, sector 35484288
end_request: I/O error, dev sde, sector 35484528
end_request: I/O error, dev sde, sector 35484528
end_request: I/O error, dev sde, sector 35484144
end_request: I/O error, dev sde, sector 35484144
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sde, sector 35484536
end_request: I/O error, dev sdf, sector 8
end_request: I/O error, dev sdf, sector 8
end_request: I/O error, dev sdf, sector 35484528
end_request: I/O error, dev sdf, sector 35484528
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484480
end_request: I/O error, dev sdf, sector 35484480
end_request: I/O error, dev sdf, sector 35484288
end_request: I/O error, dev sdf, sector 35484288
end_request: I/O error, dev sdf, sector 35484288
end_request: I/O error, dev sdf, sector 35484288
end_request: I/O error, dev sdf, sector 35484528
end_request: I/O error, dev sdf, sector 35484528
end_request: I/O error, dev sdf, sector 35484144
end_request: I/O error, dev sdf, sector 35484144
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdf, sector 35484536
end_request: I/O error, dev sdg, sector 8
end_request: I/O error, dev sdg, sector 8
end_request: I/O error, dev sdg, sector 35484528
end_request: I/O error, dev sdg, sector 35484528
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484480
end_request: I/O error, dev sdg, sector 35484480
end_request: I/O error, dev sdg, sector 35484288
end_request: I/O error, dev sdg, sector 35484288
end_request: I/O error, dev sdg, sector 35484288
end_request: I/O error, dev sdg, sector 35484288
end_request: I/O error, dev sdg, sector 35484528
end_request: I/O error, dev sdg, sector 35484528
end_request: I/O error, dev sdg, sector 35484144
end_request: I/O error, dev sdg, sector 35484144
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdg, sector 35484536
end_request: I/O error, dev sdh, sector 8
end_request: I/O error, dev sdh, sector 8
end_request: I/O error, dev sdh, sector 35484528
end_request: I/O error, dev sdh, sector 35484528
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484480
end_request: I/O error, dev sdh, sector 35484480
end_request: I/O error, dev sdh, sector 35484288
end_request: I/O error, dev sdh, sector 35484288
end_request: I/O error, dev sdh, sector 35484288
end_request: I/O error, dev sdh, sector 35484288
end_request: I/O error, dev sdh, sector 35484528
end_request: I/O error, dev sdh, sector 35484528
end_request: I/O error, dev sdh, sector 35484144
end_request: I/O error, dev sdh, sector 35484144
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdh, sector 35484536
end_request: I/O error, dev sdi, sector 8
end_request: I/O error, dev sdi, sector 8
end_request: I/O error, dev sdi, sector 35484528
end_request: I/O error, dev sdi, sector 35484528
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484480
end_request: I/O error, dev sdi, sector 35484480
end_request: I/O error, dev sdi, sector 35484288
end_request: I/O error, dev sdi, sector 35484288
end_request: I/O error, dev sdi, sector 35484288
end_request: I/O error, dev sdi, sector 35484288
end_request: I/O error, dev sdi, sector 35484528
end_request: I/O error, dev sdi, sector 35484528
end_request: I/O error, dev sdi, sector 35484144
end_request: I/O error, dev sdi, sector 35484144
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdi, sector 35484536
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 35484416
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 35484416
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sde, sector 35484416
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 35484416
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 35484416
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 35484416
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 35484416
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdc, sector 35484416
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdd, sector 35484416
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sde, sector 35484416
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdf, sector 35484416
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdg, sector 35484416
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdh, sector 35484416
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdi, sector 35484416
end_request: I/O error, dev sdi, sector 0
end_request: I/O error, dev sdc, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sde, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdg, sector 0
end_request: I/O error, dev sdh, sector 0
end_request: I/O error, dev sdi, sector 0
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 2228216k swap on /dev/vol00/swap. Priority:-1 extents:1 across:2228216k
^ permalink raw reply
* Re: [ANNOUNCE] libata: new EH, NCQ, hotplug and PM patches against stable kernel
From: Chris Boot @ 2006-05-12 14:34 UTC (permalink / raw)
To: Tejun Heo, kernel list
In-Reply-To: <20060512132437.GB4219@htj.dyndns.org>
Tejun Heo wrote:
> Patches against v2.6.16.16 is avaialbe at the following URL.
>
> http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.16.16-20060512.tar.bz2
>
> Please read README carefully before testing the patches. Keep in mind
> that these are still quite experimental and not ready for production
> use.
Are these patches likely to work alongside Alan's PATA patches?
Specifically I have a DVD-RW and an IDE tape that I'd like to use.
Thanks,
Chris
--
Chris Boot
bootc@bootc.net
http://www.bootc.net/
^ permalink raw reply
* Re: Linux poll() <sigh> again
From: Robert Hancock @ 2006-05-12 14:32 UTC (permalink / raw)
To: linux-os (Dick Johnson); +Cc: linux-kernel
In-Reply-To: <Pine.LNX.4.61.0605120745050.8670@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
>> POLLHUP means "The device has been disconnected." This would obviously
>> be appropriate for a device such as a serial line or TTY, etc. but for a
>> socket it is less obvious that this return value is appropriate.
>>
>
> Hardly "less obvious". SunOs has returned POLLHUP as has other
> Unixes like Interactive, from which the software was ported. It
> went from Interactive, to SunOs, to Linux. Linux was the first
> OS that required the hack. This was reported several years ago
> and I was simply excoriated for having the audacity to report
> such a thing. So, I just implemented a hack. Now the hack is
> biting me. It's about time for poll() to return the correct
> stuff.
The standard doesn't require that a close on a socket should report
POLLHUP. Thus this behavior may differ between UNIX implementations. If
your software is requiring a POLLHUP to indicate the socket is closed I
think it is being unnecessarily picky since read returning 0 universally
indicates that the connection has been closed. Such are the compromises
that are sometimes required to write portable software.
>
>>> I have used the subsequent read() with a returned
>>> value of zero, to indicate that the client disconnected
>>> (as a work around). However, on recent versions of
>>> Linux, this is not reliable and the read() may
>>> wait forever instead of immediately returning.
>> If you want nonblocking behavior, you should set the socket to
>> nonblocking. This is a bit strange though, unless the data was stolen by
>> another thread or something. Are you sure you've seen this?
>
> I don't use threads. The hang under the specified conditions was first
> observed on 2.6.16.4 (that I'm running on this system). The hack, previously
> used, i.e., the read of zero was used since 2.4.x with success except it's
> a hack and shouldn't be required. It was not ever required on SunOs from
> which the software was ported.
This may be a bug somewhere.. however, once again if you don't want read
to block under any circumstances, set your sockets to non-blocking!
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
^ permalink raw reply
* Re: 3c59x vortex_timer rt hack (was: rt20 patch question)
From: Steven Rostedt @ 2006-05-12 14:32 UTC (permalink / raw)
To: Andrew Morton; +Cc: mingo, markh, linux-kernel, dwalker, tglx
In-Reply-To: <20060512071645.6b59e0a2.akpm@osdl.org>
On Fri, 12 May 2006, Andrew Morton wrote:
> >
> > Andrew,
> >
> > Do you know off hand what the side-effects to the vortex card might be
> > if we use disable_irq_nosync instead of disable_irq?
> >
>
> ooh, ow, sorry, that's lost in the mists of time. I don't know why we're
> doing disable_irq() in there.
>
> Whatever it does, I think you could take vp->lock instead - that'll stop
> the interrupt handler from doing anything if it does get entered while this
> CPU is running vortex_timer().
>
Thanks Andrew, I was thinking about using that lock too.
Mark, could you try this instead of the hack, and see if it works.
Thanks,
-- Steve
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Index: linux-2.6.16-rt20/drivers/net/3c59x.c
===================================================================
--- linux-2.6.16-rt20.orig/drivers/net/3c59x.c 2006-05-12 10:27:36.000000000 -0400
+++ linux-2.6.16-rt20/drivers/net/3c59x.c 2006-05-12 10:28:22.000000000 -0400
@@ -1897,7 +1897,7 @@ vortex_timer(unsigned long data)
if (vp->medialock)
goto leave_media_alone;
- disable_irq(dev->irq);
+ spin_lock_bh(&vp->lock);
old_window = ioread16(ioaddr + EL3_CMD) >> 13;
EL3WINDOW(4);
media_status = ioread16(ioaddr + Wn4_Media);
@@ -1919,7 +1919,6 @@ vortex_timer(unsigned long data)
break;
case XCVR_MII: case XCVR_NWAY:
{
- spin_lock_bh(&vp->lock);
mii_status = mdio_read(dev, vp->phys[0], MII_BMSR);
if (!(mii_status & BMSR_LSTATUS)) {
/* Re-read to get actual link status */
@@ -1957,7 +1956,6 @@ vortex_timer(unsigned long data)
} else {
netif_carrier_off(dev);
}
- spin_unlock_bh(&vp->lock);
}
break;
default: /* Other media types handled by Tx timeouts. */
@@ -2000,7 +1998,7 @@ vortex_timer(unsigned long data)
/* AKPM: FIXME: Should reset Rx & Tx here. P60 of 3c90xc.pdf */
}
EL3WINDOW(old_window);
- enable_irq(dev->irq);
+ spin_unlock_bh(&vp->lock);
leave_media_alone:
if (vortex_debug > 2)
^ permalink raw reply
* Re: Alubook 5,8: No sound with 2.6.17-rc3-g5528e568-dirty
From: Johannes Berg @ 2006-05-12 14:27 UTC (permalink / raw)
To: Wolfgang Pfeiffer; +Cc: linuxppc-dev list, debian-powerpc, Matthias Grimm
In-Reply-To: <20060512141918.GA3566@localhost>
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
On Fri, 2006-05-12 at 16:19 +0200, Wolfgang Pfeiffer wrote:
> [Oops, something's messed up there: this actually is a 1.67 Ghz
> processor. I'll have a look at this later .. :) ]
No, it's fine, it is clocked down at boot, use cpufreq.
> I filled /etc/modules with snd_aoa modules and i have sound already
> from boot time on ... with a minor glitch (i.e. not being able to
> store a certain volume level via alsactrl to the next reboot, as it
> seems), but sound ...
There are a bunch of userland bugs... Alsamixer cannot cope with the
3..28 of the capture volume, some gnome tools can't cope with the
negative scale of the playback volume, and others.
I don't want to workaround this, please all file bugs against the
respective programs.
amixer always seems to work fine.
> I have problems doing the same with pbbuttonsd. That is I can start,
> e.g., gtkppbuttons, but when pressing <FN>-<F5> or <FN>-<F4> it seems
> being impossible to change the sound volume this way. But I can toggle
> it completely ON/OFF with <FN>-<F3.> ... not being sure tho' whether
> this is due to some of my braindead mistakes or really a pbbuttonsd
> issue ...
No idea, I no longer use pbbuttonsd.
> Thanks again a lot to everyone for your work, your time, and the
> resulting fine software ... :)
:)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
^ permalink raw reply
* Re: [RFC][PATCH 1/3] tracking dirty pages in shared mappings -V4
From: Martin J. Bligh @ 2006-05-12 14:25 UTC (permalink / raw)
To: Andy Whitcroft
Cc: Andrew Morton, Linus Torvalds, clameter, a.p.zijlstra, piggin, ak,
rohitseth, hugh, riel, andrea, arjan, mel, marcelo, anton,
paulmck, linux-mm
In-Reply-To: <4464423D.50803@shadowen.org>
> Well for what its worth (and from this thread it may not be that much)
> the testing I did over night shows green across all the test boxes I
> have. The tests do include fsx-linux across a limited range of filesystems.
There's no perf regressions anywhere in there either (across dbench,
reaim, kernbench, tbench, at least) on a multitude of machines ...
M.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* Help: Linux porting to custom target hw
From: Jayanta Das @ 2006-05-12 14:23 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 31 bytes --]
Thiago - thanks for the help.
[-- Attachment #2: Type: text/html, Size: 347 bytes --]
^ permalink raw reply
* Re: Segfault on the i386 enter instruction
From: Denis Vlasenko @ 2006-05-12 14:20 UTC (permalink / raw)
To: linux-os (Dick Johnson); +Cc: Tomasz Malesinski, linux-kernel
In-Reply-To: <Pine.LNX.4.61.0605121003450.9012@chaos.analogic.com>
On Friday 12 May 2006 17:07, linux-os (Dick Johnson) wrote:
> > .file "a.c"
> > .version "01.01"
> > gcc2_compiled.:
> > .section .rodata
> > .LC0:
> > .string "asdf\n"
> > .text
> > .align 4
> > .globl main
> > .type main,@function
> > main:
> > enter $10008, $0
> > # pushl %ebp
> > # movl %esp,%ebp
> > # subl $10008,%esp
> > addl $-12,%esp
> ^^^^^^^^^^^^^^____________ WTF
> adding a negative number is subtracting that positive value.
> You just subtracted 0xfffffff3 (on a 32-bit machine) from
> the stack pointer. It damn-well better seg-fault!
No. Try it yourself.
--
vda
^ permalink raw reply
* Re: 3c59x vortex_timer rt hack (was: rt20 patch question)
From: Andrew Morton @ 2006-05-12 14:16 UTC (permalink / raw)
To: Steven Rostedt; +Cc: mingo, markh, linux-kernel, dwalker, tglx
In-Reply-To: <Pine.LNX.4.58.0605120904110.30264@gandalf.stny.rr.com>
Steven Rostedt <rostedt@goodmis.org> wrote:
>
>
>
> On Fri, 12 May 2006, Ingo Molnar wrote:
>
> > --- linux-rt.q.orig/drivers/net/3c59x.c
> > +++ linux-rt.q/drivers/net/3c59x.c
> > @@ -1897,7 +1897,8 @@ vortex_timer(unsigned long data)
> >
> > if (vp->medialock)
> > goto leave_media_alone;
> > - disable_irq(dev->irq);
> > + /* hack! */
> > + disable_irq_nosync(dev->irq);
> > old_window = ioread16(ioaddr + EL3_CMD) >> 13;
> > EL3WINDOW(4);
> > media_status = ioread16(ioaddr + Wn4_Media);
>
> BTW, I originally thought about having Mark do this, but I'm nervious
> about the side effects that this might have. Basically, it's doing
> ioreads from the device while the interrupt could be doing iowrites.
>
> I don't know the device well enough to know if this is a problem.
> I've added Andrew Morton to the CC list, since his name is all over the
> code.
>
> Andrew,
>
> Do you know off hand what the side-effects to the vortex card might be
> if we use disable_irq_nosync instead of disable_irq?
>
ooh, ow, sorry, that's lost in the mists of time. I don't know why we're
doing disable_irq() in there.
Whatever it does, I think you could take vp->lock instead - that'll stop
the interrupt handler from doing anything if it does get entered while this
CPU is running vortex_timer().
^ permalink raw reply
* Re: [PATCH 0/3] Zone boundry alignment fixes
From: Ingo Molnar @ 2006-05-12 14:19 UTC (permalink / raw)
To: Andrew Morton
Cc: Andy Whitcroft, nickpiggin, haveblue, bob.picco, mbligh, ak,
linux-kernel, linux-mm
In-Reply-To: <20060511005952.3d23897c.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> There's some possibility here of interaction with Mel's "patchset to
> size zones and memory holes in an architecture-independent manner." I
> jammed them together - let's see how it goes.
update: Andy's 3 patches, applied to 2.6.17-rc3-mm1, fixed all the
crashes and asserts i saw. NUMA-on-x86 is now rock-solid on my testbox.
Great work Andy!
Ingo
^ permalink raw reply
* Re: [PATCH 0/3] Zone boundry alignment fixes
From: Ingo Molnar @ 2006-05-12 14:19 UTC (permalink / raw)
To: Andrew Morton
Cc: Andy Whitcroft, nickpiggin, haveblue, bob.picco, mbligh, ak,
linux-kernel, linux-mm
In-Reply-To: <20060511005952.3d23897c.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> There's some possibility here of interaction with Mel's "patchset to
> size zones and memory holes in an architecture-independent manner." I
> jammed them together - let's see how it goes.
update: Andy's 3 patches, applied to 2.6.17-rc3-mm1, fixed all the
crashes and asserts i saw. NUMA-on-x86 is now rock-solid on my testbox.
Great work Andy!
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* Re: Want to hack a new feature into pcm/pcm_file.c
From: Juan Carlos Castro y Castro @ 2006-05-12 14:18 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
In-Reply-To: <s5hy7x7zkjd.wl%tiwai@suse.de>
Takashi Iwai wrote:
>At Thu, 11 May 2006 21:35:19 -0300,
>Juan Carlos Castro y Castro wrote:
>
>
>>I guess I'd have to change snd_pcm_file_readi() and snd_pcm_file_readn()
>>-- right now they write to a file, just like snd_pcm_file_writei() and
>>snd_pcm_file_writen(). Instead, they'd have to read data from a file and
>>return that. Subject, of course, to the existence of a new configuration
>>pareameter -- say, "filein".
>>
>>Makes sense?
>>
>>
>Actually, the current pcm_file.c already has read support.
>(Though, it might not work since I've not tested it yet :)
>
>
From what I understand from the source, in read mode the plugin is
supposed to always write the "real" (i.e. from the slave PCM) sound
input to the specified file, and then provide that input unchanged to
the app. Is that the intended purpose? What I want to do is a bit
different -- provide the contents of the existing file to the app
instead of what comes from the slave.
I think it's possible to keep the first behavior in the absence of a new
confuguration parameter. Let's call it "filein". You specify a file name
just like with "file". You know what -- I'm gonna hack it right now. Let
me see if you have a CVS or SVN repository...
(...) uh, what the netherworld is "HG (Mercurial) SCM"? (...) OK. Yet
Another CVS Alternative. (...) Ah, it exists in Fedora's extras. Got it.
Did the equivalent of "cvs checkout." Let's hack.
Would you happen to use any kind of instant messenger perchance? :)
Cheers,
Juan
>Takashi
>
>
>>Juan Carlos Castro y Castro wrote:
>>
>>
>>>Hello. I'd like very much to be able to specify an existing raw audio
>>>file and have it be a "virtual microphone", i.e. recording
>>>applications using this PCM would get the sound that's stored in that
>>>file. That's the exact opposite of the "virtual speakers" thing the
>>>file plugin does now.
>>>
>>>How hard would it be to do such a thing, and where should I begin
>>>studying? I am an experienced C programmer but know precious little
>>>about the ALSA architecture. If it's already possible to do the above
>>>with existing features, please don't beat me -- I asked around in
>>>alsa-user and got no answer, so I'm assuming hacking alsa-lib will be
>>>necessary.
>>>
>>>Cheers,
>>>Juan
>>>
>>>
>>>-------------------------------------------------------
>>>Using Tomcat but need to do more? Need to support web services, security?
>>>Get stuff done quickly with pre-integrated technology to make your job
>>>easier
>>>Download IBM WebSphere Application Server v.1.0.1 based on Apache
>>>Geronimo
>>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>>_______________________________________________
>>>Alsa-devel mailing list
>>>Alsa-devel@lists.sourceforge.net
>>>https://lists.sourceforge.net/lists/listinfo/alsa-devel
>>>
>>>
>>>
>>
>>-------------------------------------------------------
>>Using Tomcat but need to do more? Need to support web services, security?
>>Get stuff done quickly with pre-integrated technology to make your job easier
>>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>_______________________________________________
>>Alsa-devel mailing list
>>Alsa-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/alsa-devel
>>
>>
>>
>
>
>-------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>_______________________________________________
>Alsa-devel mailing list
>Alsa-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/alsa-devel
>
>
>
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
^ permalink raw reply
* Re: Alubook 5,8: No sound with 2.6.17-rc3-g5528e568-dirty
From: Wolfgang Pfeiffer @ 2006-05-12 14:19 UTC (permalink / raw)
To: Johannes Berg; +Cc: linuxppc-dev list, debian-powerpc, Matthias Grimm
In-Reply-To: <20060510213028.GG3878@localhost>
Hi All
First a fat Thanks to Johannes, Benh and to all of those heroes making
it possible to run a relatively freh PPC (Apple) Powerbook model with Linux ... :)
I'm cross-posting. So a short note for those who can't know what all this is about:
I didn't have sound with a fresh git kernel, on the machine mentioned above:
$ cat /proc/cpuinfo
processor : 0
cpu : 7447A, altivec supported
clock : 833.333000MHz
revision : 0.5 (pvr 8003 0105)
bogomips : 16.57
timebase : 8320000
platform : PowerMac
machine : PowerBook5,8
motherboard : PowerBook5,8 MacRISC3 Power Macintosh
detected as : 287 (PowerBook G4 15")
pmac flags : 00000019
L2 cache : 512K unified
pmac-generation : NewWorld
[Oops, something's messed up there: this actually is a 1.67 Ghz
processor. I'll have a look at this later .. :) ]
That's why I sent a message to linuxppc-dev@ozlabs.org. The thread is
starting here:
http://ozlabs.org/pipermail/linuxppc-dev/2006-May/022736.html
On Wed, May 10, 2006 at 11:30:28PM +0200, Wolfgang Pfeiffer wrote:
> On Wed, May 10, 2006 at 06:04:13PM +0200, Johannes Berg wrote:
>
> > Also, try snd-aoa.
>
> Impossible here, it does not compile here. Neither with gcc 4.0 or 4.1
Wrong. To put it mildly .. :) Result probably of me being too tired,
too fast, and too anal when reading instructions ...
# lsmod | grep -i aoa
snd_aoa_codec_onyx 12032 2
snd_aoa_fabric_layout 7492 2
snd_aoa 8076 2 snd_aoa_codec_onyx,snd_aoa_fabric_layout
soundbus 6628 2 snd_aoa_fabric_layout,i2sbus
snd 60148 12 snd_aoa_codec_onyx,snd_aoa_fabric_layout,
snd_aoa,snd_powermac,i2sbus,snd_pcm_oss,
snd_mixer_oss,snd_pcm,snd_timer
I successfully compiled the software now, and only with gcc-4.1. Example:
# modinfo snd_aoa
filename: /lib/modules/2.6.17-rc3-gf358166a-dirty/kernel/sound/aoa/snd-aoa.ko
description: Apple Onboard Audio Sound Driver
author: Johannes Berg <johannes@sipsolutions.net>
license: GPL
vermagic: 2.6.17-rc3-gf358166a-dirty mod_unload gcc-4.1
depends: snd
srcversion: D0DFD2EF0CFEB8E7C08AAEB
The git kernel I compiled the snd-aoa modules for (must be from about
yesterday, IINM):
cat /proc/version
Linux version 2.6.17-rc3-gf358166a-dirty (root@debby1-6) (gcc version
4.1.1 20060428 (prerelease) (Debian 4.1.0-2)) #1 Fri May 12 01:13:36
CEST 2006
config for this latest kernel (Please note the
"CONFIG_PREEMPT_VOLUNTARY=y" in there ... :) ... :
<http://wolfgangpfeiffer.com/config-2.6.17-rc3-gf358166a-dirty.txt>
I filled /etc/modules with snd_aoa modules and i have sound already
from boot time on ... with a minor glitch (i.e. not being able to
store a certain volume level via alsactrl to the next reboot, as it
seems), but sound ...
>
> I took your instructions from
> http://lists.debian.org/debian-powerpc/2006/03/msg00470.html
>
I'm listening to some Internet radio station via alsaplayer while
writing this mail ... :) ...
Results, as of now:
I can change the sound volume via the software. Tested in xine and
alsaplayer-gtk so far ...
I have problems doing the same with pbbuttonsd. That is I can start,
e.g., gtkppbuttons, but when pressing <FN>-<F5> or <FN>-<F4> it seems
being impossible to change the sound volume this way. But I can toggle
it completely ON/OFF with <FN>-<F3.> ... not being sure tho' whether
this is due to some of my braindead mistakes or really a pbbuttonsd
issue ...
Thanks again a lot to everyone for your work, your time, and the
resulting fine software ... :)
Nice weekend
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
^ permalink raw reply
* Re: Trouble with setexeccon/setcon
From: Stephen Smalley @ 2006-05-12 14:16 UTC (permalink / raw)
To: Mario Fanelli; +Cc: SeLinux Mailing List
In-Reply-To: <44649047.13bdcb9a.0dcb.4ef4@mx.gmail.com>
On Fri, 2006-05-12 at 15:40 +0200, Mario Fanelli wrote:
> Yes, but runcon and newrole are user-space command.
>
> I have to modify the SuPhp C source code because I want that the
> process SuPhp has different security context depending of an
> environment variable that mod_suphp set. I try to use setexecon in
> mod_suphp beforce executing SuPhp but the security context don’t
> change..setexeccon return -1…so I try to modify the suPhp exec with a
> calling to setcon but another setcon don’t work.
>
> If I use runcon all works, but I need to modify the source code…
Right, I meant to look at the runcon.c or newrole.c source code as
examples of how to use setexeccon() as well as how to create a context
in the first place from a combination of the caller's context and some
new type. What errno do you get after the failed setexeccon() call? In
addition to replacing object_r with a legitimate process role, you also
need to ensure that the role is authorized for the type/domain.
--
Stephen Smalley
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply
* Re: [PATCH 13/14] FS-Cache: Release page->private in failed readahead [try #8]
From: Andrew Morton @ 2006-05-12 14:11 UTC (permalink / raw)
To: David Howells
Cc: dhowells, torvalds, steved, trond.myklebust, aviro, linux-fsdevel,
linux-cachefs, nfsv4, linux-kernel
In-Reply-To: <11334.1147437245@warthog.cambridge.redhat.com>
David Howells <dhowells@redhat.com> wrote:
>
> Andrew Morton <akpm@osdl.org> wrote:
>
> > The above code is identical to the below code, so a new helper function
> > would be appropriate.
> > ...
> > I think the above will be called against an unlocked page, in which case
> > the ->releasepage() implementation might choose to go BUG, or something.
> > I suppose locking the page here will suffice.
>
> I'll move that bit of code into a helper function, along with the
> page_cache_release() and call it from both places. I'll also call
> try_to_release_page() as you suggest rather than going directly. I'll lock
> the page too:
>
> static inline void read_cache_pages_release_page(struct address_space *mapping,
> struct page *page)
> {
> if (PagePrivate(page)) {
> page->mapping = mapping;
> SetPageLocked(page);
if (TestSetPagLocked(page))
BUG();
would make me more comfortable..
> try_to_release_page(page, GFP_KERNEL);
> page->mapping = NULL;
> }
>
> page_cache_release(page);
> }
>
> > But it all seems a bit abusive of what ->releasepage() is supposed to do.
>
> Where else should I do it? I'm using releasepage() to break the association
> that the cache has made with a page. If I don't do this, the cache may wind
> up retaining metadata unnecessarily.
>
> I suppose I could add another address space op to do this, and have
> page_cache_release() check page->mapping->a_ops->destroypage(), and then force
> the mapping to be passed through to page_cache_release() where necessary.
>
> > add_to_page_cache() won't set PagePrivate() anyway, so what point is there
> > in the first hunk?
>
> The PagePrivate() bit is already set before read_cache_pages() is called.
> What happens is that the cache is invoked first: it sets to read any pages it
> can satisfy from the data it holds, and marks those pages for which it has
> allocated buffer space; the unsatisfied pages are then returned to NFS, which
> then calls read_cache_pages() to invoke readpage() serially - but if any pages
> get discarded, the cache metadata _also_ needs to be discarded.
>
> > For the second hunk, is it not possible to do this cleanup in the callback
> > function?
>
> Which callback function?
I was referring to the filler_t thingy. Is it not possible to get control
of that?
> The cleanup must be done before the page is returned
> to the page allocator, and since that is performed by read_cache_pages(), in
> read_cache_pages() the cleanup must be done. The other option is to not use
> read_cache_pages(), I suppose.
hm. There's a whole pile of stuff in this email which you're the only
person in the world who knows. But a lot of people need to be able to
read, understand and work upon mm/readahead.c without having to intimately
understand the internals of cachefs behaviour.
So please, can we have some comments in there which describe the new
behaviour in a manner sufficient for a maintainer to follow so people don't
break your stuff?
> > If read_cache_pages() needs this treatment, shouldn't we also do it in
> > read_pages()?
>
> Because read_pages() doesn't give the filesystem a chance to know about pages
> between it allocating them and it releasing them when add_to_page_cache()
> fails. Although it calls readpage(), if that fails it should clean up for
> itself.
>
> read_cache_pages() does not allocate the pages for itself. It's called from a
> filesystem's readpages() op, which gives the filesystem ample opportunity to
> know about the pages that read_pages() doesn't afford it.
>
> > And in mpage_readpages()?
>
> mpage_readpages() uses PG_private for its own purposes, and so keying on that
> for any purpose but holding buffers is impossible, and if mpage_readpages()
> needs to clean those up, it must do so already.
OK.
> However, you've raised a good point, and it's one that'll need to be solved if
> I want to do caching on ISOFS and suchlike.
>
> > Again, as this appears to be some special treatment for cachefs wouldn't it
> > be better to keep this special handling within cachefs?
>
> How? CacheFS can't practically monitor the pages it has been told about just
> in case they've been given back. The netfs has to drive that end of things.
>
> I could copy read_cache_pages() and place that in fscache and change it
> thusly, but there's no requirement that a netfs should use PG_private for
> marking cached pages - that just happens to be the way I've done it in NFS and
> AFS, but it can't be the way I do it in ISOFS.
>
> Out of interest, why do we need PG_private to say there's something in
> page->private? Can't it just be assumed either that if page->private is
> non-zero or that if a_ops->releasepage() is non-NULL, then we need to
> "release" the page?
page->private is an unsigned long, not a pointer. The core kernel hence
cannot determine from its value whether or not it is live. For example, the fs
might choose to treat it as a bitmap of which-blocks-are-uptodate and
which-blocks-are-dirty.
^ permalink raw reply
* [ALSA - lib 0002114]: Unnable to conect with sound server. Crash signal 6 SIGSEGV. No sounds in sistem!
From: bugtrack @ 2006-05-12 14:13 UTC (permalink / raw)
To: alsa-devel
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2114>
======================================================================
Reported By: caroldaza
Assigned To: tiwai
======================================================================
Project: ALSA - lib
Issue ID: 2114
Category: 0_general
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 05-11-2006 21:56 CEST
Last Modified: 05-12-2006 16:13 CEST
======================================================================
Summary: Unnable to conect with sound server. Crash signal 6
SIGSEGV. No sounds in sistem!
Description:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 5886)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#41 0x407b0ef1 in kill () from /lib/libc.so.6
#42 0x40648bb1 in pthread_kill () from /lib/libpthread.so.0
#43 0x40648f2b in raise () from /lib/libpthread.so.0
#44 0x407b0b24 in raise () from /lib/libc.so.6
#45 0x407b23fd in abort () from /lib/libc.so.6
#46 0x407aa00f in __assert_fail () from /lib/libc.so.6
#47 0x40333cd4 in snd_pcm_close () from /usr/lib/./libasound.so.2
#48 0x4014fa02 in Arts::AudioIOALSA::open ()
from /opt/kde/lib/libartsflow.so.1
#49 0x4012aef8 in Arts::AudioSubSystem::open ()
from /opt/kde/lib/libartsflow.so.1
#50 0x4012ad92 in Arts::AudioSubSystem::check ()
from /opt/kde/lib/libartsflow.so.1
#51 0x08062980 in Arts::SoundServer_skel::~SoundServer_skel ()
#52 0x4079d469 in __libc_start_main () from /lib/libc.so.6
#53 0x08053dd1 in ?? ()
======================================================================
----------------------------------------------------------------------
tiwai - 05-12-06 16:13
----------------------------------------------------------------------
A known problem of arts. Should be fixed with the latest version of
alsa-lib and arts.
Issue History
Date Modified Username Field Change
======================================================================
05-11-06 21:56 caroldaza New Issue
05-12-06 16:13 tiwai Status new => resolved
05-12-06 16:13 tiwai Resolution open => fixed
05-12-06 16:13 tiwai Assigned To => tiwai
05-12-06 16:13 tiwai Note Added: 0009780
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
^ permalink raw reply
* [ALSA - driver 0002115]: No Sound, No Error Message, Unmuted
From: bugtrack @ 2006-05-12 14:12 UTC (permalink / raw)
To: alsa-devel
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2115>
======================================================================
Reported By: bthomas
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 2115
Category: PCI - hda-intel
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Distribution: Debian/GNU Linux (Sarge) 3.1r2
Kernel Version: 2.6.16.13 or 2.6.16.15 or 2.6.15.7
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 05-11-2006 23:12 CEST
Last Modified: 05-12-2006 16:12 CEST
======================================================================
Summary: No Sound, No Error Message, Unmuted
Description:
No application is able to produce any sound on Dell Inspiron 9400 using
Debian GNU Linux (Sarge) 3.1r2 with Kernel 2.6.16.15 (or 2.6.16.13 or
2.6.15.7). Alsa drivers have been build into the kernel. Listed below is
some of the relevant information (Do let me know if anything else is
required).
lspci :
--------
0000:00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 01)
cat /proc/asound/cards :
-------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xdfffc000 irq 20
cat /proc/asound/oss/sndstat :
-------------------------------
Sound Driver:3.8.1a-980706 (ALSA v1.0.11rc2 emulation code)
Kernel: Linux darwin 2.6.16.13 #1 SMP PREEMPT Sat May 6 00:52:39 EDT 2006
i686
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
HDA Intel at 0xdfffc000 irq 20
Audio devices:
0: STAC92xx Analog (DUPLEX)
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers:
7: system timer
Mixers:
0: SigmaTel STAC9200
dmesg :
--------
ALSA device list:
#0: HDA Intel at 0xdfffc000 irq 20
Kernel Config (cat .config | grep SND) :
-----------------------------------------
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_AC97_CODEC=y
CONFIG_SND_AC97_BUS=y
CONFIG_SND_HDA_INTEL=y
CONFIG_SND_INTEL8X0=y
CONFIG_SND_INTEL8X0M=m
I have tried playing around with alsamixer but it was of no help. I can
confirm that it is not muted. I did try muting IEC958 too. It may be
pertinent that I have built the alsa drivers into the kernel and not as a
module.
======================================================================
----------------------------------------------------------------------
tiwai - 05-12-06 16:12
----------------------------------------------------------------------
Already fixed in 2.6.17rc4 kernel.
Issue History
Date Modified Username Field Change
======================================================================
05-11-06 23:12 bthomas New Issue
05-11-06 23:12 bthomas Distribution => Debian/GNU Linux
(Sarge) 3.1r2
05-11-06 23:12 bthomas Kernel Version => 2.6.16.13 or
2.6.16.15 or 2.6.15.7
05-12-06 16:12 tiwai Status assigned => resolved
05-12-06 16:12 tiwai Resolution open => fixed
05-12-06 16:12 tiwai Note Added: 0009779
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
^ permalink raw reply
* [ALSA - driver 0002106]: Sound card snd-hda-intel emits NO sound
From: bugtrack @ 2006-05-12 14:11 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2106>
======================================================================
Reported By: louisvd
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 2106
Category: PCI - hda-intel
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Fedora Core 5
Kernel Version: 2.6.16-1.2111_FC5smp
======================================================================
Date Submitted: 05-08-2006 21:00 CEST
Last Modified: 05-12-2006 16:11 CEST
======================================================================
Summary: Sound card snd-hda-intel emits NO sound
Description:
Hi
I was merrily running Fedora Core 4 and after upgrading the kernel to
2.6.16 my sound no longer worked under Linux (it works under Windows).
After a lot of battling I figured I may as well upgrade to FC5 now. A
clean install, out of the box, and the sound STILL did not work. I've
applied every available patch to date and no luck. Tonight I installed
the Alsa 1.0.11 driver, lib and util tarballs -- all installed
successfully -- but there is STILL no sound produced.
Everything LOOKS normal. There are no errors that I can detect. In the X
and console versions of Alsamixer I have ALL the devices displayed and
unmuted with the volumes at max. I've removed the sound lines from
modprobe.conf and am running with alsasound and that didn't help either --
even though it says the driver has been loaded.
FYI, the OSS Volume control calls it a Realtek ALC260. lspci refers to it
as Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller
(rev 01).
Please help.
======================================================================
----------------------------------------------------------------------
louisvd - 05-12-06 00:40
----------------------------------------------------------------------
I see from below that the model is set to NULL and enable is set to N.
1. How do I make alsasound script set the model=auto?
2. Should enable=N? How do I make it set to Y?
3. I get no errors. The OS thinks the card had loaded. However,
regardless of where the volume controls are, no sound plays.
[root@vandyl init.d]# ls -l /sys/module/snd_hda_intel/parameters/
total 0
-r--r--r-- 1 root root 4096 May 12 00:37 enable
-r--r--r-- 1 root root 4096 May 12 00:37 id
-r--r--r-- 1 root root 4096 May 12 00:37 index
-r--r--r-- 1 root root 4096 May 12 00:36 model
-r--r--r-- 1 root root 4096 May 12 00:37 position_fix
-r--r--r-- 1 root root 4096 May 12 00:37 probe_mask
-r--r--r-- 1 root root 4096 May 12 00:37 single_cmd
[root@vandyl init.d]# cat /sys/module/snd_hda_intel/parameters/enable
N
[root@vandyl init.d]# cat /sys/module/snd_hda_intel/parameters/id
<NULL>
[root@vandyl init.d]# cat /sys/module/snd_hda_intel/parameters/index
-1
[root@vandyl init.d]# cat /sys/module/snd_hda_intel/parameters/model
<NULL>
[root@vandyl init.d]# cat
/sys/module/snd_hda_intel/parameters/position_fix
0
[root@vandyl init.d]# cat /sys/module/snd_hda_intel/parameters/probe_mask
-1
[root@vandyl init.d]# cat /sys/module/snd_hda_intel/parameters/single_cmd
N
----------------------------------------------------------------------
tiwai - 05-12-06 16:11
----------------------------------------------------------------------
It's not alsasound script but somewhere else to set up the module option.
Usually /etc/modprobe.d/* or /etc/modprobe.conf* file.
The enable option is a place holder for snd-hda-intel driver just for
compatibility. It's anyway ignored.
Issue History
Date Modified Username Field Change
======================================================================
05-08-06 21:00 louisvd New Issue
05-08-06 21:00 louisvd Distribution => Fedora Core 5
05-08-06 21:00 louisvd Kernel Version => 2.6.16-1.2111_FC5smp
05-10-06 16:16 tiwai Note Added: 0009722
05-10-06 16:52 louisvd Note Added: 0009731
05-10-06 16:55 tiwai Note Added: 0009732
05-10-06 20:02 louisvd Note Added: 0009751
05-12-06 00:40 louisvd Note Added: 0009770
05-12-06 10:31 UMMO Issue Monitored: UMMO
05-12-06 16:11 tiwai Note Added: 0009778
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
^ permalink raw reply
* Re: [Xenomai-core] Re: [BUG] kernel oops on registry duplicate names
From: Philippe Gerum @ 2006-05-12 14:10 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai-core
In-Reply-To: <44646CB9.9070906@domain.hid>
Jan Kiszka wrote:
> Philippe Gerum wrote:
>
>>Ignacio García Pérez wrote:
>>
>>>The subject pretty much explains it all.
>>>
>>>Just try to create a task named "foo" and a queue also named "foo".
>>>
>>>Tested in 2.1.1 and svn HEAD.
>>>
>>
>>Ok, that's the other way around, you first create the queue, then the
>>task, and the error path of the task creation routine seems to go wild
>>afterwards when it detects the registry error.
>>
>
>
> That's obviously the same issue I reported a few days ago about creating
> two tasks with identical names.
>
Fixed by commits #1084 and #1085 in both branches.
--
Philippe.
^ permalink raw reply
* Re: Symbios-NCR 6285-3621 + Adaptec 2944W multilun problem
From: James Bottomley @ 2006-05-12 14:09 UTC (permalink / raw)
To: Gabriel Gomiz; +Cc: linux-scsi
In-Reply-To: <44648D9C.2090602@cooperativaobrera.com.ar>
On Fri, 2006-05-12 at 10:29 -0300, Gabriel Gomiz wrote:
> When configuring 2.6.16.13 kernel scsi subsystem with multilun
> support,
> I'm trying to access a Symbios 6285-3621 Array via an Adaptec 2944W
> HBA
> with aic7xxx module. All scsi "virtual devices" are recognized
> sdc-sdd-sde-sdf-sdg-sdh-sdi but then when the kernel tries to detect
> the
> partition tables it gets a lot of "Buffer I/O errors".
Could we get the dmesg output, both of the devices being detected, and
when the I/O errors occur, please?
James
^ permalink raw reply
* Re: Fw: [Qemu-devel] MIPS: UART access w/o -kernel option
From: Alexander Voropay @ 2006-05-12 14:08 UTC (permalink / raw)
To: Fabrice Bellard; +Cc: qemu-devel
In-Reply-To: <4463A949.9080401@bellard.org>
"Fabrice Bellard" <fabrice@bellard.org> wrote:
> I just commited a fix.
>>> Qemu/MIPS does not initialize an ISA memory region when issued
>>> without -kernel option. (I've added some debug output).
Thank you! The new version runs 'mmon' as BIOS successfully.
If someone has an intersest, it is possible to download this port there:
http://www.nwpi.ru/~alec/mips/mmon-qemu-0.5.tgz
This mmon has too weak functionality to be a complete BIOS
so I will try to port a classic PMON or YAMON to the Qemu.
I'm thinking about adding a new MIPS platform to the Qemu:
http://www.linux-mips.org/wiki/Mips_Malta
The Malta is very popular reference platform for the MIPS development.
There is a special Linux MIPS/Malta kernel. Montavista and many
other companies are offering a MIPS Malta distributives with
pre-compiled kernels. There is a NetBSD port to the Malta.
VxWorks/Malta exists, e.t.c.
The Malta architecture is very similar to the current Qemu MIPS
machine but the ISA addresses are different. Additionally, it
has a PCI subsystem, so it should be possible to use existent
Qemu PCI devices in the future. Malta has an standart PC ISA
devices (inside the PIIX4 chip). The Qemu contains all necessary
parts to introduce a new platform (except Galileo PCI).
Fabrice, is it difficult to add a new MIPS Malta platform
to the MIPS Qemu ? Could you add at least a framework
for this platform (CLI options, initial .c files) ?
P.S.The MIPS BIOS/kernel donload code should be reusable
for the any MIPS platforms.
--
-=AV=-
^ permalink raw reply
* Re: Segfault on the i386 enter instruction
From: linux-os (Dick Johnson) @ 2006-05-12 14:07 UTC (permalink / raw)
To: Tomasz Malesinski; +Cc: linux-kernel
In-Reply-To: <20060512131654.GB2994@duch.mimuw.edu.pl>
On Fri, 12 May 2006, Tomasz Malesinski wrote:
> The code attached below segfaults on the enter instruction. It works
> when a stack frame is created by the three commented out
> instructions and also when the first operand of the enter instruction
> is small (less than about 6500 on my system).
>
> AFAIK, the only difference between creating a stack frame with the
> enter instruction or push/mov/sub is that enter checks if the new
> value of esp is inside the stack segment limit.
>
> I tested it on a vanilla kernel 2.4.26 on Intel Celeron and also on
> probably non-vanilla 2.6.16.13 running on 3 dual core AMD Opteron,
> quite busy, server. It is working in 32-bit mode. Interestingly, on
> the second machine sometimes the program worked correctly.
>
> I am not subscribed to the list. Please cc replies to me.
>
>
> .file "a.c"
> .version "01.01"
> gcc2_compiled.:
> .section .rodata
> .LC0:
> .string "asdf\n"
> .text
> .align 4
> .globl main
> .type main,@function
> main:
> enter $10008, $0
> # pushl %ebp
> # movl %esp,%ebp
> # subl $10008,%esp
> addl $-12,%esp
^^^^^^^^^^^^^^____________ WTF
adding a negative number is subtracting that positive value.
You just subtracted 0xfffffff3 (on a 32-bit machine) from
the stack pointer. It damn-well better seg-fault!
> pushl $.LC0
> call printf
> addl $16,%esp
> .L2:
> leave
> ret
> .Lfe1:
> .size main,.Lfe1-main
> .ident "GCC: (GNU) 2.95.4 20011002 (Debian prerelease)"
>
> --
> Tomek Malesinski
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.4 on an i686 machine (5592.89 BogoMips).
New book: http://www.lymanschool.com
_
\x1a\x04
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.