, 1, 20),
GROUP(i2s_out_ch23_y, 1, 5),
signed off Otto Meier gf...@gmx.net
Please find attached a fix for wrong uart_c pinning of odroid-c2
in mainline kernels
Regards
Otto
--- linux-next-20170623/drivers/pinctrl/meson/pinctrl-meson-gxbb.c.orig 2017-06-23 11:30:35.072037057 +0200
+++ linux-next-20170623/drivers/pinctrl/meson/pinctrl-meson-gxbb.c 2017-06-26
Please find attached a fix for wrong uart_c pinning of odroid-c2
in mainline kernels
Regards
Otto
--- linux-next-20170623/drivers/pinctrl/meson/pinctrl-meson-gxbb.c.orig 2017-06-23 11:30:35.072037057 +0200
+++ linux-next-20170623/drivers/pinctrl/meson/pinctrl-meson-gxbb.c 2017-06-26
I migrated my system from H77 Ivy-bridge to a haswell Platform
B85 i3-4330.
The system has three dvb-c usb receivers connected. On the Ivy
Platform everything runs fine with xHCI. On the haswell Platform
xHCI explodes with following messages:
2014-02-27T16:45:53.518332+01:00 vnas kernel: [
I migrated my system from H77 Ivy-bridge to a haswell Platform
B85 i3-4330.
The system has three dvb-c usb receivers connected. On the Ivy
Platform everything runs fine with xHCI. On the haswell Platform
xHCI explodes with following messages:
2014-02-27T16:45:53.518332+01:00 vnas kernel: [
On my i3-4330 this patch fixed the problem. works fine
Thanks
Am 26.02.2014 01:39, schrieb Rafael J. Wysocki:
> On Tuesday, February 25, 2014 10:35:37 AM dirk.brande...@gmail.com wrote:
>> From: Dirk Brandewie
>>
>> Commit fcb6a15c2e Take core C0 time into account for core busy calculation.
>>
On my i3-4330 this patch fixed the problem. works fine
Thanks
Am 26.02.2014 01:39, schrieb Rafael J. Wysocki:
On Tuesday, February 25, 2014 10:35:37 AM dirk.brande...@gmail.com wrote:
From: Dirk Brandewie dirk.j.brande...@intel.com
Commit fcb6a15c2e Take core C0 time into account for core
Am 20.02.2014 17:48, schrieb Dirk Brandewie:
> On 02/20/2014 07:01 AM, Borislav Petkov wrote:
>> Add lists to CC.
>>
>> On Thu, Feb 20, 2014 at 03:32:36PM +0100, Otto Meier wrote:
>>> Hello,
>>>
>>> My System which runs with older kernels
Hello,
My System which runs with older kernels up to 3.13.3
fine on my i3-4330 with 3.5 Ghz and governor powersave.
and pstate driver.
With kernel 3.14-rc3 and Governor powersave it runs
only at 770Mhz and never switches to higher Freq. on load.
Even compiling a kernel with make -j4 does not
Hello,
My System which runs with older kernels up to 3.13.3
fine on my i3-4330 with 3.5 Ghz and governor powersave.
and pstate driver.
With kernel 3.14-rc3 and Governor powersave it runs
only at 770Mhz and never switches to higher Freq. on load.
Even compiling a kernel with make -j4 does not
Am 20.02.2014 17:48, schrieb Dirk Brandewie:
On 02/20/2014 07:01 AM, Borislav Petkov wrote:
Add lists to CC.
On Thu, Feb 20, 2014 at 03:32:36PM +0100, Otto Meier wrote:
Hello,
My System which runs with older kernels up to 3.13.3
fine on my i3-4330 with 3.5 Ghz and governor powersave
I just changed MB for my Home Server from GA75N to H87-ITX.
Attached to this server I run 3 WINTV HVR 930C DVB-C usb receivers.
with the Series Seven MB everything works as it should. with the H87
MB the USB3 Stack crashed as soon as i get more then one Stream from
the DVB-C receivers.
the Error
I just changed MB for my Home Server from GA75N to H87-ITX.
Attached to this server I run 3 WINTV HVR 930C DVB-C usb receivers.
with the Series Seven MB everything works as it should. with the H87
MB the USB3 Stack crashed as soon as i get more then one Stream from
the DVB-C receivers.
the Error
Hello,
I got the following in my logs:
Jun 24 19:06:40 gate2 kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x0
Jun 24 19:06:40 gate2 kernel: ata4.00: (port_status 0x1000)
Jun 24 19:06:40 gate2 kernel: ata4.00: cmd
35/00:00:c1:17:92/00:04:17:00:00/e0 tag 0 cdb 0x0 data 524288
Hello,
I got the following in my logs:
Jun 24 19:06:40 gate2 kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x0
Jun 24 19:06:40 gate2 kernel: ata4.00: (port_status 0x1000)
Jun 24 19:06:40 gate2 kernel: ata4.00: cmd
35/00:00:c1:17:92/00:04:17:00:00/e0 tag 0 cdb 0x0 data 524288
Hi,
As of now there is only support for x86
arch of dyntick in 2.6.21. When will it be
available for x86_64?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
As of now there is only support for x86
arch of dyntick in 2.6.21. When will it be
available for x86_64?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hallo,
this Patch get the Promise SATA300 TX4 card working.
Please accept. Patch is against 2.6.13-rc3-git5.
Signed-off-by: Otto Meier <[EMAIL PROTECTED]>
--- linux/drivers/scsi/sata_promise.c.orig 2005-08-01
17:09:48.474824778 +0200
+++ linux/drivers/scsi/sata_promise.c 2005-07
Hallo,
this Patch get the Promise SATA300 TX4 card working.
Please accept. Patch is against 2.6.13-rc3-git5.
Signed-off-by: Otto Meier [EMAIL PROTECTED]
--- linux/drivers/scsi/sata_promise.c.orig 2005-08-01
17:09:48.474824778 +0200
+++ linux/drivers/scsi/sata_promise.c 2005-07-31 12
Jens Axboe wrote:
On Mon, Aug 01 2005, Jeff Garzik wrote:
Jens Axboe wrote:
On Mon, Aug 01 2005, Daniel Drake wrote:
Otto Meier wrote:
My question is also are these features (NCQ/TCQ) and the heigher
datarate be supported by this
modification? or is only the basic
Jens Axboe wrote:
On Mon, Aug 01 2005, Jeff Garzik wrote:
Jens Axboe wrote:
On Mon, Aug 01 2005, Daniel Drake wrote:
Otto Meier wrote:
My question is also are these features (NCQ/TCQ) and the heigher
datarate be supported by this
modification? or is only the basic
Daniel Drake wrote:
Otto Meier wrote:
This card use the sata chip pdc 40718 (as of my card)
the lastest sata_promise kernel with sata promise patch driver
doesn't recognise
this card.
I added the following line to static struct pci_device_id
pdc_ata_pci_tbl[] in sata_promise.c
Daniel Drake wrote:
Otto Meier wrote:
This card use the sata chip pdc 40718 (as of my card)
the lastest sata_promise kernel with sata promise patch driver
doesn't recognise
this card.
I added the following line to static struct pci_device_id
pdc_ata_pci_tbl[] in sata_promise.c
Daniel Drake wrote:
Otto Meier wrote:
This card use the sata chip pdc 40718 (as of my card)
the lastest sata_promise kernel with sata promise patch driver
doesn't recognise
this card.
I added the following line to static struct pci_device_id
pdc_ata_pci_tbl[] in sata_promise.c
Daniel Drake wrote:
Otto Meier wrote:
This card use the sata chip pdc 40718 (as of my card)
the lastest sata_promise kernel with sata promise patch driver
doesn't recognise
this card.
I added the following line to static struct pci_device_id
pdc_ata_pci_tbl[] in sata_promise.c
I run linux 2.4.2-ac24 on the ULTRA 100 card with pdc 20267 Chip.
Drives are MAXTOR 53073H4 UDMA100.
Everything runs fine so far. The only thing which iritates me is
that :
/proc/ide/pdc202xx reports that the drives run in UDMA4 mode.
I have the above mentioned drives running as master each
I run linux 2.4.2-ac24 on the ULTRA 100 card with pdc 20267 Chip.
Drives are MAXTOR 53073H4 UDMA100.
Everything runs fine so far. The only thing which iritates me is
that :
/proc/ide/pdc202xx reports that the drives run in UDMA4 mode.
I have the above mentioned drives running as master each
On Thu, 8 Mar 2001 08:55:28 +1100 (EST), Neil Brown wrote:
>On Wednesday March 7, [EMAIL PROTECTED] wrote:
>> I run a Dual prozessor SMP system on 2.4.2-ac12 for a while
>> in degraded mode. Today I put in a new disk to switch to
>> full raid5 mode. Shortly after the command raidhotadd the
>>
On Thu, 8 Mar 2001 08:55:28 +1100 (EST), Neil Brown wrote:
On Wednesday March 7, [EMAIL PROTECTED] wrote:
I run a Dual prozessor SMP system on 2.4.2-ac12 for a while
in degraded mode. Today I put in a new disk to switch to
full raid5 mode. Shortly after the command raidhotadd the
system
I run a Dual prozessor SMP system on 2.4.2-ac12 for a while
in degraded mode. Today I put in a new disk to switch to
full raid5 mode. Shortly after the command raidhotadd the
system crashed with the message lost interrupt on cpu1.
This continued after reboot. I finaly managed to get it running
Two days ago I tried new kernels on my SMP SW RAID5 System
and expirienced serous file system corruption with kernels 2.4.1-pre8,9 as
2.4.0-ac8,9,10.
The same error has been reported by other people on this list. With 2.4.0 release
everything runs fine. So I backsteped to it and had no error
Two days ago I tried new kernels on my SMP SW RAID5 System
and expirienced serous file system corruption with kernels 2.4.1-pre8,9 as
2.4.0-ac8,9,10.
The same error has been reported by other people on this list. With 2.4.0 release
everything runs fine. So I backsteped to it and had no error
On Tue, 02 Jan 2001 18:19:41 +0100, Otto Meier wrote:
>>Dual Celeron (SMP,raid5)
>> As stated in my first mail I run actually my raid5 devices in degrated mode
>> and as I remenber there has been some raid5 stuff changed between
>> test13p3 and newer kernels.
>So t
On Tue, 02 Jan 2001 18:19:41 +0100, Otto Meier wrote:
Dual Celeron (SMP,raid5)
As stated in my first mail I run actually my raid5 devices in degrated mode
and as I remenber there has been some raid5 stuff changed between
test13p3 and newer kernels.
So tell us, why do you run your raid5
Perhaps a deadlock with a normal (not irq) spinlock.
Could you enable SysRQ and press ++ ("showPc")
Then write down the EIP values (including the [< >] brackets) and
translate them with ksymoops.
Ksymoops repeats only the EIP values.
But searching through the System.map file has only Labels
On all kernels newer than 2.4.0t13p3 I have the following problem.
shorly after boot (some seconds) the system freeze. I can only swith consoles
but i am not able to login. Over the net I get onyl responses to
pings nothing else.
Up to kernel 2.4.0.t13p3 everythings works fine.
Sorry for this
On all kernels newer than 2.4.0t13p3 I have the following problem.
shorly after boot (some seconds) the system freeze. I can only swith consoles
but i am not able to login. Over the net I get onyl responses to
pings nothing else.
Up to kernel 2.4.0.t13p3 everythings works fine.
Sorry for this
On all kernels newer than 2.4.0t13p3 I have the following problem.
shorly after boot (some seconds) the system freeze. I can only swith consoles
but i am not able to login. Over the net I get onyl responses to
pings nothing else.
Up to kernel 2.4.0.t13p3 everythings works fine.
Sorry for this
On all kernels newer than 2.4.0t13p3 I have the following problem.
shorly after boot (some seconds) the system freeze. I can only swith consoles
but i am not able to login. Over the net I get onyl responses to
pings nothing else.
Up to kernel 2.4.0.t13p3 everythings works fine.
Sorry for this
39 matches
Mail list logo
