can be the greatest one. So this is normally treated as a
special case, defined to be 0 by convention, as this makes the use of
gcd "nicer" in other areas of mathematics.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
To unsubscribe from this list: s
49 c7 44 24 18 8c 00 00 00 78 1e 49 83 7e 08 00 74 04 <0f> 0b eb fe 49 8b 3e
4d 89 6e 08 4c 89 e6 e8 1f 27 fa ff 85 c0
RIP [] nfs_idmap_legacy_upcall+0x10c/0x15e [nfs]
RSP
---[ end trace ee7d4fa42e626e1f ]---
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
To unsub
t;slashes". This implies that
it must either modify the provided string or copy it somewhere else
(POSIX admits either behaviour).
On the other hand, GNU basename does not trim trailing '/' characters
and returns the empty string in this case. It's truly unfortunate that
g
ace/linux-2.6
WTF? 3.5 is fine. I will try to bisect this later, but I figured I'd
throw this out there now in case anyone has any ideas...
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
To unsubscribe from this list: send the line "unsubscribe linu
quot;permission denied" errors when all the permissions
involved look fine. As far as I know, the owner, group and mode of
symlinks have always been completely meaningless. Upgrade to 3.6, and
they're suddenly meaningful in extremely non-obvious ways.
Cheers,
--
Nick Bowler, Ellipt
On 2012-10-04 08:49 -0700, Kees Cook wrote:
> On Thu, Oct 04, 2012 at 09:35:04AM -0400, Nick Bowler wrote:
> > On 2012-10-03 13:54 -0700, Linus Torvalds wrote:
> > > On Wed, Oct 3, 2012 at 1:49 PM, Kees Cook wrote:
> > > > I think the benefits of this being o
On 2012-10-04 09:14 -0700, Kees Cook wrote:
> On Thu, Oct 04, 2012 at 12:03:54PM -0400, Nick Bowler wrote:
> > On 2012-10-04 08:49 -0700, Kees Cook wrote:
> > > On Thu, Oct 04, 2012 at 09:35:04AM -0400, Nick Bowler wrote:
[...]
> > > > The thing that bothers me mo
20 48 8b 43 18 48 85 c0 75 1f 48 8b 43 20
RIP [] ext4_ext_remove_space+0x725/0x9db [ext4]
RSP
CR2: 0028
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
;s quite likely that this does not have to be a fixed mapping
> > any more. Just have a look at how drivers/clocksource/dw_apb_timer_of.c
> > calls of_iomap() to get the address.
>
> Yes, this is already on my list of plans. The in-tree TTC driver
> unfortunately doesn't
oblem of how to
> solve the SCU mapping problem generically.
Then the static mapping can be removed if and when the we "solve the SCU
mapping problem generically". There's no point in removing it until
then since it doesn't cause any actual problems, does it?
Chee
On 2012-10-23 23:08 -0400, Theodore Ts'o wrote:
> On Tue, Oct 23, 2012 at 08:50:22PM -0400, Nick Bowler wrote:
> > I just saw an ext4 oops on one of my machines after a couple months of
> > uptime, on Linux 3.5.2. I doubt I will be able to reproduce the problem
> > easil
t CPU_V7
> select GENERIC_CLOCKEVENTS
> select ICST
I'd prefer if we just added "select COMMON_CLK" instead of removing this
so we don't have to re-add this later, but I guess it doesn't really
matter either way.
Cheers,
--
Nick Bowler, Elliptic Tech
On 2012-10-23 18:42 -0500, Josh Cartwright wrote:
> On Tue, Oct 23, 2012 at 04:27:03PM -0400, Nick Bowler wrote:
> > Just FYI, I sent a patch to fix the same bug a while back
> >
> > https://patchwork.kernel.org/patch/1156361/
> >
> > together with other patches
Fails
0xf800Truncated
0xf8001000Works
0xfef0Truncated
0xfef01000Works
0xfef08000Fails
0xfef0f000Fails
0xfeffFails
0xfeff1000Fails
0xfeffe000Fails
0xfefff000Fails
Judging by the list, the console seems to only work properly
On 2012-10-25 16:29 -0500, Josh Cartwright wrote:
> On Thu, Oct 25, 2012 at 04:17:01PM -0400, Nick Bowler wrote:
> > Did you test this on any real hardware? I can't get the ZC702 to work
> > with the UART mapped at this address (this ends up being mapped at
> > 0xFEFFF
y for UART0 even though it is
the the default if UART1 is not selected.
As there are currently known issues related to the UART virtual
mappings, this is KNOWN BROKEN, not to be merged yet!
Not-Yet-Signed-off-by: Nick Bowler
---
arch/arm/Kconfig.debug | 17 +
On 2012-10-30 12:27 +0100, Michal Simek wrote:
> On 10/29/2012 07:19 PM, Nick Bowler wrote:
> > +#if IS_ENABLED(CONFIG_DEBUG_ZYNQ_UART1)
> > +# define LL_UART_PADDRUART1_PHYS
> > +# define LL_UART_VADDRUART_VIRT
> > +#else
> > +# define LL_UART_P
There is absolutely no reason to crash the kernel when we have a
perfectly good return value already available to use for conveying
failure status.
Let's return an error code instead of crashing the kernel: that sounds
like a much better plan.
Signed-off-by: Nick Bowler
---
lib/scatterl
y for UART0 even though it is
the the default if UART1 is not selected.
Signed-off-by: Nick Bowler
Tested-by: Josh Cartwright
---
Sorry all for the phenominal delay in sending this out. Josh, I kept
your Tested-By since this version is Obviously Equivalent™ to v2...
v2: rebase on newest patch s
On 2012-10-29 10:56 -0600, Josh Cartwright wrote:
> On Thu, Oct 25, 2012 at 06:47:34PM -0400, Nick Bowler wrote:
> > The main UART on the Xilinx ZC702 board is UART1, located at address
> > e0001000. Add a Kconfig option to select this device as the low-level
> > debugging p
y for UART0 even though it is
the the default if UART1 is not selected.
Signed-off-by: Nick Bowler
Tested-by: Josh Cartwright
---
v2: rebase on newest patch series, signoff.
This should apply cleanly on top of Josh Cartwright's v5 "zynq subarch
cleanups" series.
ar
On 2012-10-04 23:30 +0200, Stefan Richter wrote:
> On Oct 04 Nick Bowler wrote:
> > On 2012-10-04 09:14 -0700, Kees Cook wrote:
> > > On Thu, Oct 04, 2012 at 12:03:54PM -0400, Nick Bowler wrote:
> > > > On 2012-10-04 08:49 -0700, Kees Cook wrote:
> > > &g
y UP machines. It is, in fact, the only
option.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
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://vg
On 2012-11-13 09:08 -0800, Paul E. McKenney wrote:
> On Tue, Nov 13, 2012 at 09:46:20AM -0500, Nick Bowler wrote:
> > On 2012-11-12 16:49 -0800, Paul E. McKenney wrote:
> > > Hello!
> > >
> > > I know of people using TINY_RCU, TREE_RCU, and TREE_PREEMPT_RCU,
On 2012-11-13 13:19 -0800, Paul E. McKenney wrote:
> On Tue, Nov 13, 2012 at 12:56:54PM -0500, Nick Bowler wrote:
> > On 2012-11-13 09:08 -0800, Paul E. McKenney wrote:
> > > Suppose that TREE_PREEMPT_RCU was available for !SMP && PREEMPT builds.
> > > Woul
On 2012-11-13 14:25 -0800, Paul E. McKenney wrote:
> On Tue, Nov 13, 2012 at 04:47:20PM -0500, Nick Bowler wrote:
> > On 2012-11-13 13:19 -0800, Paul E. McKenney wrote:
> > > On Tue, Nov 13, 2012 at 12:56:54PM -0500, Nick Bowler wrote:
> > > > On 2012-11-13 09:08
On 2012-11-14 13:05 -0800, Andrew Morton wrote:
> On Thu, 1 Nov 2012 15:03:00 -0400
> Nick Bowler wrote:
>
> > There is absolutely no reason to crash the kernel when we have a
> > perfectly good return value already available to use for conveying
> > failure status.
Ping?
On 2013-03-07 10:06 -0500, Nick Bowler wrote:
> Yesterday I upgraded one of my machines to 3.8.2 from 3.6.6. This
> machine has an old NV36 AGP board. With the new kernel, as soon as
> nouveau takes over the console the display connected via DVI goes dark
> (the monitor goes
89 bb d0 00 00 00 48 83 c2 45 48 89 53 38 48 8b
[ 64.218124] RIP [] nlmclnt_setlockargs+0x50/0xca [lockd]
[ 64.218124] RSP
[ 64.218124] CR2: 0008
[ 64.236645] ---[ end trace 2fe8ddfc44039798 ]---
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.ellipticte
/~agd5f/linux into drm-fixes
git bisect bad 39df01cd6ce9f6dd755ace0030e2bebe75da7727
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
nouveau-black-lcd.log.xz
Description: application/xz
On 2013-03-07 10:06 -0500, Nick Bowler wrote:
> I started a bisection... here's the first steps so far. I will try to
> finish the procedure over the next couple days but I'm reporting this
> now in case someone needs me to get some other info.
I carried this on a bit further
with vers=4. I guess
the v4 mount is what crashed so it didn't show up in the list.
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger
,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
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 FA
On 2012-08-18 13:57 -0400, Nick Bowler wrote:
> I just noticed the following WARNING in my logs. Looking through the
> older logs, I see quite a few of these going (at least) all the way back
> to 3.3.x days. The process which triggers the warning always seems to
> be the
On 2013-01-08 18:35 -0500, Paul Gortmaker wrote:
> From: Nick Bowler
>
>---
> This is a commit scheduled for the next v2.6.34 longterm release.
> http://git.kernel.org/?p=linux/kernel/git/paulg/longterm-queue-2.6.34.git
> If you
Hi,
On my Asus C201 laptop (rk3288) the HDMI has been behaving weirdly after
Linux upgrade.
~50% of the time after a hotplug, there is a vertical pink bar on the
left of the display area and audio is not working at all. According to
the sink device the display size is 1282x720 which seems pretty
Hi,
I completed bisecting this issue. See below.
On 2017-11-02, Nick Bowler wrote:
> ~50% of the time after a hotplug, there is a vertical pink bar on the
> left of the display area and audio is not working at all. According to
> the sink device the display size is 1282x720 which see
Hi,
This issue is still present in 4.3-rc4.
On 9/24/15, Nick Bowler wrote:
> Testing out 4.3-rc2, first thing I notice is that the VGA output is
> not working. Specifically, the display is continuously powering on
> and off -- at no point is any image visible on the screen (I am expec
On 10/7/15, Ville Syrjälä wrote:
> On Tue, Oct 06, 2015 at 11:42:33AM -0400, Nick Bowler wrote:
>> On 9/24/15, Nick Bowler wrote:
>> > Testing out 4.3-rc2, first thing I notice is that the VGA output is
>> > not working. Specifically, the display is continuously pow
On 10/7/15, Ville Syrjälä wrote:
> On Wed, Oct 07, 2015 at 10:29:22AM -0400, Nick Bowler wrote:
>> On 10/7/15, Ville Syrjälä wrote:
>> > On Tue, Oct 06, 2015 at 11:42:33AM -0400, Nick Bowler wrote:
>> >> On 9/24/15, Nick Bowler wrote:
>> >> > Test
On 10/7/15, Nick Bowler wrote:
> On 10/7/15, Ville Syrjälä wrote:
>> On Wed, Oct 07, 2015 at 10:29:22AM -0400, Nick Bowler wrote:
>>> On 10/7/15, Ville Syrjälä wrote:
>>> > On Tue, Oct 06, 2015 at 11:42:33AM -0400, Nick Bowler wrote:
>>> >> On 9/24
On 10/7/15, Ville Syrjälä wrote:
> On Wed, Oct 07, 2015 at 10:29:22AM -0400, Nick Bowler wrote:
>> On 10/7/15, Ville Syrjälä wrote:
>> > On Tue, Oct 06, 2015 at 11:42:33AM -0400, Nick Bowler wrote:
>> >> On 9/24/15, Nick Bowler wrote:
>> >> > Test
Hi Greg,
On 2018-08-16, Greg KH wrote:
> I'm announcing the release of the 4.14.63 kernel.
>
> All users of the 4.14 kernel series must upgrade.
This fails to build:
CC drivers/rtc/rtc-cmos.o
In file included from /scratch_space/linux/drivers/rtc/rtc-cmos.c:45:0:
/scratch_space/lin
to accept these packets with or without the patch.
I have also been trying to test source routing options (using traceroute -g),
but haven't had much luck getting this option to work *without* AH, let alone
with.
Signed-off-by: Nick Bowler <[EMAIL PROTECTED]>
---
net/ipv4/ah4.c |2
e IPPROTO_UDP and IPPROTO_TCP instead of 17 and 6, respectively.
Instead of littering the code with #if blah #else blah, you could also simply
provide implementations for the 2.6.22 functions #if LINUX_VERSION_CODE <
KERNEL_VERSION(2,6,22).
--
Nick Bowler, Elliptic Semiconductor (http://www.e
The owner member is supposed to be set to the module implementing the
device driver, i.e., THIS_MODULE. This enables the appropriate module
link in sysfs.
Signed-off-by: Nick Bowler
---
drivers/rtc/rtc-pcf8563.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers
Set the of_match_table for this driver so that devices can be described
in the device tree.
Signed-off-by: Nick Bowler
---
drivers/rtc/rtc-pcf8563.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/drivers/rtc/rtc-pcf8563.c b/drivers/rtc/rtc-pcf8563.c
index
gt; Sorry about this people, I'll just give up and use 'git send-email' from
> now on, as it doesn't cause as many problems as my old scripts seem to.
In addition to the threading problems, patch 23/23 from the 3.0-stable
series seems to have never made it to the list. All t
On 2014-02-05 14:59 -0500, Paul Gortmaker wrote:
> From: Nick Bowler
>
>---
> This is a commit scheduled for the next v2.6.34 longterm release.
> http://git.kernel.org/?p=linux/kernel/git/paulg/longterm-queue-2.6.34.git
> If you
On 1/20/16, Nick Bowler wrote:
> Hi,
>
> On 2016-01-20, Jindal, Sonika wrote:
>> Can you please check if you have following patch:
>> "commit 3d8acd1f667b45c531401c8f0c2033072e32a05d
>> Author: Gary Wang
>> Date: Wed Dec 23 16:11:35 2015 +0800
>&
On 2016-01-21, Jindal, Sonika wrote:
> On 1/21/2016 8:59 AM, Nick Bowler wrote:
>> On 1/20/16, Nick Bowler wrote:
>>> On 2016-01-20, Jindal, Sonika wrote:
[...]
>>>> Does the same system works with any other monitor?
>>> I'll see if I can find another
On 1/28/16, Nick Bowler wrote:
> On 2016-01-21, Nick Bowler wrote:
>> On 2016-01-21, Jindal, Sonika wrote:
>>> On 1/21/2016 8:59 AM, Nick Bowler wrote:
>>>> On 1/20/16, Nick Bowler wrote:
>>>>> On 2016-01-20, Jindal, Sonika wrote:
>> [..
On 2/9/16, Ville Syrjälä wrote:
> BTW I'm not at all convinced about the current live status bit defines
> we have for g4x. Supposedly someone tested them and found that they
> don't match the spec, but IIRC when I tried them on one g4x machine
> here, they did match the spec (well, at least for t
On 9/20/19, Nick Bowler wrote:
> I hit this oops on Linux 5.3 yesterday. The crash itself occurred while
> compiling Linux (source and build dirs on NFS). Afterwards, the system
> remained mostly alive but my NFS mounts became very busted with lots
> (but not all) I/O operations
On 9/20/19, Nick Bowler wrote:
> On 9/20/19, Trond Myklebust wrote:
>> On Fri, 2019-09-20 at 14:23 -0400, Nick Bowler wrote:
>>> Not sure how reproducible this is. Since I've never seen a crash
>>> like this before it may be a regression compared to, say, Lin
Hi all,
I hit this oops on Linux 5.3 yesterday. The crash itself occurred while
compiling Linux (source and build dirs on NFS). Afterwards, the system
remained mostly alive but my NFS mounts became very busted with lots
(but not all) I/O operations appearing to hang forever.
Not sure how reprod
On 9/20/19, Trond Myklebust wrote:
> On Fri, 2019-09-20 at 14:23 -0400, Nick Bowler wrote:
>> Not sure how reproducible this is. Since I've never seen a crash
>> like this before it may be a regression compared to, say, Linux 4.19
>> but I am not certain because this p
Hi,
Testing out 4.3-rc2, first thing I notice is that the VGA output is
not working. Specifically, the display is continuously powering on
and off -- at no point is any image visible on the screen (I am expecting
to see the console output). The display connected to the HDMI output is
working fin
On 2016-01-21, Nick Bowler wrote:
> On 2016-01-21, Jindal, Sonika wrote:
>> On 1/21/2016 8:59 AM, Nick Bowler wrote:
>>> On 1/20/16, Nick Bowler wrote:
>>>> On 2016-01-20, Jindal, Sonika wrote:
> [...]
>>>>> Does the same system works with any ot
Hi,
On 2016-01-20, Jindal, Sonika wrote:
> Can you please check if you have following patch:
> "commit 3d8acd1f667b45c531401c8f0c2033072e32a05d
> Author: Gary Wang
> Date: Wed Dec 23 16:11:35 2015 +0800
>
> drm/i915: increase the tries for HDMI hotplug live status checking"
Yes, that patch se
On 2020-07-27, Al Viro wrote:
> On Thu, Jul 23, 2020 at 11:51:01AM -0400, Nick Bowler wrote:
>> Hi,
>>
>> After installing Linux 5.8-rc6, it seems cryptsetup can no longer
>> open LUKS volumes. Regardless of the entered passphrase (correct
>> or otherwise
On 2020-07-27, Al Viro wrote:
> On Mon, Jul 27, 2020 at 05:05:54PM +0100, Al Viro wrote:
>> On Thu, Jul 23, 2020 at 11:51:01AM -0400, Nick Bowler wrote:
>> > After installing Linux 5.8-rc6, it seems cryptsetup can no longer
>> > open LUKS volumes. Regardless of the
Hi,
After installing Linux 5.8-rc7 I seem to get no video output on my
NV36 card once the nouveau module is loaded. The display (connected
to the digital output) simply reports "No Signal".
I bisected to the following commit, and reverting this commit on
top of 5.8-rc7 appears to correct the iss
On 2020-07-29, Dave Airlie wrote:
> On Wed, 29 Jul 2020 at 15:05, Nick Bowler wrote:
>>
>> Hi,
>>
>> After installing Linux 5.8-rc7 I seem to get no video output on my
>> NV36 card once the nouveau module is loaded. The display (connected
>> to the di
fish-xts256b N/A N/A
aes-xts512b N/A N/A
serpent-xts512b N/A N/A
twofish-xts512b N/A N/A
Cheers,
--
Nick Bowler
05-28T16:00:30-04:00 emergent kernel: CS: 0010 DS: ES: CR0:
80050033
2019-05-28T16:00:30-04:00 emergent kernel: CR2: 0098 CR3:
54043000 CR4: 000406e0
[ and on and on and on on ... ]
--
Nick Bowler
On 2019-05-29, Olga Kornievskaia wrote:
> On Wed, May 29, 2019 at 1:14 PM Trond Myklebust
> wrote:
>>
>> On Wed, 2019-05-29 at 11:10 -0400, Nick Bowler wrote:
>> > Hi,
>> >
>> > I upgraded to Linux 5.1.5 on one machine yesterday, and this morn
On 2019-06-03, Nick Bowler wrote:
> On 2019-05-29, Olga Kornievskaia wrote:
>> On Wed, May 29, 2019 at 1:14 PM Trond Myklebust
>>> OK, I think this is the same problem that Olga was seeing (Cced), and
>>> it looks like I missed the use-after-free issue when the serv
Hi,
Any ideas on this issue? Are there any additional tests I can perform
to help debug this?
On 2017-11-05 11:41 -0500, Nick Bowler wrote:
> I completed bisecting this issue. See below.
>
> On 2017-11-02, Nick Bowler wrote:
> > ~50% of the time after a hotplug, there is a ve
On 2017-12-04 10:04 +, Jose Abreu wrote:
> On 03-12-2017 05:20, Nick Bowler wrote:
> > I brought the original test equipment back to the setup so I can
> > see the video and pink bar again. The symptoms remain the same
> > (unexpected size, pink bar, and no audio).
&g
of the for loop execute before the condition
> becomes true?
Judging from the log posted elsethread (where I added extra printouts),
it seems to consistently become true on the second iteration.
I will try to rule out read side effects by replacing the polling loop
with an unconditional delay.
On 2017-12-04 21:34 +0200, Laurent Pinchart wrote:
> On Monday, 4 December 2017 21:30:01 EET Nick Bowler wrote:
> > On 2017-12-04 21:06 +0200, Laurent Pinchart wrote:
> > > As you reported that the PLL lock failure message is not printed, the
> > > failure can only come
On 2017-12-04 13:33 -0500, Nick Bowler wrote:
> On 2017-12-04 10:04 +, Jose Abreu wrote:
> > Hmmm, my first thought was that audio is being configured first
> > because of the phy lock wait time, I've seen this happening before.
> >
> > Lets try this:
>
Hi,
On 11/27/17, Laurent Pinchart wrote:
> The driver should print a "PHY PLL failed to lock" error message to the
> kernel log in that case. Nick, does that happen on your system ?
I will try to test the other things later today, but after bootup there
were no messages whatsoever printed to the
On 2017-11-27 11:00 +0200, Laurent Pinchart wrote:
> On Monday, 27 November 2017 06:05:03 EET Archit Taneja wrote:
> > On 2017-11-05 11:41 -0500, Nick Bowler wrote:
[...]
> > > Bisection implicates the following commit:
> > >
> > > 181e0ef092a4952aa523c5b9cb21
Hi,
On 2017-11-27 22:30 -0500, Nick Bowler wrote:
> A note about the test setup: I had to remove the test equipment so I
> no longer have any information about the video mode from the sink side
> (like in the photos). Thus, with the current setup, I am using the
> presense or absense
Hi Jose,
On 2017-12-02 17:11 +, Jose Abreu wrote:
> On 01-12-2017 00:11, Nick Bowler wrote:
> > Another data point... the following patch appears sufficient to
> > restore working behaviour.
[...]
> I don't think you can do this. The phy pll lock check is
> recom
77 matches
Mail list logo
