S=m ||
RTC_DRV_CMOS=y)
config APB_TIMER
Applying this patch does not change anything, this kernel is "bad".
Jiri Polach
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Finally! After another 50+ compilations a have it! It took some time as
first I had to find a reason why some revisions did not boot (almost 2/3
were unbootable and the first bad commit was among them). Having this
solved I have been able to bisect without "skipping". The result is
surprising (a
out commit 6610e089 and apply the
patch below to see if we can't narrow it down?
With the patch applied the system does not show the strange behavior (=
is "good").
Could you also send your .config to me?
Sure. It is attached. I have found that if I turn CONFIG_RTC_DRV_CMOS
of
On 10/31/2011 2:06 PM, Clarinet wrote:
On 10/30/2011 4:25 PM, Ben Hutchings wrote:
On Sun, 2011-10-30 at 07:05 -0400, Jiri Polach wrote:
Package: linux-2.6
Version: 2.6.39-3~bpo60+1
Severity: normal
>>
>> ...
That might be too large a range for developers to consider. Can y
Package: initscripts
Version: 2.86.ds1-12
Severity: normal
During shutdown, if /usr is NFS-mounted, it gets unmounted before umountfs is
called, but umountfs script operation relies on 'sort' command, which is in
/usr/bin. If sort is not found, local filesystems are not unmounted at all.
-- Syst
Package: lm-sensors
Version: 1:2.10.0-1
Severity: normal
lm-sensors startup script (/etc/rcS.d/S36lm-sensors) is called before NFS
filesystems are mounted (/etc/rcS.d/S45mountnfs.sh). If /usr is to be NFS
mounted (e.g on diskless nodes), /usr/bin/sensors cannot be run from this
script. The startu
6 matches
Mail list logo
