Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
On 03/13/13 10:15, Thomas Meyer wrote:
Hi,
-*- Early printk
help text says:
You should normally N here, unless you want to debug such a crash.
(Depends on: EXPERT [=n])
How to normally N here?
You'll have
Hi,
-*- Early printk
help text says:
"You should normally N here, unless you want to debug such a crash.
(Depends on: EXPERT [=n])"
How to normally N here?
kind regards
thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi,
-*- Early printk
help text says:
You should normally N here, unless you want to debug such a crash.
(Depends on: EXPERT [=n])
How to normally N here?
kind regards
thomas
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Hi,
in include/linux/lockdep.h:
#define LOCK_CONTENDED(_lock, try, lock) \
lock(_lock)
Where is this lock() function defined?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
[25693.253108] [ cut here ]
[25693.253117] WARNING: at drivers/tty/tty_buffer.c:428
flush_to_ldisc+0x162/0x170()
[25693.253118] Hardware name: Aspire 1810T
[25693.253119] tty is NULL
[25693.253148] Modules linked in: fuse ip6t_REJECT nf_conntrack_ipv6
nf_defrag_ipv6
[25693.253108] [ cut here ]
[25693.253117] WARNING: at drivers/tty/tty_buffer.c:428
flush_to_ldisc+0x162/0x170()
[25693.253118] Hardware name: Aspire 1810T
[25693.253119] tty is NULL
[25693.253148] Modules linked in: fuse ip6t_REJECT nf_conntrack_ipv6
nf_defrag_ipv6
Hi,
in include/linux/lockdep.h:
#define LOCK_CONTENDED(_lock, try, lock) \
lock(_lock)
Where is this lock() function defined?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Am Freitag, den 08.03.2013, 21:19 -0500 schrieb Alan Stern:
> On Fri, 8 Mar 2013, Peter Hurley wrote:
>
> > [ +linux-usb ]
> >
> > On Fri, 2013-03-08 at 14:12 -0500, Shawn Starr wrote:
> > > Hello folks,
> > >
> > > I am noticing since rc0 and now rc1, very poor interrupt handling.
> > >
Am Freitag, den 08.03.2013, 21:19 -0500 schrieb Alan Stern:
On Fri, 8 Mar 2013, Peter Hurley wrote:
[ +linux-usb ]
On Fri, 2013-03-08 at 14:12 -0500, Shawn Starr wrote:
Hello folks,
I am noticing since rc0 and now rc1, very poor interrupt handling.
Keyboard response, mouse
[1.883369] input: C-Media Electronics Inc. USB Multimedia Audio Device as
/devices/pci:00/:00:1d.7/usb2/2-1/2-1.2/2-1.2:1.3/input/input7
[1.883668] hid-generic 0003:0D8C:0105.0001: input,hidraw0: USB HID v1.00
Device [C-Media Electronics Inc. USB Multimedia Audio Device] on
[1.883369] input: C-Media Electronics Inc. USB Multimedia Audio Device as
/devices/pci:00/:00:1d.7/usb2/2-1/2-1.2/2-1.2:1.3/input/input7
[1.883668] hid-generic 0003:0D8C:0105.0001: input,hidraw0: USB HID v1.00
Device [C-Media Electronics Inc. USB Multimedia Audio Device] on
Hi,
ERROR: "read_current_timer" [drivers/gpu/drm/udl/udl.ko] undefined!
ERROR: "read_current_timer" [crypto/tcrypt.ko] undefined!
"read_current_timer() is not an exported symbol so you cannot use it
from modules. This is most likely an error in the Kconfig entries for
those modules. They
Hi,
ERROR: read_current_timer [drivers/gpu/drm/udl/udl.ko] undefined!
ERROR: read_current_timer [crypto/tcrypt.ko] undefined!
read_current_timer() is not an exported symbol so you cannot use it
from modules. This is most likely an error in the Kconfig entries for
those modules. They shouldn't be
Am Sonntag, den 12.08.2012, 14:22 -0700 schrieb Bernie Thompson:
> On Sun, Aug 12, 2012 at 3:34 AM, Thomas Meyer wrote:
> guilty driver is probably udl_fb.c
> any ideas?
>
>
> Hi Thomas,
Hi Bernie!
> We were seeing similar issues in udlfb (the o
Am Sonntag, den 12.08.2012, 14:22 -0700 schrieb Bernie Thompson:
On Sun, Aug 12, 2012 at 3:34 AM, Thomas Meyer tho...@m3y3r.de wrote:
guilty driver is probably udl_fb.c
any ideas?
Hi Thomas,
Hi Bernie!
We were seeing similar issues in udlfb (the original fbdev version
Hi,
guilty driver is probably udl_fb.c
any ideas?
[ 42.890551] open /dev/fb1 user=1 fb_info=880130e0a800 count=1
[ 42.890585] released /dev/fb1 user=1 count=0
[ 42.890702] open /dev/fb1 user=1 fb_info=880130e0a800 count=1
[ 43.053034] type=1400 audit(1344698343.496:9): avc:
Hi,
guilty driver is probably udl_fb.c
any ideas?
[ 42.890551] open /dev/fb1 user=1 fb_info=880130e0a800 count=1
[ 42.890585] released /dev/fb1 user=1 count=0
[ 42.890702] open /dev/fb1 user=1 fb_info=880130e0a800 count=1
[ 43.053034] type=1400 audit(1344698343.496:9): avc:
The semantic patch that makes this change is available
in scripts/coccinelle/api/err_cast.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/gpu/drm/nouveau/nouveau_prime.c
b/drivers/gpu/drm/nouveau
The semantic patch that makes this change is available
in scripts/coccinelle/api/err_cast.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/gpu/drm/exynos/exynos_drm_gem.c
b/drivers/gpu/drm/exynos
The semantic patch that makes this change is available
in scripts/coccinelle/api/err_cast.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/gpu/drm/udl/udl_gem.c b/drivers/gpu/drm/udl/udl_gem.c
The semantic patch that makes this change is available
in scripts/coccinelle/api/err_cast.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/drivers/gpu/drm/udl/udl_gem.c b/drivers/gpu/drm/udl
The semantic patch that makes this change is available
in scripts/coccinelle/api/err_cast.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/drivers/gpu/drm/exynos/exynos_drm_gem.c
b/drivers
The semantic patch that makes this change is available
in scripts/coccinelle/api/err_cast.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/drivers/gpu/drm/nouveau/nouveau_prime.c
b/drivers
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/arch/m68k/amiga/platform.c b/arch/m68k/amiga/platform.c
--- a/arch
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
--- a/fs/btrfs/volumes.c
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/spi/spi-fsl-spi.c b/drivers/spi/spi-fsl-spi.c
--- a/drivers
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/scsi/libsas/sas_scsi_host.c
b/drivers/scsi/libsas
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/net/appletalk/cops.c b/drivers/net/appletalk/cops.c
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/arch/m68k/q40/config.c b/arch/m68k/q40/config.c
--- a/arch/m68k/q40
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/arch/m68k/kernel/time.c b/arch/m68k/kernel/time.c
--- a/arch/m68k
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/drivers/net/ethernet/amd/atarilance.c
b/drivers/net/ethernet/amd
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/sound/soc/soc-io.c b/sound/soc/soc-io.c
--- a/sound/soc/soc-io.c
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer
---
diff -u -p a/arch/arm/mach-imx/mach-mx31moboard.c
b/arch/arm/mach-imx/mach
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/arch/arm/mach-imx/mach-mx31moboard.c
b/arch/arm/mach
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/sound/soc/soc-io.c b/sound/soc/soc-io.c
--- a/sound
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/drivers/net/ethernet/amd/atarilance.c
b/drivers/net
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/arch/m68k/kernel/time.c b/arch/m68k/kernel/time.c
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/arch/m68k/q40/config.c b/arch/m68k/q40/config.c
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/drivers/net/appletalk/cops.c b/drivers/net/appletalk
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/drivers/scsi/libsas/sas_scsi_host.c
b/drivers/scsi
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/drivers/spi/spi-fsl-spi.c b/drivers/spi/spi-fsl-spi.c
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
--- a/fs/btrfs
The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.
More information about semantic patching is available at
http://coccinelle.lip6.fr/
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/arch/m68k/amiga/platform.c b/arch/m68k/amiga
Stefan Richter schrieb:
My conclusion so far: There is something wrong with your system which
is below/ before the control of the ieee1394 or firewire stack.
Yes. I agree with you. So i did a "make clean" and a "make" (not a make
-j3 as i use to do) and recompiled 2.6.25-rc3 and now it works
Stefan Richter schrieb:
My conclusion so far: There is something wrong with your system which
is below/ before the control of the ieee1394 or firewire stack.
Yes. I agree with you. So i did a make clean and a make (not a make
-j3 as i use to do) and recompiled 2.6.25-rc3 and now it works
Stefan Richter schrieb:
I wrote:
Thomas Meyer wrote at LKML:
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
There are junk interrupt events sent to ohci1394's IRQ handler.
PS, do you still have th
Stefan Richter schrieb:
I wrote:
Thomas Meyer wrote at LKML:
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
There are junk interrupt events sent to ohci1394's IRQ handler.
PS, do you still have the log
Stefan Richter schrieb:
Thomas Meyer wrote at LKML:
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
ohc
Stefan Richter schrieb:
Thomas Meyer wrote at LKML:
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
ohci1394
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
ohci1394: fw-host0: Iso Recv 3 Context died: ctrl[d4000d0e]
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
ohci1394: fw-host0: Iso Recv 3 Context died: ctrl[d4000d0e]
H. Peter Anvin schrieb:
Thomas Meyer wrote:
H. Peter Anvin schrieb:
Thomas Meyer wrote:
I can not revert the commit
e429795c68d3001ecae74f6465420c9f043b0ece. it gave me errors.
but i'm also not sure what could be wrong with this commit!
my first idea was that the commit
H. Peter Anvin schrieb:
Thomas Meyer wrote:
H. Peter Anvin schrieb:
Thomas Meyer wrote:
I can not revert the commit
e429795c68d3001ecae74f6465420c9f043b0ece. it gave me errors.
but i'm also not sure what could be wrong with this commit!
my first idea was that the commit
H. Peter Anvin schrieb:
Thomas Meyer wrote:
I can not revert the commit e429795c68d3001ecae74f6465420c9f043b0ece.
it gave me errors.
but i'm also not sure what could be wrong with this commit!
my first idea was that the commit
"[2215e69d2cf5024647f9a034807990590d25dd4e] x86 boot: use
H. Peter Anvin schrieb:
[EMAIL PROTECTED] wrote:
The latest linux kernel doesn't boot on my computer
(h=21511abd0a248a3f225d3b611cfabb93124605a7).
elilo hangs while booting this kernel. 2.6.24 works.
Wow, so we know it's affected with EFI, since you're using elilo.
You gave absolutely zero
H. Peter Anvin schrieb:
Thomas Meyer wrote:
I can not revert the commit e429795c68d3001ecae74f6465420c9f043b0ece.
it gave me errors.
but i'm also not sure what could be wrong with this commit!
my first idea was that the commit
[2215e69d2cf5024647f9a034807990590d25dd4e] x86 boot: use E820
Hi,
I confirm Peter's observations:
> To repeat:
>
> 1. Start with an empty drive.
> 2. pktsetup 0 /dev/scd0
> 3. Insert a CD containing an isofs filesystem.
> 4. mount /dev/pktcdvd/0 /mnt/tmp
> 5. umount /mnt/tmp
> 6. Press the eject button.
> 7. Insert a DVD containing a
Hi,
I confirm Peter's observations:
To repeat:
1. Start with an empty drive.
2. pktsetup 0 /dev/scd0
3. Insert a CD containing an isofs filesystem.
4. mount /dev/pktcdvd/0 /mnt/tmp
5. umount /mnt/tmp
6. Press the eject button.
7. Insert a DVD containing a non-writable
Hi,
is somebody actually working on this bug?
http://bugzilla.kernel.org/show_bug.cgi?id=9370
I don't want to be impolite, but it's now more than a month since the
bug was opened.
The bug still exists in v2.6.24-rc5-43-gda8cadb:
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660
Hi,
is somebody actually working on this bug?
http://bugzilla.kernel.org/show_bug.cgi?id=9370
I don't want to be impolite, but it's now more than a month since the
bug was opened.
The bug still exists in v2.6.24-rc5-43-gda8cadb:
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660
Kay Sievers schrieb:
> On Fri, 2007-11-02 at 18:03 +0100, Thomas Meyer wrote:
>
>> Kay Sievers schrieb:
>>
>>> On Mon, 2007-10-29 at 00:18 -0700, Andrew Morton wrote:
>>>
>>>
>>>> On Sun, 21 Oct 2
Kay Sievers schrieb:
On Fri, 2007-11-02 at 18:03 +0100, Thomas Meyer wrote:
Kay Sievers schrieb:
On Mon, 2007-10-29 at 00:18 -0700, Andrew Morton wrote:
On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer [EMAIL PROTECTED] wrote:
I have an external hard drive
Thomas Meyer schrieb:
> i get these errors in the kernel log while trying to copy a file from an
> iso9660 file system (/dev/sr0) to my intenal hard disk. This is the
> second cd/dvd that gives me this error. kernel 2.6.23 works without any
> problems, so i think this is not an
i get these errors in the kernel log while trying to copy a file from an
iso9660 file system (/dev/sr0) to my intenal hard disk. This is the
second cd/dvd that gives me this error. kernel 2.6.23 works without any
problems, so i think this is not an medium error:
ISO 9660 Extensions: Microsoft
i get these errors in the kernel log while trying to copy a file from an
iso9660 file system (/dev/sr0) to my intenal hard disk. This is the
second cd/dvd that gives me this error. kernel 2.6.23 works without any
problems, so i think this is not an medium error:
ISO 9660 Extensions: Microsoft
Thomas Meyer schrieb:
i get these errors in the kernel log while trying to copy a file from an
iso9660 file system (/dev/sr0) to my intenal hard disk. This is the
second cd/dvd that gives me this error. kernel 2.6.23 works without any
problems, so i think this is not an medium error:
ISO
Andrey Borzenkov schrieb:
> Thomas Meyer wrote:
>
>
>> i just wanted to report this:
>>
>> in v2.6.24-rc1-497-gb1d08ac the kde battery icon is no longer displayed.
>>
>> with 2.6.23 shows the battery icon.
>>
>> current config:
>>
>>
Andrey Borzenkov schrieb:
Thomas Meyer wrote:
i just wanted to report this:
in v2.6.24-rc1-497-gb1d08ac the kde battery icon is no longer displayed.
with 2.6.23 shows the battery icon.
current config:
grep -i acpi .config
# Power management options (ACPI, APM)
CONFIG_ACPI=y
i just wanted to report this:
in v2.6.24-rc1-497-gb1d08ac the kde battery icon is no longer displayed.
with 2.6.23 shows the battery icon.
current config:
grep -i acpi .config
# Power management options (ACPI, APM)
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS is not set
Kay Sievers schrieb:
> On Mon, 2007-10-29 at 00:18 -0700, Andrew Morton wrote:
>
>> On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer <[EMAIL PROTECTED]> wrote:
>>
>>> I have an external hard drive with an encrypted partition. I am using
>&g
i just wanted to report this:
in v2.6.24-rc1-497-gb1d08ac the kde battery icon is no longer displayed.
with 2.6.23 shows the battery icon.
current config:
grep -i acpi .config
# Power management options (ACPI, APM)
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS is not set
Kay Sievers schrieb:
On Mon, 2007-10-29 at 00:18 -0700, Andrew Morton wrote:
On Sun, 21 Oct 2007 21:23:21 +0200 Thomas Meyer [EMAIL PROTECTED] wrote:
I have an external hard drive with an encrypted partition. I am using
kde so all i had to do under 2.6.23 was
cryptsetup luksOpen
Thomas Meyer schrieb:
> Thomas Meyer schrieb:
>
>> i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
>> another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
>> stuck:
>>
>> PID: 0, comm: swapper
>> EIP is at
Thomas Meyer schrieb:
> i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
> another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
> stuck:
>
> PID: 0, comm: swapper
> EIP is at acpi_idle_enter_bm+0x258/0x2fa (processor)
>
> ->
i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
stuck:
PID: 0, comm: swapper
EIP is at acpi_idle_enter_bm+0x258/0x2fa (processor)
-> cpuidle_idle_call+0x5c/0x81
-> cpuidle_idle_call+0x0/0x81
->
Thomas Meyer schrieb:
> Oct 23 17:13:55 [kernel] usb 1-1: new high speed USB device using
> ehci_hcd and address 7
> Oct 23 17:13:55 [kernel] usb 1-1: configuration #1 chosen from 1 choice
> Oct 23 17:13:55 [kernel] hub 1-1:1.0: USB hub found
> Oct 23 17:13:55 [kernel] hub 1
Oct 23 17:13:55 [kernel] usb 1-1: new high speed USB device using
ehci_hcd and address 7
Oct 23 17:13:55 [kernel] usb 1-1: configuration #1 chosen from 1 choice
Oct 23 17:13:55 [kernel] hub 1-1:1.0: USB hub found
Oct 23 17:13:55 [kernel] hub 1-1:1.0: 4 ports detected
Oct 23 17:13:55 [kernel]
Oct 23 17:13:55 [kernel] usb 1-1: new high speed USB device using
ehci_hcd and address 7
Oct 23 17:13:55 [kernel] usb 1-1: configuration #1 chosen from 1 choice
Oct 23 17:13:55 [kernel] hub 1-1:1.0: USB hub found
Oct 23 17:13:55 [kernel] hub 1-1:1.0: 4 ports detected
Oct 23 17:13:55 [kernel]
Thomas Meyer schrieb:
Oct 23 17:13:55 [kernel] usb 1-1: new high speed USB device using
ehci_hcd and address 7
Oct 23 17:13:55 [kernel] usb 1-1: configuration #1 chosen from 1 choice
Oct 23 17:13:55 [kernel] hub 1-1:1.0: USB hub found
Oct 23 17:13:55 [kernel] hub 1-1:1.0: 4 ports detected
i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
stuck:
PID: 0, comm: swapper
EIP is at acpi_idle_enter_bm+0x258/0x2fa (processor)
- cpuidle_idle_call+0x5c/0x81
- cpuidle_idle_call+0x0/0x81
-
Thomas Meyer schrieb:
i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
stuck:
PID: 0, comm: swapper
EIP is at acpi_idle_enter_bm+0x258/0x2fa (processor)
- cpuidle_idle_call+0x5c/0x81
Thomas Meyer schrieb:
Thomas Meyer schrieb:
i try to kexec from 0895e91d60ef9bdef426d1ce14bb94bd5875870d into
another (older) commit kernel after 2.6.23 (bisect) and the kernel gets
stuck:
PID: 0, comm: swapper
EIP is at acpi_idle_enter_bm+0x258/0x2fa (processor)
- cpuidle_idle_call
Hi.
I have an external hard drive with an encrypted partition. I am using
kde so all i had to do under 2.6.23 was
"cryptsetup luksOpen /dev/sdb2 crypt-extern"
then udev/hal/kde (?)automatically created an desktop icon. i could
click this icon to mount and open the drive.
when i do the
Takashi Iwai schrieb:
>
> Both are handled as patch_stac925x. That's what I meant. With your
> patch, there will be no master any more.
>
> So, how about the patch below?
>
>
> Takashi
>
> diff -r fb9512ce24e0 pci/hda/patch_sigmatel.c
> --- a/pci/hda/patch_sigmatel.cThu Oct 18 10:48:43
Takashi Iwai schrieb:
Both are handled as patch_stac925x. That's what I meant. With your
patch, there will be no master any more.
So, how about the patch below?
Takashi
diff -r fb9512ce24e0 pci/hda/patch_sigmatel.c
--- a/pci/hda/patch_sigmatel.cThu Oct 18 10:48:43 2007 +0200
Hi.
I have an external hard drive with an encrypted partition. I am using
kde so all i had to do under 2.6.23 was
cryptsetup luksOpen /dev/sdb2 crypt-extern
then udev/hal/kde (?)automatically created an desktop icon. i could
click this icon to mount and open the drive.
when i do the luksOpen
Takashi Iwai schrieb:
> At Wed, 17 Oct 2007 00:18:42 +0200,
> Thomas Meyer wrote:
>
>> $ dmesg
>>
>> [schnipp]
>>
>> ACPI: PCI Interrupt :00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
>> PCI: Enabling bus mastering for device :00:1b.0
&
Takashi Iwai schrieb:
At Wed, 17 Oct 2007 00:18:42 +0200,
Thomas Meyer wrote:
$ dmesg
[schnipp]
ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) - IRQ 21
PCI: Enabling bus mastering for device :00:1b.0
PCI: Setting latency timer of device :00:1b.0 to 64
hda_codec
$ dmesg
[schnipp]
ACPI: PCI Interrupt :00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
PCI: Enabling bus mastering for device :00:1b.0
PCI: Setting latency timer of device :00:1b.0 to 64
hda_codec: STAC922x, Apple subsys_id=106b0200
ACPI: PCI interrupt for device :00:1b.0 disabled
Randy Dunlap schrieb:
> On Tue, 16 Oct 2007 21:51:13 +0200 Thomas Meyer wrote:
>
> [adding kexec mailing list]
>
>
>> Look at this:
>>
>> $ file arch/x86/boot/bzImage (tree 821f3eff7cdb9d6c7076effabd46c96c322daed1)
>> arch/x86/boot/bzImage: Linux ker
Hi.
Look at this:
$ file arch/x86/boot/bzImage (tree 821f3eff7cdb9d6c7076effabd46c96c322daed1)
arch/x86/boot/bzImage: Linux kernel x86 boot executable zImage, version
2.6.23 ([EMAIL PROTECTED]) #39, RO-rootFS, root_dev 0x803, swap_dev
0x1, Prompt for Videomode
$ file /boot/bzImage-2.6.23
Hi.
Look at this:
$ file arch/x86/boot/bzImage (tree 821f3eff7cdb9d6c7076effabd46c96c322daed1)
arch/x86/boot/bzImage: Linux kernel x86 boot executable zImage, version
2.6.23 ([EMAIL PROTECTED]) #39, RO-rootFS, root_dev 0x803, swap_dev
0x1, Prompt for Videomode
$ file /boot/bzImage-2.6.23
Randy Dunlap schrieb:
On Tue, 16 Oct 2007 21:51:13 +0200 Thomas Meyer wrote:
[adding kexec mailing list]
Look at this:
$ file arch/x86/boot/bzImage (tree 821f3eff7cdb9d6c7076effabd46c96c322daed1)
arch/x86/boot/bzImage: Linux kernel x86 boot executable zImage, version
2.6.23 ([EMAIL
$ dmesg
[schnipp]
ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) - IRQ 21
PCI: Enabling bus mastering for device :00:1b.0
PCI: Setting latency timer of device :00:1b.0 to 64
hda_codec: STAC922x, Apple subsys_id=106b0200
ACPI: PCI interrupt for device :00:1b.0 disabled
HDA
Andrew Morton schrieb:
> On Fri, 21 Sep 2007 10:24:34 +1000 Nigel Cunningham <[EMAIL PROTECTED]> wrote:
>
>
>> Hi Andrew.
>>
>> On Thursday 20 September 2007 20:09:41 Pavel Machek wrote:
>>
>>> Seems like good enough for -mm to me.
>>>
>>>
Andrew Morton schrieb:
On Fri, 21 Sep 2007 10:24:34 +1000 Nigel Cunningham [EMAIL PROTECTED] wrote:
Hi Andrew.
On Thursday 20 September 2007 20:09:41 Pavel Machek wrote:
Seems like good enough for -mm to me.
Takashi Iwai schrieb:
> At Wed, 29 Aug 2007 18:42:56 +0300,
> Ivan N. Zlatev wrote:
>
> ... but without the hardware :-<
>
> IMO, this is actually no real regression. In the earlier verison, you
> didn't have controls for multiple outputs, thus the mixer control was
> named as Master. Now you
Takashi Iwai schrieb:
At Wed, 29 Aug 2007 18:42:56 +0300,
Ivan N. Zlatev wrote:
... but without the hardware :-
IMO, this is actually no real regression. In the earlier verison, you
didn't have controls for multiple outputs, thus the mixer control was
named as Master. Now you do have
Ivan N. Zlatev schrieb:
> On 8/24/07, Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>
>> ALSA
>>
>> Subject : Master volume control broken
>> References : http://lkml.org/lkml/2007/8/18/46
>> Last known good : ?
>> Submitter
Ivan N. Zlatev schrieb:
On 8/24/07, Michal Piotrowski [EMAIL PROTECTED] wrote:
ALSA
Subject : Master volume control broken
References : http://lkml.org/lkml/2007/8/18/46
Last known good : ?
Submitter : Thomas Meyer [EMAIL PROTECTED]
Caused-By : Ivan N. Zlatev
501 - 600 of 698 matches
Mail list logo
