ep 7-8
>- Sep 28-29
>- Oct 12-13
>- Oct 19-20
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
ability to read or write anything that is longer than one hundred and sixty
charact
"NMI watchdog: BUG: soft
>> lockup" - see the screenshot in the attachment.
>>
>> Booting and running installer was successful after adding acpi=off
>> kernel parameter.
>
>Is that something to be fixed on the kernel side? Or some buggy UEFI
>that would need a workaround maybe?
That's a good question. acpi=off is often a workaround for buggy
firmware in my experience, but not typically something fixable
externally.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"You can't barbecue lettuce!" -- Ellie Crane
On Mon, Sep 04, 2017 at 08:13:39PM +0200, rpr // wrote:
>On 4 September 2017 at 16:50, Steve McIntyre wrote:
>>>
>>>Is that something to be fixed on the kernel side? Or some buggy UEFI
>>>that would need a workaround maybe?
>>
>> That's a good que
e reliability issues you pointed out on the wiki.
Right - we're trying to consider the issues as we go.
>> I would like to know everyone's opinions about these approaches, if you
>> agree to go forward with the second approach described above and how do
>> we solve the
On Mon, Oct 09, 2017 at 07:00:14PM +0100, Ben Hutchings wrote:
>On Mon, 2017-10-09 at 17:38 +0100, Steve McIntyre wrote:
>> On Mon, Oct 09, 2017 at 02:01:15PM +0100, Ben Hutchings wrote:
>[...]
>> > It also appears to mean that buildds can get anything signed on dema
as much as I can. I recognise that not everybody might
be able to (or willing to) attend in person, but I don't think that
should be a barrier to constructive discussions. Thoughts?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?
signature.asc
Description: PGP signature
unds like a more useful compromise.
>Secondly, the detached signatures would be uploaded as an extra package
>to a separate archive suite, similar to the way debug symbol packages
>are now handled. Those extra packages could easily be ignored when
>attempting
t; other will be present.
>> @ftpmasters and @Ben, if you could reply if you would be willing to
>> attend it would be great, so we can start organizing it and work
>> together to find a good solution.
>
>I am willing to attend and work on this if we can agree on the
&
cureBoot#Wrap-up_of_the_discussions_so_far
[2] https://lists.debian.org/debian-efi/2017/10/msg00029.html
[3] https://lists.debian.org/debian-efi/2017/11/msg00007.html
[4] https://lists.debian.org/debian-efi/2017/11/msg8.html
--
Steve McIntyre, Cambridge, UK.
4 disks and you're trying to boot off it with
grub-pc. You're hitting BIOS limitations here - the BIOS is only
capable of accessing 4 disks. I'm *guessing* that maybe the newer grub
in jessie is just being pickier about checking BIOS access to those
disks. Try just us
seem to be any major
downsides, just a very small amount of extra code size AFAICS.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
ability to read or write anything that is longer t
Package: src:linux
Version: 3.16.7-ckt9-3~deb8u1
Severity: serious
Hi guys,
Just debugged on harris.debian.org (imx53, Debian porter box) -
there's a missing patch that's needed for the imx53 sata controller to
work. At some point, it looks like the code in drivers/ata/ahci_imx.c
has changed and
Package: linux-image-4.0.0-trunk-arm64
Version: 4.0-1~exp1
Severity: serious
As mentioned on IRC, this package is missing all the DTBs for arm64
machines. Looks like it's a change to the DTB layout in the upstream
tree causing it.
-- System Information:
Debian Release: 7.8
APT prefers oldoldsta
m
+
+ * arm64: enable XHCI USB on APM X-Gene
+ * usb: host: allow 64-bit DMA mask for XHCI
+
+ -- Steve McIntyre <93...@debian.org> Fri, 15 May 2015 09:41:31 +0100
+
linux (3.16.7-ckt9-2) unstable; urgency=medium
* btrfs: simplify insert_orphan_item (Closes: #782362)
diff -Nru linux-
On Tue, May 19, 2015 at 02:20:08PM +0100, Ben Hutchings wrote:
>On Tue, 2015-05-19 at 12:52 +0100, Steve McIntyre wrote:
>> diff -Nru linux-3.16.7-ckt9/debian/changelog
>> linux-3.16.7-ckt9/debian/changelog
>> --- linux-3.16.7-ckt9/debian/changelog 2015-04-13 01:
On Tue, May 19, 2015 at 08:03:12PM +0100, Ian Campbell wrote:
>On Tue, 2015-05-19 at 20:02 +0100, Ian Campbell wrote:
>> On Tue, 2015-05-19 at 12:52 +0100, Steve McIntyre wrote:
>> > +CONFIG_USB_XHCI_PLATFORM=y
>>
>> This guy seems to match on:
>&
Here's patch v2...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back
diff -Nru linux-3.16.7-ckt9/debian/changelog linux-3.16.7-ckt9/debian/changelog
--- linux-3.16.7-ckt9/d
On Thu, May 21, 2015 at 07:49:37PM +0100, Ian Campbell wrote:
>On Wed, 2015-05-20 at 07:53 +0100, Steve McIntyre wrote:
>> Here's patch v2...
>
>Thanks.
>
>Has this been posted to anywhere upstream? Usual policy is that this
>should happen before we take it into our k
spotted there was a v3 and b) committed it to
>svn for both Sid and Jessie already, so I shall be doing no such thing!
Yay! :-)
(Belatedly) tested and working for me - my Mustang happily talks USB
now \o/.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
&quo
Source: linux
Version: 4.9.13-1~bpo8+1
Severity: minor
Hi guys,
In Linaro we're making a lot of use of USB-over-IP devices these days
for our testing lab. We've hit a (very small!) limit defined in kernel
config for the number of virtual host controllers and the ports
allowed per controller.
Cur
On Wed, Apr 05, 2017 at 03:51:14PM +0200, Bjørn Mork wrote:
>Steve McIntyre writes:
>
>> In Linaro we're making a lot of use of USB-over-IP devices these days
>> for our testing lab. We've hit a (very small!) limit defined in kernel
>> config for the number o
Source: linux
Version: 4.9.25-1
Severity: normal
Hi folks,
4.9 already includes ACPI support for arm64, which is great. There's
one driver fixup which only went into 4.10, and it would be lovely if
you could backport it for 4.9 (and hence Stretch):
https://git.kernel.org/pub/scm/linux/kernel/git
mp;.cgifields=type
>
>Adding debian-cd@ accordingly.
scsi-modules-* has been in the exclude-udebs list since forever... I
can remove that if desired? Not sure of exactly why this was added -
tracking back through debian-cd history now.
--
Steve McIntyre, Cambridge, UK.
On Thu, Jul 13, 2017 at 01:09:58AM +0100, Steve McIntyre wrote:
>On Thu, Jul 13, 2017 at 01:50:34AM +0200, Cyril Brulebois wrote:
>>
>>> But this package is also missing on the "release" DVDs for "amd64".
>>> Nearly every other architecture has thi
e to integrate the github fix for the realtek
>adapter rtl8723bs with SDIO supporrt into the unsupported part of the debian
>distribution?
Hi Thomas,
The Debian-CD list isn't the best place for this kind of
request. You're better off talking to the kernel maintainers - see t
On Wed, Jul 25, 2018 at 04:25:03PM +0100, Steve McIntyre wrote:
>On Mon, Jul 23, 2018 at 09:40:33PM +0200, Aurelien Jarno wrote:
>>control: affects -1 glibc
>>control: found linux/4.17.6-2
>>
>>On 2018-07-23 21:31, Aurelien Jarno wrote:
>>> Package: src:linux
ge too). Please fill in there the
dates that you can make and we'll get organised.
Cheers,
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Google-bait: http://www.debian.org/CD/free-linux-cd
Debian does NOT ship free CDs. Please do NOT contact the mailing
lists asking us to send them to you.
On Mon, Jan 15, 2018 at 05:42:24PM +, Steve McIntyre wrote:
>
>Hey Helen! Thanks for picking this up. Apologies for me going dark
>about this. I had a torrid time of things in December with a family
>bereavement, and this was one of many things that I had to drop
>temporarily.
&
On Mon, Jan 22, 2018 at 02:42:41AM +0530, Chris Lamb wrote:
>Hi Steve,
>
>> We have 7 people with dates in the poll so far:
>
>I wrote it in the poll form so perhaps repeating in this context; I'm only
>listed as a "backup" of sorts!
ACK, I saw that. :-
On Sun, Jan 21, 2018 at 05:49:20PM +, Steve McIntyre wrote:
>
>We have 7 people with dates in the poll so far:
>
> Helen Koike
> Luke Faraone
> Me
> Ben Hutchings
> Tollef Fog Heen
> Chris Lamb
> Philipp Hahn
>
>Any more people interested in coming? If so, p
lks - sorry, looks like this is your bug (and clearly
upstream!).
Quickly responding here again - we've just tried the latest kernel
from experimental (4.15.0-rc8) and this still shows the same problem.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Who n
On Sun, Jan 28, 2018 at 11:46:10AM +, Steve McIntyre wrote:
>
>HOWEVER... those dates clash with another group already booked in at
>the LinuxHotel in Essen. So we've started talking to people in Fulsa
>as a fallback option. We have a tentative space for a venue and now we
&g
On Sat, Aug 22, 2015 at 03:23:50PM +0200, Hendrik Weimer wrote:
>Steve McIntyre writes:
>
>> We'll need to make sure that the same set of modules are included in
>> the initramfs generated on the installed system, of course...
>
>This doesn't seem to be the c
devices but on others harmless / useful /
required (even); several years of writing SCSI-based storage
management software has show me that. :-) Allowing a mechanism for an
admin to override the in-kernel policy on a per-device, per-command
basis could allow us to safely allow non-root CD/DVD burning,
ext with
this to try and get such a feature into the kernel - the main kernel
list, the SCSI list, the debian kernel list? Of course, comments on
the code/design of what I've done would be more than welcome. Patch
(against 2.6.13) attached for interest...
--
Steve McIntyre, Cambridge, U
[ Bugger, got the cdrtools-devel address wrong on the first mail. Now
fixed. ]
On Fri, Nov 11, 2005 at 12:53:00AM +0100, Christoph Hellwig wrote:
>On Thu, Nov 10, 2005 at 11:47:29PM +0000, Steve McIntyre wrote:
>> In kernel 2.6.8 and later, SCSI generic commands are verified for
>&g
ary: field. This seems to be the case for both lenny and
sid. Is that a bug in the package, or somewhere else (e.g. dak)?
Cheers,
--
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
We don't need no education.
We don't need no thought control.
--
To UNSUBSCR
On Wed, Sep 10, 2008 at 11:49:51PM +0100, Steve McIntyre wrote:
>Hi folks,
>
>I've been tracking down a build failure in the current lenny
>multi-arch i386/amd64/powerpc/source DVD. What I've found is an oddity
>in the Sources.gz file: the stanza for the source package
17.0 +0100
@@ -378,6 +379,8 @@
struct hd_driveid *id = drive->id;
#endif /* CONFIG_WDC_ALI15X3 */
+ return 0;
+
if (m5229_revision <= 0x20) {
return 0;
} else if ((m5229_revision < 0xC2) &&
--
Steve McIntyre, Cambridge,
On Sun, Apr 15, 2007 at 06:26:35PM -0700, Martin Michlmayr wrote:
>* Steve McIntyre <[EMAIL PROTECTED]> [2007-04-16 00:29]:
>> On the "cats" machines that we use for arm buildd work, it seems the
>> kernel is too aggressive in enabling UDMA support for the onboard ID
On Tue, Nov 14, 2006 at 07:11:33PM +0100, Dennis Grevenstein wrote:
>On 11/14/06, Steve McIntyre <[EMAIL PROTECTED]> wrote:
>
>>OK, same problem then. I had to install woody, then build a custom
>>kernel too. I'll dig out my patch for you if you like.
>
>sure
===
Other stuff
===
That's the list of things I'm hoping to learn more about from this
review of teams. Of course, I'm sure there are many other things in
Debian that you'd like to ask or tell me about. By all means, talk t
Source: linux
Version: 4.9.82-1+deb9u3
Severity: normal
Tags: patch
Hey folks,
I've backported support for the onboard network interface on the
Qualcomm Centriq arm64 server platform, mostly straight cherry-picks
from upstream 4.15. Please apply the patch to add this support for the
next Stretch
se, at
https://salsa.debian.org/kernel-team/linux/merge_requests/8
Please shout if you need me to do anything more.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
There's no sensation to compare with this
Suspended animation, A state of bliss
On Mon, Apr 30, 2018 at 12:21:28PM +0100, Steve McIntyre wrote:
>I've also added a backport for the one erratum that's known about for
>Falkor v2 CPUs (E1041). Other Qualcomm errata code is in upstream, but
>the other snippets are for v1 which is not widely available so
th the situation for a
>short while, or do 9.5 before 8.11. In practical terms, that would
>likely mean both 9.5 and 8.11 on June 23rd, freezing both next weekend.
>How do people feel about that?
That works ok for me.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"This dress doesn't reverse." -- Alden Spiess
9.5, we know that June 30th is a no-go, Debcamp
>starts on July 21st and then Debconf on the 28th. So that leaves us with:
>
>- July 7th
>- July 14th
>
>Are people available for either or both of those dates?
Both look good for me, yup.
--
Steve McIntyre, Cambridge, UK.
all.
>>
>
>I forgot to say that the problem is reproducible with kernel 4.17.6.
Fix proposed in https://lkml.org/lkml/2018/7/25/409
--
Steve McIntyre, Cambridge, UK.st...@einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane...
se) updated in
>stable. This would greatly help building, testing, and running
>debian-installer without having to special-case everything in various
>places. Of course this is subject to a green light from the release
>team, but I might be trusted to get things right (and/or to get the
On Mon, Aug 13, 2018 at 01:44:48PM +0200, Julien Cristau wrote:
>On 08/13/2018 01:57 AM, Steve McIntyre wrote:
>> On Thu, Aug 02, 2018 at 10:56:59AM +0200, Cyril Brulebois wrote:
>>> => Question: should we restrict architectures we build images for?
>>
>> Proba
his for users and be consistent for all the EFI
signed binaries - there's no point in signing i386 grub and fwupd or
having a signed shim if we don't have a signed kernel.
Agreed?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislik
On Wed, Dec 06, 2023 at 11:44:52PM +0100, Pascal Hambourg wrote:
>Hello,
>
>On 06/12/2023 at 22:09, Steve McIntyre wrote:
>>
>> On Wed, Dec 06, 2023 at 06:01:17PM +0100, Bastian Blank wrote:
>> >
>> > I would like do stop signing i386 kernels.
>>
d
>https://salsa.debian.org/kernel-team/linux/-/merge_requests/502#note_315464
>
>The proposed patch felt probably trough the cracks.
Nod.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
The two hard things in computing:
* naming things
* cache invalidation
* off-by-one errors -- Stig Sandbeck Mathisen
for
>kernels).
It's a difficult thing to do, especially in light of significant
pushback from upstream developers.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"I can't ever sleep on planes ... call it irrational if you like, but I'm
afraid I'll miss my stop" -- Vivek Das Mohapatra
the desktop system, if I kill one of the bits in the stack
(e.g. pipewire-pulse), things re-initialise OK and the device shows
up.
I don't know if this data point is useful, but I thought it was worth
sharing maybe.
--
Steve McIntyre, Cambridge, UK.st...@e
ce I'd guess we would get more
>things to look at.
>
>I'll let Steve comment on the preferred timings.
Let's go, I think - if the 6.10.8-1 upload builds and migrates OK then
let's try and get a d-i release built with that. I should have time in
the next week o
gt;thread).
>
>> Once 6.11 would be released and we know it's stabilised in
>> experimental we would like to move it to unstable and make the way
>> free in experimental for 6.12-rcX, as the later is in particular
>> important to make 6.12.y ready as this is expected to
On Sun, Sep 15, 2024 at 12:31:12AM +0200, Cyril Brulebois wrote:
>Steve McIntyre (2024-09-14):
>>
>> That looks great for me, thanks.
>
>Then I think my work here is done:
>
>kibi@respighi:~$ dak ls debian-installer -s testing,unstable -a source
>
On Sun, Sep 15, 2024 at 11:08:34PM +0200, Cyril Brulebois wrote:
>Steve McIntyre (2024-09-15):
>> Kibi: just checking, are you happy for me to call this trixie d-i
>> alpha 1?
>
>As communicated a few times in previous mails already: not at all.
Understood, I'm glad
oot chain. :-( There's a
mitigating factor here: *such* new machines may already reject our
older signed binaries anyway.
We're stuck in a bad situation here I'm afraid; I think the only
sensible way is forward, applying NX patches as soon as they&#x
Hey Antonio,
On Wed, Jan 25, 2023 at 04:17:50PM -0300, Antonio Terceiro wrote:
>On Wed, Jan 25, 2023 at 06:11:45PM +0000, Steve McIntyre wrote:
>>
>> The MS and cert issues are now both resolved, and I'm now working on a
>> shim *15.7* upload. There's a little m
bookworm.
HTH!
--
Steve McIntyre, Cambridge, UK.st...@einval.com
“Why do people find DNS so difficult? It’s just cache invalidation and
naming things.”
-– Jeff Waugh (https://twitter.com/jdub)
Source: linux
Version: 6.1.12-1
Severity: important
Hey folks,
I've just upgraded my Seattle-based system to bookworm and it no
longer finds the onboard AHCI SATA storage so it stops at an initramfs
prompt. Going back to the current bullseye kernel (5.10.162-1), it all
works just fine.
As far as
On Sun, Mar 05, 2023 at 12:09:24AM +, Steve McIntyre wrote:
>Source: linux
>Version: 6.1.12-1
>Severity: important
>
>Hey folks,
>
>I've just upgraded my Seattle-based system to bookworm and it no
>longer finds the onboard AHCI SATA storage so it stops at an ini
. Your tone and wording in several of your messages
here are utterly unacceptable. You've used abusive language about
people who are volunteers working to improve Debian in their own
time. I would strongly suggest that you revisit what you've written
and consider apologi
On Mon, Aug 16, 2021 at 12:54:47PM +0200, Justus Winter wrote:
>Steve McIntyre writes:
>> On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote:
>>>Package: debian-installer
>>>Version: 20210731
>>>Severity: critical
>>>Tags: d-i
>>
On Mon, Aug 16, 2021 at 01:24:14PM +0200, Justus Winter wrote:
>Steve McIntyre writes:
>>
>> OK, and my upgrade worked just fine. The key difference that I'm
>> seeing is that on my system ACPI is *not* used:
>>
>> root@mustang4:/home/steve# grep ACPI /var/
e a synquacer here still and I'll take a look. I noticed on
bullseye release day that USB stuff didn't seem to work in the
installer on the synquacer either. Maybe there's been a regression in
config. :-/
I'll take a look...
--
Steve McIntyre, Cambridge, UK.
On Sat, Sep 04, 2021 at 06:50:16PM +0100, Steve McIntyre wrote:
>
>I have a synquacer here still and I'll take a look. I noticed on
>bullseye release day that USB stuff didn't seem to work in the
>installer on the synquacer either. Maybe there's been a regression in
even for
64-bit systems" (#768461)
Hopefully a combination of these 2 fixes will make your system work
out of the box...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane..
he installer.
We'll need to make sure that the same set of modules are included in
the initramfs generated on the installed system, of course...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"I used to be the first kid on the block wanting a cranial
Package: src:linux
Severity: wishlist
Tags: patch
Hi folks,
This patch has been accepted by the efi maintainer for the efi/next
tree. It would be lovely if you'd accept it for the Jessie kernel
too, for the Bay Trail etc. support.
--
Steve McIntyre, Cambridg
Package: src:linux
Version: 3.16.7-ckt4-2
Severity: grave
Tags: patch upstream
The latest upstream stable kernel pull is broken on arm64. The system
panics during early boot in arch_timer setup.
The cause is simple. Commit 0b46b8a718c6e90910a1b1b0fe797be3c167e186
was pulled into stable, but a lat
Package: src:linux
Version: 3.16.7-ckt7-1
Severity: grave
Tags: upstream
Hi folks,
We've upgraded a couple of our Marvell Armada XP based (armel/armhf)
buildd machines to Jessie, and they've almost immediately fallen over
with symptoms of really bad data corruption. On further investigation
and d
Control: tag -1 +pending
On Fri, Mar 20, 2015 at 04:13:20PM +, Steve McIntyre wrote:
>Package: src:linux
>Version: 3.16.7-ckt7-1
>Severity: grave
>Tags: upstream
>
>Hi folks,
>
>We've upgraded a couple of our Marvell Armada XP based (armel/armhf)
>buildd machin
Source: linux
Version: 4.19.118-2+deb10u1
Severity: serious
Hi folks,
Trying to reproduce #963462 on my Thinkpad T470, I'm repeatedly
getting a hard lockup running the strace testsuite. I've done this 4
times to be sure. Each time it seems to have failed in a slightly
different place in the tests
Hey Salvatore!
On Wed, Jun 24, 2020 at 05:57:42PM +0200, Salvatore Bonaccorso wrote:
>Control: found -1 4.19.118-1
>Control: tags -1 + upstream
>
>Hi Steve,
>
>On Mon, Jun 22, 2020 at 12:58:35PM +0100, Steve McIntyre wrote:
>> Source: linux
>> Version: 4.19.118-
On Wed, Jun 24, 2020 at 05:39:38PM +0100, Steve McIntyre wrote:
>On Wed, Jun 24, 2020 at 05:57:42PM +0200, Salvatore Bonaccorso wrote:
>>Control: found -1 4.19.118-1
>>Control: tags -1 + upstream
>>
>>>
>>> As I can reproduce this quite easily, I'm hap
7b812116f19de6967084a647e
865a227665e460e159502f21e8a16e6fa590bf50 M security
Considering I'm running strace build tests to provoke this bug,
finding the failure in a commit talking about ptrace changes does look
very suspicious...!
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further c
running strace build tests to provoke this bug,
finding the failure in a commit talking about ptrace changes does look
very suspicious...!
Annoyingly, I can't reproduce this on my disparate other machines
here, suggesting it's maybe(?) timing related.
Hope this helps - happy to give more
Hey Greg,
On Fri, Jun 26, 2020 at 03:41:32PM +0200, Greg KH wrote:
>On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
>>
>> e58f543fc7c0926f31a49619c1a3648e49e8d233 is the first bad commit
>> commit e58f543fc7c0926f31a49619c1a3648e49e8d233
>> Author: Ja
On Fri, Jun 26, 2020 at 02:45:18PM +0100, Steve McIntyre wrote:
>Hey Greg,
>
>On Fri, Jun 26, 2020 at 03:41:32PM +0200, Greg KH wrote:
>>On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
>>>
>>> e58f543fc7c0926f31a49619c1a3648e49e8d233 i
Hi Jann,
On Fri, Jun 26, 2020 at 04:25:59PM +0200, Jann Horn wrote:
>On Fri, Jun 26, 2020 at 3:41 PM Greg KH wrote:
>> On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
...
>> > Considering I'm running strace build tests to provoke this bug,
>> >
Hi again,
On Fri, Jun 26, 2020 at 05:50:00PM +0100, Steve McIntyre wrote:
>On Fri, Jun 26, 2020 at 04:25:59PM +0200, Jann Horn wrote:
>>On Fri, Jun 26, 2020 at 3:41 PM Greg KH wrote:
>>> On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
>
>...
>
>>&
On Fri, Jun 26, 2020 at 10:29:28AM -0700, John Johansen wrote:
>On 6/26/20 9:50 AM, Steve McIntyre wrote:
>>
>> OK, will try that second...
>>
>
>I have not been able to reproduce but
>
>So looking at linux-4.19.y it looks like
>1f8266ff5884 apparmor: don&#x
On Thu, Sep 17, 2020 at 07:25:36PM +0100, Ben Hutchings wrote:
>On Tue, 2020-09-15 at 10:01 +0100, Steve McIntyre wrote:
>>
>> And fixed as of today's daily builds.
>>
>> Thanks for the report!
>
>Thanks Steve. We probably should have thought to update
On Tue, Aug 19, 2014 at 01:38:44PM -0700, Ben Hutchings wrote:
>
>So far as I know, no progress has been made on the above steps or any
>alternate approach.
Ditto, I've not seen (or done) anything about this.
--
Steve McIntyre, Cambridge, UK.st
Source: linux
Version: 4.19.28-2
Severity: important
Hi folks,
The TaiShan is an arm64 server made by Huawei, using the HiSilicon
1620 CPU. It's a nice big beast of a machine, with lots of cores,
memory etc. We've been loaned one to use (maybe as a buildd?), but at
the moment the Buster kernel do
On Sat, Jun 15, 2019 at 01:19:08PM +0100, Steve McIntyre wrote:
>Source: linux
>Version: 4.19.28-2
>Severity: important
>
>Hi folks,
>
>The TaiShan is an arm64 server made by Huawei, using the HiSilicon
>1620 CPU. It's a nice big beast of a machine, with lots of c
x27;t find a carrier on any of the
network interfaces.
I'm going to dig into this further and see if I can make any progress
to see what's up. For reference, Ubuntu 18.04.01 seems to work fine on
the same hardware (kernel 4.15.0-58).
Cheers,
Steve McIntyre
IMPORTANT NOTICE: The contents of
bian 4.9.144-4~20190217~1 (2019-02-17)
>armv7l GNU/Linux
Yes, me too. Built similar and tested on the Marvell Armada XP here
and it solved the problem.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"Because heaters aren't purple!" -- Catherine Pitt
ed kernelci as a useful thing to help here,
but we really need to be testing kernels complete with all the Debian
patches to...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Armed with "Valor": "Centurion" represents quality of Discipline,
Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
concord the digital world while feeling safe and proud.
t: [PATCH] Update debian/arm-avoid-abi-change-in-4.9.139.patch (Closes:
> #922478).
>
>This makes it take into account the function pointers reordering in
>arch/arm/mm/proc-macros.S (addition of check_bugs), fixing the failure
>to boot many armhf devices.
>
>With thanks to Adrian
s like block
device support modules here.
Cheers,
Steve
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich
On Fri, Apr 26, 2019 at 07:00:39PM +0100, Ben Hutchings wrote:
>On Fri, 2019-04-26 at 02:17 +0100, Steve McIntyre wrote:
>> Hey folks,
>>
>> I;m just trying to do a buster install of arm64 (using buster d-i RC1)
>> in a qemu VM, and it's failing to find the virtio
On Sat, Apr 27, 2019 at 12:07:05AM +0100, Ben Hutchings wrote:
>On Fri, 2019-04-26 at 22:40 +0100, Steve McIntyre wrote:
>[...]
>> Hmmm, looking at my local mirror, I think there's another problem
>> then. I don't see scsi-modules-4.19* for arm64. Looks like we
On Sat, Apr 27, 2019 at 12:39:31AM +0100, Steve McIntyre wrote:
>On Sat, Apr 27, 2019 at 12:07:05AM +0100, Ben Hutchings wrote:
>>On Fri, 2019-04-26 at 22:40 +0100, Steve McIntyre wrote:
>>[...]
>>> Hmmm, looking at my local mirror, I think there's another probl
the BMC virtual console graphic output works well after adding
>the hibmc_drm.ko into the netboot initrd, could you please help to built and
>include this driver module in the installer?
I've just added a merge request for this:
https://salsa.debian.org/kernel-team/linux/merge_requests
>- Oct 19-20
>> >
>> > Either of those is fine for me.
>> >
>> Alright, let's go for
>>
>> Oct 12-13: 7.3
>
>Obviously I meant 7.2...
>
>> Oct 19-20: 6.0.8
Works for me...
--
Steve McIntyre, Cambridge, UK.
grub-install, reboot,
>manually create EFI boot entry in BIOS setup menu.
>
>What can I do to debug this issue?
It sounds like you have either a kernel or hardware issue here -
efibootmgr just uses the kernel-provided files in /sys as its
interface to the hardware. Add
1 - 100 of 141 matches
Mail list logo
