On Thu, Nov 24, 2011 at 07:31:08AM +, Ben Hutchings wrote:
> On Tue, 2011-11-22 at 17:11 +0100, Marc Haber wrote:
> > On Mon, Nov 21, 2011 at 06:36:49AM +, Ben Hutchings wrote:
> > > On Sat, 2011-11-19 at 21:13 +0100, Marc Haber wrote:
> > > > On Sat, Nov 19, 2011 at 07:37:16PM +, Ben H
On Tue, 2011-11-22 at 17:11 +0100, Marc Haber wrote:
> On Mon, Nov 21, 2011 at 06:36:49AM +, Ben Hutchings wrote:
> > On Sat, 2011-11-19 at 21:13 +0100, Marc Haber wrote:
> > > On Sat, Nov 19, 2011 at 07:37:16PM +, Ben Hutchings wrote:
> > > > But I can provide you with a rebuilt tg3.ko so
On Mon, Nov 21, 2011 at 06:36:49AM +, Ben Hutchings wrote:
> On Sat, 2011-11-19 at 21:13 +0100, Marc Haber wrote:
> > On Sat, Nov 19, 2011 at 07:37:16PM +, Ben Hutchings wrote:
> > > But I can provide you with a rebuilt tg3.ko so you can test just that
> > > change in the installer like you
On Sat, Nov 19, 2011 at 07:37:16PM +, Ben Hutchings wrote:
> But I can provide you with a rebuilt tg3.ko so you can test just that
> change in the installer like you did previously.
Already forgot about that. Yes, of course, that would be a way to go.
No need to hurry, I won't be on site befor
On Sat, 2011-11-19 at 19:45 +0100, Marc Haber wrote:
> On Fri, Nov 18, 2011 at 11:54:35AM -0800, Matt Carlson wrote:
> > I think I misspoke earlier. The commit I mentioned above fixes a problem
> > introduced in an earlier patch. (commit ID
> > d2394e6bb1aa636f3bd142cb6f7845a4332514b5, entitled
>
On Fri, Nov 18, 2011 at 11:54:35AM -0800, Matt Carlson wrote:
> I think I misspoke earlier. The commit I mentioned above fixes a problem
> introduced in an earlier patch. (commit ID
> d2394e6bb1aa636f3bd142cb6f7845a4332514b5, entitled
> "tg3: Always turn on APE features in mac_mode reg") So the
On Wed, Oct 26, 2011 at 12:41:44AM -0700, Ben Hutchings wrote:
> On Tue, 2011-10-25 at 17:20 -0700, Matt Carlson wrote:
> > On Mon, Oct 24, 2011 at 04:47:54PM -0700, Ben Hutchings wrote:
> > > On Mon, 2011-10-24 at 14:24 -0700, Matt Carlson wrote:
> > > > On Fri, Oct 21, 2011 at 05:19:39AM -0700, B
On Tue, 2011-10-25 at 17:20 -0700, Matt Carlson wrote:
> On Mon, Oct 24, 2011 at 04:47:54PM -0700, Ben Hutchings wrote:
> > On Mon, 2011-10-24 at 14:24 -0700, Matt Carlson wrote:
> > > On Fri, Oct 21, 2011 at 05:19:39AM -0700, Ben Hutchings wrote:
> > > > On Fri, 2011-10-21 at 11:08 +0200, Marc Hab
On Mon, Oct 24, 2011 at 04:47:54PM -0700, Ben Hutchings wrote:
> On Mon, 2011-10-24 at 14:24 -0700, Matt Carlson wrote:
> > On Fri, Oct 21, 2011 at 05:19:39AM -0700, Ben Hutchings wrote:
> > > On Fri, 2011-10-21 at 11:08 +0200, Marc Haber wrote:
> > > > On Fri, Oct 21, 2011 at 11:00:46AM +0200, Mar
On Mon, 2011-10-24 at 14:24 -0700, Matt Carlson wrote:
> On Fri, Oct 21, 2011 at 05:19:39AM -0700, Ben Hutchings wrote:
> > On Fri, 2011-10-21 at 11:08 +0200, Marc Haber wrote:
> > > On Fri, Oct 21, 2011 at 11:00:46AM +0200, Marc Haber wrote:
> > > > On Thu, Oct 20, 2011 at 05:28:34AM +0100, Ben Hu
On Fri, Oct 21, 2011 at 05:19:39AM -0700, Ben Hutchings wrote:
> On Fri, 2011-10-21 at 11:08 +0200, Marc Haber wrote:
> > On Fri, Oct 21, 2011 at 11:00:46AM +0200, Marc Haber wrote:
> > > On Thu, Oct 20, 2011 at 05:28:34AM +0100, Ben Hutchings wrote:
> > > > I don't see any changes that would obvio
On Fri, 2011-10-21 at 11:08 +0200, Marc Haber wrote:
> On Fri, Oct 21, 2011 at 11:00:46AM +0200, Marc Haber wrote:
> > On Thu, Oct 20, 2011 at 05:28:34AM +0100, Ben Hutchings wrote:
> > > I don't see any changes that would obviously change the way this device
> > > is reconfigured during a down/up
On Fri, Oct 21, 2011 at 11:00:46AM +0200, Marc Haber wrote:
> On Thu, Oct 20, 2011 at 05:28:34AM +0100, Ben Hutchings wrote:
> > I don't see any changes that would obviously change the way this device
> > is reconfigured during a down/up cycle. There were some changes to
> > power management that
On Thu, Oct 20, 2011 at 05:28:34AM +0100, Ben Hutchings wrote:
> I don't see any changes that would obviously change the way this device
> is reconfigured during a down/up cycle. There were some changes to
> power management that should just let the PCI core do some work that the
> driver used to,
On Mon, Oct 17, 2011 at 11:44, Marc Haber wrote:
...
> Does the installer use a different kernel from what actually gets used
> in the installed system?
It ought to be in sync at install time but the binaries are different.
In installer we build the udebs using the generated binary from the
archi
On Tue, Oct 18, 2011 at 02:24:52AM +0100, Ben Hutchings wrote:
> The kernel log you sent shows the interface being brought up and down
> several times in quick succession:
I have noticed this and cannot explain.
> Could you test whether the same problem occurs if you do something
> similar after
Now, let me try to understand this regression.
The kernel log you sent shows the interface being brought up and down
several times in quick succession:
First time:
[ 224.139579] tg3 :04:04.0: irq 30 for MSI/MSI-X
[ 224.174436] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 224.185365] tg3
On Mon, Oct 17, 2011 at 04:48:25PM +0200, Marc Haber wrote:
> On Mon, Oct 17, 2011 at 03:29:53PM +0100, Ben Hutchings wrote:
> > I didn't see any report from you after the (repeated) calls for testing
> > the point release.
>
> Why should I be doing your job? Making sure that features added during
On Mon, Oct 17, 2011 at 03:29:53PM +0100, Ben Hutchings wrote:
> I didn't see any report from you after the (repeated) calls for testing
> the point release.
Why should I be doing your job? Making sure that features added during
a stable release don't break existing stuff is a package maintainers'
On Mon, 2011-10-17 at 15:54 +0200, Marc Haber wrote:
> [keeping debian-kernel]
>
> On Mon, Oct 17, 2011 at 08:51:37AM -0500, Jonathan Nieder wrote:
> > Marc Haber wrote:
> >
> > > Why was a new tg3 introduced in a point release kernel in the first
> > > place?
> >
> > * tg3,broadcom: Backport
[keeping debian-kernel]
On Mon, Oct 17, 2011 at 08:51:37AM -0500, Jonathan Nieder wrote:
> Marc Haber wrote:
>
> > Why was a new tg3 introduced in a point release kernel in the first
> > place?
>
> * tg3,broadcom: Backport changes up to Linux 2.6.38 (Closes: #627705)
> - Add support for BC
Marc Haber wrote:
> Why was a new tg3 introduced in a point release kernel in the first
> place?
* tg3,broadcom: Backport changes up to Linux 2.6.38 (Closes: #627705)
- Add support for BCM5717, BCM5719, BCM57765
- Add support for BCM50610M and BCM5241 PHYs
- Fix support for BCM5755
On Mon, Oct 17, 2011 at 10:53:51AM -0200, Otavio Salvador wrote:
> On Fri, Oct 14, 2011 at 07:07, Marc Haber
> wrote:
> ...
> > this is a regression from 6.0.2.1 to 6.0.3.
> >
> > The IBM HS12 blade server has a Broadcom network chip:
> >
> > 04:04.0 Ethernet controller [0200]: Broadcom Corporatio
On Fri, Oct 14, 2011 at 07:07, Marc Haber
wrote:
...
> this is a regression from 6.0.2.1 to 6.0.3.
>
> The IBM HS12 blade server has a Broadcom network chip:
>
> 04:04.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme 5714S
> Gigabit Ethernet [14e4:1669] (rev a3)
> 04:04.1 Ethernet con
Package: debian-installer
Severity: important
Tags: d-i squeeze
Hi,
this is a regression from 6.0.2.1 to 6.0.3.
The IBM HS12 blade server has a Broadcom network chip:
04:04.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme 5714S
Gigabit Ethernet [14e4:1669] (rev a3)
04:04.1 Ethernet
25 matches
Mail list logo
