Kernel: 5.9.3
Arch: x86_64
These are showing up in dmesg every so often and they are not
associated with any type of message/alert or user associated action.
What is causing this & why are there no details associated with this
message?
[Wed Nov 4 17:05:56 2020] md0:
[Thu Nov 5 08:23:32 2020]
Hello,
Going to be turning these options off for now (zswap+zram) under 5.2 and
hopefully this makes the machine stable again-but just wanted to point out
under 5.1.xx never had any issues but with 5.2 the kernel crashes fairly
quickly when performing heavy I/O with these options enabled: (note:
On Mon, May 20, 2019 at 7:56 AM Mel Gorman wrote:
>
> On Sun, May 12, 2019 at 04:27:45AM -0400, Justin Piszcz wrote:
> > Hello,
> >
> > I've turned off zram/zswap and I am still seeing the following during
> > periods of heavy I/O, I am returning to 5.0.xx in the m
On Mon, May 20, 2019 at 7:56 AM Mel Gorman wrote:
>
> On Sun, May 12, 2019 at 04:27:45AM -0400, Justin Piszcz wrote:
> > Hello,
> >
> > I've turned off zram/zswap and I am still seeing the following during
> > periods of heavy I/O, I am returning to 5.0.xx in the m
On Thu, May 16, 2019 at 10:17 AM Justin Piszcz wrote:
>
> On Thu, May 16, 2019 at 10:14 AM Justin Piszcz
> wrote:
> >
> > On Tue, May 14, 2019 at 9:16 AM Kirill A. Shutemov
> > wrote:
> >
> > > Could you check what khugepaged doing?
>
On Thu, May 16, 2019 at 10:14 AM Justin Piszcz wrote:
>
> On Tue, May 14, 2019 at 9:16 AM Kirill A. Shutemov
> wrote:
>
> > Could you check what khugepaged doing?
> >
> > cat /proc/$(pidof khugepaged)/stack
>
> It is doing it again, 10:12am - 2019-05-16
>
On Tue, May 14, 2019 at 9:16 AM Kirill A. Shutemov wrote:
> Could you check what khugepaged doing?
>
> cat /proc/$(pidof khugepaged)/stack
It is doing it again, 10:12am - 2019-05-16
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
77 root 39 19 0
> -Original Message-
> From: Kirill A. Shutemov [mailto:kir...@shutemov.name]
> Sent: Thursday, May 09, 2019 7:14 AM
> To: Justin Piszcz
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: 5.1 kernel: khugepaged stuck at 100%
>
> On Thu, May 09, 2019 at 05:54:5
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Sunday, May 12, 2019 4:28 AM
> To: LKML
> Subject: 5.1 and 5.1.1: BUG: unable to handle kernel paging request at
> ea000203
>
> Hello,
>
> I've turned off zr
Hello,
I've turned off zram/zswap and I am still seeing the following during
periods of heavy I/O, I am returning to 5.0.xx in the meantime.
Kernel: 5.1.1
Arch: x86_64
Dist: Debian x86_64
[29967.019411] BUG: unable to handle kernel paging request at ea000203
[29967.019414] #PF error:
On Thu, May 9, 2019 at 5:54 AM Justin Piszcz wrote:
>
> Hello,
>
> Kernel: 5.1 (self-compiled, no modules)
> Arch: x86_64
> Distro: Debian Testing
>
> Issue: I was performing a dump of ext3 and ext4 filesystems and then
> restoring them to a separate volume (test
Hello,
Kernel: 5.1 (self-compiled, no modules)
Arch: x86_64
Distro: Debian Testing
Issue: I was performing a dump of ext3 and ext4 filesystems and then
restoring them to a separate volume (testing)-- afterwards I noticed that
khugepaged is stuck at 100% CPU. It is currently still stuck at 100%
Hello,
Kernel: 4.12.0
Arch: x86_64
What causes this issue?
[199141.434449] NETDEV WATCHDOG: eth1 (igb): transmit queue 7 timed out
[199141.434501] [ cut here ]
[199141.434515] WARNING: CPU: 10 PID: 0 at net/sched/sch_generic.c:316
dev_watchdog+0x212/0x220
[199141.434528]
Hello,
Kernel: 4.12.0
Arch: x86_64
What causes this issue?
[199141.434449] NETDEV WATCHDOG: eth1 (igb): transmit queue 7 timed out
[199141.434501] [ cut here ]
[199141.434515] WARNING: CPU: 10 PID: 0 at net/sched/sch_generic.c:316
dev_watchdog+0x212/0x220
[199141.434528]
> -Original Message-
> From: Cong Wang [mailto:xiyou.wangc...@gmail.com]
> Sent: Thursday, June 29, 2017 9:44 PM
> To: Justin Piszcz
> Cc: LKML
> Subject: Re: WARNING: CPU: 3 PID: 0 at kernel/cgroup/cgroup.c:441
> cgroup_get+0x4b/0x50
>
> On Thu, Jun 29, 2017
> -Original Message-
> From: Cong Wang [mailto:xiyou.wangc...@gmail.com]
> Sent: Thursday, June 29, 2017 9:44 PM
> To: Justin Piszcz
> Cc: LKML
> Subject: Re: WARNING: CPU: 3 PID: 0 at kernel/cgroup/cgroup.c:441
> cgroup_get+0x4b/0x50
>
> On Thu, Jun 29, 2017
Hello,
Kernel: 4.11.0
Arch: x86_64
First time I have run into a WARN in a while, .config is attached:
$ cp /proc/config.gz .
Snippet:
[22606.516656] [ cut here ]
[22606.516669] WARNING: CPU: 3 PID: 0 at kernel/cgroup/cgroup.c:441
cgroup_get+0x4b/0x50
[22606.516672]
Hello,
Kernel: 4.11.0
Arch: x86_64
First time I have run into a WARN in a while, .config is attached:
$ cp /proc/config.gz .
Snippet:
[22606.516656] [ cut here ]
[22606.516669] WARNING: CPU: 3 PID: 0 at kernel/cgroup/cgroup.c:441
cgroup_get+0x4b/0x50
[22606.516672]
On Tue, Oct 4, 2016 at 8:58 PM, Liping Zhang <zlpnob...@gmail.com> wrote:
> Hi Justin,
>
> 2016-10-05 6:02 GMT+08:00 Justin Piszcz <jpis...@lucidpixels.com>:
>> Hello,
>>
[ .. ]
>
> Which one are you using? iptables or nftables?
# iptables -V
ipta
On Tue, Oct 4, 2016 at 8:58 PM, Liping Zhang wrote:
> Hi Justin,
>
> 2016-10-05 6:02 GMT+08:00 Justin Piszcz :
>> Hello,
>>
[ .. ]
>
> Which one are you using? iptables or nftables?
# iptables -V
iptables v1.6.0
>
> Could you please paste the related ipt
Hello,
kernel 4.8 with ulogd-2.0.5- IPs are no longer logged:
Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT=
MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00
TTL=0 ID=0 PROTO=0 MARK=0
Oct 4 17:51:31 atom INPUT_BLOCK IN=eth1 OUT=
MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00
Hello,
kernel 4.8 with ulogd-2.0.5- IPs are no longer logged:
Oct 4 17:51:30 atom INPUT_BLOCK IN=eth1 OUT=
MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00 LEN=0 TOS=00 PREC=0x00
TTL=0 ID=0 PROTO=0 MARK=0
Oct 4 17:51:31 atom INPUT_BLOCK IN=eth1 OUT=
MAC=00:1b:21:9c:3b:fa:3e:94:d5:d2:49:1e:08:00
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Saturday, February 28, 2015 5:57 PM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
>
Removing the card did not
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Saturday, February 28, 2015 5:57 PM
To: linux-kernel@vger.kernel.org
Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
Removing the card did not fix the issue.
I've gone
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Saturday, February 28, 2015 5:19 PM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
>
>
>
> > --
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Friday, February 27, 2015 10:54 AM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
>
>
>
> > --
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Friday, February 27, 2015 10:54 AM
To: linux-kernel@vger.kernel.org
Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
-Original Message-
From: Justin Piszcz
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Saturday, February 28, 2015 5:19 PM
To: linux-kernel@vger.kernel.org
Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
-Original Message-
From: Justin
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Friday, February 27, 2015 9:54 AM
> To: linux-kernel@vger.kernel.org
> Subject: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
>
> Hello,
>
> With kernel 3
Hello,
With kernel 3.15, I do not recall having any issues, with 3.19, I am getting
a kernel crash when I copy files over NFS from machine A to B.
Is this a known issue?
I suspect it has to do something with this:
Feb 27 09:31:20 remote-host [ 15.745342] dmar: DRHD: handling fault status
reg 2
Hello,
With kernel 3.15, I do not recall having any issues, with 3.19, I am getting
a kernel crash when I copy files over NFS from machine A to B.
Is this a known issue?
I suspect it has to do something with this:
Feb 27 09:31:20 remote-host [ 15.745342] dmar: DRHD: handling fault status
reg 2
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Friday, February 27, 2015 9:54 AM
To: linux-kernel@vger.kernel.org
Subject: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
Hello,
With kernel 3.15, I do not recall having any
> -Original Message-
> From: Tantilov, Emil S [mailto:emil.s.tanti...@intel.com]
> Sent: Monday, February 23, 2015 11:43 AM
[ .. ]
> The reset is a side effect of the Tx hang - the driver is trying to
recover from
> the hang by resetting the interface.
>
> If you could open up a
On Sun, Feb 22, 2015 at 7:01 AM, Justin Piszcz wrote:
>
> Hello,
>
> Kernel: 3.19.0
> Issue: When using robocopy to copy files (from Windows 8/8.1) to
> Linux/samba, the 10GbE NIC resets - dmesg [1] below. To get it back working
> again, I have to down/up the interface. J
On Sun, Feb 22, 2015 at 7:01 AM, Justin Piszcz jpis...@lucidpixels.com wrote:
Hello,
Kernel: 3.19.0
Issue: When using robocopy to copy files (from Windows 8/8.1) to
Linux/samba, the 10GbE NIC resets - dmesg [1] below. To get it back working
again, I have to down/up the interface. Jumbo
-Original Message-
From: Tantilov, Emil S [mailto:emil.s.tanti...@intel.com]
Sent: Monday, February 23, 2015 11:43 AM
[ .. ]
The reset is a side effect of the Tx hang - the driver is trying to
recover from
the hang by resetting the interface.
If you could open up a ticket at
Hello,
Kernel: 3.19.0
Issue: When using robocopy to copy files (from Windows 8/8.1) to
Linux/samba, the 10GbE NIC resets - dmesg [1] below. To get it back working
again, I have to down/up the interface. Jumbo frames are being used (mtu of
9014) on each side. The lspci output is listed below.
Hello,
Kernel: 3.19.0
Issue: When using robocopy to copy files (from Windows 8/8.1) to
Linux/samba, the 10GbE NIC resets - dmesg [1] below. To get it back working
again, I have to down/up the interface. Jumbo frames are being used (mtu of
9014) on each side. The lspci output is listed below.
> -Original Message-
> From: Bruno Prémont [mailto:bonb...@linux-vserver.org]
> Sent: Tuesday, April 01, 2014 4:22 PM
> To: Justin Piszcz
> Cc: linux-kernel@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: Re: X.org doesn't start with 3.14: [KMS] drm report
-Original Message-
From: Bruno Prémont [mailto:bonb...@linux-vserver.org]
Sent: Tuesday, April 01, 2014 4:22 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; dri-de...@lists.freedesktop.org
Subject: Re: X.org doesn't start with 3.14: [KMS] drm report modesetting
isn't
Hello,
Do I need some updated ATI firmware (I believe this might have happened in
the past)..?
I booted back to 3.13.6, Xorg starts up fine, but with 3.14 it does not
start.
Thoughts?
3.13.6:
$ ps auxww|grep X
root 4368 5.3 0.0 296648 37364 tty7 Ssl+ 18:23 0:00 /usr/bin/X
:0 vt7
Hello,
Do I need some updated ATI firmware (I believe this might have happened in
the past)..?
I booted back to 3.13.6, Xorg starts up fine, but with 3.14 it does not
start.
Thoughts?
3.13.6:
$ ps auxww|grep X
root 4368 5.3 0.0 296648 37364 tty7 Ssl+ 18:23 0:00 /usr/bin/X
:0 vt7
> -Original Message-
> From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
> Sent: Thursday, November 28, 2013 8:13 AM
>
>
> Martin> http://marc.info/?l=linux-scsi=138252394614920=2
>
> Justin> Awesome, thank you! This patch is over a month old, do you know
> Justin>
-Original Message-
From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
Sent: Thursday, November 28, 2013 8:13 AM
Martin http://marc.info/?l=linux-scsim=138252394614920w=2
Justin Awesome, thank you! This patch is over a month old, do you know
Justin if is
-Original Message-
From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
Sent: Thursday, November 28, 2013 8:13 AM
[ .. ]
Martin> http://marc.info/?l=linux-scsi=138252394614920=2
Justin> Awesome, thank you! This patch is over a month old, do you know
Justin> if is currently
-Original Message-
From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
Sent: Thursday, November 28, 2013 8:00 AM
To: Justin Piszcz
Cc: open list; linux-e...@vger.kernel.org; linux-s...@vger.kernel.org
Subject: Re: 3.12.0: sda2: WRITE SAME failed. Manually zeroing. with 3w-
-Original Message-
From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
Sent: Thursday, November 28, 2013 8:00 AM
To: Justin Piszcz
Cc: open list; linux-e...@vger.kernel.org; linux-s...@vger.kernel.org
Subject: Re: 3.12.0: sda2: WRITE SAME failed. Manually zeroing. with 3w-
-Original Message-
From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
Sent: Thursday, November 28, 2013 8:13 AM
[ .. ]
Martin http://marc.info/?l=linux-scsim=138252394614920w=2
Justin Awesome, thank you! This patch is over a month old, do you know
Justin if is currently in
Hello,
Using 3.12.0 and ext4fs with 2 x SSDs in a RAID-1 configuration on a
3ware HW RAID card, no md/dm, I noticed the following recently:
[178339.353565] sda2: WRITE SAME failed. Manually zeroing.
It seems to be similar to this issue here:
http://permalink.gmane.org/gmane.linux.kernel/1494512
Hello,
Using 3.12.0 and ext4fs with 2 x SSDs in a RAID-1 configuration on a
3ware HW RAID card, no md/dm, I noticed the following recently:
[178339.353565] sda2: WRITE SAME failed. Manually zeroing.
It seems to be similar to this issue here:
http://permalink.gmane.org/gmane.linux.kernel/1494512
On Mon, Nov 11, 2013 at 7:39 PM, Brad Campbell
wrote:
> On 11/07/2013 06:54 PM, Justin Piszcz wrote:
>>
>> On Mon, Nov 4, 2013 at 5:25 AM, Justin Piszcz
>> wrote:
>>>
>>> Hi,
>>>
>>> I run two SSDs in a RAID-1 configuration a
On Mon, Nov 11, 2013 at 7:39 PM, Brad Campbell
lists2...@fnarfbargle.com wrote:
On 11/07/2013 06:54 PM, Justin Piszcz wrote:
On Mon, Nov 4, 2013 at 5:25 AM, Justin Piszcz jpis...@lucidpixels.com
wrote:
Hi,
I run two SSDs in a RAID-1 configuration and I have a swap partition on a
third SSD
On Mon, Nov 4, 2013 at 5:25 AM, Justin Piszcz wrote:
> Hi,
>
> I run two SSDs in a RAID-1 configuration and I have a swap partition on a
> third SSD. Over time, the mismatch_cnt between the two devices grows higher
> and higher.
>
> Once a week, I run a check and repair a
On Mon, Nov 4, 2013 at 5:25 AM, Justin Piszcz jpis...@lucidpixels.com wrote:
Hi,
I run two SSDs in a RAID-1 configuration and I have a swap partition on a
third SSD. Over time, the mismatch_cnt between the two devices grows higher
and higher.
Once a week, I run a check and repair against
Hi,
I run two SSDs in a RAID-1 configuration and I have a swap partition on a
third SSD. Over time, the mismatch_cnt between the two devices grows higher
and higher.
Once a week, I run a check and repair against the md devices to help bring
the mismatch_cnt down. When I run the check and
Hi,
I run two SSDs in a RAID-1 configuration and I have a swap partition on a
third SSD. Over time, the mismatch_cnt between the two devices grows higher
and higher.
Once a week, I run a check and repair against the md devices to help bring
the mismatch_cnt down. When I run the check and
Hello,
I recent upgraded from 3.10 to 3.11 and see these on occasion in the kernel log:
perf samples too long (2501 > 2500), lowering
kernel.perf_event_max_sample_rate to 5
perf samples too long (5040 > 5000), lowering
kernel.perf_event_max_sample_rate to 25000
I was curious what is causing
Hello,
I recent upgraded from 3.10 to 3.11 and see these on occasion in the kernel log:
perf samples too long (2501 2500), lowering
kernel.perf_event_max_sample_rate to 5
perf samples too long (5040 5000), lowering
kernel.perf_event_max_sample_rate to 25000
I was curious what is causing
-Original Message-
From: NeilBrown [mailto:ne...@suse.de]
Sent: Monday, July 29, 2013 1:57 AM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org
Subject: Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x
SSD)
On Fri, 26 Jul 2013 05:56:51 -0
-Original Message-
From: NeilBrown [mailto:ne...@suse.de]
Sent: Monday, July 29, 2013 1:57 AM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org
Subject: Re: 3.10.1: echo repair sync_action causes hang on RAID-1 (2 x
SSD)
On Fri, 26 Jul 2013 05:56:51 -0400
-Original Message-
From: NeilBrown [mailto:ne...@suse.de]
Sent: Thursday, July 25, 2013 8:36 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org
Subject: Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x
SSD)
On Thu, 25 Jul 2013 19:10
-Original Message-
From: NeilBrown [mailto:ne...@suse.de]
Sent: Thursday, July 25, 2013 8:36 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org
Subject: Re: 3.10.1: echo repair sync_action causes hang on RAID-1 (2 x
SSD)
On Thu, 25 Jul 2013 19:10:50
-Original Message-
From: NeilBrown [mailto:ne...@suse.de]
Sent: Sunday, July 21, 2013 7:03 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org
Subject: Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x
SSD)
> Hi Justin,
> this i
-Original Message-
From: NeilBrown [mailto:ne...@suse.de]
Sent: Sunday, July 21, 2013 7:03 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org
Subject: Re: 3.10.1: echo repair sync_action causes hang on RAID-1 (2 x
SSD)
Hi Justin,
this is a known bug
Hi,
When I run repair on an MD-RAID1 sync_action, the speed slows down and it
stays like this (below) for hours.
The system is then completely unresponsive to user input. I have replaced a
failing SSD; however, after a check, mismatch_cnt seems to increase over
time. When I run repair, the
Hi,
When I run repair on an MD-RAID1 sync_action, the speed slows down and it
stays like this (below) for hours.
The system is then completely unresponsive to user input. I have replaced a
failing SSD; however, after a check, mismatch_cnt seems to increase over
time. When I run repair, the
Intel's Secure Erase), I RMA'd it.
Interesting though that it did not drop out of the array but froze the
system (the failure scenario was odd).
Justin.
On Tue, Jul 16, 2013 at 3:15 AM, NeilBrown wrote:
> On Sat, 13 Jul 2013 06:34:19 -0400 "Justin Piszcz"
> wrote:
>
>>
Intel's Secure Erase), I RMA'd it.
Interesting though that it did not drop out of the array but froze the
system (the failure scenario was odd).
Justin.
On Tue, Jul 16, 2013 at 3:15 AM, NeilBrown ne...@suse.de wrote:
On Sat, 13 Jul 2013 06:34:19 -0400 Justin Piszcz jpis...@lucidpixels.com
wrote
Hello,
Running 3.10 and I see the following for an md-raid1 of two SSDs:
Checking /sys/block/md1/queue:
add_random: 0
discard_granularity: 512
discard_max_bytes: 2147450880
discard_zeroes_data: 0
hw_sector_size: 512
iostats: 0
logical_block_size: 512
max_hw_sectors_kb: 32767
subscribe linux-raid
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
subscribe linux-raid
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hello,
Running 3.10 and I see the following for an md-raid1 of two SSDs:
Checking /sys/block/md1/queue:
add_random: 0
discard_granularity: 512
discard_max_bytes: 2147450880
discard_zeroes_data: 0
hw_sector_size: 512
iostats: 0
logical_block_size: 512
max_hw_sectors_kb: 32767
Thanks for these details!
On Thu, Jul 11, 2013 at 4:47 AM, Jean Delvare wrote:
> Hi Guenter, Justin,
>
> On Wed, 3 Jul 2013 07:42:01 -0700, Guenter Roeck wrote:
>> On Wed, Jul 03, 2013 at 08:35:59AM -0400, Justin Piszcz wrote:
>> > I also found:
>> > http://www.l
Thanks for these details!
On Thu, Jul 11, 2013 at 4:47 AM, Jean Delvare kh...@linux-fr.org wrote:
Hi Guenter, Justin,
On Wed, 3 Jul 2013 07:42:01 -0700, Guenter Roeck wrote:
On Wed, Jul 03, 2013 at 08:35:59AM -0400, Justin Piszcz wrote:
I also found:
http://www.lm-sensors.org/wiki
Re-sending as text.
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Wednesday, July 03, 2013 5:00 PM
To: 'Guenter Roeck'
Cc: linux-kernel@vger.kernel.org; lm-sens...@lm-sensors.org
Subject: RE: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
-Original Message-
From: Guenter Roeck [mailto:li...@roeck-us.net]
Sent: Wednesday, July 03, 2013 1:17 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sens...@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
-Original Message-
From: Guenter Roeck [mailto:li...@roeck-us.net]
Sent: Wednesday, July 03, 2013 12:33 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sens...@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
-Original Message-
From: Guenter Roeck [mailto:li...@roeck-us.net]
Sent: Wednesday, July 03, 2013 10:42 AM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sens...@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
-Original Message-
From: Alex Deucher [mailto:alexdeuc...@gmail.com]
Sent: Tuesday, July 02, 2013 3:41 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; dri-de...@lists.freedesktop.org
Subject: Re: 3.10 kernel: [drm:evergreen_startup] *ERROR* radeon: error
initializing UVD (-1
Hi,
I saw this in the device drive section and was curious which Intel-based
NICs contain temperature sensors?
Intel(R) 10GbE PCI Express adapters HWMON support
Intel(R) PCI-Express Gigabit adapters HWMON support
I checked the boards below and none appear to expose a hwmon interface:
08:00.0
Hello,
Currently running 3.10 with:
CONFIG_SENSORS_NCT6775=y
Motherboard: Supermicro X9SRL-F
A couple questions:
1) Was curious if the PCH CHIP/CPU/MCH temperatures should be populated for
this board?
2) Additionally, why is the CPUTIN in alarm?
I also found:
Hello,
Currently running 3.10 with:
CONFIG_SENSORS_NCT6775=y
Motherboard: Supermicro X9SRL-F
A couple questions:
1) Was curious if the PCH CHIP/CPU/MCH temperatures should be populated for
this board?
2) Additionally, why is the CPUTIN in alarm?
I also found:
Hi,
I saw this in the device drive section and was curious which Intel-based
NICs contain temperature sensors?
Intel(R) 10GbE PCI Express adapters HWMON support
Intel(R) PCI-Express Gigabit adapters HWMON support
I checked the boards below and none appear to expose a hwmon interface:
08:00.0
-Original Message-
From: Alex Deucher [mailto:alexdeuc...@gmail.com]
Sent: Tuesday, July 02, 2013 3:41 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; dri-de...@lists.freedesktop.org
Subject: Re: 3.10 kernel: [drm:evergreen_startup] *ERROR* radeon: error
initializing UVD (-1
-Original Message-
From: Guenter Roeck [mailto:li...@roeck-us.net]
Sent: Wednesday, July 03, 2013 10:42 AM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sens...@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
-Original Message-
From: Guenter Roeck [mailto:li...@roeck-us.net]
Sent: Wednesday, July 03, 2013 12:33 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sens...@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
-Original Message-
From: Guenter Roeck [mailto:li...@roeck-us.net]
Sent: Wednesday, July 03, 2013 1:17 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; lm-sens...@lm-sensors.org
Subject: Re: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
Re-sending as text.
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Wednesday, July 03, 2013 5:00 PM
To: 'Guenter Roeck'
Cc: linux-kernel@vger.kernel.org; lm-sens...@lm-sensors.org
Subject: RE: [lm-sensors] 3.10: NCT6776F sensor question with Supermicro
X9SRL-F motherboard
-Original Message-
From: Alex Deucher [mailto:alexdeuc...@gmail.com]
Sent: Tuesday, July 02, 2013 2:36 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; dri-de...@lists.freedesktop.org
Subject: Re: 3.10 kernel: [drm:evergreen_startup] *ERROR* radeon: error
initializing UVD (-1
Hello,
I use an ATI graphics card (PCI-e x1) for a server:
Card: [AMD/ATI] Park [Mobility Radeon HD 5430]
I upgraded my kernel from 3.9.x to 3.10, after rebooting I found the driver
now wants a new firmware:
radeon :05:00.0: radeon_uvd: Can't load firmware
"radeon/CYPRESS_uvd.bin"
I pulled
Hello,
I use an ATI graphics card (PCI-e x1) for a server:
Card: [AMD/ATI] Park [Mobility Radeon HD 5430]
I upgraded my kernel from 3.9.x to 3.10, after rebooting I found the driver
now wants a new firmware:
radeon :05:00.0: radeon_uvd: Can't load firmware
radeon/CYPRESS_uvd.bin
I pulled
-Original Message-
From: Alex Deucher [mailto:alexdeuc...@gmail.com]
Sent: Tuesday, July 02, 2013 2:36 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; dri-de...@lists.freedesktop.org
Subject: Re: 3.10 kernel: [drm:evergreen_startup] *ERROR* radeon: error
initializing UVD (-1
Hello,
This bug I reported in November 2012:
http://www.kernelhub.org/?p=2=170797
http://home.comcast.net/~jpiszcz/20121128/highpoint.jpg
Some discussion on the patches:
http://www.kernelhub.org/?p=2=172597
http://www.kernelhub.org/?p=2=171846
http://www.kernelhub.org/?p=2=172346
My current
Hello,
This bug I reported in November 2012:
http://www.kernelhub.org/?p=2msg=170797
http://home.comcast.net/~jpiszcz/20121128/highpoint.jpg
Some discussion on the patches:
http://www.kernelhub.org/?p=2msg=172597
http://www.kernelhub.org/?p=2msg=171846
http://www.kernelhub.org/?p=2msg=172346
My
On Sun, Mar 3, 2013 at 8:35 PM, Andrew Cooks wrote:
> On Sat, Mar 2, 2013 at 7:18 AM, Justin Piszcz wrote:
>>
>> Against a clean 3.7.10 (from ftp.kernel.org)
>>
>> # patch -p1 <
>> ../patch/RFC-Fix-Intel-IOMMU-support-for-Marvell-88SE91xx-SATA-controllers
On Sun, Mar 3, 2013 at 8:35 PM, Andrew Cooks aco...@gmail.com wrote:
On Sat, Mar 2, 2013 at 7:18 AM, Justin Piszcz jpis...@lucidpixels.com wrote:
Against a clean 3.7.10 (from ftp.kernel.org)
# patch -p1
../patch/RFC-Fix-Intel-IOMMU-support-for-Marvell-88SE91xx-SATA-controllers..
patch
On Sat, Mar 2, 2013 at 7:18 AM, Justin Piszcz
wrote:
>
> Against a clean 3.7.10 (from ftp.kernel.org)
>
> # patch -p1 <
>
../patch/RFC-Fix-Intel-IOMMU-support-for-Marvell-88SE91xx-SATA-controllers..
> patch
> patching file drivers/iommu/intel-iommu.c
> patching file
On Sat, Mar 2, 2013 at 7:18 AM, Justin Piszcz jpis...@lucidpixels.com
wrote:
Against a clean 3.7.10 (from ftp.kernel.org)
# patch -p1
../patch/RFC-Fix-Intel-IOMMU-support-for-Marvell-88SE91xx-SATA-controllers..
patch
patching file drivers/iommu/intel-iommu.c
patching file drivers/pci
-Original Message-
From: Andrew Cooks [mailto:aco...@gmail.com]
Sent: Friday, March 01, 2013 5:19 PM
To: Justin Piszcz
Cc: Joerg Roedel; YingChu; Chu Ying; Alex Williamson; bhelg...@google.com;
David Woodhouse; open list:INTEL IOMMU (VT-d); open list; open list:PCI
SUBSYSTEM
Subject: Re
-Original Message-
From: Andrew Cooks [mailto:aco...@gmail.com]
Sent: Friday, March 01, 2013 3:26 AM
To: aco...@gmail.com; j...@8bytes.org; xjtuy...@hotmail.com;
gm.y...@gmail.com; alex.william...@redhat.com; bhelg...@google.com;
jpis...@lucidpixels.com; dw...@infradead.org
Cc: open
1 - 100 of 692 matches
Mail list logo
