> "Vineet" == Vineet Gupta writes:
> On 1/7/21 9:04 AM, Petr Mladek wrote:
>> On Thu 2021-01-07 08:43:16, Vineet Gupta wrote:
>>> Hi John,
>>>
>>> On 1/7/21 1:02 AM, John Ogness wrote:
Hi Vineet,
On 2021-01-06, Vineet Gupta wrote:
> This breaks ARC booting (no o
On Thu 2021-01-07 21:18:20, Vineet Gupta wrote:
> On 1/7/21 7:48 PM, Sergey Senozhatsky wrote:
> > On (21/01/07 09:58), Vineet Gupta wrote:
> > > On 1/7/21 9:04 AM, Petr Mladek wrote:
> > > > On Thu 2021-01-07 08:43:16, Vineet Gupta wrote:
> > > > > Hi John,
> > > > >
> > > > > On 1/7/21 1:02 AM,
On 1/7/21 7:48 PM, Sergey Senozhatsky wrote:
On (21/01/07 09:58), Vineet Gupta wrote:
On 1/7/21 9:04 AM, Petr Mladek wrote:
On Thu 2021-01-07 08:43:16, Vineet Gupta wrote:
Hi John,
On 1/7/21 1:02 AM, John Ogness wrote:
Hi Vineet,
On 2021-01-06, Vineet Gupta wrote:
This breaks ARC booting
On (21/01/07 09:58), Vineet Gupta wrote:
> On 1/7/21 9:04 AM, Petr Mladek wrote:
> > On Thu 2021-01-07 08:43:16, Vineet Gupta wrote:
> > > Hi John,
> > >
> > > On 1/7/21 1:02 AM, John Ogness wrote:
> > > > Hi Vineet,
> > > >
> > > > On 2021-01-06, Vineet Gupta wrote:
> > > > > This breaks ARC bo
On 1/7/21 9:04 AM, Petr Mladek wrote:
On Thu 2021-01-07 08:43:16, Vineet Gupta wrote:
Hi John,
On 1/7/21 1:02 AM, John Ogness wrote:
Hi Vineet,
On 2021-01-06, Vineet Gupta wrote:
This breaks ARC booting (no output on console).
Could you provide the kernel boot arguments that you use? This
On Thu 2021-01-07 08:43:16, Vineet Gupta wrote:
> Hi John,
>
> On 1/7/21 1:02 AM, John Ogness wrote:
> > Hi Vineet,
> >
> > On 2021-01-06, Vineet Gupta wrote:
> > > This breaks ARC booting (no output on console).
> >
> > Could you provide the kernel boot arguments that you use? This series is
>
Hi John,
On 1/7/21 1:02 AM, John Ogness wrote:
Hi Vineet,
On 2021-01-06, Vineet Gupta wrote:
This breaks ARC booting (no output on console).
Could you provide the kernel boot arguments that you use? This series is
partly about addressing users that have used boot arguments that are
technica
Vineet, All,
On 2021-01-06 15:36 -0800, Vineet Gupta spake thusly:
> On 11/11/20 5:54 AM, Petr Mladek wrote:
[--SNIP--]
> >Make sure that stdin, stdout, stderr, and /dev/console are always
> >available by a fallback to the existing ttynull driver. It has
> >been implemented for exactly this purpos
Hi John,
On 7/1/21 7:02 pm, John Ogness wrote:
On 2021-01-06, Vineet Gupta wrote:
This breaks ARC booting (no output on console).
Could you provide the kernel boot arguments that you use? This series is
partly about addressing users that have used boot arguments that are
technically incorrec
On Wed 2021-01-06 15:36:36, Vineet Gupta wrote:
> +CC Buildroot folks
>
> Hi Petr,
>
> On 11/11/20 5:54 AM, Petr Mladek wrote:
> > stdin, stdout, and stderr standard I/O stream are created for the init
> > process. They are not available when there is no console registered
> > for /dev/console. I
[CC'in linux-um since there is a similar issue]
On Thu, Jan 7, 2021 at 12:38 AM Vineet Gupta wrote:
>
> +CC Buildroot folks
>
> Hi Petr,
>
> On 11/11/20 5:54 AM, Petr Mladek wrote:
> > stdin, stdout, and stderr standard I/O stream are created for the init
> > process. They are not available wh
Hi Vineet,
On 2021-01-06, Vineet Gupta wrote:
> This breaks ARC booting (no output on console).
Could you provide the kernel boot arguments that you use? This series is
partly about addressing users that have used boot arguments that are
technically incorrect (even if had worked). Seeing the boo
+CC Buildroot folks
Hi Petr,
On 11/11/20 5:54 AM, Petr Mladek wrote:
stdin, stdout, and stderr standard I/O stream are created for the init
process. They are not available when there is no console registered
for /dev/console. It might lead to a crash when the init process
tries to use them, see
On Thu 2020-11-12 10:45:46, Sergey Senozhatsky wrote:
> On (20/11/12 09:17), Sergey Senozhatsky wrote:
> > On (20/11/11 14:54), Petr Mladek wrote:
> > [..]
> > > diff --git a/init/main.c b/init/main.c
> > > index 130376ec10ba..24413c055a85 100644
> > > --- a/init/main.c
> > > +++ b/init/main.c
> >
On (20/11/12 09:17), Sergey Senozhatsky wrote:
> On (20/11/11 14:54), Petr Mladek wrote:
> [..]
> > diff --git a/init/main.c b/init/main.c
> > index 130376ec10ba..24413c055a85 100644
> > --- a/init/main.c
> > +++ b/init/main.c
> > @@ -1470,8 +1470,14 @@ void __init console_on_rootfs(void)
> > s
On Wed, Nov 11, 2020 at 02:54:49PM +0100, Petr Mladek wrote:
> stdin, stdout, and stderr standard I/O stream are created for the init
> process. They are not available when there is no console registered
> for /dev/console. It might lead to a crash when the init process
> tries to use them, see the
On (20/11/11 14:54), Petr Mladek wrote:
> stdin, stdout, and stderr standard I/O stream are created for the init
> process. They are not available when there is no console registered
> for /dev/console. It might lead to a crash when the init process
> tries to use them, see the commit 48021f9813088
On (20/11/11 14:54), Petr Mladek wrote:
[..]
> diff --git a/init/main.c b/init/main.c
> index 130376ec10ba..24413c055a85 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -1470,8 +1470,14 @@ void __init console_on_rootfs(void)
> struct file *file = filp_open("/dev/console", O_RDWR, 0);
>
On Wed, Nov 11, 2020 at 02:54:49PM +0100, Petr Mladek wrote:
> stdin, stdout, and stderr standard I/O stream are created for the init
> process. They are not available when there is no console registered
> for /dev/console. It might lead to a crash when the init process
> tries to use them, see the
stdin, stdout, and stderr standard I/O stream are created for the init
process. They are not available when there is no console registered
for /dev/console. It might lead to a crash when the init process
tries to use them, see the commit 48021f98130880dd742 ("printk: handle
blank console arguments
20 matches
Mail list logo
