On Mon, Jul 01, 2019 at 08:47:30PM -0700, Paul E. McKenney wrote:
> On Mon, Jul 01, 2019 at 12:04:13AM -0400, Joel Fernandes (Google) wrote:
> > The t->rcu_read_unlock_special union's need_qs bit can be set by the
> > scheduler tick (in rcu_flavor_sched_clock_irq) to indicate that help is
> >
On Mon, Jul 01, 2019 at 12:04:13AM -0400, Joel Fernandes (Google) wrote:
> The t->rcu_read_unlock_special union's need_qs bit can be set by the
> scheduler tick (in rcu_flavor_sched_clock_irq) to indicate that help is
> needed from the rcu_read_unlock path. When this help arrives however, we
> can
On Mon, Jul 01, 2019 at 12:04:13AM -0400, Joel Fernandes (Google) wrote:
> The t->rcu_read_unlock_special union's need_qs bit can be set by the
> scheduler tick (in rcu_flavor_sched_clock_irq) to indicate that help is
> needed from the rcu_read_unlock path. When this help arrives however, we
> can
The t->rcu_read_unlock_special union's need_qs bit can be set by the
scheduler tick (in rcu_flavor_sched_clock_irq) to indicate that help is
needed from the rcu_read_unlock path. When this help arrives however, we
can do better to speed up the quiescent state reporting which if
Hello Beloved,
my name is Mrs. Evelyn Allyson. I was diagnosed with cancer about 2
years ago, and I am receiving treatment for it, but now the doctors
are saying I have a short time to live. I had no children of my own
with my late husband. I have decided to donate US$ 10.5M (Ten Million
Five
Hello Beloved,
my name is Mrs. Evelyn Allyson. I was diagnosed with cancer about 2
years ago, and I am receiving treatment for it, but now the doctors
are saying I have a short time to live. I had no children of my own
with my late husband. I have decided to donate US$ 10.5M (Ten Million
Five
Hi,
Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
dirty and access bits if CPU sets them after pmdp dereference, but
before set_pmd_at().
The bug doesn't lead to user-visible misbehaviour in current kernel, but
fixing this would be critical for future work on THP: both
Hi,
Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
dirty and access bits if CPU sets them after pmdp dereference, but
before set_pmd_at().
The bug doesn't lead to user-visible misbehaviour in current kernel, but
fixing this would be critical for future work on THP: both
On Thursday 15 June 2017 02:18 PM, Kirill A. Shutemov wrote:
O
I am not suggesting we don't do the invalidate (the need for that is
documented in __split_huge_pmd_locked(). I am suggesting we need a new
interface, something like Andrea suggested.
old_pmd = pmdp_establish(pmd_mknotpresent());
On Thursday 15 June 2017 02:18 PM, Kirill A. Shutemov wrote:
O
I am not suggesting we don't do the invalidate (the need for that is
documented in __split_huge_pmd_locked(). I am suggesting we need a new
interface, something like Andrea suggested.
old_pmd = pmdp_establish(pmd_mknotpresent());
On Thu, Jun 15, 2017 at 06:35:21AM +0530, Aneesh Kumar K.V wrote:
>
>
> On Wednesday 14 June 2017 10:25 PM, Will Deacon wrote:
> > Hi Aneesh,
> >
> > On Wed, Jun 14, 2017 at 08:55:26PM +0530, Aneesh Kumar K.V wrote:
> > > On Wednesday 14 June 2017 07:21 PM, Kirill A. Shutemov wrote:
> > > >
On Thu, Jun 15, 2017 at 06:35:21AM +0530, Aneesh Kumar K.V wrote:
>
>
> On Wednesday 14 June 2017 10:25 PM, Will Deacon wrote:
> > Hi Aneesh,
> >
> > On Wed, Jun 14, 2017 at 08:55:26PM +0530, Aneesh Kumar K.V wrote:
> > > On Wednesday 14 June 2017 07:21 PM, Kirill A. Shutemov wrote:
> > > >
On Thursday 15 June 2017 06:35 AM, Aneesh Kumar K.V wrote:
W.r.t pmdp_invalidate() usage, I was wondering whether we can do that
early in __split_huge_pmd_locked().
BTW by moving pmdp_invalidate early, we can then get rid of
pmdp_huge_split_prepare(vma, haddr, pmd);
On Thursday 15 June 2017 06:35 AM, Aneesh Kumar K.V wrote:
W.r.t pmdp_invalidate() usage, I was wondering whether we can do that
early in __split_huge_pmd_locked().
BTW by moving pmdp_invalidate early, we can then get rid of
pmdp_huge_split_prepare(vma, haddr, pmd);
On Wednesday 14 June 2017 10:30 PM, Vlastimil Babka wrote:
On 06/14/2017 06:55 PM, Will Deacon wrote:
May be we should relook at pmd PTE udpate interface. We really need an
interface that can update pmd entries such that we don't clear it in
between. IMHO, we can avoid the pmdp_invalidate()
On Wednesday 14 June 2017 10:30 PM, Vlastimil Babka wrote:
On 06/14/2017 06:55 PM, Will Deacon wrote:
May be we should relook at pmd PTE udpate interface. We really need an
interface that can update pmd entries such that we don't clear it in
between. IMHO, we can avoid the pmdp_invalidate()
On Wednesday 14 June 2017 10:25 PM, Will Deacon wrote:
Hi Aneesh,
On Wed, Jun 14, 2017 at 08:55:26PM +0530, Aneesh Kumar K.V wrote:
On Wednesday 14 June 2017 07:21 PM, Kirill A. Shutemov wrote:
Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
dirty and access bits if
On Wednesday 14 June 2017 10:25 PM, Will Deacon wrote:
Hi Aneesh,
On Wed, Jun 14, 2017 at 08:55:26PM +0530, Aneesh Kumar K.V wrote:
On Wednesday 14 June 2017 07:21 PM, Kirill A. Shutemov wrote:
Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
dirty and access bits if
On 06/14/2017 06:55 PM, Will Deacon wrote:
>>
>> May be we should relook at pmd PTE udpate interface. We really need an
>> interface that can update pmd entries such that we don't clear it in
>> between. IMHO, we can avoid the pmdp_invalidate() completely, if we can
>> switch from a pmd PTE entry
On 06/14/2017 06:55 PM, Will Deacon wrote:
>>
>> May be we should relook at pmd PTE udpate interface. We really need an
>> interface that can update pmd entries such that we don't clear it in
>> between. IMHO, we can avoid the pmdp_invalidate() completely, if we can
>> switch from a pmd PTE entry
Hi Aneesh,
On Wed, Jun 14, 2017 at 08:55:26PM +0530, Aneesh Kumar K.V wrote:
> On Wednesday 14 June 2017 07:21 PM, Kirill A. Shutemov wrote:
> >Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
> >dirty and access bits if CPU sets them after pmdp dereference, but
> >before
Hi Aneesh,
On Wed, Jun 14, 2017 at 08:55:26PM +0530, Aneesh Kumar K.V wrote:
> On Wednesday 14 June 2017 07:21 PM, Kirill A. Shutemov wrote:
> >Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
> >dirty and access bits if CPU sets them after pmdp dereference, but
> >before
On Wednesday 14 June 2017 07:21 PM, Kirill A. Shutemov wrote:
Hi,
Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
dirty and access bits if CPU sets them after pmdp dereference, but
before set_pmd_at().
The bug doesn't lead to user-visible misbehaviour in current kernel,
On Wednesday 14 June 2017 07:21 PM, Kirill A. Shutemov wrote:
Hi,
Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
dirty and access bits if CPU sets them after pmdp dereference, but
before set_pmd_at().
The bug doesn't lead to user-visible misbehaviour in current kernel,
Hi Kirill,
On Wed, 14 Jun 2017 16:51:40 +0300
"Kirill A. Shutemov" wrote:
> Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
> dirty and access bits if CPU sets them after pmdp dereference, but
> before set_pmd_at().
>
> The bug doesn't
Hi Kirill,
On Wed, 14 Jun 2017 16:51:40 +0300
"Kirill A. Shutemov" wrote:
> Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
> dirty and access bits if CPU sets them after pmdp dereference, but
> before set_pmd_at().
>
> The bug doesn't lead to user-visible misbehaviour in
Hi,
Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
dirty and access bits if CPU sets them after pmdp dereference, but
before set_pmd_at().
The bug doesn't lead to user-visible misbehaviour in current kernel, but
fixing this would be critical for future work on THP: both
Hi,
Vlastimil noted that pmdp_invalidate() is not atomic and we can loose
dirty and access bits if CPU sets them after pmdp dereference, but
before set_pmd_at().
The bug doesn't lead to user-visible misbehaviour in current kernel, but
fixing this would be critical for future work on THP: both
Hi,
I mentioned overheating problem of Odroid XU3-Lite after enabling
cpufreq-dt (when busy in a quite warm room). [0]
The patchset tries to fix this by adding CPU cooling device.
Unfortunately apparently I screwed something because on next-20160216
it does not help.
The fan works at full but
Hi,
I mentioned overheating problem of Odroid XU3-Lite after enabling
cpufreq-dt (when busy in a quite warm room). [0]
The patchset tries to fix this by adding CPU cooling device.
Unfortunately apparently I screwed something because on next-20160216
it does not help.
The fan works at full but
An update: see there:
http://ffmpeg.org/pipermail/ffmpeg-devel/2015-July/175796.html
--
Bluecherry developer.
--
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
An update: see there:
http://ffmpeg.org/pipermail/ffmpeg-devel/2015-July/175796.html
--
Bluecherry developer.
--
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
An update with a request for help.
Asking for help with h264 headers generation. Both copying headers
from similar videos and porting headers generation code from reference
driver don't work for me (ref driver is weird and very complicated, so
porting involved importing of lots of code, but still
An update with a request for help.
Asking for help with h264 headers generation. Both copying headers
from similar videos and porting headers generation code from reference
driver don't work for me (ref driver is weird and very complicated, so
porting involved importing of lots of code, but still
On Fri, Jul 3, 2015 at 5:23 PM, Andrey Utkin
wrote:
> Up... we are moving much slower than we expected, desperately needing help.
>
> Running reference driver with Ubuntu 9 (with kernel 2.6.28.10) with
> 16-port card shows that the
> reference driver fails to work with it correctly. Also that
On Fri, Jul 3, 2015 at 5:23 PM, Andrey Utkin
andrey.ut...@corp.bluecherry.net wrote:
Up... we are moving much slower than we expected, desperately needing help.
Running reference driver with Ubuntu 9 (with kernel 2.6.28.10) with
16-port card shows that the
reference driver fails to work with
On Wed, Jun 3, 2015 at 1:03 AM, Andrey Utkin
wrote:
> Hi! I am working on making a Linux driver for TW5864-based video
> capture and encoding PCI boards. The driver is to be submitted for
> inclusion to Linux upstream.
> The following two links are links to boards available for buying:
>
On Wed, Jun 3, 2015 at 1:03 AM, Andrey Utkin
andrey.ut...@corp.bluecherry.net wrote:
Hi! I am working on making a Linux driver for TW5864-based videoaudio
capture and encoding PCI boards. The driver is to be submitted for
inclusion to Linux upstream.
The following two links are links to boards
Hi! I am working on making a Linux driver for TW5864-based video
capture and encoding PCI boards. The driver is to be submitted for
inclusion to Linux upstream.
The following two links are links to boards available for buying:
http://www.provideo.com.tw/web/DVR%20Card_TW-310.htm
Hi! I am working on making a Linux driver for TW5864-based videoaudio
capture and encoding PCI boards. The driver is to be submitted for
inclusion to Linux upstream.
The following two links are links to boards available for buying:
http://www.provideo.com.tw/web/DVR%20Card_TW-310.htm
TL;DR:
media: cx23885 broken by commit 453afdd9ce33293f640e84dc17e5f366701516e8
"[media] cx23885: convert to vb2"
Broken mean: until this commit driver was rock solid, after I started to
receive
IOMMU related warnings and sometimes card stopped working
Full report:
On 09.01.2015 10:34,
TL;DR:
media: cx23885 broken by commit 453afdd9ce33293f640e84dc17e5f366701516e8
[media] cx23885: convert to vb2
Broken mean: until this commit driver was rock solid, after I started to
receive
IOMMU related warnings and sometimes card stopped working
Full report:
On 09.01.2015 10:34,
Hello.
I would like to receive comments, suggestions and criticism
on my plan to bisect following problem.
History of problem:
1) I own computer based on AMD Athlon(tm) II X2 240e Processor on Asus
M5A97 LE R2.0 motherboard
2) I own TBS6981 card (Dual DVB-S/S2 PCIe receiver, in kernel driver)
Hello.
I would like to receive comments, suggestions and criticism
on my plan to bisect following problem.
History of problem:
1) I own computer based on AMD Athlon(tm) II X2 240e Processor on Asus
M5A97 LE R2.0 motherboard
2) I own TBS6981 card (Dual DVB-S/S2 PCIe receiver, in kernel driver)
Hi,
In the context of solving the below original issue, I came across
below error while I was running "sudo make install". Wondering what
the below error means?
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for
module r8169
-Madhu
On Wed, Jan 22, 2014 at 11:11 PM, Mark
Hi,
In the context of solving the below original issue, I came across
below error while I was running sudo make install. Wondering what
the below error means?
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for
module r8169
-Madhu
On Wed, Jan 22, 2014 at 11:11 PM, Mark
On Wed, Jan 22, 2014 at 7:47 AM, Madhusudhan Rao Sripalle
wrote:
> I have attached the boot directory contents, /boot/grub/grub.cfg and
> /etc/default/grub contents. Also attached the mount points on the
> system.
>
> On Wed, Jan 22, 2014 at 8:39 PM, Mark Knecht wrote:
>> On Wed, Jan 22, 2014 at
I have attached the boot directory contents, /boot/grub/grub.cfg and
/etc/default/grub contents. Also attached the mount points on the
system.
On Wed, Jan 22, 2014 at 8:39 PM, Mark Knecht wrote:
> On Wed, Jan 22, 2014 at 7:05 AM, Madhusudhan Rao Sripalle
> wrote:
>> The grub file is
On Wed, Jan 22, 2014 at 4:05 PM, Madhusudhan Rao Sripalle
wrote:
> The grub file is /boot/grub/grub.cfg. The newly built kernel is
> reflected in grub.cfg. But, the grub doesn't display this new kernel
> at the boot time. I tried few tips from the web. It is no help. That
> is why I sought help
The grub file is /boot/grub/grub.cfg. The newly built kernel is
reflected in grub.cfg. But, the grub doesn't display this new kernel
at the boot time. I tried few tips from the web. It is no help. That
is why I sought help from this forum.
On Wed, Jan 22, 2014 at 8:25 PM, Mark Knecht wrote:
> On
On Wed, Jan 22, 2014 at 7:05 AM, Madhusudhan Rao Sripalle
wrote:
> The grub file is /boot/grub/grub.cfg. The newly built kernel is
> reflected in grub.cfg. But, the grub doesn't display this new kernel
> at the boot time. I tried few tips from the web. It is no help. That
> is why I sought help
On Wed, Jan 22, 2014 at 6:34 AM, Madhusudhan Rao Sripalle
wrote:
> Thanks to Randy and Ryan for the responses. The pointers are really
> helpful. Currently I am facing an issue with Ubuntu's grub not
> displaying the newly built kernel.
>
> Existing kernel on the ubuntu system is
Thanks to Randy and Ryan for the responses. The pointers are really
helpful. Currently I am facing an issue with Ubuntu's grub not
displaying the newly built kernel.
Existing kernel on the ubuntu system is 3.2.0-23-generic. While the
new one is 3.11.10. The Grub has/displays fedora and ubuntu
Thanks to Randy and Ryan for the responses. The pointers are really
helpful. Currently I am facing an issue with Ubuntu's grub not
displaying the newly built kernel.
Existing kernel on the ubuntu system is 3.2.0-23-generic. While the
new one is 3.11.10. The Grub has/displays fedora and ubuntu
On Wed, Jan 22, 2014 at 6:34 AM, Madhusudhan Rao Sripalle
madhu.sripa...@gmail.com wrote:
Thanks to Randy and Ryan for the responses. The pointers are really
helpful. Currently I am facing an issue with Ubuntu's grub not
displaying the newly built kernel.
Existing kernel on the ubuntu system
On Wed, Jan 22, 2014 at 7:05 AM, Madhusudhan Rao Sripalle
madhu.sripa...@gmail.com wrote:
The grub file is /boot/grub/grub.cfg. The newly built kernel is
reflected in grub.cfg. But, the grub doesn't display this new kernel
at the boot time. I tried few tips from the web. It is no help. That
is
The grub file is /boot/grub/grub.cfg. The newly built kernel is
reflected in grub.cfg. But, the grub doesn't display this new kernel
at the boot time. I tried few tips from the web. It is no help. That
is why I sought help from this forum.
On Wed, Jan 22, 2014 at 8:25 PM, Mark Knecht
On Wed, Jan 22, 2014 at 4:05 PM, Madhusudhan Rao Sripalle
madhu.sripa...@gmail.com wrote:
The grub file is /boot/grub/grub.cfg. The newly built kernel is
reflected in grub.cfg. But, the grub doesn't display this new kernel
at the boot time. I tried few tips from the web. It is no help. That
is
I have attached the boot directory contents, /boot/grub/grub.cfg and
/etc/default/grub contents. Also attached the mount points on the
system.
On Wed, Jan 22, 2014 at 8:39 PM, Mark Knecht markkne...@gmail.com wrote:
On Wed, Jan 22, 2014 at 7:05 AM, Madhusudhan Rao Sripalle
On Wed, Jan 22, 2014 at 7:47 AM, Madhusudhan Rao Sripalle
madhu.sripa...@gmail.com wrote:
I have attached the boot directory contents, /boot/grub/grub.cfg and
/etc/default/grub contents. Also attached the mount points on the
system.
On Wed, Jan 22, 2014 at 8:39 PM, Mark Knecht
You can just go to http://www.kernel.org to get the Linux kernel source code.
If you want to use a certain Linux distribution, search "Linux distributions"
using your favorite Web search engine.
Sent from my iPad
> On Jan 18, 2014, at 2:16 PM, Randy Dunlap wrote:
>
>> On 01/18/2014 09:34 AM,
On 01/18/2014 09:34 AM, Madhusudhan Rao Sripalle wrote:
> Hi,
>
> I am an expert of HP-UX (kernel and drivers), while being novice at
> linux. I am currently looking ways for quick ramp up so that I could
> contribute to linux community.
>
> Kindly provide pointers starting from where I could
Hi,
I am an expert of HP-UX (kernel and drivers), while being novice at
linux. I am currently looking ways for quick ramp up so that I could
contribute to linux community.
Kindly provide pointers starting from where I could get the kernel
sources. Appreciate help in advance.
-Madhu
--
To
Hi,
I am an expert of HP-UX (kernel and drivers), while being novice at
linux. I am currently looking ways for quick ramp up so that I could
contribute to linux community.
Kindly provide pointers starting from where I could get the kernel
sources. Appreciate help in advance.
-Madhu
--
To
On 01/18/2014 09:34 AM, Madhusudhan Rao Sripalle wrote:
Hi,
I am an expert of HP-UX (kernel and drivers), while being novice at
linux. I am currently looking ways for quick ramp up so that I could
contribute to linux community.
Kindly provide pointers starting from where I could get the
You can just go to http://www.kernel.org to get the Linux kernel source code.
If you want to use a certain Linux distribution, search Linux distributions
using your favorite Web search engine.
Sent from my iPad
On Jan 18, 2014, at 2:16 PM, Randy Dunlap rdun...@infradead.org wrote:
On
Dear All,
I need help with following problem.
We use kernel 2.4.32 ,
Motherboard is Tyan k8SE which uses Nvidia Nforce 2200 (CK8-04) chips,
we have 2 Dualcore opterons and 4G ram , and SATA disk WD1600YS-01S .
Sometimes (once a 3-4 weeks) the computer stops responding with following
message:
Dear All,
I need help with following problem.
We use kernel 2.4.32 ,
Motherboard is Tyan k8SE which uses Nvidia Nforce 2200 (CK8-04) chips,
we have 2 Dualcore opterons and 4G ram , and SATA disk WD1600YS-01S .
Sometimes (once a 3-4 weeks) the computer stops responding with following
message:
[EMAIL PROTECTED] wrote:
I am currently writing some code to send some ATA commands directly to
the drive using ioctl and SG_IO which seems to work fine. However I
also need to read the ATA status register values in real time which I
am unsure how to do.
I have seen in the libata developers
[EMAIL PROTECTED] wrote:
I am currently writing some code to send some ATA commands directly to
the drive using ioctl and SG_IO which seems to work fine. However I
also need to read the ATA status register values in real time which I
am unsure how to do.
I have seen in the libata developers
> >
> >
> > > WARNING: vmlinux.o(.text+0x43524): Section mismatch: reference to
> > > .init.text: (between 'timer_cpu_notify' and 'msleep')
> > > WARNING: vmlinux.o(.text+0x4c6f6): Section mismatch: reference to
> > > .init.text: (between 'rcu_cpu_notify' and 'wakeme_after_rcu')
> > > WARNING:
On Sat, Jan 19, 2008 at 11:52:55AM -0800, Randy Dunlap wrote:
> On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
>
> > kbuild emit section mismatch warnings when it detects that someone does a
> > call from a non-init section to a init section.
> > The rationale here is that the init section
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
> kbuild emit section mismatch warnings when it detects that someone does a
> call from a non-init section to a init section.
> The rationale here is that the init section are discarded at runtime and
> if this call happens after the init
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
kbuild emit section mismatch warnings when it detects that someone does a
call from a non-init section to a init section.
The rationale here is that the init section are discarded at runtime and
if this call happens after the init section
On Sat, Jan 19, 2008 at 11:52:55AM -0800, Randy Dunlap wrote:
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
kbuild emit section mismatch warnings when it detects that someone does a
call from a non-init section to a init section.
The rationale here is that the init section are
WARNING: vmlinux.o(.text+0x43524): Section mismatch: reference to
.init.text: (between 'timer_cpu_notify' and 'msleep')
WARNING: vmlinux.o(.text+0x4c6f6): Section mismatch: reference to
.init.text: (between 'rcu_cpu_notify' and 'wakeme_after_rcu')
WARNING:
On Thu, Jan 10, 2008 at 11:19:18AM -0800, Randy Dunlap wrote:
> On Wed, 9 Jan 2008 22:25:42 -0800 Randy Dunlap wrote:
>
> > On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
> >
> >
> > > This is the current list of warnings
> >
> > Sam,
> >
> > Several of these are due to driver variable
On Thu, Jan 10, 2008 at 11:19:18AM -0800, Randy Dunlap wrote:
On Wed, 9 Jan 2008 22:25:42 -0800 Randy Dunlap wrote:
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
This is the current list of warnings
Sam,
Several of these are due to driver variable names not matching
On Wed, Jan 09, 2008 at 10:25:42PM -0800, Randy Dunlap wrote:
> On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
>
>
> > This is the current list of warnings
>
> Sam,
>
> Several of these are due to driver variable names not matching
> the whitelisted names in modpost. I have patches for
On Wed, 9 Jan 2008 22:25:42 -0800 Randy Dunlap wrote:
> On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
>
>
> > This is the current list of warnings
>
> Sam,
>
> Several of these are due to driver variable names not matching
> the whitelisted names in modpost. I have patches for the
On Wed, 9 Jan 2008 22:25:42 -0800 Randy Dunlap wrote:
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
This is the current list of warnings
Sam,
Several of these are due to driver variable names not matching
the whitelisted names in modpost. I have patches for the ones
that I
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
> This is the current list of warnings
Sam,
Several of these are due to driver variable names not matching
the whitelisted names in modpost. I have patches for the ones
that I have identified so far. And I have patches for a few of
the
On Sun, 6 Jan 2008 15:07:28 +0100 Sam Ravnborg wrote:
This is the current list of warnings
Sam,
Several of these are due to driver variable names not matching
the whitelisted names in modpost. I have patches for the ones
that I have identified so far. And I have patches for a few of
the
kbuild emit section mismatch warnings when it detects that someone does a
call from a non-init section to a init section.
The rationale here is that the init section are discarded at runtime and
if this call happens after the init section has gone we have an oops.
This check is planned to be
kbuild emit section mismatch warnings when it detects that someone does a
call from a non-init section to a init section.
The rationale here is that the init section are discarded at runtime and
if this call happens after the init section has gone we have an oops.
This check is planned to be
On 9/28/07, Frans Pop <[EMAIL PROTECTED]> wrote:
> Current help for CONFIG_UEVENT_HELPER_PATH is:
>Path to uevent helper program forked by the kernel for
>every uevent.
> With default value of /sbin/hotplug.
>
> Help! I don't have /sbin/hotplug (Debian unstable, using udev).
> What do I do
On 9/28/07, Frans Pop [EMAIL PROTECTED] wrote:
Current help for CONFIG_UEVENT_HELPER_PATH is:
Path to uevent helper program forked by the kernel for
every uevent.
With default value of /sbin/hotplug.
Help! I don't have /sbin/hotplug (Debian unstable, using udev).
What do I do now?
Current help for CONFIG_UEVENT_HELPER_PATH is:
Path to uevent helper program forked by the kernel for
every uevent.
With default value of /sbin/hotplug.
Help! I don't have /sbin/hotplug (Debian unstable, using udev).
What do I do now? Will my hardware be unsupported because I don't have
Current help for CONFIG_UEVENT_HELPER_PATH is:
Path to uevent helper program forked by the kernel for
every uevent.
With default value of /sbin/hotplug.
Help! I don't have /sbin/hotplug (Debian unstable, using udev).
What do I do now? Will my hardware be unsupported because I don't have
Jan Engelhardt wrote:
I am not sure (would have to check again), but I believe both opensuse and
fedora (the latter of which uses LVM for all partitions by default) have
that working, while still using GRUB.
Keyword: partitions. I.e., they partition the hard drive (so that the first
31
On Jun 16 2007 11:38, Alexander E. Patrakov wrote:
> Jan Engelhardt wrote:
>> On Jun 15 2007 16:03, Christian Schmidt wrote:
>
>> > Thanks for the clarification. I didn't use LVM on the device on purpose,
>> > as root on LVM requires initrd (which I strongly dislike as
>> >
On Jun 16 2007 11:38, Alexander E. Patrakov wrote:
Jan Engelhardt wrote:
On Jun 15 2007 16:03, Christian Schmidt wrote:
Thanks for the clarification. I didn't use LVM on the device on purpose,
as root on LVM requires initrd (which I strongly dislike as
yet-another-point-of-failure). As
Jan Engelhardt wrote:
I am not sure (would have to check again), but I believe both opensuse and
fedora (the latter of which uses LVM for all partitions by default) have
that working, while still using GRUB.
Keyword: partitions. I.e., they partition the hard drive (so that the first
31
Jan Engelhardt wrote:
On Jun 15 2007 16:03, Christian Schmidt wrote:
Thanks for the clarification. I didn't use LVM on the device on purpose,
as root on LVM requires initrd (which I strongly dislike as
yet-another-point-of-failure). As LVM is on the large partition anyway
I'll just add the
On Jun 15 2007 16:03, Christian Schmidt wrote:
>Hi Andi,
>
>Andi Kleen wrote:
>> Christian Schmidt <[EMAIL PROTECTED]> writes:
>>> Where is the inherent limit? The partitioning software, or partitioning
>>> all by itself?
>>
>> DOS style partitioning don't support more than 2TB. You either need
Hi Andi,
Andi Kleen wrote:
> Christian Schmidt <[EMAIL PROTECTED]> writes:
>> Where is the inherent limit? The partitioning software, or partitioning
>> all by itself?
>
> DOS style partitioning don't support more than 2TB. You either need
> to use EFI partitions (e.g. using parted) or LVM.
Christian Schmidt <[EMAIL PROTECTED]> writes:
>
> Where is the inherent limit? The partitioning software, or partitioning
> all by itself?
DOS style partitioning don't support more than 2TB. You either need
to use EFI partitions (e.g. using parted) or LVM. Since parted's
user interface is not
Hi everyone,
I added a drive to a linux software RAID-5 last night. Now that worked
fine... until I changed the partition table.
Disk /dev/md_d5: 2499.9 GB, 240978560 bytes
2 heads, 4 sectors/track, 610349360 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start
Hi everyone,
I added a drive to a linux software RAID-5 last night. Now that worked
fine... until I changed the partition table.
Disk /dev/md_d5: 2499.9 GB, 240978560 bytes
2 heads, 4 sectors/track, 610349360 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start
Christian Schmidt [EMAIL PROTECTED] writes:
Where is the inherent limit? The partitioning software, or partitioning
all by itself?
DOS style partitioning don't support more than 2TB. You either need
to use EFI partitions (e.g. using parted) or LVM. Since parted's
user interface is not good
1 - 100 of 164 matches
Mail list logo